BSOD randomly occuring since last week, trouble pinpointing cause

moly · 10 Jun 2012

Is Windows 7 . . .
Yes

- x86 (32-bit) or x64 ?
x64

- the original installed OS on the system?
original install

- an OEM or full retail version?
OEM

- What is the age of system (hardware)?
Less than 1 year laptop. Toshiba Satellite L755D
Put in 2x4gb sticks of ram in January.

- What is the age of OS installation (have you re-installed the OS?)
Same age as laptop, no reinstalls.

attachments:
Windows_NT6_BSOD_jcgriff2
perfmon report

Summary:
Wife's laptop, started crashing randomly since last week (17 minidumps created since June 1st). I haven't seen any blue screens myself, but have seen the random "xxx has stopped working" (explorer, chrome, task manager). This just happened today. Shortly after running BSOD Dump & System File Collection app everything crashed and left me at an empty desktop background with no taskbar, only Ctrl+Shift+Esc brought up the task manager, but this would crash with the "stopped working" message after 20-30 seconds. I hadn't had a chance to run perfmon /report yet, but I had increased my virtual memory to 8gb without restarting yet (was reading on how to force full memory dumps on systems over 2gb ram). I ran the perfmon /report command after restarting my PC after the above everything "stops working" incident.

Hopefully it's just a driver update issue or something. Memtest86+ finishes with no errors, 1 pass. Computer is primarily used for browsing facebook, webcam. I have no issue with reinstalling windows if required.

Any help would be greatly appreciated.

Thanks,
Steve

usasma · 10 Jun 2012

Running the last 10 memory dumps.....

I'd suggest starting with these free hardware diagnostics: Initial Hardware Diagnostics. Be sure to run MemTest86+ for at least 3 passes (overnight is better).

Running 10 memory dumps generated over 6 days (4 to 10 Jun 2012)
5 different BSOD error codes cited (plus 2 corrupted memory dumps)
4 different causes blamed

This is most likely a hardware error. They (hardware errors) are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

Video drivers are outdated (they date from May 2011). Please update them from the AMD/ATI website: Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

Beyond that I don't see much in the way of other suspects - so I'd have to say it's most likely a hardware error. I'm thinking of the hard drive - due to the one dump that blames ntfs.sys and the 2 corrupted dumps - but that's just a guess. Try the hardware diagnostics that I linked to above and see if they pin the blame on something.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys    Fri Mar 09 06:05:26 2012 (4F59E3F6)
TVALZ_O.SYS     Mon Jul 13 22:19:26 2009 (4A5BEB2E)
Sftvollh.sys    Fri Sep 30 12:42:46 2011 (4E85F186)
atikmpag.sys    Wed May 25 23:28:48 2011 (4DDDC8F0)
L1C62x64.sys    Tue Feb 08 21:06:40 2011 (4D51F6B0)
rtl8192Ce.sys   Tue Jan 04 11:50:10 2011 (4D234FC2)
tdcmdpst.sys    Thu Jul 30 04:39:35 2009 (4A715C47)
pgeffect.sys    Sun Jan 16 21:09:10 2011 (4D33A4C6)
atikmdag.sys    Thu May 26 00:12:42 2011 (4DDDD33A)
AtihdW76.sys    Fri Sep 24 01:44:48 2010 (4C9C3AD0)
SynTP.sys       Thu Feb 03 21:59:28 2011 (4D4B6B90)
TVALZFL.sys     Fri Jun 19 06:05:44 2009 (4A3B62F8)
QIOMem.sys      Mon Jun 15 01:58:48 2009 (4A35E318)
CHDRT64.sys     Thu Jul 07 03:02:12 2011 (4E1559F4)
cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D)
Sftfslh.sys     Fri Sep 30 12:43:06 2011 (4E85F19A)
Sftplaylh.sys   Fri Sep 30 12:43:05 2011 (4E85F199)
Sftredirlh.sys  Fri Sep 30 12:43:14 2011 (4E85F1A2)
mbam.sys        Thu Dec 16 15:53:16 2010 (4D0A7C3C)
RtsUStor.sys    Wed Dec 01 02:46:14 2010 (4CF5FD46)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061012-37034-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun Jun 10 10:07:35.442 2012 (UTC - 4:00)
System Uptime: 0 days 12:29:18.361
Probably caused by : Sftplaylh.sys ( Sftplaylh+23dd2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  sftlist.exe
FAILURE_BUCKET_ID:  X64_0x3B_Sftplaylh+23dd2
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`08554dd2 fffff880`0a24eb70 00000000`00000000
BiosVersion = 1.30
BiosReleaseDate = 08/19/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060912-16536-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat Jun  9 16:50:43.539 2012 (UTC - 4:00)
System Uptime: 0 days 6:46:33.459
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+7271 )
BUGCHECK_STR:  0x1a_31
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MOM.exe
FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+7271
Bugcheck code 0000001A
Arguments 00000000`00000031 fffffa80`096282d0 fffff880`07ec4000 fffff8a0`0399ac68
BiosVersion = 1.30
BiosReleaseDate = 08/19/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060612-16224-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed Jun  6 12:52:54.055 2012 (UTC - 4:00)
System Uptime: 0 days 21:39:33.601
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1d1
Bugcheck code 0000000A
Arguments fffff6fc`50155dd0 00000000`00000000 00000000`00000000 fffff800`02c72b6b
BiosVersion = 1.30
BiosReleaseDate = 08/19/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060512-20997-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun  5 15:09:46.101 2012 (UTC - 4:00)
System Uptime: 0 days 2:01:23.020
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355e4 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`03c427b0 00000000`0000ffff 00000000`00000000
BiosVersion = 1.30
BiosReleaseDate = 08/19/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060512-14632-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun  5 13:07:26.951 2012 (UTC - 4:00)
System Uptime: 0 days 2:56:42.870
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )
BUGCHECK_STR:  0x4E_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d
Bugcheck code 0000004E
Arguments 00000000`00000002 00000000`0016d8d6 00000000`001fefff 00000000`00000001
BiosVersion = 1.30
BiosReleaseDate = 08/19/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060512-16270-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun  5 10:09:46.671 2012 (UTC - 4:00)
System Uptime: 0 days 2:28:46.201
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Vid.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1d1
Bugcheck code 0000000A
Arguments fffff680`0010b570 00000000`00000000 00000000`00000000 fffff800`02cc7b6b
BiosVersion = 1.30
BiosReleaseDate = 08/19/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060512-22432-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun  5 07:40:24.633 2012 (UTC - 4:00)
System Uptime: 0 days 18:41:22.162
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+7271 )
BUGCHECK_STR:  0x1a_31
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MOM.exe
FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+7271
Bugcheck code 0000001A
Arguments 00000000`00000031 fffffa80`09405c60 fffff880`040c7000 fffff8a0`03184c64
BiosVersion = 1.30
BiosReleaseDate = 08/19/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060412-24445-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon Jun  4 09:04:01.471 2012 (UTC - 4:00)
System Uptime: 0 days 0:09:30.000
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+280 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteFcb+280
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0318c308 fffff880`0318bb60 fffff800`02fe08b0
BiosVersion = 1.30
BiosReleaseDate = 08/19/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060412-24507-01.dmp]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060412-34023-01.dmp]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

moly · 11 Jun 2012

Updated display drivers yesterday. I had to go to toshiba website as the latest AMD drivers wouldn't install and directed me the the manufacturers web site. Was hell installing, must have BSODed at least three times before/during/after update.

Re-ran the memtest overnight after removing one of the sticks. Only 53% though the first pass shows 2990 errors. Leaving it on over night (5 passes) came up with 50000+ errors on one stick. I then too that stick out and put the other in. 3 passes and no errors. Looks like i'll be getting a new stick of RAM first.

I'll run it like this for a little bit, and see how it goes. In the mean time, updating my backups, and looking for gigabyte warranty info.

New Windows_NT6_BSOD_jcgriff2 attached

Thanks for your help.

usasma · 11 Jun 2012

Errors in MemTest = bad RAM or bad slots in the mobo.
Start at Step 6 of my procedure to help rule out the slots.

As long as the memory is spitting errors there's no point in working on the other stuff.
Once the memory errors are fixed, then we can analyze any subsequent errors.
Good luck!