Having 2 ongoing problems hoping someon could help me

[MraK]

Been starting to have some small problems with my second gaming rig (see sig) and was hoping someone could shed some light onto this problem I am having.

1) since i built this rig (had it running so far for over a week now, i have had since 2 BSODs. My question is do you guys think it may have something to do with my OC?? Memory timings?? new software I installed?

2) since i built the rig everytime at start up and sometimes during use of the rig my mouse would not be able to click onto anyting until i would "ctrl-alt-delet" and then the mouse works and I could click and anything to open anything or highlight. Does anyone have an idea on this?

Thanks in advance!

 

[Billb2]

1.) Look in Event Viewer and see what went wrong.
Or just Google the first set of numbers in the BSOD error code.

2.) Again, Event Viewer.

 

[ch33zw1z]

Originally posted by: MrAK
Been starting to have some small problems with my second gaming rig (see sig) and was hoping someone could shed some light onto this problem I am having.

1) since i built this rig (had it running so far for over a week now, i have had since 2 BSODs. My question is do you guys think it may have something to do with my OC?? Memory timings?? new software I installed?

2) since i built the rig everytime at start up and sometimes during use of the rig my mouse would not be able to click onto anyting until i would "ctrl-alt-delet" and then the mouse works and I could click and anything to open anything or highlight. Does anyone have an idea on this?

Thanks in advance!

1) If you're overclocking at all, bring everything back to stock and run MemTest86+ for at least 12 hours, 24 is preferable(Run memtest86+ no matter what). Update to latest firmware and device drivers, using the method suggested in the driver readme's. I recommend booting to Safe Mode, uninstalling the drivers, and reinstalling them after you reboot into regular mode.

2) Like Bill said, What's in event viewer? What's your OS? Complete Hardware Listing? What mouse/keyboard are you using and does it come with software that you had to install?

 

[MraK]

this is what was shown below:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000010
BCP2: 000000000000000C
BCP3: 0000000000000008
BCP4: 0000000000000010
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini093009-03.dmp
C:\Users\Nong_(main)\AppData\Local\Temp\WER-119671-0.sysdata.xml
C:\Users\Nong_(main)\AppData\Local\Temp\WER778.tmp.version.txt





Do you guys think it was because the configuration of my OC was kinda not stable?

 

[Axon]

Run memtest86. That's going to help decide what the bad hardware is, if any. Typically, when you OC beyond a chip's ability, the system either will not POST or you will see artifacts on your graphics - at least that's my experience. With the cooling you're throwing at those two systems in your sig and the speed you're running them at, I doubt it's the CPU.

I would say the following culprits are responsible, in this order of likelihood: (1) Drivers; (2) Memory - 1 bad stick or more; (3) Motherboard; (4) PSU; (5) CPU. As cheesewiz said, bring everything back to stock and run Memtest86 for some time, at least 12 hours. If that yields nothing, you can try taking one stick out at a time and booting your system, but that's tedious. Also, you can run Prime95 in blend and SmallFFT mode. I suspect you'd see a rounding error in the Blend test within 2 minutes. Small FFT will likely produce no error. But if there are no errors in those tests, it's probably a driver (at least that's what I'm reading on a few other forums).

Back up your HDD with any important material and boot from safe mode, etc etc

 

[ch33zw1z]

Originally posted by: MrAK
Do you guys think it was because the configuration of my OC was kinda not stable?

That's always a possibility when OCing.

edit: didn't click send before you posted Axon, good info!

 

[MraK]

found the culprit, it was the drivers from my new sound card that was giving it a BSOD issue, reassembled both computers plus returned the old sound card and installed a new sound card. Oh and also just "dummy clocked" my EGVA rig for the time being, for now everything is back to normal, everything pretty much running good at this time. (asked a friend who was a tech at a near by PC store, fpr some help and so far it did the trick)