Windows 7 Rare BSOD just became too common

[Kaidonni]

Suffering from the dreaded BSOD quite frequently at the moment. It was only occasional before yesterday, but now it has become endemic. The primary trigger for the repeatable BSODs is Skyrim, except only from yesterday (installed since 25th December 2012, played it for 128 hours plus without any BSOD). Played for 30-40 minutes in the afternoon after installing Dawnguard, no issue - but now somewhere between 5-10 minutes (maybe a little less), there is a guaranteed BSOD, which started late last night. At least twice now a BSOD has occured *without* being in the game. Any BSOD has only occured before when no one has been using the computer at the time - but now once last night, shortly after a BSOD in Skyrim (computer was back in Windows after successfully logging in), and once today while the computer was recovering (it got to the login screen, I typed password in, and bam!).

It's extremely frustrating. Before it was just odd, happening now and then, and never in any game. Now it's gone psychotic...

If I recall, at least one BSOD yesterday was a Bad Pool Header, and the two today have been PFN List Corrupt errors. Below is the system information. I will note that Event Viewer refers to a harddrive\dr0 having a bad block, but chkdsk /r hasn't found anything wrong with any drives. Tomorrow I hope to try out Seatools for Windows to scan the hard drives. It's certainly memory intensive processes that are causing trouble, although that doesn't quite explain the BSODs that struck when no one was even using the computer. One morning I'd turned it on, logged in, checked my email (I think, or just logged in), went to have my wash - came back and it was mysteriously at the login screen (I can confirm from the Event Viewer that the bad block error happened).

Windows 7 64-bit
AMD Athlon II X4 Processor (4 CPUs), ~3.0GHz
4096MB RAM
DirectX 11
NVIDIA GeForce GT 240
Driver version: 8.17.12.7061

I'd attach the .dmp files, but it seems Windows keeps refusing permission DESPITE all users having access. For crying out loud...!

 

[usasma]

Since the HDD is likely to be dead/dying, the BSOD's may be "normal" for this situation. They're not quite as random as I'm used to seeing - so I have to wonder if there are other problems. Once the new hard drive is installed (and the old one is out of the system), then we'll see about other tests within Windows.

While waiting for the new hard drive, please run this free memory diagnostic also: Link Removed

 

[Kaidonni]

I'm hoping to deal with the drivers tonight to see if they had any bearing on the issue. Maybe the add-on to Skyrim installed new drivers/mucked about with the drivers and messed things up (games do occasionally install new drivers or update DirectX, so it might be wise for me to reinstall those games then deal with any changes they made). Still, the disk error isn't normal, and on closer inspection of Event Viewer, it appears to happen on booting up the computer and shutdown, not before a BSOD event (although that in itself doesn't mean it isn't a problem - the occasional error happens during the day in the list).

As to randomness...the very first time it happened (the most common BSOD, PFN_LIST_CORRUPT) was when only the internet was running, early morning (19/12/12). The second time, MEMORY_MANAGEMENT on 25/12/12, no games were running. The third time, PFN_LIST_CORRUPT on 31/1/13, the Creation Kit for Skyrim hadn't closed properly and stopped responding (Windows found an odd solution to that issue...). On 1/2/13, IRQL_NOT_LESS_OR_EQUAL, only internet and Windows Explorer running, no one even in the house. The BAD_POOL_HEADER took place while using the internet after a previous BSOD minutes before in-game, while the final PFN_LIST_CORRUPT was at the login screen after another previous BSOD minutes before in-game.

 

[Kaidonni]

Burned an ISO of SeaTools for DOS to CD, ran it...3 errors on the main harddrive that contains drive C. SeaTools couldn't repair the errors. Looks like the harddrive is going to cyber-heaven.

He also suggested that if Skyrim was more memory demanding than certain other games, it was reading/writing to memory more often and therefore more likely to access the corrupt sectors of the harddrive.

EDIT: Ooookay, BSOD while surfing the net...

KMODE_EXCEPTION_NOT_HANDLED
0x0000001e
ffffffff`c0000005
fffff800`034c1f60
00000000`00000000
ffffffff`ffffffff

It says it was caused by the driver ndis.sys.

 

[usasma]

You can continue to expect BSOD's until you've replaced the hard drive.
If they continue after the hard drive is replaced, please post back with the dump files.

These are other things that might be causing BSOD's:
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 and Win8). Also a part of many Asus utilities
Link Removed

adfs.SYS Thu Jun 26 16:52:37 2008 (48640195)
Adobe File System Driver
Link Removed

archlp.sys Fri Feb 6 07:39:29 2009 (498C2F81)
Arcsoft Total Media Player driver
Link Removed

mcdbus.sys Tue Feb 24 05:34:07 2009 (49A3CD1F)
MagicISO SCSI Host Controller driver
Link Removed

L1C62x64.sys Wed Apr 1 01:09:17 2009 (49D2F6FD)
Atheros NIC driver
Link Removed

lirsgt.sys Sun May 17 09:06:57 2009 (4A100BF1)
part of a Copy Protection platform developed by Tages SA
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Thu Feb  7 17:21:34.712 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020713-77251-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17592.amd64fre.win7sp1_gdr.110408-1631
System Uptime:[B]0 days 2:39:22.961[/B]
Probably caused by :[B]memory_corruption ( nt!MiReplenishPageSlist+c0 )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffff800034c1f60, 0, ffffffffffffffff}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800034c1f60, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  avgnsa.exe
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!MiReplenishPageSlist+c0[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  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]**************************Thu Feb  7 17:21:34.712 2013 (UTC - 5:00)**************************
[B]ASACPI.sys                  Sun Mar 27 22:30:36 2005 (42476C4C)[/B]
[B]adfs.SYS                    Thu Jun 26 16:52:37 2008 (48640195)[/B]
[B]archlp.sys                  Fri Feb  6 07:39:29 2009 (498C2F81)[/B]
[B]mcdbus.sys                  Tue Feb 24 05:34:07 2009 (49A3CD1F)[/B]
[B]L1C62x64.sys                Wed Apr  1 01:09:17 2009 (49D2F6FD)[/B]
[B]lirsgt.sys                  Sun May 17 09:06:57 2009 (4A100BF1)[/B]
wacomvhid.sys               Mon Sep 21 19:29:14 2009 (4AB80C4A)
mvusbews.sys                Thu Mar  4 03:46:42 2010 (4B8F7372)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
LHidFilt.Sys                Tue Aug 24 13:21:36 2010 (4C73FFA0)
LMouFilt.Sys                Tue Aug 24 13:21:43 2010 (4C73FFA7)
LUsbFilt.Sys                Tue Aug 24 13:21:47 2010 (4C73FFAB)
nvhda64v.sys                Thu Mar  3 10:59:02 2011 (4D6FBAC6)
nvBridge.kmd                Thu Apr  7 23:14:49 2011 (4D9E7DA9)
nvlddmkm.sys                Thu Apr  7 23:22:12 2011 (4D9E7F64)
atksgt.sys                  Sat Jun  4 11:22:26 2011 (4DEA4DB2)
avgmfx64.sys                Fri Dec 23 07:08:12 2011 (4EF46F2C)
avgrkx64.sys                Mon Jan 30 22:11:41 2012 (4F275BED)
avgidsha.sys                Wed Apr 18 22:19:15 2012 (4F8F7623)
avgtdia.sys                 Fri Aug 24 09:20:13 2012 (50377F8D)
avgldx64.sys                Wed Nov  7 21:24:03 2012 (509B17C3)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[Kaidonni]

Yes, I'll insist those are updated on the reinstall. It'll be next Tuesday, as my brother works from home and that's the next time he's able to sit down long enough to go through the reinstall. Thanks for all of the help so far, hopefully the new harddrive solves my problems.

 

[Kaidonni]

Here I am again...

Computer was fully reinstalled on 12/13th Feb with new harddrive, previous issues went away completely. This morning, it was reported by a family member that the screen went black and the computer rebooted while surfing the internet. Attached are the W7F Diagnostic results.

To think, I was about to come on here to report that the issue had been successfully resolved...ouch! I know it isn't my game, managed well over another 26 hours since the 13th (ran out of the room after loading it up the first time, made a cup of tea, hoped it was still running 10 minutes later!), including last night. Wasn't even running during this 'black screen of death' (family member didn't notice any blue screen).

One event that stands out in the Event Viewer is:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

 

[usasma]

Only 71 Windows Updates installed. Most systems have 140 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

Asus ATK0110 device isn't installed. This driver is needed, and older versions are known to cause BSOD's. Please install the 2009 version of the Asus ATK0110 ACPI Utility driver from the Asus website.

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! :

adfs.SYS Thu Jun 26 16:52:37 2008 (48640195)
Adobe File System Driver
Link Removed

mcdbus.sys Tue Feb 24 05:34:07 2009 (49A3CD1F)
MagicISO SCSI Host Controller driver
Link Removed

L1C62x64.sys Wed Apr 1 01:09:17 2009 (49D2F6FD)
Atheros NIC driver
Link Removed

AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Sat Feb 23 05:03:14.572 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022313-16832-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:05:13.195[/B]
Probably caused by :[B]memory_corruption ( nt!MmZeroPageThread+96c )[/B]
BugCheck [B]4E, {8d, 7efb1, 510080, fffff6800003774b}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000000000008d, 
Arg2: 000000000007efb1
Arg3: 0000000000510080
Arg4: fffff6800003774b
BUGCHECK_STR:  0x4E_8d
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x4E_8d_nt!MmZeroPageThread+96c[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  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]**************************Sat Feb 23 05:03:14.572 2013 (UTC - 5:00)**************************
[B]adfs.SYS           Thu Jun 26 16:52:37 2008 (48640195)[/B]
[B]mcdbus.sys         Tue Feb 24 05:34:07 2009 (49A3CD1F)[/B]
[B]L1C62x64.sys       Wed Apr  1 01:09:17 2009 (49D2F6FD)[/B]
[B]AsUpIO.sys         Sun Jul  5 22:21:38 2009 (4A515FB2)[/B]
AsIO.sys           Mon Aug  3 03:03:16 2009 (4A768BB4)
mvusbews.sys       Thu Mar  4 03:46:42 2010 (4B8F7372)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvhda64v.sys       Tue Jul  3 11:25:04 2012 (4FF30ED0)
LHidFilt.Sys       Tue Sep 18 05:26:53 2012 (50583E5D)
LMouFilt.Sys       Tue Sep 18 05:26:58 2012 (50583E62)
LUsbFilt.Sys       Tue Sep 18 05:27:01 2012 (50583E65)
lvrs64.sys         Fri Sep 21 15:02:17 2012 (505CB9B9)
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)
nvlddmkm.sys       Sat Dec 29 01:47:52 2012 (50DE9218)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aswrdr2.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

 

[Kaidonni]

This is getting extremely annoying now...after that BSOD on Saturday, everything was fine. Updated Windows, uninstalled MagicISO. Using an older version of the Adobe programs, so didn't bother with that. Tonight, had BSOD, this time SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. WhoCrashed seems to indicate dxgmms1.sys was responsible, but BlueScreenViewer oddly does not indicate any driver...

On Wed 27/02/2013 22:16:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-14773-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1EA53)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880043BCA53, 0xFFFFF8800458E6D8, 0xFFFFF8800458DF30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Attached is the W7F log dump...

To be honest, I regret following the advice of mucking about with the drivers. I never had this error before AT ALL until tonight. The updates were done on Monday evening, hardly touched Skyrim since then (it was certainly fine on Saturday and Sunday!). I thought it might be linked to my DirectX 11 version, but the previous dxdiag indicates it's the same driver file and driver version as Saturday (since I reinstalled the game but did not cancel the DirectX installation part). It's very annoying since it's this magical problem, and it never had it before. I must have put over 120 hours in in-game WITHOUT such an error, so I have no idea what's happening. Everything was absolutely fine after the full reinstall/new harddrive, then after that BSOD on Saturday everything was fine again, now this...I'm cursed. If a game isn't going to work, it should just stop working and that be it, not come up with a new excuse next week!

 

[usasma]

Sometimes it takes a bit of time to fix these things. Occasionally we'll even fix the BSOD's, only to be faced with problems with the system freezing or black screening.

There is lot's of video driver involvement in the raw stack text. While this isn't a definitive diagnostic tool, it may be beneficial to update your nVidia display drivers: http://www.geforce.com/drivers/results/57096

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! :

Please remove this program:
adfs.SYS Thu Jun 26 16:52:37 2008 (48640195)
Adobe File System Driver
Link Removed

Please update this one. If no update is available, please let us know.
AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Link Removed

I wonder about this driver as I haven't seen it very often:

mvusbews.sys Thu Mar 4 03:46:42 2010 (4B8F7372)
USB EWS Device Driver (May be related to HP printer software)
Link Removed

If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Link Removed



Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Wed Feb 27 17:16:38.887 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022713-14773-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 10:36:41.120[/B]
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fbf )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff880043bca53, fffff8800458e6d8, fffff8800458df30}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880043bca53, The address that the exception occurred at
Arg3: fffff8800458e6d8, Exception Record Address
Arg4: fffff8800458df30, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]X64_0x7E_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fbf[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  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]**************************Wed Feb 27 17:16:38.887 2013 (UTC - 5:00)**************************
[B]adfs.SYS           Thu Jun 26 16:52:37 2008 (48640195)[/B]
[B]AsUpIO.sys         Sun Jul  5 22:21:38 2009 (4A515FB2)[/B]
AsIO.sys           Mon Aug  3 03:03:16 2009 (4A768BB4)
mvusbews.sys       Thu Mar  4 03:46:42 2010 (4B8F7372)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
L1C62x64.sys       Mon Sep 27 02:36:23 2010 (4CA03B67)
nvhda64v.sys       Tue Jul  3 11:25:04 2012 (4FF30ED0)
LHidFilt.Sys       Tue Sep 18 05:26:53 2012 (50583E5D)
LMouFilt.Sys       Tue Sep 18 05:26:58 2012 (50583E62)
LUsbFilt.Sys       Tue Sep 18 05:27:01 2012 (50583E65)
lvrs64.sys         Fri Sep 21 15:02:17 2012 (505CB9B9)
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)
nvlddmkm.sys       Sat Dec 29 01:47:52 2012 (50DE9218)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aswrdr2.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

 

[Kaidonni]

Urgh, it happened again (Skyrim, ~10 minutes), and a cascade (two events) of BSOD events occured in Windows afterwards. First time I barely got a look at BlueScreenViewer, second time I had a little longer and even ran WhoCrashed.

On the drivers update/deletion: Tried the Asus website, it can't even find my motherboard (M4A78LT-M-LE), so messing with drivers there isn't an option. We also do have a HP printer, and are using an older version of Adobe, so not messing with those drivers.

Attached are the new reports. It all seems rather random, but there's gotta be some logic to it. There is another thing in Event Viewer, however:

The Desktop Window Manager is experiencing heavy resource contention.
Reason : Graphics subsystem resources are over-utilized.
Diagnosis : A consistent degradation in frame rate for the Desktop Window Manager was observed over a period of time.

The Desktop Window Manager is experiencing heavy resource contention.
Scenario : The Desktop Window Manager responsiveness has degraded.

Windows has shutdown:
Shutdown Duration : 31307ms
IsDegradation : false
Incident Time (UTC) : ‎2013‎-‎02‎-‎27T23:24:49.470450300Z

And errors including:

Windows has started up:
Boot Duration : 69709ms
IsDegradation : false
Incident Time (UTC) : ‎2013‎-‎02‎-‎27T22:17:45.718400400Z

Lots of these, lots and lots...

EDIT: I just had an idea what might be wrong, it's the only thing I can honestly think really changed between the times Skyrim worked and then did not.

On the 25/12/12, I cancelled the DirectX portion of the install, but on the 2/2/13 when installing Dawnguard, I wasn't around when it finished downloading from Steam, so don't know if it affected anything. On the 13/2/13 with the new harddrive and OS install, I again cancelled the DirectX portion of Skyrim's install, but when reinstalling Skyrim on the 25/2/13, I did not.

EDIT 2: Just thought I'd add that one of the dump files is dated 1/3/13, but that is because I left the computer off after the second Windows BSOD last night, so it only got registered this morning. I wasn't going to restart it again after it went twice inside Windows.

I can't do much more at the moment because my brother is going away for three weeks soon, and I think until he returns it's best for me to not muck about too much. There are temperature, driver verifier, and video card stress tests that I realise would be a very good idea to run, but I only want to do it with him around in case anything goes wrong. I do appreciate the help...if it's not my aquarium, it's the computer, and if it's not the computer, I don't want to know what's next.

 

[usasma]

90+% (or more) BSOD's are due to drivers. Not updating drivers just isn't possible when troubleshooting BSOD's.
This appears to be your motherboard: Link Removed So you should be able to update some of the drivers from there.

If you don't want to mess with it until your brother comes back, that's fine with me. Just reply to this topic when you have new info and I'll get an email about it.

Good luck!

 

[Kaidonni]

A new thing happened tonight, testing out another game for the time being that has never caused issues. This time it was Empire Total War, I left the room for 15-20 minutes while the screen to choose to initiate battle, autoresolve or withdraw was up (as I have done in the past - it's even safe to alt-tab while the screen is up, and you can exit to the menu, etc). When I returned, the game had frozen and the sound had hung. I tried alt-tab, nothing happened, and worried I rebooted. If this was a crash of the application, I'd expect it to have crashed to Windows (never tried ctrl-alt-delete, which I wished I'd tried). However, no BSOD, and the BlueScreenView shows nothing for it either (neither does Event Viewer - the game did create a crash dump log of its own, but the system had hung). The game had run fine for 2+ hours earlier, including in a number of battles. I'm really hoping this is somehow connected and not just a random error of another type. Not touching that game again either, though. It's a shame all this is happening now (it should have waited another 3 weeks). I'll leave games for the whole 3 weeks, not going to tempt it anymore.

On trying to boot into safe mode, however...BSOD. This was a new one, it was DRIVER_CORRUPTED_EXPOOL. I turned the whole system off anticipating it would keep doing it, came back about 40 minutes later.

My brother had installed an application to monitor the temperature of the components, but it had frozen at 47C.

 

[usasma]

Please gather a fresh set of the reports again and upload them with your next report. Also, please do this:

- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

 

[Kaidonni]

New reports and admin.evtx archives attached. Will note that there are warnings about attempts to shut down the computer failing - that's because the backup program, which we thought had been scheduled not to backup at shutdown, keeps insisting on backing up at shutdown; usually, either force shutdown is used to bypass the issue, or cancelling and then selecting shutdown from the Start menu again works as it should.

 

[usasma]

I see a WinRing library event in the Admin.etl file. Many different programs that center around the using of the WinRing libraries (RealTemp, Corsair Link2 (known BSOD issues w/Win8), Razer GameBooster, etc) - Please un-install it from your system.

Also, if you're overclocking, please stop while we're troubleshooting. Feel free to resume the overclock once the BSOD's have stopped and the system has been stabilized.

This is looking more and more like a low-level issue.

Out of the last 4 memory dumps there were 4 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems (such as the WinRing stuff)
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed or Link Removed ).

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! :

adfs.SYS Thu Jun 26 16:52:37 2008 (48640195)
Adobe File System Driver
Link Removed

AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Link Removed

If you're looking for hardware to suspect, I'd suggest starting with testing your USB devices - since the last memory dump blamed Microsoft USB drivers.


Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Sat Mar  2 15:12:05.975 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030213-15912-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:00:15.865[/B]
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]C5, {80, 2, 0, fffff8000240e9bc}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000080, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8000240e9bc, address which referenced memory
BUGCHECK_STR:  0xC5_2
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb 28 18:07:57.621 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030113-17347-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:03:11.244[/B]
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff88003f9bffb, fffff880031f8698, fffff880031f7ef0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003f9bffb, The address that the exception occurred at
Arg3: fffff880031f8698, Exception Record Address
Arg4: fffff880031f7ef0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb 28 18:02:06.042 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022813-17097-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:01:52.666[/B]
Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
BugCheck [B]4E, {99, ab903, 0, ab8fb}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000ab903, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000000ab8fb, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  GFIBackup.exe
FAILURE_BUCKET_ID: [B]X64_0x4E_99_nt!MiBadShareCount+4c[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb 28 17:59:17.866 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022813-14991-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 13:30:55.489[/B]
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VidSchiUpdateContextRunningTimeAtISR+76 )[/B]
BugCheck [B]D1, {4, 5, 0, fffff880053a30c6}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000004, memory referenced
Arg2: 0000000000000005, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880053a30c6, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_dxgmms1!VidSchiUpdateContextRunningTimeAtISR+76[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  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]**************************Sat Mar  2 15:12:05.975 2013 (UTC - 5:00)**************************
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb 28 18:07:57.621 2013 (UTC - 5:00)**************************
[B]adfs.SYS           Thu Jun 26 16:52:37 2008 (48640195)[/B]
[B]AsUpIO.sys         Sun Jul  5 22:21:38 2009 (4A515FB2)[/B]
AsIO.sys           Mon Aug  3 03:03:16 2009 (4A768BB4)
mvusbews.sys       Thu Mar  4 03:46:42 2010 (4B8F7372)
L1C62x64.sys       Mon Sep 27 02:36:23 2010 (4CA03B67)
nvhda64v.sys       Tue Jul  3 11:25:04 2012 (4FF30ED0)
LHidFilt.Sys       Tue Sep 18 05:26:53 2012 (50583E5D)
LMouFilt.Sys       Tue Sep 18 05:26:58 2012 (50583E62)
LUsbFilt.Sys       Tue Sep 18 05:27:01 2012 (50583E65)
lvrs64.sys         Fri Sep 21 15:02:17 2012 (505CB9B9)
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)
nvlddmkm.sys       Sat Dec 29 01:47:52 2012 (50DE9218)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aswrdr2.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

 

[Kaidonni]

Just to let you know, I shall be doing a test on Sunday evening since my brother is back next week. The last thing I did was update the Nvidia drivers to the latest version (February 18th). I've also downloaded and installed HWMonitor, since I want to see what happens if a BSOD occurs on the test (or if the system hangs like it did with Empire). Not entirely certain what I should be looking for with the voltage parameters (there is a CPU VCORE, +3.3V, +12V, -12V and VBAT parameter.

At the moment, the temperatures for the motherboard seem to be 39 degrees, and the processors ~25. There's also a Powers parameter, with Package at 31.20W. Erm...not doing anything particularly strenuous on the computer, but the graphics card is reading at 51 degrees at the moment.

Attached the .txt with the details in if anyone can understand it better than me. Been away from troubleshooting for almost 3 weeks...it was like a dream. However, I don't want this BSOD issue coming back (not playing games, hasn't happened - but then it first started *outside* of games anyway), especially not for my work in Photoshop (using very large files, +1GB).

 

[usasma]

Sorry, but I have no knowledge of the voltage requirements. I'd suggest posting over in the Hardware forums for more expert advice.

FWIW - I did hear (a long time ago) that there were memory problems with some Asus M4 boards, but haven't seen them myself.
Here's my previous post about it:

Just FYI - a recent poster (early Nov 2011) states that they were advised by Asus to manually set their memory settings/timings/voltages because of issues with the M4 series of motherboards.
You can get the settings/timings/voltages from the website of your RAM manufacturer.

In other words, the original poster suggested NOT using the Auto setting for RAM in the M4 series of boards. Rather that you should get the recommended settings/timings/voltages from the RAM manufacturer and manually enter them into your BIOS.

Good luck!

 

[Kaidonni]

New BSOD event. Yesterday I was able to do some testing in games, had to restart the computer to do so (nothing serious, just one newly [re]installed game required a restart as directed by the installer). No issues with that, or with Empire either, then decided to go for Windows Memory Diagnostic. It didn't find anything wrong. Played about an hour of Star Trek Online, followed by forty-five minutes of web surfing. The shut off period was ~10 hours. This morning it must've been on for thirty-forty minutes, and while surfing the web it went (ironically, I was visiting a site named 'Can I Run It' at that exact moment - apparently I cannot!). Attached is a new set of logs, it's the latest - MEMORY_MANAGEMENT. I went through the rebooting process, and it may have happened a second time, as it was back at the screen for selecting to boot up normally or allow Windows to try repairing the issue a short while later - I allowed Windows to try it's magic.

A concerned family member thinks it's the games that did it, since there were no issues for three whole weeks... Maybe it is a game, but not the way they are thinking. I believe that something is causing system instability, and I'm thinking the RAM has something wrong with it, or one of the slots. The MEMORY_MANAGEMENT issue also happened on the 25th December when no one was on the computer, and it was basically left idle (not sure if a game was running, but it would have been alt-tabbed at the time).

Because memtest requires time to run and quite a bit of fiddling about inside the computer, I need my brother to show me how to remove and change the RAM around.

 

[usasma]

Out of 4 memory dumps there were 4 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed or Link Removed ).

Please start with these free diagnostics: Link Removed
Please let us know the results of the diagnostics. Then we can move on from there.

Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Mon Mar 25 06:01:52.102 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032513-16192-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:40:07.726[/B]
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]1A, {5003, fffff780c0000000, 34e9, 570000006952}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff780c0000000
Arg3: 00000000000034e9
Arg4: 0000570000006952
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  GFIBackup.exe
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  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 Mar 25 06:01:52.102 2013 (UTC - 4:00)**************************
[B]adfs.SYS           Thu Jun 26 16:52:37 2008 (48640195)[/B]
[B]AsUpIO.sys         Sun Jul  5 22:21:38 2009 (4A515FB2)[/B]
AsIO.sys           Mon Aug  3 03:03:16 2009 (4A768BB4)
mvusbews.sys       Thu Mar  4 03:46:42 2010 (4B8F7372)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
L1C62x64.sys       Mon Sep 27 02:36:23 2010 (4CA03B67)
LHidFilt.Sys       Tue Sep 18 05:26:53 2012 (50583E5D)
LMouFilt.Sys       Tue Sep 18 05:26:58 2012 (50583E62)
LUsbFilt.Sys       Tue Sep 18 05:27:01 2012 (50583E65)
lvrs64.sys         Fri Sep 21 15:02:17 2012 (505CB9B9)
nvhda64v.sys       Wed Dec 19 00:41:41 2012 (50D15395)
nvlddmkm.sys       Sat Feb  9 18:13:08 2013 (5116D804)
aswRvrt.sys        Wed Mar  6 18:21:43 2013 (5137CF87)
aswFsBlk.SYS       Wed Mar  6 18:22:01 2013 (5137CF99)
aswMonFlt.sys      Wed Mar  6 18:22:08 2013 (5137CFA0)
aswTdi.SYS         Wed Mar  6 18:22:10 2013 (5137CFA2)
aswrdr2.sys        Wed Mar  6 18:22:24 2013 (5137CFB0)
aswSP.SYS          Wed Mar  6 18:23:05 2013 (5137CFD9)
aswSnx.SYS         Wed Mar  6 18:23:10 2013 (5137CFDE)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aswRvrt.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
aswrdr2.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

 

[Kaidonni]

Can confirm not overclocking. I'm going to reinstall DirectX first, as someone had issues with BSODs while using the Creation Kit - and only while using it. Somehow, a dll had been corrupted. Second, Avast has not detected any malware, but I remain unconvinced, so I might download and try another anti-malware program temporarily to see if anything is detected. Third, I've got the go-ahead on memtest, so Friday I'll probably burn an iso and test the RAM (unfortunately, the motherboard has only 2 slots for RAM, and they are paired in a manner that they both have to be in use for the computer to run, so unsure how this impacts the memtest and swapping/testing individual sticks).