BSOD at random times.

[evan88]

This problem started July 2010 I believe. I get random blue screens even if no programs are running.

ASUS Notebook N61Jq
-x64
-Original OS installed on system
-OEM
-Bought system in Feb. 2010 from Newegg
- OS has not been reinstalled

Drinks on me if you guys can help me figure this out. Thanks in advance!

 

[Jonathan_King]

A quick glance at your dumps suggests a hardware error. One of the dumps was a 0x124, so see this article: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Test your CPU: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Test your hard drive: HD Diagnostic

A bit deeper look reveals the presence of Daemon Tools Lite, which is using the driver SPTD.sys. SPTD is known for causing BSODs, even 0x124 ones. I would therefore remove Daemon Tools, and then uninstall SPTD with this tool: HD Diagnostic

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 24 19:24:15.393 2010 (UTC - 4:00)
System Uptime: 0 days 1:05:07.454
BugCheck 124, {4, fffffa8004bc8038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_4
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 24 17:08:37.761 2010 (UTC - 4:00)
System Uptime: 0 days 1:16:26.822
BugCheck 1A, {41790, fffffa8000cc60f0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  SkypeNames2.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 23:26:00.660 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:45.721
BugCheck 50, {76f00000, 0, fffff8000309d6d7, 8}
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BUGCHECK_STR:  0x50
PROCESS_NAME:  consent.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 02:34:38.550 2010 (UTC - 4:00)
System Uptime: 0 days 1:06:41.612
BugCheck 3B, {c0000005, fffff800030c81c1, fffff8800a72f010, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeRemoveQueueEx+301 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 27 21:59:44.154 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:22.216
BugCheck 24, {1904fb, fffff880059425d8, fffff88005941e40, fffff800030b0bb3}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 27 21:51:38.277 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:34.339
BugCheck 50, {fffff6fc5505fc38, 0, fffff800030dd018, 2}
Probably caused by : memory_corruption ( nt!MiLockProtoPoolPage+38 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[ttran]

I suspect the Ram.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Please do a disk check, then hard drive diagnostic (Download from manufacture site):
http://www.sevenforums.com/tutorials/433-disk-check.html
HD Diagnostic

Have you overclocked anything? If so, reset it to default setting.
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

Please update these out of date drivers:

fffff880`04fef000 fffff880`04ff8000   Afc      Afc.sys      Wed Jul 12 12:48:20 2006 (44B48D24) 
[COLOR=Blue]Arcsoft(R) ASPI Shell (CD/DVD program)[/COLOR]
fffff880`0608f000 fffff880`06096000   ASMMAP64 ASMMAP64.sys Mon Feb 05 02:52:56 2007 (45C63998)
[COLOR=Blue]LENOVO ATK0101 ACPI UTILITY[/COLOR]
fffff880`03dda000 fffff880`03de2a80   sncduvc  sncduvc.SYS  Mon Dec 29 16:14:26 2008 (495894F2)
[COLOR=Blue]Suyin USB 2.0 Webcam driver[/COLOR]

if all of those doesn't help, try this:

Third party antivirus software are notorious for casuing BSOD and mcafee is not an exception. I would suggest to remove it for testing, then try Microsoft Security essential for protection and make sure firewall is on.
How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)
http://www.microsoft.com/security_essentials

Let us know if you need help

Tuan

 

[evan88]

Actions taken:

-Removed McAfee
-Removed Daemon Tools
-Installed MSE

----------------------

I was going to update the drivers before I ran those tests. Where can I find them? They are not in Device Manager. Thanks.

 

[Jonathan_King]

Hold off on the old drivers for now in favor of the tests. When the tests are complete, update the drivers by installing the latest drivers from the manufacturer's site.

 

[evan88]

Ok, I burned the Memtest86 ISO to a disk and tried to boot from it. When I select the disk during startup, the screen goes black for a few seconds and just logs on to windows normally.

 

[Jonathan_King]

Did you use ISO Recorder to burn the ISO, or did you drag the file to a CD and burn it?

You may also try a USB drive. See this article: Memory Diagnostics

 

[evan88]

Memtest

I didn't realize the memory test took so long to do. I let it go for an hour, but I needed to send some e-mails out. I have attached a picture of it as I am not sure if/where a log is kept. I imagine all those errors are not a good thing...

 

[ttran]

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot, or compatibility between different stick of rams. Test the sticks individually, and if you find a good one, test it in all slots.

 

[zigzag3143]

I didn't realize the memory test took so long to do. I let it go for an hour, but I needed to send some e-mails out. I have attached a picture of it as I am not sure if/where a log is kept. I imagine all those errors are not a good thing...

You need no more testing. Just look at the number of errors display on the screen in your snip. That stick is bad. If you have more than one stick in I would test them separately.