Windows BSOD :(

[dasupalouie]

Hi Guys,

My Windows 7 Ultimate Retail x86 (64 bit) keeps crashing. I'm suspecting hardware issues because of how sporadic the BSOD's occur (around once a day doing normal tasks) but I could be wrong. I ran memtest overnight and found no errors. Now I'm stuck

Here is my dump:

http://members.shaw.ca/lwalsh85/DUMP.zip

Here is my PC info:

http://members.shaw.ca/lwalsh85/MONOLITH1.txt

Your help is greatly appreciated

 

[dasupalouie]

Also here is a report of all the recent crashes

http://members.shaw.ca/lwalsh85/report.html

 

[usasma]

Your D-Link DWA-552 XtremeN Desktop Adapter is disabled. Is this deliberate? If so, I'd suggest uninstalling the software/drivers and removing the device from your system.

Only running the 7 memory dumps from November. The rest are from far enough back that they likely aren't significant.

From your BlueScreenView report, there are 12 memory dumps with 9 different BSOD error messages.
This is likely to be a hardware issue.

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

One of the memory dumps blames your Norton protection. But the MSINFO32 file doesn't show Norton as being installed. So, I'd suggest this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: KB Article Not Found
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

If you've already uninstalled the Norton, just skip that step - and still install a free antivirus and use the Norton Removal Tool

Also, you have the 2005 version of the ASACPI.sys driver - this is a known BSOD cause. Please update it from the Asus website for your system here: ASUSTeK Computer Inc.-Support- download_item_mkt
It's under the Utilities heading and is named: ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit

Also, there are BSODE issues with the Asus P5 series of boards and memory with Win7. I suggest that you visit the Crucial website and get the appropriate timings/settings/voltages for your RAM - then set those settings in the BIOS (in other words, DON'T use the Auto setting for memory in the BIOS).

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Wed Nov 10 20:51:58.870 2010 (UTC - 5:00)
System Uptime: 0 days 0:12:59.431
Probably caused by : memory_corruption ( nt!MiRealSuccessor+18 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0303d388 fffff880`07ce2f70 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Wed Nov 10 20:37:26.649 2010 (UTC - 5:00)
System Uptime: 0 days 19:36:34.600
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  plugin-contain
Bugcheck code 0000000A
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`02cb8884
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Tue Nov  9 21:28:51.051 2010 (UTC - 5:00)
System Uptime: 0 days 0:30:51.002
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c7b )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`071f5e60 fffffa80`051f5e60 fffffa80`071f5e60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Tue Nov  9 20:56:39.036 2010 (UTC - 5:00)
System Uptime: 0 days 0:02:55.596
Probably caused by : memory_corruption ( nt!MiSwapWslEntries+21a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
Bugcheck code 0000000A
Arguments fffff704`401a65bc 00000000`00000000 00000000`00000001 fffff800`02d0165a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Mon Nov  8 14:07:36.177 2010 (UTC - 5:00)
System Uptime: 0 days 0:08:26.802
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`98cd9585 00000000`00000000 10adc3a5`258c43be 00000000`00000101
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Mon Nov  8 13:57:50.052 2010 (UTC - 5:00)
System Uptime: 3 days 13:44:38.613
Probably caused by : atapi.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0782b680 fffff800`00b9c518 fffffa80`0b045010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Mon Nov  1 19:11:41.105 2010 (UTC - 5:00)
System Uptime: 5 days 0:43:47.666
*** WARNING: Unable to verify timestamp for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+58c5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0bb028c5 fffff880`031cb708 fffff880`031caf70
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[dasupalouie]

Thanks usasma for the prompt and detailed response!

So I removed the wireless NIC since I'm not using it and uninstalled the driver. I ran memtest and the HD scan and found no errors. Right after I got that BSOD I did a full remove of norton to eliminate the possibility of nav being the culprit, hence it shows in the log my bad. I updated the motherboard ASACPI.sys driver. Hasn't bluescreened yet, crossing my fingers

 

[dasupalouie]

Hmmm I looked at crucial's website and the specs for my ram is the following:

Module Size: 4GB kit (2GBx2)
Package: Ballistix 240-pin DIMM
Feature: DDR2 PC2-6400
Specs: DDR2 PC2-6400 • 4-4-4-12 • Unbuffered • NON-ECC • DDR2-800 • 2.0V • 256Meg x 64 •

On auto settings, I noticed the ram is at 5-5-5-18. Should I change the settings so it runs at 4-4-4-12 and 2.0 VDim? Or just wait and see what happens?

 

[usasma]

Let's see what happens.
If the BSOD's stop, then it's "if it ain't broke, don't fix it"
If the BSOD's don't stop, then it's worth a try.

Should the problem return at a later date, then try the new settings then.
The issues with the P5 series of boards doesn't necessarily apply to all users. It's just that I've seen quite a few here on systems that were BSOD'ing