Random BSODs, all diff errors

[SteveS97]

Hey guys, new to W7 forums and I've got some BSOD issues on my computer I built that is running Windows 7 64bit.

I have received around a dozen BSODs over the last month, sometimes multiple in one day, sometimes it will go a week without a hitch. I have yet to see the same error twice, so I don't think there is a point in listing them.

Some other information:
-BSODs started after installing 4 more gb of RAM into system, for a total of 8. However removing the new RAM or rearranging the modules didn't help. System still BSODs now with RAM that has been tested good with Memtest86.
-BSODs most often occur while the system is under load, but have occured while I am checking email, etc
-Most recent BSOD was "System_Service_Exception" with error 0x0000003B
-System was custom built by myself in December of 2010
-OS has not been reinstalled
-Specs:

SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM SATA 3.0Gb/s 3.5" Internal Hard Drive
ASUS M4A87TD EVO AM3 AMD 870 SATA 6Gb/s USB 3.0 ATX AMD Motherboard
CORSAIR Enthusiast Series CMPSU-650TX 650W
AMD Phenom II X4 925 Deneb 2.8GHz Socket AM3 95W Quad-Core Processor HDX925WFGIBOX
G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
EDIMAX EW-7128G PCI Wireless Card
SAPPHIRE 100283-3L Radeon HD 5770 1GB 128-bit GDDR5


Please help, and thank you in advance

 

[zigzag3143]

Hey guys, new to W7 forums and I've got some BSOD issues on my computer I built that is running Windows 7 64bit.

I have received around a dozen BSODs over the last month, sometimes multiple in one day, sometimes it will go a week without a hitch. I have yet to see the same error twice, so I don't think there is a point in listing them.

Some other information:
-BSODs started after installing 4 more gb of RAM into system, for a total of 8. However removing the new RAM or rearranging the modules didn't help. System still BSODs now with RAM that has been tested good with Memtest86.
-BSODs most often occur while the system is under load, but have occured while I am checking email, etc
-Most recent BSOD was "System_Service_Exception" with error 0x0000003B
-System was custom built by myself in December of 2010
-OS has not been reinstalled
-Specs:

SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM SATA 3.0Gb/s 3.5" Internal Hard Drive
ASUS M4A87TD EVO AM3 AMD 870 SATA 6Gb/s USB 3.0 ATX AMD Motherboard
CORSAIR Enthusiast Series CMPSU-650TX 650W
AMD Phenom II X4 925 Deneb 2.8GHz Socket AM3 95W Quad-Core Processor HDX925WFGIBOX
G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
EDIMAX EW-7128G PCI Wireless Card
SAPPHIRE 100283-3L Radeon HD 5770 1GB 128-bit GDDR5


Please help, and thank you in advance

Its a driver. Please run these two tests to find out which


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[SteveS97]

I'm confused. When running the Driver Verifier and the system BSODs, how do I diagnose which driver is faulty?

 

[zigzag3143]

I'm confused. When running the Driver Verifier and the system BSODs, how do I diagnose which driver is faulty?

You upload the DMP and we examine it.

 

[SteveS97]

Ok thank you. I am going on vacation in a day, but I will try to get that done before then.

 

[SteveS97]

Update: Using memtest, I have verified 2 working DIMM slots, and 2 working modules of RAM. I currently have those 2 modules installed (I had 4 modules at my disposal). So from this point on, let's assume it is not RAM.

In addition, crashed 3 more times since last post, 1 had a "Memory_Management" BSOD, and 2 were just straight crashes, no BSOD. Two new minidumps have been created and I ran the BSOD Dump & System File Collection app again.

 

[SteveS97]

Alright I am now back home from vacation, and plan to run the driver verifier tool today. One last question, how do I disable the tool once I have finished the stress testing and found what causes the BSOD?

 

[ickymay]

Alright I am now back home from vacation, and plan to run the driver verifier tool today. One last question, how do I disable the tool once I have finished the stress testing and found what causes the BSOD?

To disable Driver Verifier so that it no longer performs verification checks at startup, run Driver Verifier Manager again and select Delete Existing Settings in the initial dialog box.
Alternatively, click Start, then Run, and type verifier /reset in the Open box

 

[SteveS97]

Sounds good. I currently haven't had a BSOD in 2 days (a new record). This is since I changed the configuration of my RAM. Since it's possible that the problem is fixed, I'll wait and see if it BSODs again before running the verifier :huh:

 

[SteveS97]

Ran the verifier, no problems came up. Haven't had a BSOD in a week, so I'm calling it closed for now. Will post again if a problem arises. Thank you everyone

 

[Maguscreed]

Just to toss something in that no one else brought up.

nusb3xhc.sys Fri Nov 20 05:16:01 2009 (4B066C61) NEC Electronics USB 3.0 Host Controller Driver (previous issues w/BSOD's) FAQ/Support | Renesas Electronics

This is loading on your system right now and has had problems. You may want to follow the link and see if you can find a driver in their support pages.

 

[SteveS97]

Darn. Turned on computer this morning, ran fine for 3-5 minutes, then black screen and restart. No blue screen or new minidump. Weird thing is, when I did check the minidump folder, there was a file in there from 3am this morning when I wasn't even on my computer? Maybe the times got messed up, I've attached the BSV.

 

[Maguscreed]

Huh this actually looks audio related by that screen.
If you right click your speaker icon in tray and choose playback devices.
How many items are listed there?

 

[SteveS97]

here are my playback devices

 

[Maguscreed]

Disable all of the playback devices not in use. Which looks like all but the Via HD.
So leave the VIA speakers alone... you apparently aren't using the spdif so we can disable it for now and you can just reverse it later if you need it.

To disable:
select a device click properties and use the drop down box at the bottom to set disabled.

Reboot, this will help us determine if the devices are conflicting.

 

[SteveS97]

Disabled what you requested. In other news, just had 2 crashes within 5 minutes. one gave the black screen, no restart. The other gave a BSOD (interestingly, part of the bsod screen was cutoff and it had a greenish tint). something I think I forgot to mention, I have been getting a message about 1/3 the time I boot my computer up saying "a new cpu has been installed, press 1 to load default values, press 2 to...." and so on. Obviously I haven't been installing new CPUs every day... The plot thickens

 

[Maguscreed]

ASUSTeK Computer Inc. - Motherboards- ASUS M4A87TD EVO

I never would have guessed this with a board as new as yours but there has been a lot of major updates to the bios on that system.
You should probably look into updating the bios.
If you haven't done that before it's definitely something you should read the manual and instructions about first.
It sounds like your bios is resetting between boots though. Since your system is too new to have a dead bios battery already I'm going to guess the problem is the bios itself.

 

[SteveS97]

I have never flashed my bios before, so I will definitely read up on this before I try it. All I know about it is that it has a very high chance of bricking your mobo if you do it wrong. I can't wait

 

[SteveS97]

Well... I attempted to use Asus's bios update utility. I tried 4 times and got 4 different errors, 2 of which were just meaningless symbols, one said "catastrophic failure", and one said "no ASUS motherboard detected". This is going well

 

[SteveS97]

alright, the bios have been updated to the most recent version