Rare BSOD just became too common

#1
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...!
 


Last edited:

usasma

Fantastic Member
Microsoft Community Contributor
#2
Start with these free hardware diagnostics: Initial Hardware Diagnostics

Please provide this information so we can provide a complete analysis: http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html

I that doesn't work, then try the data collection program from here: Blue Screen of Death (BSOD) Posting Instructions - Windows 8, 7 & Vista
 


#3
Just got BlueScreenView.

PFN_LIST_CORRUPT (0x00000004e) appears 5 times in the 11 dump files, along with MEMORY_MANAGEMENT (0x00000001a) twice, IRQL_NOT_LESS_OR_EQUAL (0x0000000a) and DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x0000000d1) and BAD_POOL_HEADER ((0x000000019) each once. Interesting that the earliest dump file is the 7th of May 2012, then the next one is 19th December (I thought the morning when the computer mysteriously reappeared at the login screen was the 28th November, it seems I was wrong - it was a morning I went to college, though).

Now, there was a BSOD on the 25/12/2012, when I installed Skyrim - I wasn't at the computer at the time, nor was it running. The dump file right after that one, though, was last Thursday (31/1/2013) - more than a month later, and while using the Creation Kit which ended up freezing (except it had frozen for a good two or so hours, and only trying to close the program led to the BSOD). However, the fifth dump file (1/2/2013) concerned an event when no one was even in the house, and only the internet would have been running (I've since uninstalled Super Anti Spyware which I hoped was a cause of some of the issues...).
 


Last edited:

usasma

Fantastic Member
Microsoft Community Contributor
#4
Does the system BSOD in Safe Mode? To test, rapidly tap the F8 key after the manufacturer's splash screen goes away.
If it does, then it's most likely a 3rd party driver (as opposed to a harware problem or a Windows problem).

We still need you to try the diagnostics and see if you can generate those reports. The reports contain (among other things) the memory dumps that you're having difficulty getting.
 


#5
Well, because the first idea back on Saturday evening was possible harddrive failure (Event Viewer displays harddrive\dr0 has a bad block repeatedly, including when starting up/shutting down the computer and during the BSOD events), I've just ran the SeaTools for Windows harddrive scan - it's doing a Long Generic on both drives, but it instantly failed the one while the other has been going for a good 10 minutes or so without fail).

EDIT: So, the one disk drive passed SMART test, but it failed Long Generic, Short Generic, and Short Drive Test. The other drive passed all of these.

EDIT 2: BlueScreenViewer info attached.
 


Attachments

Last edited:
#6
Is there any way to figure out which drives are contained on hard drive serial number S20BJA0ZA46615? I can't find anywhere on the computer or an internet search that even remotely provides this info. If C drive is on that hard drive, then it means full install (*groan*), and I'd rather know for certain before any mucking about...
 


usasma

Fantastic Member
Microsoft Community Contributor
#7
Without the reports that I requested earlier I can't figure a thing out.
Try looking in diskmgmt.msc for that info.
 


#8
Okay, done that, zip file attached. Don't know how I didn't pay attention to that link...trying to be smart, I guess...
 


Attachments

usasma

Fantastic Member
Microsoft Community Contributor
#9
Well, we've got the memory dumps now, but not the rest of the reports.
Please let the data collection app run for at least 15 minutes (or until it says it's done).
Those reports are what I need to answer your hard drive question.

The dumps tend to confirm that there is a hardware problem, but there also may be a software problem.

So, you can also just disconnect one of the hard drives and then run the long test on the one that remains hooked up. That'll tell you if it's the bad or the good one.

Then, see if you can boot into Windows with it. If you can't, then that's not the one with the C: drive on it. Also try the other one to see if you can boot into Windows with it - as you may have to do a repair install if the boot stuff is on one hard drive and the OS is on the other.

Here's the info from the dumps - don't pay attention to it until we've seen which drive is which.

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
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys

adfs.SYS Thu Jun 26 16:52:37 2008 (48640195)
Adobe File System Driver
http://www.carrona.org/drivers/driver.php?id=adfs.SYS

archlp.sys Fri Feb 6 07:39:29 2009 (498C2F81)
Arcsoft Total Media Player driver
http://www.carrona.org/drivers/driver.php?id=archlp.sys

mcdbus.sys Tue Feb 24 05:34:07 2009 (49A3CD1F)
MagicISO SCSI Host Controller driver
http://www.carrona.org/drivers/driver.php?id=mcdbus.sys

L1C62x64.sys Wed Apr 1 01:09:17 2009 (49D2F6FD)
Atheros NIC driver
http://www.carrona.org/drivers/driver.php?id=L1C62x64.sys

lirsgt.sys Sun May 17 09:06:57 2009 (4A100BF1)
part of a Copy Protection platform developed by Tages SA
http://www.carrona.org/drivers/driver.php?id=lirsgt.sys



Analysis:
The following is for informational purposes only.
Code:
[FONT=lucida console]**************************Sun Feb  3 15:11:43.288 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020313-75847-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 0:01:45.911[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3824b )[/B]
BugCheck [B]4E, {7, 414d8, 80, 0}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000004E"]PFN_LIST_CORRUPT (4e)[/URL]
Arguments: 
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 00000000000414d8, page frame number
Arg3: 0000000000000080, current share count
Arg4: 0000000000000000, 0
BUGCHECK_STR:  0x4E_7
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0x4E_7_nt!_??_::FNODOBFM::_string_+3824b[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Feb  3 15:09:07.727 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020313-78936-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 1:19:41.960[/B]
Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
BugCheck [B]4E, {99, 39940, 3, 61fa4}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000004E"]PFN_LIST_CORRUPT (4e)[/URL]
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000039940, page frame number
Arg3: 0000000000000003, current page state
Arg4: 0000000000061fa4, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  Pen_Tablet.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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Feb  2 17:27:36.838 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020213-83788-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 0:03:30.071[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!IopXxxControlFile+c61 )[/B]
BugCheck [B]19, {20, fffffa80075aa900, fffffa80075ab390, ca9da30}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000019"]BAD_POOL_HEADER (19)[/URL]
Arguments: 
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa80075aa900, The pool entry we were looking for within the page.
Arg3: fffffa80075ab390, The next pool entry.
Arg4: 000000000ca9da30, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  avgrsa.exe
FAILURE_BUCKET_ID: [B]X64_0x19_20_nt!IopXxxControlFile+c61[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Feb  2 17:23:16.786 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020213-82914-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 1:52:45.035[/B]
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )[/B]
BugCheck [B]10E, {1f, fffff8a014eb2830, 0, 991a0}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000010E"]VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)[/URL]
Arguments: 
Arg1: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a014eb2830
Arg3: 0000000000000000
Arg4: 00000000000991a0
BUGCHECK_STR:  0x10e_1f
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Feb  2 15:27:52.299 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020213-82243-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 0:05:45.922[/B]
Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
BugCheck [B]4E, {99, 1dd22, 2, 12a2c}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000004E"]PFN_LIST_CORRUPT (4e)[/URL]
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000001dd22, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000012a2c, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  TESV.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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Feb  2 15:21:16.541 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020213-83148-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 10:31:02.774[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VidSchiUpdateContextStatus+275 )[/B]
BugCheck [B]D1, {3, 2, 1, fffff8800412080d}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x000000D1"]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/URL]
Arguments: 
Arg1: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800412080d, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_dxgmms1!VidSchiUpdateContextStatus+275[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  1 06:16:43.738 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020113-75395-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 1:26:38.361[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiCommitThreadWait+28a )[/B]
BugCheck [B]A, {3220, 2, 1, fffff8000349d04a}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000000A"]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
Arguments: 
Arg1: 0000000000003220, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000349d04a, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiCommitThreadWait+28a[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 31 11:26:40.720 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\013113-86845-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 6:31:47.343[/B]
Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
BugCheck [B]4E, {99, abf51, 0, abf49}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000004E"]PFN_LIST_CORRUPT (4e)[/URL]
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000abf51, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000000abf49, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  CreationKit.ex
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 25 15:00:53.318 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\122512-83054-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 10:03:10.941[/B]
Probably caused by :[B]memory_corruption ( nt!MiRelinkStandbyPage+115 )[/B]
BugCheck [B]1A, {8885, fffffa80036667b0, fffffa8000c29640, 502}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000001A"]MEMORY_MANAGEMENT (1a)[/URL]
Arguments: 
Arg1: 0000000000008885, The subtype of the bugcheck.
Arg2: fffffa80036667b0
Arg3: fffffa8000c29640
Arg4: 0000000000000502
BUGCHECK_STR:  0x1a_8885
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0x1a_8885_nt!MiRelinkStandbyPage+115[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 19 03:02:59.638 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\121912-77360-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 0:22:49.261[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+11718 )[/B]
BugCheck [B]4E, {2, 42e05, 137fff, 1}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000004E"]PFN_LIST_CORRUPT (4e)[/URL]
Arguments: 
Arg1: 0000000000000002, A list entry was corrupt
Arg2: 0000000000042e05, entry in list being removed
Arg3: 0000000000137fff, highest physical page number
Arg4: 0000000000000001, reference count of entry being removed
BUGCHECK_STR:  0x4E_2
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x4E_2_nt!_??_::FNODOBFM::_string_+11718[/B]
  BIOS Version                  0704   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon May  7 15:53:22.469 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\050712-36566-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 12:09:56.092[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+38ef0 )[/B]
BugCheck [B]1A, {888a, fffff8a00013c998, fffff8a002769f9b, fffffa80010d1e40}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000001A"]MEMORY_MANAGEMENT (1a)[/URL]
Arguments: 
Arg1: 000000000000888a, Internal memory management structures (likely the PTE or PFN) are corrupt.
Arg2: fffff8a00013c998
Arg3: fffff8a002769f9b
Arg4: fffffa80010d1e40
BUGCHECK_STR:  0x1a_888a
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID: [B]X64_0x1a_888a_nt!_??_::FNODOBFM::_string_+38ef0[/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.
Code:
[FONT=lucida console]**************************Sun Feb  3 15:11:43.288 2013 (UTC - 5:00)**************************
[COLOR=RED][B]ASACPI.sys                  Sun Mar 27 22:30:36 2005 (42476C4C)[/B][/COLOR]
[COLOR=RED][B]adfs.SYS                    Thu Jun 26 16:52:37 2008 (48640195)[/B][/COLOR]
[COLOR=RED][B]archlp.sys                  Fri Feb  6 07:39:29 2009 (498C2F81)[/B][/COLOR]
[COLOR=RED][B]mcdbus.sys                  Tue Feb 24 05:34:07 2009 (49A3CD1F)[/B][/COLOR]
[COLOR=RED][B]L1C62x64.sys                Wed Apr  1 01:09:17 2009 (49D2F6FD)[/B][/COLOR]
[COLOR=RED][B]lirsgt.sys                  Sun May 17 09:06:57 2009 (4A100BF1)[/B][/COLOR]
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)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 25 15:00:53.318 2012 (UTC - 5:00)**************************
avgldx64.sys                Wed Jul 25 20:56:48 2012 (501095D0)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon May  7 15:53:22.469 2012 (UTC - 5:00)**************************
avgldx64.sys                Thu Jan  6 23:36:39 2011 (4D269857)
AVGIDSEH.Sys                Tue Feb 22 00:23:04 2011 (4D634838)
avgmfx64.sys                Tue Mar  1 07:25:15 2011 (4D6CE5AB)
avgrkx64.sys                Wed Mar 16 10:06:34 2011 (4D80C3EA)
avgtdia.sys                 Mon Apr  4 17:54:35 2011 (4D9A3E1B)
[/FONT]
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=adfs.SYS
http://www.carrona.org/drivers/driver.php?id=archlp.sys
http://www.carrona.org/drivers/driver.php?id=mcdbus.sys
http://www.carrona.org/drivers/driver.php?id=L1C62x64.sys
http://www.carrona.org/drivers/driver.php?id=lirsgt.sys
http://www.carrona.org/drivers/driver.php?id=wacomvhid.sys
http://www.carrona.org/drivers/driver.php?id=mvusbews.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LUsbFilt.Sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvBridge.kmd
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=atksgt.sys
http://www.carrona.org/drivers/driver.php?id=avgmfx64.sys
http://www.carrona.org/drivers/driver.php?id=avgrkx64.sys
http://www.carrona.org/drivers/driver.php?id=avgidsha.sys
http://www.carrona.org/drivers/driver.php?id=avgtdia.sys
http://www.carrona.org/drivers/driver.php?id=avgldx64.sys
http://www.carrona.org/drivers/driver.php?id=avgldx64.sys
http://www.carrona.org/drivers/driver.php?id=avgldx64.sys
http://www.carrona.org/drivers/driver.php?id=AVGIDSEH.Sys
http://www.carrona.org/drivers/driver.php?id=avgmfx64.sys
http://www.carrona.org/drivers/driver.php?id=avgrkx64.sys
http://www.carrona.org/drivers/driver.php?id=avgtdia.sys
 


Last edited:
#10
Quick update, will get to gathering the extra info - rechecked Event Viewer to see *when* the harddrive errors started. They started on 22/9/12, and the errors concern the file system structure on volume C: being corrupt and unusable. It looks like the computer attempted repairs, but the bad block error started. So, when taking out the drive, the serial number will tell all - looks like C drive is the culprit for the failed test.

And sorry about not following the instructions. Never dealt with this issue before myself. Brother moved out last year, and this is the first time anything serious has happened. Before that, he solved the issues. He has been able to assist, but without coming over he doesn't have much access to any of the info.
 


Last edited:

usasma

Fantastic Member
Microsoft Community Contributor
#11
Not a problem, that's what we're here for.
 


#12
Here we are, full gathering of the reports done (I think).
 


Attachments

usasma

Fantastic Member
Microsoft Community Contributor
#13
Code:
[U][B]Disk 0[/B][/U] (Boots from this one)
Partition 0 - 100 mb
Partition 1 - 146.39 gb = [COLOR=#ff0000]C:[/COLOR]
Partition 2 - 224.61 gb = [COLOR=#ff0000]E:[/COLOR]
Partition 3 - 94.67 gb = [COLOR=#ff0000]X:[/COLOR]

[U][B]Disk 1[/B][/U]
Partition 0 - 92.77 gb = [COLOR=#ff0000]Y:[/COLOR]
Partition 1 - 97.66 gb = [COLOR=#ff0000]D:[/COLOR]
Partition 2 - 275.33 gb = [COLOR=#ff0000]F:[/COLOR]
Boot to the Seatools diagnostic tool and read the serial numbers from there.
Seatools will also tell you which is Drive 0 and which is Drive 1

If it's Disk 1 that's the problem, you should be able to just remove it and the issues "should" stop. Windows should boot without issue because the boot stuff and the OS are both on Disk 0.
 


Last edited:
#14
I wondered if SeaTools put the drives in order. The top one failed all but the SMART test, and when going into Device Manager, the top drive can't be disconnected (the icon for that disappears when selecting it). Since C drive is also flagged in Event Viewer from way back in September 2012, looks like very bad news (full reinstall...).

I can't for the life of me find anything in SeaTools that lists the volumes on either of the drives along with the serial number. System Info simply provides info on what is on either drive, but without noting the specific serial number for that drive. I do assume it places them in order in the lists.
 


usasma

Fantastic Member
Microsoft Community Contributor
#15
From my experience with the Seatools diagnostic, the model number and serial number are listed.
I can't recall exactly where as, when confronted with this situation at work, we just disconnect one drive and see what happens.
I have 5 of the exact same drives on my home system and use the "disconnect and see" method on them also.

Be sure to use anti-static precautions when messing around inside the case: unplug the system from the wall and ensure that you're grounded and holding onto the metal of the case BEFORE sticking your hands inside the case to mess with cables and such.

The easiest thing for you is to remove (unplug) one drive and attempt to start the computer. If it goes to boot to Windows - it's Drive 0 that's connected (and Drive 1 is disconnected)

If it doesn't boot to Windows, then it's Drive 1 that's connected - and Drive 0 is the disconnected one.

Good luck!
 


#16
I take it the error reports point to harddrive failure, then?

I ran two other games last night as a test - Stalker and Empire Total War. I left them running for a bit, then moved around in the game world. No BSOD in either case, and they certainly ran longer than Skyrim was with the BSOD events. Not that this eliminates the threat posed by the bad blocks on the harddrive, but I'm wondering why the other games didn't set off a BSOD.
 


#17
I didn't use SeaTools for Dos...wondering if there'd be any difference in doing that, as I've read anything accessing the drive can interfere with SeaTools for Windows. Or do the other reports and Event Viewer confirm SeaTools' prognosis as reliable?
 


#18
Just noticed another issue in Event Viewer - a USER32 event keeps occuring everytime the computer is turned off (not during any of the BSOD events), stating: The process Explorer.EXE has initiated the power off of computer PARENTS-PC on behalf of user Parents-PC\Parents for the following reason: Other (Unplanned). Reason Code: 0x0

Another of the USER32 errors states: The process C:\Windows\system32\winlogon.exe (PARENTS-PC) has initiated the power off of computer PARENTS-PC on behalf of user Parents-PC\Parents for the following reason: No title for this reason could be found. Reason Code: 0x500ff

These seem to appear from before the 22/9/12...
 


usasma

Fantastic Member
Microsoft Community Contributor
#19
If it failed the Long/Extended test in Seatools, then it's most likely that that drive is dead/dying and must be replaced.
I suggest that you run Seatools for DOS, but suspect that the results will be the same.
 


#20
While I'm waiting for the new harddrive to come (and my brother, since there are a few tests I'd like to run with him around), I decided to test Stalker: Shadow of Chernobyl in static lighting. After ~10 minutes of playing, no BSOD. Multiple reloads, no BSOD...

Something I forgot to mention earlier was that at the start of last week (28/1/12), the computer had an error pop-up stating 'Display driver NVIDIA Windows Kernel Mode Driver, Version 270.61 stopped responding and has successfully recovered'. The screen flashed black for a moment before this, and I haven't seen it appear since. Event Viewer states: Display driver nvlddmkm stopped responding and has successfully recovered.

EDIT: Played another 20 minutes with higher graphics settings, still no BSOD.

Just ran 'WhoCrashed':

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 03/02/2013 20:11:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-75847-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x4E (0x7, 0x414D8, 0x80, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 03/02/2013 20:11:43 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x7, 0x414D8, 0x80, 0x0)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 03/02/2013 20:09:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-78936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x4E (0x99, 0x39940, 0x3, 0x61FA4)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 02/02/2013 22:27:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-83788-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80075AA900, 0xFFFFFA80075AB390, 0xCA9DA30)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 02/02/2013 22:23:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-82914-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A014EB2830, 0x0, 0x991A0)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
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.



On Sat 02/02/2013 20:27:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-82243-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x4E (0x99, 0x1DD22, 0x2, 0x12A2C)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 02/02/2013 20:21:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-83148-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xD80D)
Bugcheck code: 0xD1 (0x3, 0x2, 0x1, 0xFFFFF8800412080D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.



On Fri 01/02/2013 11:16:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020113-75395-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0x3220, 0x2, 0x1, 0xFFFFF8000349D04A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 31/01/2013 16:26:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013113-86845-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x4E (0x99, 0xABF51, 0x0, 0xABF49)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 25/12/2012 20:00:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122512-83054-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x8885, 0xFFFFFA80036667B0, 0xFFFFFA8000C29640, 0x502)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 19/12/2012 08:02:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121912-77360-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x4E (0x2, 0x42E05, 0x137FFF, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 07/05/2012 20:53:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050712-36566-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x888A, 0xFFFFF8A00013C998, 0xFFFFF8A002769F9B, 0xFFFFFA80010D1E40)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


I shall get around to dealing with the third party drivers listed in your earlier post, Usasma - but I feel better waiting until tomorrow night when my brother is around before I go messing about with those. The harddrive that is failing is still under warranty, and the new one is en-route, so I understand that issue still needs to be dealt with (good job these BSOD events highlighted it, or it may have snuck up on me).
 


Last edited:
This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top