Multiple BSOD Asus laptop

iloveffxi · 28 Jun 2012

Purchased laptop in December from amazon
Was running smooth like a month ago then started having random BSOD once every two or three weeks, did not think much of it then starting yesterday started doing it multiple times a day, 7 times just this morning.

Attacehd is zip file with required information.

Thank you in advance for your help with this matter.

Windows 7 ultimate 64bit

usasma · 28 Jun 2012

5 memory dumps
There were 4 different BSOD error codes cited
and 3 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 (such as Daemon Tools)
- low-level driver problems (such as your ATK 0101 HotKey Utility)
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

You are having issues with your Avast - and there's a problem with your Security Processor Loader.
This is usually indicative of the damage caused by an infection (either one that's on the system, or one that's been removed).

Please perform a couple of these free scans to ensure that the infection(s) are removed: Free Online AntiMalware Resources
If you find an infection present, please post over in the Security forums for more expert assistance in removing it.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

Update your ATK Hotkey ATK0101 ACPI UTILITY as it dates from 2009

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

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:


ASMMAP64.sys     Thu Jul 02 05:13:26 2009 (4A4C7A36)
ETD.sys          Mon Dec 13 08:08:38 2010 (4D061AD6)
GEARAspiWDM.sys  Mon May 18 08:17:04 2009 (4A1151C0)
HECIx64.sys      Tue Oct 19 19:33:43 2010 (4CBE2AD7)
RTKVHD64.sys     Tue Oct 04 06:59:05 2011 (4E8AE6F9)
Rt64win7.sys     Tue Aug 23 09:55:41 2011 (4E53B15D)
SbieDrv.sys      Thu Mar 22 06:14:07 2012 (4F6AFB6F)
TurboB.sys       Fri Apr 16 19:07:26 2010 (4BC8EDAE)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
aswFsBlk.SYS     Tue Mar 06 19:01:31 2012 (4F56A55B)
aswMonFlt.sys    Tue Mar 06 19:01:51 2012 (4F56A56F)
aswSP.SYS        Tue Mar 06 19:04:03 2012 (4F56A5F3)
aswSnx.SYS       Tue Mar 06 19:04:05 2012 (4F56A5F5)
aswTdi.SYS       Tue Mar 06 19:01:56 2012 (4F56A574)
aswrdr2.sys      Tue Mar 06 19:02:19 2012 (4F56A58B)
athrx.sys        Tue Oct 04 02:49:29 2011 (4E8AAC79)
atkwmiacpi64.sys Mon Jul 26 01:56:49 2010 (4C4D23A1)
dtsoftbus01.sys  Fri Jun 17 03:38:37 2011 (4DFB047D)
dump_iaStor.sys  Tue Nov 29 22:39:19 2011 (4ED5A567)
iaStor.sys       Tue Nov 29 22:39:19 2011 (4ED5A567)
igdkmd64.sys     Mon Mar 19 19:31:54 2012 (4F67C1EA)
kbfiltr.sys      Mon Jul 20 05:21:42 2009 (4A643726)
nvlddmkm.sys     Tue May 15 03:35:36 2012 (4FB20748)
nvpciflt.sys     Tue May 15 03:36:26 2012 (4FB2077A)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062812-18236-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 28 03:19:19.630 2012 (UTC - 4:00)
System Uptime: 0 days 0:17:47.520
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = K53SV.315
BiosReleaseDate = 09/26/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K53SV
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: 2294
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062812-19765-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 28 02:44:21.918 2012 (UTC - 4:00)
System Uptime: 0 days 0:56:51.808
BugCheck 3B, {c0000005, fffff80002ed0bf9, fffff8800d239f50, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueueApc+69 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  IAStorIcon.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiInsertQueueApc+69
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02ed0bf9 fffff880`0d239f50 00000000`00000000
BiosVersion = K53SV.315
BiosReleaseDate = 09/26/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K53SV
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: 2294
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062812-24726-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 28 00:30:53.114 2012 (UTC - 4:00)
System Uptime: 0 days 1:07:37.378
BugCheck 9F, {3, fffffa80089cea10, fffff80000b9c3d8, fffffa800b5bea10}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : pci.sys
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`089cea10 fffff800`00b9c3d8 fffffa80`0b5bea10
BiosVersion = K53SV.315
BiosReleaseDate = 09/26/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K53SV
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: 2294
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062812-26176-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 28 00:43:59.611 2012 (UTC - 4:00)
System Uptime: 0 days 0:12:09.501
BugCheck A, {48, 2, 1, fffff80002f7834f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f
Bugcheck code 0000000A
Arguments 00000000`00000048 00000000`00000002 00000000`00000001 fffff800`02f7834f
BiosVersion = K53SV.315
BiosReleaseDate = 09/26/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K53SV
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: 2294
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062812-43040-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 28 01:46:31.592 2012 (UTC - 4:00)
System Uptime: 0 days 1:01:34.857
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = K53SV.315
BiosReleaseDate = 09/26/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K53SV
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: 2294
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

iloveffxi · 28 Jun 2012

Thank you for taking time to help me with this issue.
Laptop is running stock settings since I've purchased it and did not attempt to overclock it.

I performed free online security scans as you have suggested and go no threats detected.

I also uninstalled Daemon tools and made sure sptd.sys driver was removed as well.

So far have had 3 more BSOD and looking for update for ATK Hotkey ATK0101 ACPI UTILITY. While i continue trying to find newer version of it i am uploading new files.

Thank you again for your help.

usasma · 28 Jun 2012

Do you recall removing any viruses from the system recently?

Next step is to run Driver Verifier. Please use these instructions: Driver Verifier Settings

Depending on the results of Driver Verifier, I may suggest a Windows reinstall. For this you'll need your recovery disks (because I'll ask you to wipe the hard drive clean first), and you'll have to have all your stuff backed up (since the hard drive will be wiped).

I'm also getting symbol errors from the debugger, could you please run this procedure: Windows Genuine and Activation Issue Posting Instructions. Post the results in your next post; do not start a new thread.