BSOD Problems

Kyjibo · 07 Mar 2010

I'd been having issues with intermittent BSODs and decided to wipe in an attempt to resolve what I thought I had traced the problem to (Using ACPI mode).

Unfortunately, that did not solve all of my problems. All of my drivers are up-to date and I am going to run memtest overnight to check the ram. The impression I am getting from the varied state of the errors makes me worried it is a motherboard problem but before I go spend money replacing parts I'm interested in a second opinion.

os: Win7 x64
mobo: ASUS P5B
video: ATI Radeon 4870
sound: HTOmega Striker 7.1
network: D-Link DWA-556

myzr7 · 07 Mar 2010

Welcome to SevenForums.
I read all your mini dumps. Two reference to athros which I believe is a wireless internet adapter, one a usb port and one nt kernal. I would suggest looking at updating wireless adapter driver. Good luck to you.

******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffff880045b8710, 8000000177d4e121, fffff80003be0400, a}
Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+1010 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

usasma · 07 Mar 2010

Normally a number of different errors would signal a hardware problem.
I'm not convinced that you've experienced enough differing errors to suppose that this is a hardware problem.

The Asus P5 series of boards have been known to have issues with memory timings/settings/voltages that have caused BSOD's - so I'd visit both the Asus support website and the support website of the manufacturer of your RAM to ensure that you have the correct settings/timings/voltages.

The dump files point to athrx.sys and USBPORT.SYS. I suspect you D-Link DWA-556 wireless networking adapter (which is not certified as compatible with Win7).

There are directions on the D-Link website (in the FAQ's) on how to install this adapter in Win7 - so I would suggest following them. D-Link Xtreme N PCI Express Desktop Adapter

Summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Mar  4 00:55:55.779 2010 (GMT-5)
System Uptime: 0 days 0:14:29.350
BugCheck D1, {8b0040, 2, 0, fffff88004595e00}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+10ae00 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Mar  4 15:04:28.020 2010 (GMT-5)
System Uptime: 0 days 0:55:53.924
BugCheck 50, {fffff800022df7b0, 8, fffff800022df7b0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42907 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Steam.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar  6 23:07:13.869 2010 (GMT-5)
System Uptime: 0 days 0:54:13.648
BugCheck D1, {0, 2, 0, fffff88003b4a480}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_ProcessNeoStateChangeList+18 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Mar  7 01:00:45.337 2010 (GMT-5)
System Uptime: 0 days 1:52:30.241
BugCheck BE, {fffff880045b8710, 8000000177d4e121, fffff80003be0400, a}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+1010 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  left4dead2.exe

Kyjibo · 20 Mar 2010

I returned from a trip from being out of town today and booted the computer normally and everything was working fine. Then I started up Team Fortress 2 and after playing for about a minute the computer BSODed. I glanced at the debug screen and hit the reset button and stepped away. When I returned I was greeted by another blue screen. Since then everything has operated normally.

On the advice you gave me earlier - my network drivers are up to date with the latest from Atheros - D-Link's website has no Windows 7 drivers for this particular hardware. I also ran the inf update utility from Intel (ASUS's site had an outdated version) and that was all I could find for motherboard updates. The timings CPU-Z is reporting match what the ram specs are so I don't think that is the problem. Could it be reporting them incorrectly?

Attached are the dumps from the two consecutive crashes today.