Windows 7: Win7 32-bit Daily BSOD crashes (dmp files included)

Algan · 01 Jul 2010

I've been having numerous daily BSODs with my Windows 7 32-bit install (My system was even worse with 64-bit).

I've discussed it with numerous people, and even have gone to the lengths of buying 8 new GB of RAM for my system, and it's just the same as it was - troublesome.

Included is a .zip of my dump files, and my dxdiag. Any help would be greatly appreciated - I spent a lot of money building this machine, and to have it not only not work in 64-bit, but not work at all, is very exasperating.

Thanks!

zigzag3143 · 01 Jul 2010

Quote: Originally Posted by Algan

I've been having numerous daily BSODs with my Windows 7 32-bit install (My system was even worse with 64-bit).

I've discussed it with numerous people, and even have gone to the lengths of buying 8 new GB of RAM for my system, and it's just the same as it was - troublesome.

Included is a .zip of my dump files, and my dxdiag. Any help would be greatly appreciated - I spent a lot of money building this machine, and to have it not only not work in 64-bit, but not work at all, is very exasperating.

Thanks!

17 BSOD will take a while I am doing the newest ones now

The newest two have some but not more information.
The Usual causes: Memory,Insufficient disk space, Device driver, Video card, BIOS, Hardware incompatibility, Faulty system service.

Since both memory and system service are mentioned you will need to do two things. The first parameter in all of them refer to a memory exception so run memtest first.

1-Download a 3rd party app called memtestx86, burn it to a cd, and run it for at least 6 passes.

2-Run a system file check. To do that type cmd in search>right click and run as admin>sfc /scannow

Let us know the results

Ken

Algan · 02 Jul 2010

Quote: Originally Posted by zigzag3143

2-Run a system file check. To do that type cmd in search>right click and run as admin>sfc /scannow

The results are as follows:

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Running MemTest after I post this, will post those results tonight. Thanks for looking into this.

Jonathan_King · 02 Jul 2010

I have to suspect a bad video card, or perhaps video card drivers.

Please uninstall your current nVidia drivers, and install an older version.

If you have another video card, try it, because I actually suspect a failing card.

SUMMARY OF THE BSODS

Code:


Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Jun 24 20:08:56.957 2010 (UTC - 4:00)
System Uptime: 0 days 16:51:59.517
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BUGCHECK_STR:  0x50
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun 21 22:13:14.611 2010 (UTC - 4:00)
System Uptime: 1 days 0:35:37.798
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 21:37:01.853 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:49.414
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 21:11:57.877 2010 (UTC - 4:00)
System Uptime: 0 days 1:10:01.438
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 20:01:11.288 2010 (UTC - 4:00)
System Uptime: 0 days 8:03:55.474
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jun 19 22:50:50.689 2010 (UTC - 4:00)
System Uptime: 0 days 23:05:13.250
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Jun 18 23:44:35.214 2010 (UTC - 4:00)
System Uptime: 0 days 1:59:18.775
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck 1000008E, {c0000005, 82ab0bb3, a200f91c, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+2b316 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 23:55:23.188 2010 (UTC - 4:00)
System Uptime: 0 days 23:44:48.748
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 00:21:51.441 2010 (UTC - 4:00)
System Uptime: 2 days 5:11:25.627
BugCheck D1, {a0ae5, 2, 0, 90e87163}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+86163 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Algan · 02 Jul 2010

Hi Jonathan. I noticed a lot of what you've listed lists WoW.exe as the culprit. In the most recent patch of World of Warcraft, there was an issue with the game reaching an out of memory error over the course of an hour or so of gameplay, particularly in areas of large view distance. So perhaps that contributed to the issue some. To note, I am using one version previous to the most current version of the drivers (which was released earlier this month). I am using drivers from April.

Zig: I ran memtest86x for a few hours, and it popped over 1200 errors before I rebooted to post this response. I honestly don't think it is RAM, since I purchased a completely new 8GB of it (4x2GB) a couple weeks ago, and the new RAM is in. Of course, I could be extremely unlucky and get two sets of RAM each with a bad stick or something like that.

Honestly, at this point, I'm suspecting a lemon motherboard with bad RAM slots, a faulty CPU, or now, perhaps a failing video card.

CarlTR6 · 02 Jul 2010

I suggest that you run Memtest again on one stick at a time for 7 passes. When you are finished, take a known good stick and test it in each slot for 7 passes.

Jonathan_King · 02 Jul 2010

I agree with Carl. Remember, anytime Memtest reports errors, it can be compatibility issues with the RAM or motherboard, a bad motherboard slot, or bad RAM.

Test stick #1 in slot #1. If it passes, test it in all the other slots.

Then test stick #2 in slot #1, etc.

Windows 7: Win7 32-bit Daily BSOD crashes (dmp files included)

Win7 32-bit Daily BSOD crashes (dmp files included) problems?