BSOD after virus?

[harpagornis]

I got an virus via a mail and now I get BSOD's. I don't know if this is related.
I couldn't do a System Health report but I have lots of minidumps. View attachment 139553
I have Windows 7 64 bit Retail. Hardware is 1,5 year old. Except for harddisk 3 years.

What I did so far:

Cleaned the virus
Checked memory with windows.
Checked system HD c:\
Checked windows services and startup items
Though I can't find anything. :shock:
Updated drivers

Thanks in advance!

 

[usasma]

39 memory dumps over 8 days (one lone dump from Jan 31 - not analyzed)
7 different BSOD error codes
7 different causes blamed.
This is most likely a hardware problem, but it can be caused by lower level drivers or compatibility issues also.

Please uninstall Daemon Tools. It has a troublesome driver (sptd.sys) that causes BSOD's.
Once it's uninstalled, please use this free tool to remove the troublesome sptd.sys driver: DuplexSecure - FAQ - Remove 64 bit sptd.sys

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:

[FONT=lucida console]
AVGIDSEH.Sys     Mon Sep 13 18:46:38 2010 (4C8EA9CE)
AtiPcie.sys      Tue May 05 11:00:22 2009 (4A005486)
avgrkx64.sys     Mon Sep 06 20:49:37 2010 (4C858C21)
avgmfx64.sys     Mon Sep 06 20:49:14 2010 (4C858C0A)
vpcnfltr.sys     Wed Jul 22 18:20:17 2009 (4A6790A1)
avgtdia.sys      Fri Nov 12 06:08:42 2010 (4CDD203A)
vpcvmm.sys       Wed Jul 22 18:20:22 2009 (4A6790A6)
SASKUTIL64.SYS   Tue Feb 09 17:27:34 2010 (4B71E156)
SASDIFSV64.SYS   Mon Feb 08 19:11:52 2010 (4B70A848)
ElbyCDIO.sys     Tue Feb 17 12:11:23 2009 (499AEFBB)
Rt64win7.sys     Thu Mar 04 08:42:52 2010 (4B8FB8DC)
mcdbus.sys       Tue Feb 24 05:34:07 2009 (49A3CD1F)
vpcusb.sys       Wed Jul 22 18:20:23 2009 (4A6790A7)
usbrpm.sys       Mon Jul 13 20:35:14 2009 (4A5BD2C2)
vpchbus.sys      Wed Jul 22 18:20:23 2009 (4A6790A7)
[COLOR=Red]ElbyCDFL.sys     Thu Dec 14 16:22:27 2006 (4581C093)[/COLOR]
usbfilter.sys    Tue Dec 22 03:26:22 2009 (4B3082AE)
AtiHdmi.sys      Wed Nov 18 18:25:33 2009 (4B04826D)
AVGIDSFilter.Sys Tue Aug 03 18:23:21 2010 (4C5896D9)
RTKVHD64.sys     Tue Jul 06 06:05:16 2010 (4C32FFDC)
000.fcl          Fri Sep 26 09:11:22 2008 (48DCDF7A)
AVGIDSDriver.Sys Tue Aug 03 18:24:45 2010 (4C58972D)
AODDriver2.sys   Thu Apr 22 06:28:05 2010 (4BD024B5)
atikmpag.sys     Tue Jan 04 21:19:38 2011 (4D23D53A)
mbam.sys         Thu Dec 16 15:53:16 2010 (4D0A7C3C)
atikmdag.sys     Tue Jan 04 21:48:52 2011 (4D23DC14)
pbfilter.sys     Mon Sep 28 02:02:08 2009 (4AC05160)
avgtdia.sys      Thu Jun 03 17:09:57 2010 (4C081A25)
avgmfx64.sys     Sun Apr 25 17:06:15 2010 (4BD4AEC7)
avgldx64.sys     Thu Jun 03 17:06:48 2010 (4C081968)
[/FONT]

http://www.carrona.org/dvrref.html#AVGIDSEH.Sys
http://www.carrona.org/dvrref.html#AtiPcie.sys
http://www.carrona.org/dvrref.html#avgrkx64.sys
http://www.carrona.org/dvrref.html#avgmfx64.sys
http://www.carrona.org/dvrref.html#vpcnfltr.sys
http://www.carrona.org/dvrref.html#avgtdia.sys
http://www.carrona.org/dvrref.html#vpcvmm.sys
http://www.carrona.org/dvrref.html#ElbyCDIO.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#mcdbus.sys
http://www.carrona.org/dvrref.html#vpcusb.sys
http://www.carrona.org/dvrref.html#usbrpm.sys
http://www.carrona.org/dvrref.html#vpchbus.sys
http://www.carrona.org/dvrref.html#ElbyCDFL.sys
http://www.carrona.org/dvrref.html#usbfilter.sys
http://www.carrona.org/dvrref.html#AtiHdmi.sys
http://www.carrona.org/dvrref.html#AVGIDSFilter.Sys
http://www.carrona.org/dvrref.html#RTKVHD64.sys
http://www.carrona.org/dvrref.html#000.fcl
http://www.carrona.org/dvrref.html#AVGIDSDriver.Sys
http://www.carrona.org/dvrref.html#avgldx64.sys
http://www.carrona.org/dvrref.html#atikmpag.sys
http://www.carrona.org/dvrref.html#atikmdag.sys
http://www.carrona.org/dvrref.html#pbfilter.sys
http://www.carrona.org/dvrref.html#avgtdia.sys
http://www.carrona.org/dvrref.html#avgmfx64.sys
http://www.carrona.org/dvrref.html#avgldx64.sys

Please do the following:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 00:07:25.438 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:10.874
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04a94038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 20 19:44:44.219 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:59.905
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02ee72b3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 20 19:30:00.875 2011 (UTC - 5:00)
System Uptime: 0 days 10:40:36.311
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02edd2b3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 13:04:08.149 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:08.834
*** WARNING: Unable to verify timestamp for AVGIDSDriver.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.Sys
Probably caused by : AVGIDSDriver.Sys ( AVGIDSDriver+96dc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0xA_AVGIDSDriver+96dc
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02e922b3
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 12:54:23.642 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:17.078
Probably caused by : hardware ( nt!ExfWakePushLock+150 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02e70000 00000000`00000000 00000000`0000228c
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 12:51:21.567 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:19.253
BugCheck F7, {2b99085c8620, 2b992ddfa232, ffffd466d2205dcd, 0}
Probably caused by : msrpc.sys ( msrpc!_report_gsfailure+26 )
DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
BUGCHECK_STR:  0xF7
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0xF7_MISSING_GSFRAME_msrpc!_report_gsfailure+26
Bugcheck code 000000F7
Arguments 00002b99`085c8620 00002b99`2ddfa232 ffffd466`d2205dcd 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 12:25:37.633 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:45.319
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+20d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  tracerpt.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiCommitThreadWait+20d
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02e869cd 00000000`00000000 ffffffff`ffffffff
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 12:12:45.992 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:38.678
Probably caused by : ntkrnlmp.exe ( nt!ObpDeleteNameCheck+2a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpDeleteNameCheck+2a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`031b699a fffff880`09f0ecf0 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 12:09:19.119 2011 (UTC - 5:00)
System Uptime: 0 days 0:14:22.555
*** WARNING: Unable to verify timestamp for AVGIDSDriver.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.Sys
Probably caused by : AVGIDSDriver.Sys ( AVGIDSDriver+15db2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID:  X64_0xA_AVGIDSDriver+15db2
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02e9a2b3
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 11:54:13.051 2011 (UTC - 5:00)
System Uptime: 0 days 0:14:10.487
Probably caused by : ntkrnlmp.exe ( nt!KiApcInterrupt+1f1 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiApcInterrupt+1f1
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02e67591 00000000`00000000 ffffffff`ffffffff
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 05:58:08.266 2011 (UTC - 5:00)
System Uptime: 0 days 12:19:50.952
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  schtasks.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiTryUnwaitThread+28
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02ec1cd8 00000000`00000000 ffffffff`ffffffff
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 17:37:08.255 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:40.941
BugCheck F7, {2b990a0ca420, 2b992ddfa232, ffffd466d2205dcd, 0}
Probably caused by : msrpc.sys ( msrpc!_report_gsfailure+26 )
DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
BUGCHECK_STR:  0xF7
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  X64_0xF7_MISSING_GSFRAME_msrpc!_report_gsfailure+26
Bugcheck code 000000F7
Arguments 00002b99`0a0ca420 00002b99`2ddfa232 ffffd466`d2205dcd 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 17:33:30.482 2011 (UTC - 5:00)
System Uptime: 0 days 0:45:36.918
BugCheck D1, {fffff88009886748, 2, 0, fffff88000faec50}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeLogCrbActive+bc
Bugcheck code 000000D1
Arguments fffff880`09886748 00000000`00000002 00000000`00000000 fffff880`00faec50
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 16:20:37.404 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:28.089
BugCheck D1, {fffff88006ef43f8, 2, 0, fffff8800111ac50}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  SMSvcHost.exe
FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeLogCrbActive+bc
Bugcheck code 000000D1
Arguments fffff880`06ef43f8 00000000`00000002 00000000`00000000 fffff880`0111ac50
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 16:16:58.194 2011 (UTC - 5:00)
System Uptime: 0 days 0:14:17.630
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiTryUnwaitThread+28
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02e83cd8 00000000`00000000 ffffffff`ffffffff
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 15:44:16.173 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:22.859
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiTryUnwaitThread+28
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02e8fcd8 fffff880`0807aab0 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 15:17:41.386 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:41.072
Probably caused by : ntkrnlmp.exe ( nt!ObpDeleteNameCheck+2a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpDeleteNameCheck+2a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0318499a fffff880`0962dcf0 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 10:51:48.388 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:44.074
BugCheck F7, {2b99098f2420, 2b992ddfa232, ffffd466d2205dcd, 0}
Probably caused by : msrpc.sys ( msrpc!_report_gsfailure+26 )
DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
BUGCHECK_STR:  0xF7
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  X64_0xF7_MISSING_GSFRAME_msrpc!_report_gsfailure+26
Bugcheck code 000000F7
Arguments 00002b99`098f2420 00002b99`2ddfa232 ffffd466`d2205dcd 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 10:35:49.058 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:44.759
Probably caused by : ntkrnlmp.exe ( nt!IoBoostThreadIoPriority+2ed )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!IoBoostThreadIoPriority+2ed
Bugcheck code 0000000A
Arguments 00000000`00000022 00000000`00000002 00000000`00000000 fffff800`02e0a36d
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 10:20:41.530 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:00.030
Probably caused by : ntkrnlmp.exe ( nt!KiApcInterrupt+1f1 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiApcInterrupt+1f1
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`020b4591 00000000`00000000 ffffffff`ffffffff
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 10:18:59.386 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:12.072
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  reg.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02eab448 fffff880`07d93ab0 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 10:15:18.090 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:29.526
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+1d5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  reg.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+1d5
Bugcheck code 0000000A
Arguments 00000000`00000090 00000000`00000002 00000000`00000000 fffff800`02ed6995
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 10:05:40.146 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:20.582
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`02e59d19
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 09:38:51.916 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:42.352
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  find.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiTryUnwaitThread+28
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02e7ecd8 fffff880`096ede40 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 06:53:50.627 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:49.250
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiTryUnwaitThread+28
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02ec7cd8 00000000`00000000 ffffffff`ffffffff
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 05:20:19.263 2011 (UTC - 5:00)
System Uptime: 0 days 0:04:47.012
BugCheck D1, {fffff8800869f6f8, 2, 0, fffff88000fc7c50}
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeLogCrbActive+bc
Bugcheck code 000000D1
Arguments fffff880`0869f6f8 00000000`00000002 00000000`00000000 fffff880`00fc7c50
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 05:14:50.460 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:09.068
Probably caused by : ntkrnlmp.exe ( nt!CcAcquireByteRangeForWrite+5e2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!CcAcquireByteRangeForWrite+5e2
Bugcheck code 00000050
Arguments ffffffff`fffffff0 00000000`00000000 fffff800`02ec5771 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 05:12:49.757 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:52.380
Probably caused by : win32k.sys ( win32k!MultiUserGreCleanupHmgOwnRemoveAllLocks+5c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!MultiUserGreCleanupHmgOwnRemoveAllLocks+5c
Bugcheck code 0000000A
Arguments 00000000`000001b0 00000000`00000002 00000000`00000001 fffff800`02e93cd8
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 04:50:41.254 2011 (UTC - 5:00)
System Uptime: 0 days 0:04:44.612
BugCheck D1, {fffff880027e46f8, 2, 0, fffff88000fd0c50}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeLogCrbActive+bc
Bugcheck code 000000D1
Arguments fffff880`027e46f8 00000000`00000002 00000000`00000000 fffff880`00fd0c50
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 04:31:40.646 2011 (UTC - 5:00)
System Uptime: 0 days 10:52:22.253
Probably caused by : ntkrnlmp.exe ( nt!ObpDeleteNameCheck+2a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  conhost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpDeleteNameCheck+2a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0317199a fffff880`08e7ecf0 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Feb 15 17:38:10.012 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:52.620
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02ee82b3
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Feb 15 17:23:36.596 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:13.219
Probably caused by : fltmgr.sys ( fltmgr!FltpProcessOperationStatusCallbacks+2d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  conhost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_fltmgr!FltpProcessOperationStatusCallbacks+2d
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff880`00fb95dd 00000000`00000000 00000000`00000200
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb 14 17:00:38.804 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:12.240
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  avgtray.exe
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`02cafd29
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb 14 16:48:38.014 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:38.763
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`020ea2b3
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb 14 16:46:06.810 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:58.560
Probably caused by : ntkrnlmp.exe ( nt!KiApcInterrupt+1f1 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiApcInterrupt+1f1
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`0206a5a1 00000000`00000000 ffffffff`ffffffff
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb 14 16:43:08.608 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:39.309
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
Bugcheck code 0000000A
Arguments 00000000`67060009 00000000`00000002 00000000`00000001 fffff800`02cac44b
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb 14 16:10:03.211 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:01.961
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  AtBroker.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiDispatchException+1b9
Bugcheck code 0000001E
Arguments ffffffff`c0000005 00000001`0233002d 00000000`00000008 00000001`0233002d
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb 14 16:07:15.015 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:49.451
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`02cb2d29
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb 14 15:47:33.901 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:38.603
BugCheck D1, {fffff88007a193f8, 2, 0, fffff8800116dc50}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeLogCrbActive+bc
Bugcheck code 000000D1
Arguments fffff880`07a193f8 00000000`00000002 00000000`00000000 fffff880`0116dc50
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

http://www.carrona.org/dvrref.html#avgldx64.sys

 

[DeanP]

I'd remove AVG including Identity Protection if I was you. It is a known cause of BSOD on some Windows 7 Systems. Use this AVG removal tool when it is removed: AVG - Download tools

I do not recommend that you install AVG again.

If you want a free AV, try: MSE OR Avast
If you want a paid AV, try: Avast

 

[harpagornis]

I'm grateful for your help.

What I've done so far:
- Removed Deamon tools and Deamon driver
- Removed AVG (thx DeanP), installed Avast (and ran a Bootscan)
- Checked all listed drivers and updated them (except for Windows)
- Ran Hardware Diagnostics and no faults were found

BSOD's happen mostly at startup.
I set Bios on fail/safe profile.

Should I run some other Hardware Diagnostics?
Can the memory Timings be a problem?
I do have other compatible Memory.

Thanks in advance!

 

[DeanP]

Run chkdsk for at least 3 times in elevated command prompt.

I'd run Memtest86+ for at least 7 passes.

 

[harpagornis]

Ok. I'll do that. What do you mean with elevated? Should I run chkdsk in Windows 7?

 

[DeanP]

Elevated Command Prompt - Command Prompt in Admin Mode
Yes, chkdsk in Windows 7. (at least 3 times)

 

[usasma]

Here's a long laundry list of things to try when isolating hardware issues:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

and here's some more free stress tests. This is a DRAFT of my discussion about Prime95:

DRAFT Prime95 testing procedure
This is in case you are getting errors in Prime95 and want to nail down the cause

Run HDD diag and MemTest prior to Prime95

Run Blend test
Run Inplace Large FFT's test
Run Small FFT's test

Run CPU Stress Tests
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld - PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface - XtremeSystems Forums

Run Video Stress Tests
- FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
- МИРNVIDIA / Утилиты / VMT
- МИРNVIDIA / Утилиты / Artifact Locator

Swap RAM sticks around per Steps 7 through 10 of this link and run Prime95 (in Blend mode) on each stick/slot: Memory Diagnostics
This is because of issues found in this topic: http://www.sevenforums.com/crashes-debugging/124155-blue-screens-again-2.html#post1076674
************************
DISCUSSION:
Small FFT's test CPU cache and very little memory.
Large FFT's access' a lot of memory - but in-place option keeps it limited
Blend is not run in-place, so it cycles the tests through a lot of RAM

All tests stress the CPU
In-place large FFT's and Blend also test CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- This would then be testing the memory controller onboard the CPU in the Athlon64 and i-series processors
In-place large FFT's stress CPU more than Blend
MemTest is better at testing RAM

Prime 95 tests 3 things:
- Memory
- CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- CPU

FWIW - the distinction between RAM and different types of memory in the system is one that I've made. The documentation that I've read speaks of RAM issues and CPU cache - and doesn't mention the other aspects. BUT, this is just speculation on my part, so we'll have to see how it works for us.
Link to explanation about i-series CPU/RAM interface: Intel Core - Wikipedia, the free encyclopedia

Common features of all Nehalem based processors include an integrated DDR3 memory controller as well as QuickPath Interconnect or PCI Express and Direct Media Interface on the processor replacing the aging quad-pumped Front Side Bus used in all earlier Core processors.

 

[harpagornis]

chkdsk

Elevated Command Prompt - Command Prompt in Admin Mode
Yes, chkdsk in Windows 7. (at least 3 times)

I did try an elevated Chkskd /f /r. Windows says the drive is locked? So had to run it from boot.

I need to say I already did lots of chkdsk's. Only not elevated.

Still running chkdsk however...

 

[harpagornis]

@Usama Can the PSU be the culprit?

 

[usasma]

Don't go buying anything yet, but here's some PSU suggestions:
- get a PSU tester ($10-15 US) - not 100% effective
- remove all power sapping devices (disconnect unneeded devices (such as CD/DVD ROM, spare hard drives, and case fans) - use a house fan to take the place of the case fans (with the case open).
- buy a new power supply from a place that will allow you to return it. Then try the new one out.

We'll have to see some more BSOD memory dumps to draw further conclusions.

 

[harpagornis]

shut down external video card

Shut down external video card in bios. Now using onboard video. BSOD's seem to be gone. Will run Windows for another day and shall then continue.

Shall I focus on Video card diagnosing or shall I disconnect some unneeded devices and focus on PSU?

 

[usasma]

Only change one thing at a time - that way any changes in the systems behavior can be attributed to the one thing that you changed.

For example, if switching to the onboard video stops the BSOD's - then it's obvious that the discreet video card is the problem BUT only if the BSOD's are truly stopped.

So, try video stress tests now and see if the onboard video can ride them out. Then put the discrete video card back in and try the same stress tests - does that throw BSOD's?

 

[harpagornis]

BSOD's have stopped for sure now. I was thinking how to tackle the problem.

I will carry out the video stress tests. Thank you for your advice!

 

[harpagornis]

BSOD's came back after I tried to run on onboard video. And I realised that I never actually turned off the onboard video. I saw both video adapters in device manager.

Eventually I did manage to turn it off 785GM-E51 vga problem
Though I still have the BSOD's occasionally.

Maybe you can have a look at the BSOD's
I guess they are still random View attachment 140628

 

[usasma]

So, this set of dumps looks to be hardware related. Looking at your links to the MSI forum, it appears that they also have some question about the motherboard or PSU.

Test with onboard video - and uninstall discrete video software/drivers and remove the card from the machine.
Then test with discrete video software/drivers and card - and ensure that onboard video is disabled in the BIOS and doesn't show in Device Manager.

Test with video stress test such as Furmark.

14 memory dumps over a 2 day period
8 different BSOD error codes
5 different causes are blamed
That says hardware to me.

Please run Driver Verifier according to these directions. I don't suspect that it'll tell us much, but it will help to confirm that this is a hardware error:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system.
Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:

[FONT=lucida console]
amdxata.sys    Tue May 19 13:56:59 2009 (4A12F2EB)
AtiPcie.sys    Tue May 05 11:00:22 2009 (4A005486)
vpcvmm.sys     Wed Jul 22 18:20:22 2009 (4A6790A6)
SASKUTIL64.SYS Tue Feb 09 17:27:34 2010 (4B71E156)
SASDIFSV64.SYS Mon Feb 08 19:11:52 2010 (4B70A848)
vpcnfltr.sys   Wed Jul 22 18:20:17 2009 (4A6790A1)
mcdbus.sys     Tue Feb 24 05:34:07 2009 (49A3CD1F)
amdiox64.sys   Thu Feb 18 10:17:53 2010 (4B7D5A21)
vpcusb.sys     Wed Jul 22 18:20:23 2009 (4A6790A7)
usbrpm.sys     Mon Jul 13 20:35:14 2009 (4A5BD2C2)
vpchbus.sys    Wed Jul 22 18:20:23 2009 (4A6790A7)
Rt64win7.sys   Thu Mar 04 08:42:52 2010 (4B8FB8DC)
usbfilter.sys  Tue Dec 22 03:26:22 2009 (4B3082AE)
RTKVHD64.sys   Tue Jul 06 06:05:16 2010 (4C32FFDC)
000.fcl        Fri Sep 26 09:11:22 2008 (48DCDF7A)
msibios64.sys  Tue Dec 09 22:35:05 2008 (493F38E9)
pbfilter.sys   Mon Sep 28 02:02:08 2009 (4AC05160)
FLASHSYS64.sys Fri Feb 15 03:00:23 2008 (47B54697)
AtiHdmi.sys    Wed Nov 18 18:25:33 2009 (4B04826D)
AODDriver2.sys Thu Apr 22 06:28:05 2010 (4BD024B5)
[/FONT]

http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#AtiPcie.sys
http://www.carrona.org/dvrref.html#vpcvmm.sys
http://www.carrona.org/dvrref.html#SASKUTIL64.SYS
http://www.carrona.org/dvrref.html#SASDIFSV64.SYS
http://www.carrona.org/dvrref.html#vpcnfltr.sys
http://www.carrona.org/dvrref.html#atikmpag.syshttp://www.carrona.org/dvrref.html#AtihdW76.syshttp://www.carrona.org/dvrref.html#mcdbus.sys
http://www.carrona.org/dvrref.html#amdiox64.sys
http://www.carrona.org/dvrref.html#vpcusb.sys
http://www.carrona.org/dvrref.html#usbrpm.sys
http://www.carrona.org/dvrref.html#vpchbus.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#usbfilter.sys
http://www.carrona.org/dvrref.html#RTKVHD64.sys
http://www.carrona.org/dvrref.html#000.fcl
http://www.carrona.org/dvrref.html#msibios64.sys
http://www.carrona.org/dvrref.html#pbfilter.sys
http://www.carrona.org/dvrref.html#FLASHSYS64.sys
http://www.carrona.org/dvrref.html#mbam.syshttp://www.carrona.org/dvrref.html#AtiHdmi.sys
http://www.carrona.org/dvrref.html#AODDriver2.sys
http://www.carrona.org/dvrref.html#aswRdr.SYS
BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 21:50:54.657 2011 (UTC - 5:00)
System Uptime: 0 days 0:04:11.108
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireScbForLazyWrite+21 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x34
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x34_Ntfs!NtfsAcquireScbForLazyWrite+21
Bugcheck code 00000034
Arguments 00000000`00050830 fffff880`031468e8 fffff880`03146150 fffff880`012e3f99
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 20:52:32.434 2011 (UTC - 5:00)
System Uptime: 0 days 0:04:56.870
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`02e9ed19
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 20:39:13.131 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:12.832
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+1ba )
BUGCHECK_STR:  0x1E_c0000096
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x1E_c0000096_nt!KeStackAttachProcess+1ba
Bugcheck code 0000001E
Arguments ffffffff`c0000096 fffff800`02e570ea 00000000`00000000 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 20:35:51.287 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:49.723
Probably caused by : win32k.sys ( win32k!TraceGreAcquireSemaphoreShared+b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!TraceGreAcquireSemaphoreShared+b
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02ef72b3
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 20:25:22.391 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:17.843
BugCheck FC, {fffff8800727ec20, 800000007cb37963, fffff8800727e5c0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40a25 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+40a25
Bugcheck code 000000FC
Arguments fffff880`0727ec20 80000000`7cb37963 fffff880`0727e5c0 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 20:23:16.588 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:42.039
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`02e5dd19
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 20:18:44.052 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:49.753
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+1d5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+1d5
Bugcheck code 0000000A
Arguments 00000000`00000090 00000000`00000002 00000000`00000000 fffff800`02e81995
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 20:12:58.643 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:37.017
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`02eb3d19
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 20:08:46.782 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:42.389
BugCheck D1, {fffff88006179748, 2, 0, fffff88000e01c50}
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeLogCrbActive+bc
Bugcheck code 000000D1
Arguments fffff880`06179748 00000000`00000002 00000000`00000000 fffff880`00e01c50
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 20:04:52.622 2011 (UTC - 5:00)
System Uptime: 0 days 21:07:48.548
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )
BUGCHECK_STR:  0x19_22
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x19_22_nt!_??_::FNODOBFM::_string_+72f8
Bugcheck code 00000019
Arguments 00000000`00000022 fffff8a0`05800000 00000000`00000001 00000000`00000000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 24 22:41:36.114 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:13.722
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Sf.bin
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!RtlImageNtHeaderEx+3f
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02e6d7e7 00000000`00000000 00000000`7efa0000
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 24 22:21:16.904 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:13.605
BugCheck D1, {fffff88008f656f8, 2, 0, fffff88000e24c50}
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeLogCrbActive+bc
Bugcheck code 000000D1
Arguments fffff880`08f656f8 00000000`00000002 00000000`00000000 fffff880`00e24c50
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 24 22:17:19.116 2011 (UTC - 5:00)
System Uptime: 0 days 0:57:37.818
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!ExFreePoolWithTag+43
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02ffb0f3 fffff880`02faf8d8 fffff880`02faf140
SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]