Windows 7 Troubleshooting a few BSOD's

[lifeonloan3]

Hey all,

First let me say thanks for the useful forums--they've been helpful just as a searching resource as I've been trying to pin down my issues. I'm feeling a bit out of my depth though, so it seems I need to actually post!

System:
ASUS M4A88TD-V EVO/USB3 Motherboard
AMD Phenom II X6 1055T Thuban 2.8GHz Socket AM3 125W Six-Core Desktop Processor
Sapphire Radeon HD 6850 Video Card - 1GB, GDDR5, PCIe, mini-Display Port, HDMI, Dual DVI
Kingston HyperX 8GB (2 x 4GB) DDR3 1600 Ram
ABS Majesty series MJ900 Continuous 900W Power supply

I just recently replaced Ram with the Kingston--which is recommended for the motherboard--in hopes of solving at least some of my issues. Not much difference. I have run memtest and error-checking on the HD, no hits on either. After my last re-install of Windows I really don't know what's next.
I bought this system from a college kid as an upgrade from my old rig I built... My old rig may have been slower, but it was at least more stable!

EDIT: Also get a few random power-off's that do not produce dump files interspersed with the vanilla BSOD's. Power supply maybe?

Thanks,
-Bryan

 

[usasma]

Run Prime95 to stress the RAM (the Blend test is the most RAM intensive). It's free here: Free Software - GIMPS
Run it for 24 hours (you can use your computer while running it - but it's going to slow the system down a lot).

Set the RAM timings on your motherboard manually (get the settings/timings/voltages for your RAM from the Kingston website). DO NOT use the Auto setting for memory in the BIOS - we have seen some issues with the Asus M4 series of mobo's using the Auto settings.

Power off w/o a BSOD are usually Event ID 41 - Kernel Power errors - which usually indicate a hardware problem. It could be the PSU, but it could also be an overheating condition, or other hardware issues.

Only 97 updates since SP1 - most systems have 130 to 140. Please visit Windows Update and get ALL available updates.

You have a WIBU - CodeMeter-Stick USB Device that has 0 bytes free space (which will cause many problems if this is an accurate figure that the OS uses). I would suggest removing this device from your system to see if it is the cause of some of your issues.

These devices have problems:

Universal Serial Bus (USB) Controller PCI\VEN_1033&DEV_0194&SUBSYS_84131043&REV_03\FFFFFFFFFFFFFFFF00 The drivers for this device are not installed.

Ethernet Controller PCI\VEN_10EC&DEV_8168&SUBSYS_84321043&REV_06\01000000684CE00000 The drivers for this device are not installed.

Please install these drivers. I believe the USB controller is the USB 3.0 controller on your mobo.

You have the 2005 version of ASACPI.sys installed - this is a known cause of BSOD's on some Win7 systems.
Please go to this link ( ASUS - Motherboards- ASUS M4A88TD-V EVO/USB3 ), enter your OS in the dropdown box and then select the Utilities section. The "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" is the last item in that section. Please download and install it.

We have seen issues with wireless XBox controllers in the recent past. I see that you have an XBox controller installed but it isn't showing the usual driver that we associate with BSOD's. You can un-install this device and physically remove it from your system if you'd like to test it (in order to be sure it's not a problem).

But, the above driver is very old and it's likely to not be compatible with Win7 SP1. I'd suggest updating it to a more recent version. If a more recent version isn't available, then un-install it.

Please update your video drivers to the latest available version from ATI.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities
Link Removed

xnacc.sys Mon Jul 13 20:01:05 2009 (4A5BCAC1)
XNA Common Controller Driver [XBox]
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Mon Dec  3 16:55:55.042 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120312-22916-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:47:12.166[/B]
Probably caused by :[B]atikmpag.sys ( atikmpag+a82f )[/B]
BugCheck [B]3B, {c0000005, fffff8800444582f, fffff88008b548e0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800444582f, Address of the instruction which caused the bugcheck
Arg3: fffff88008b548e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]ACBSP.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_atikmpag+a82f[/B]
  BIOS Version                  2301   
  BIOS Release Date             08/09/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec  3 06:34:21.620 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120312-25162-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:03:49.368[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!IoRemoveIoCompletion+9f )[/B]
BugCheck [B]3B, {c0000005, fffff80002d6c1ef, fffff88009838090, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002d6c1ef, Address of the instruction which caused the bugcheck
Arg3: fffff88009838090, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]chrome.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!IoRemoveIoCompletion+9f[/B]
  BIOS Version                  2301   
  BIOS Release Date             08/09/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  2 12:05:48.213 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120212-25443-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:43:01.961[/B]
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )[/B]
BugCheck [B]10E, {1f, fffff8a00394e400, 0, 95d7c}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a00394e400
Arg3: 0000000000000000
Arg4: 0000000000095d7c
BUGCHECK_STR:  0x10e_1f
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148[/B]
  BIOS Version                  2301   
  BIOS Release Date             08/09/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  2 10:26:39.057 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120212-22900-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:01:20.181[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+163 )[/B]
BugCheck [B]3D, {fffff8800788d110, 0, 0, fffff800028a7ca0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff8800788d110
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff800028a7ca0
BUGCHECK_STR:  0x3D
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3D_nt!KiInterruptDispatchNoLock+163[/B]
  BIOS Version                  2301   
  BIOS Release Date             08/09/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  2 10:24:23.434 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120212-22776-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:00:38.198[/B]
Probably caused by :[B]rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )[/B]
BugCheck [B]1A, {1236, fffffa800da0b890, fffffa800da0b988, 40cc1a}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000001236, The subtype of the bugcheck.
Arg2: fffffa800da0b890
Arg3: fffffa800da0b988
Arg4: 000000000040cc1a
BUGCHECK_STR:  0x1a_1236
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e[/B]
  BIOS Version                  2301   
  BIOS Release Date             08/09/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Mon Dec  3 16:55:55.042 2012 (UTC - 5:00)**************************
[B]ASACPI.sys                  Sun Mar 27 22:30:36 2005 (42476C4C)[/B]
[B]xnacc.sys                   Mon Jul 13 20:01:05 2009 (4A5BCAC1)[/B]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
netr6164.sys                Wed Apr  7 08:07:21 2010 (4BBC7579)
ffusb2audio.sys             Thu Oct 13 11:40:18 2011 (4E970662)
atikmpag.sys                Wed Nov  9 21:12:44 2011 (4EBB331C)
atikmdag.sys                Wed Nov  9 21:52:46 2011 (4EBB3C7E)
aswrdr2.sys                 Mon Oct  8 04:23:43 2012 (50728D8F)
aswFsBlk.SYS                Tue Oct 30 18:43:04 2012 (509057F8)
aswMonFlt.sys               Tue Oct 30 18:43:09 2012 (509057FD)
aswTdi.SYS                  Tue Oct 30 18:43:16 2012 (50905804)
aswSP.SYS                   Tue Oct 30 18:44:06 2012 (50905836)
aswSnx.SYS                  Tue Oct 30 18:44:08 2012 (50905838)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  2 10:26:39.057 2012 (UTC - 5:00)**************************
netr6164.sys                Tue Jun  2 05:35:28 2009 (4A24F260)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
ffusb2audio.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[lifeonloan3]

Thanks for your detailed reply--I've been going through and updating the items you pointed out. I believe I've gotten to all the drivers.

It's been a day or so since a 'true' BSOD, but I've been having weird "lock-ups" and crashes not resulting in a BSOD.
They basically come in three flavors:
1. Everything frozen, locked up and unresponsive. Manual power off necessary.
2. Complete power off randomly, no BSOD, just black screen and restarts.
3. There may be a word for this, but basically the screen turns to what I can only describe as all the pixels being shot out horizontally to infinity, then it powers off. Almost like TV interference.

I just ran a SeaTools scan of my system drive and the long scan found bad sectors on it, so that may be a portion of the issue. It supposedly "repaired" them, but to my knowledge once a HD is going bad, there's not much saving it, at least for long.

Any thoughts? I can re-run the earlier reports if needed. Thanks again for taking the time to help!
-Bryan

 

[usasma]

I agree with your assessment of bad sectors on a hard drive - it's better to replace it than to watch it go slowly through it's death throes. If you're replacing the HDD no more reports are needed.

If not, then please rerun the set of reports so we can see what's going on internally.

 

[lifeonloan3]

Well, just to update on this for future reference and all, I did replace the HDD. Unfortunately, this did not really help anything stability-wise. Crashes and BSODS were continuing, and I would have to say almost getting worse. Had it crash once while re-installing windows and decided on that note it had to be hardware-related. Other strange things pointed this direction as well--my onboard sound output was not working, USB devices as you mentioned throwing errors, etc. Graphics card removal also did not change a thing.

So today I bit the bullet and bought/installed a new motherboard. So far so good! I'm installing a game to test that all is well, but before I would've gotten several crashes and BSODs by now.

Thanks for your help going through the troubleshoot process usasma, very much appreciated.

-Bryan

 

[usasma]

Sorry to hear about the mobo - but glad to hear that the BSOD's seem to have stopped!
Thanks for letting us know!