Two Months of random, yet consistent, BSOD's

MvdB · 03 Sep 2011

Could still be memory....but, lets check one other thing first. I see some weird stuff on mouse and keyboard.
As a test, de-install third party mouse and keyboard software. Also go in Devices and delete all occurrences of mouse and keyboard. Reboot and let W7 use basic W7 drivers for your mouse and keyboard....

The Trekkie · 04 Sep 2011

Thanks for your continuing help.

I ran driververifier, rebooted...and it crashed before it even got to my desktop. Constantly. Had to boot into Safe Mode to deactive it. Each time I got an odd BSOD reason [plese forgive my ignorance] but it said something along the lines of

'Driver is trying to access memory when it has been reassigned' or something similar. Even the error code was odd: 0d5.

Im uploading the BSOD files & I am now going to delete all instances of Keyboard/Mice stuff from my devices screen.

Thanks

The Trekkie · 05 Sep 2011

Ok, I uninstalled my Razer & Zseries programs & went into devices and removed all instances of Mouse and Keyboard stuff. Although I didn't delete them in the 'human interface devices' section...

maxseven · 05 Sep 2011

Memtest86+ errors are no good, no good at all. If you don't pass Memtest86+ you're not going to be able to run anything.

You might want to join the Corsair site and give RAMGUY a look at your situation. He will want to know what your BIOS settings are for the RAM, and may have some advice for you based upon your specific mobo and PSU.

If the RAM is determined to be bad, a thread there can become the basis for a RMA.

MvdB · 05 Sep 2011

The Trekkie said:

Ok, now im even more disheartened. I spent today testing the RAM from my USB stick.

I tried both stick individually for two hours each and they both passed. I then tried them together...and they passed.

Thing is, my motherboard does display the red RAM error light when I turn the sytem on then it vanishes. When I tested one of the sticks I did get some bizarre 'overclocking failed' message and then nothing would respond but a reset put things back to normal.

Im really baffled. Why would it fail a test with both yesterday then pass them all today? Im desperate to get to the root of the problem with your help.

Thanks

How many passes did you test here? Had you re-seated the sticks?

The Trekkie · 05 Sep 2011

I had ran 4 passes If I remember right and yeah I had taken both out, tried them individually then tried them together.

I think the RAM may be the culprit [though I need someone to read the last log I posted when I ran driver verifier as it did BSOD] as I just ran an extensive 6 hour scan tonight and:

It passed once and returned 13 million errors!

So that means I have ran the scanner 3 times and 2 of those times it has failed. Im thinking I will have to return the RAM to Corsair.

maxseven · 05 Sep 2011

maxseven said:

You might want to join the Corsair site and give RAMGUY a look at your situation. He will want to know what your BIOS settings are for the RAM, and may have some advice for you based upon your specific mobo and PSU.

Again, check at the Corsair forum as RAMGUY may want you to change some BIOS settings for your RAM.

The Trekkie · 05 Sep 2011

maxseven said:

You might want to join the Corsair site and give RAMGUY a look at your situation. He will want to know what your BIOS settings are for the RAM, and may have some advice for you based upon your specific mobo and PSU.

Again, check at the Corsair forum as RAMGUY may want you to change some BIOS settings for your RAM.

Thanks, I have signed up and posted a thread asking for help on their forums. Atleast I seem to be getting to the root of the problem and its the RAM seemingly to blame. [Oh and I will make sure to give everyone here who helped positive feedback]

MvdB · 07 Sep 2011

The faulty ram could easily be the cause of the driver verifier problems at booting. Replace ram first and we'll go on from there... Glad we got somewhere in the end...