Hey all,
I've been on this HP Pavillion running W7 since February, with no BSOD's. Recently, about once a week, I would get the following error after loading up my desktop for a few seconds:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002C91A88
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
I've done some reading and it seems that this might indicate a hardware error?!
I am absolutely terrified of opening my box as I'm extremely clumsy and manage to mess everything up when it comes to hardware. But I do want to fix this problem, especially if it will screw me over later on, or get worse...
I have attached both the Minidump and the system data log in the temp folder.
Many thanks in advance!!
Best wishes,
Pie
I've been on this HP Pavillion running W7 since February, with no BSOD's. Recently, about once a week, I would get the following error after loading up my desktop for a few seconds:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002C91A88
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
I've done some reading and it seems that this might indicate a hardware error?!
I am absolutely terrified of opening my box as I'm extremely clumsy and manage to mess everything up when it comes to hardware. But I do want to fix this problem, especially if it will screw me over later on, or get worse...I have attached both the Minidump and the system data log in the temp folder.
Many thanks in advance!!
Best wishes,
Pie
The dump shows a stop error of A which is a hardware/hardware related error.
The dmp does not point to any specific cause. I will look a little deeper and by right back.
Quote:
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_mini,sysdatadump.zip\072910-30264-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50 Debug session time: Thu Jul 29 18:21:29.443 2010 (GMT-4) System Uptime: 0 days 0:01:17.567 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, fffff80002c91a88} Unable to load image \SystemRoot\system32\drivers\gamingms.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) Followup: MachineOwner --------- 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000000, 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: fffff80002c91a88, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb10e0 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KeReleaseSemaphore+38 fffff800`02c91a88 f00fba2907 lock bts dword ptr [rcx],7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff88003392760 -- (.trap 0xfffff88003392760) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002c91a88 rsp=fffff880033928f0 rbp=0000000000000000 r8=0000000000000002 r9=fffff88006de0500 r10=0000000000000000 r11=fffff88003392ab8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KeReleaseSemaphore+0x38: fffff800`02c91a88 f00fba2907 lock bts dword ptr [rcx],7 ds:0060:00000000`00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c7a469 to fffff80002c7af00 STACK_TEXT: fffff880`03392618 fffff800`02c7a469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`03392620 fffff800`02c790e0 : 00000000`00000000 00000000`00000000 00000000`00006000 fffff880`0587dddb : nt!KiBugCheckDispatch+0x69 fffff880`03392760 fffff800`02c91a88 : fffffa80`0aac7b98 fffffa80`0aac7a10 00000000`00000000 fffffa80`0aac7050 : nt!KiPageFault+0x260 fffff880`033928f0 fffff880`06ddffdd : 00000000`00000001 fffffa80`00000000 fffffa80`0c97a700 fffffa80`0aa92e00 : nt!KeReleaseSemaphore+0x38 fffff880`03392970 00000000`00000001 : fffffa80`00000000 fffffa80`0c97a700 fffffa80`0aa92e00 00000000`00000000 : gamingms+0xfdd fffff880`03392978 fffffa80`00000000 : fffffa80`0c97a700 fffffa80`0aa92e00 00000000`00000000 fffff800`02e08880 : 0x1 fffff880`03392980 fffffa80`0c97a700 : fffffa80`0aa92e00 00000000`00000000 fffff800`02e08880 00000000`00000000 : 0xfffffa80`00000000 fffff880`03392988 fffffa80`0aa92e00 : 00000000`00000000 fffff800`02e08880 00000000`00000000 00000000`00000000 : 0xfffffa80`0c97a700 fffff880`03392990 00000000`00000000 : fffff800`02e08880 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0aa92e00 STACK_COMMAND: kb FOLLOWUP_IP: gamingms+fdd fffff880`06ddffdd ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: gamingms+fdd FOLLOWUP_NAME: MachineOwner MODULE_NAME: gamingms IMAGE_NAME: gamingms.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4b064c89 FAILURE_BUCKET_ID: X64_0xA_gamingms+fdd BUCKET_ID: X64_0xA_gamingms+fdd Followup: MachineOwner --------- 7: kd> lmtsmn start end module name fffff880`0550e000 fffff880`0554c000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`01000000 fffff880`01057000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`04750000 fffff880`047da000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`05f80000 fffff880`05f96000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`0144c000 fffff880`01457000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`06d69000 fffff880`06d8b000 AtiHdmi AtiHdmi.sys Tue Mar 09 05:08:38 2010 (4B961E26) fffff880`04e64000 fffff880`0550e000 atikmdag atikmdag.sys Tue Apr 20 00:58:51 2010 (4BCD348B) fffff880`04a1e000 fffff880`04a54000 atikmpag atikmpag.sys Mon Apr 19 23:23:12 2010 (4BCD1E20) fffff960`00870000 fffff960`008d1000 ATMFD ATMFD.DLL unavailable (00000000) fffff880`02e00000 fffff880`02e07000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`04cd3000 fffff880`04dbe000 BHDrvx64 BHDrvx64.sys Tue May 11 20:28:29 2010 (4BE9F62D) fffff880`04cc2000 fffff880`04cd3000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`05772000 fffff880`05790000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff880`04c26000 fffff880`04cc2000 ccHPx64 ccHPx64.sys Fri Feb 05 16:05:45 2010 (4B6C8829) fffff960`00710000 fffff960`00737000 cdd cdd.dll unavailable (00000000) fffff880`0445c000 fffff880`04486000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00c00000 fffff880`00cc0000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`00e00000 fffff880`00e30000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00d23000 fffff880`00d81000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00d81000 fffff880`00df4000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`05f70000 fffff880`05f80000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`063d9000 fffff880`063e7000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`06375000 fffff880`063b2000 CT20XUT CT20XUT.SYS Mon Jul 13 13:36:20 2009 (4A5B7094) fffff880`0554c000 fffff880`055f4880 ctaud2k ctaud2k.sys Mon Jul 13 13:35:01 2009 (4A5B7045) fffff880`06c05000 fffff880`06d69000 CTEXFIFX CTEXFIFX.SYS Mon Jul 13 13:36:14 2009 (4A5B708E) fffff880`06a00000 fffff880`06a1c000 CTHWIUT CTHWIUT.SYS Mon Jul 13 13:36:24 2009 (4A5B7098) fffff880`05f24000 fffff880`05f55000 ctoss2k ctoss2k.sys Mon Jul 13 13:30:53 2009 (4A5B6F4D) fffff880`05f55000 fffff880`05f5d000 ctprxy2k ctprxy2k.sys Mon Jul 13 13:35:03 2009 (4A5B7047) fffff880`06bbd000 fffff880`06bf5000 ctsfm2k ctsfm2k.sys Mon Jul 13 13:30:29 2009 (4A5B6F35) fffff880`04a00000 fffff880`04a1e000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`04bd6000 fffff880`04be5000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01600000 fffff880`01616000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`04e3d000 fffff880`04e5f000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`063e7000 fffff880`063fa000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`0422b000 fffff880`04433000 dump_iaStor dump_iaStor.sys Fri Oct 02 15:58:50 2009 (4AC65B7A) fffff880`06da8000 fffff880`06db4000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`058ee000 fffff880`059e2000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`05800000 fffff880`05846000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`04b3b000 fffff880`04bb1000 eeCtrl64 eeCtrl64.sys Fri May 21 17:44:45 2010 (4BF6FECD) fffff880`0632b000 fffff880`06375000 emupia2k emupia2k.sys Mon Jul 13 13:30:18 2009 (4A5B6F2A) fffff880`02fd1000 fffff880`02ff1000 ENG64 ENG64.SYS Thu Jul 01 14:11:13 2010 (4C2CDA41) fffff880`04bb1000 fffff880`04bd6000 EraserUtilRebootDrv EraserUtilRebootDrv.sys Fri May 21 17:44:45 2010 (4BF6FECD) fffff880`02e17000 fffff880`02fd1000 EX64 EX64.SYS Thu Jul 01 14:19:15 2010 (4C2CDC23) fffff880`01511000 fffff880`01525000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`01457000 fffff880`014a3000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`017ee000 fffff880`017f8000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01200000 fffff880`0123a000 fvevol fvevol.sys Mon Jul 13 19:22:15 2009 (4A5BC1A7) fffff880`0188b000 fffff880`018d5000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff880`06ddf000 fffff880`06de1880 gamingms gamingms.sys Fri Nov 20 03:00:09 2009 (4B064C89) fffff880`05f63000 fffff880`05f70000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0) fffff880`06a30000 fffff880`06bbd000 ha20x22k ha20x22k.sys Mon Jul 13 13:34:21 2009 (4A5B701D) fffff800`031e6000 fffff800`0322f000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`05846000 fffff880`0586a000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`0586a000 fffff880`0587b000 HECIx64 HECIx64.sys Thu Sep 17 15:54:16 2009 (4AB293E8) fffff880`063b2000 fffff880`063cb000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`06df0000 fffff880`06df8080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`06de2000 fffff880`06df0000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`056aa000 fffff880`05772000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`019eb000 fffff880`019f4000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`01244000 fffff880`0144c000 iaStor iaStor.sys Fri Oct 02 15:58:50 2009 (4AC65B7A) fffff880`04ac5000 fffff880`04b3b000 IDSvia64 IDSvia64.sys Thu May 27 04:07:18 2010 (4BFE2836) fffff880`04de4000 fffff880`04dfa000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`0450c000 fffff880`04533000 Ironx64 Ironx64.SYS Tue Apr 27 20:48:23 2010 (4BD785D7) fffff880`05e56000 fffff880`05e65000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`063cb000 fffff880`063d9000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bbc000 fffff800`00bc6000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`05ee1000 fffff880`05f24000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`017c3000 fffff880`017dd000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01860000 fffff880`0188b000 ksecpkg ksecpkg.sys Mon Jul 13 19:50:34 2009 (4A5BC84A) fffff880`05f5d000 fffff880`05f62200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`06244000 fffff880`06259000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`06200000 fffff880`06223000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00ccb000 fffff880`00d0f000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`06db4000 fffff880`06dc2000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`05e65000 fffff880`05e74000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`06a1c000 fffff880`06a29000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00f96000 fffff880`00fb0000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`05790000 fffff880`057a8000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`057a8000 fffff880`057d4000 mrxsmb mrxsmb.sys Mon Jul 13 19:23:59 2009 (4A5BC20F) fffff880`05600000 fffff880`0564d000 mrxsmb10 mrxsmb10.sys Mon Jul 13 19:24:08 2009 (4A5BC218) fffff880`0564d000 fffff880`05670000 mrxsmb20 mrxsmb20.sys Mon Jul 13 19:24:05 2009 (4A5BC215) fffff880`045cd000 fffff880`045d8000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`01057000 fffff880`01061000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01560000 fffff880`015be000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`04aba000 fffff880`04ac5000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`019d9000 fffff880`019eb000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`018e7000 fffff880`019d9000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`05fba000 fffff880`05fc6000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`05fc6000 fffff880`05ff5000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`06316000 fffff880`0632b000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`04685000 fffff880`04694000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`04600000 fffff880`04645000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01800000 fffff880`01860000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`045d8000 fffff880`045e9000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`04aae000 fffff880`04aba000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02c09000 fffff800`031e6000 nt ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600) fffff880`01620000 fffff880`017c3000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`02ff1000 fffff880`02ffa000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`0464e000 fffff880`04674000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`011d2000 fffff880`011e7000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00f07000 fffff880`00f3a000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`017dd000 fffff880`017ee000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`076e5000 fffff880`0778b000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`04e00000 fffff880`04e3d000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00d0f000 fffff880`00d23000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`04674000 fffff880`04685000 pssdk42 pssdk42.sys Tue Jun 23 08:11:57 2009 (4A40C68D) fffff880`05f96000 fffff880`05fba000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`05e00000 fffff880`05e1b000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`05e1b000 fffff880`05e3c000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`05e3c000 fffff880`05e56000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`04a5d000 fffff880`04aae000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`045b2000 fffff880`045bb000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`045bb000 fffff880`045c4000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`045c4000 fffff880`045cd000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`015be000 fffff880`015f8000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`06259000 fffff880`06271000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`047da000 fffff880`047f4000 SCDEmu SCDEmu.SYS Mon Apr 12 04:52:25 2010 (4BC2DF49) fffff880`011a3000 fffff880`011d2000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0) fffff880`0778b000 fffff880`07796000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`018d5000 fffff880`018dd000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`01073000 fffff880`0119a000 sptd sptd.sys Wed Apr 07 21:29:00 2010 (4BBD315C) fffff880`04486000 fffff880`0450c000 SRTSP64 SRTSP64.SYS Wed Feb 24 18:59:29 2010 (4B85BD61) fffff880`04533000 fffff880`04547000 SRTSPX64 SRTSPX64.SYS Wed Feb 24 18:59:48 2010 (4B85BD74) fffff880`07850000 fffff880`078e8000 srv srv.sys Mon Jul 13 19:25:11 2009 (4A5BC257) fffff880`07600000 fffff880`07669000 srv2 srv2.sys Mon Jul 13 19:25:02 2009 (4A5BC24E) fffff880`07796000 fffff880`077c3000 srvnet srvnet.sys Mon Jul 13 19:24:58 2009 (4A5BC24A) fffff880`05e74000 fffff880`05e75480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`014a3000 fffff880`01511000 SYMDS64 SYMDS64.SYS Mon Aug 17 19:35:30 2009 (4A89E942) fffff880`01525000 fffff880`01560000 SYMEFA64 SYMEFA64.SYS Wed Apr 21 17:47:39 2010 (4BCF727B) fffff880`04547000 fffff880`0457d000 SYMEVENT64x86 SYMEVENT64x86.SYS Thu Aug 13 18:28:21 2009 (4A849385) fffff880`046da000 fffff880`04750000 SYMTDIV SYMTDIV.SYS Tue May 04 00:38:27 2010 (4BDFA4C3) fffff880`01a03000 fffff880`01c00000 tcpip tcpip.sys Mon Jul 13 19:25:34 2009 (4A5BC26E) fffff880`077c3000 fffff880`077d5000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`0421e000 fffff880`0422b000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`04200000 fffff880`0421e000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`046af000 fffff880`046c3000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00420000 fffff960`0042a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`04dbe000 fffff880`04de4000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`05e76000 fffff880`05e88000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`06dc2000 fffff880`06ddf000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`06da6000 fffff880`06da7f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`0587b000 fffff880`0588c000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`062bc000 fffff880`06316000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`0588c000 fffff880`058e2000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`06d8b000 fffff880`06da6000 USBSTOR USBSTOR.SYS Mon Jul 13 20:06:34 2009 (4A5BCC0A) fffff880`01061000 fffff880`0106e000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`02e07000 fffff880`02e15000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`0457d000 fffff880`045a2000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`011e7000 fffff880`011fc000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00f3a000 fffff880`00f96000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`00fb0000 fffff880`00ffc000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`04694000 fffff880`046af000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`045a2000 fffff880`045b2000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00e54000 fffff880`00ef8000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00ef8000 fffff880`00f07000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`04645000 fffff880`0464e000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`000c0000 fffff960`003cf000 win32k win32k.sys unavailable (00000000) fffff880`0119a000 fffff880`011a3000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`06223000 fffff880`06244000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) fffff880`078e8000 fffff880`07919000 WUDFRd WUDFRd.sys Mon Jul 13 20:06:06 2009 (4A5BCBEE) Unloaded modules: fffff880`00e30000 fffff880`00e3e000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`04241000 fffff880`04449000 dump_iaStor. Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`04449000 fffff880`0445c000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
I suspect your Primax USB Optical Mouse Drivers are the cause. Dated November 2009, I suspect there may be an update.
Code:
Timestamp: Fri Nov 20 03:00:09 2009 (4B064C89)
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_mini,sysdatadump.zip\072910-30264-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50 Debug session time: Thu Jul 29 18:21:29.443 2010 (UTC - 4:00) System Uptime: 0 days 0:01:17.567 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, fffff80002c91a88} Unable to load image \SystemRoot\system32\drivers\gamingms.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) Followup: MachineOwner --------- 7: kd> lmvm gamingms start end module name fffff880`06ddf000 fffff880`06de1880 gamingms T (no symbols) Loaded symbol image file: gamingms.sys Image path: \SystemRoot\system32\drivers\gamingms.sys Image name: gamingms.sys Timestamp: Fri Nov 20 03:00:09 2009 (4B064C89) CheckSum: 00007181 ImageSize: 00002880 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 I would like a full system report to get you some drivers. Please follow these directions: http://www.sevenforums.com/crashes-d...tructions.html
I also find sptd.sys on your system. Although this driver is up to date, I recommend that you 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. Do not reinstall the program untill you have your system running smoothly. I recommed that you not reinstall it at all.
Jonathan pointed your mouse driver. I have found two slightly out of date drivers that you should update.
GEARAspiWDM.sys Mon May 18 08:17:04 2009
pssdk42.sys Tue Jun 23 08:11:57 2009
Jonathan pointed your mouse driver. I have found two slightly out of date drivers that you should update.
GEARAspiWDM.sys Mon May 18 08:17:04 2009
pssdk42.sys Tue Jun 23 08:11:57 2009
Gotcha.
Here's my BSOD report:
W7 x64, original installed, OEM, age of system, 6 months (i7-860, Radeon 4850, 1TB HD, X-Fi). I restored to manufacture default in May after an audio driver fiasco.
Rest is attached.
So, how should I go about getting new drivers for these? I have had some pretty bad experiences in the past (Creative X-Fi driver totally screwed up on me, had no audio for 1 month, then had to restore to manufacture default to fix the error), I installed that update through Windows Update.
I also uninstalled MagicIso and PowerIso, so should I run the Duplex uninstaller next?
Here's my BSOD report:
W7 x64, original installed, OEM, age of system, 6 months (i7-860, Radeon 4850, 1TB HD, X-Fi). I restored to manufacture default in May after an audio driver fiasco.
Rest is attached.
So, how should I go about getting new drivers for these? I have had some pretty bad experiences in the past (Creative X-Fi driver totally screwed up on me, had no audio for 1 month, then had to restore to manufacture default to fix the error), I installed that update through Windows Update.
I also uninstalled MagicIso and PowerIso, so should I run the Duplex uninstaller next?
Yes, run Duplex.
Those two drivers I listed may not be critical; but generally Windows does like drivers older that July 13, 2009.
Those two drivers I listed may not be critical; but generally Windows does like drivers older that July 13, 2009.
If you are uninstalling MagicISO and PowerISO, you might as well go the whole way and remove SPTD. Go ahead and run the SPTD remover.
I don't see the mouse drivers on your HP support page. I see the original install date for Windows was 5/2/2010, so I suspect your computer is still under warranty. I suggest contacting their tech support and telling them your mouse or its drivers is causing BSODs.
Maybe it is a problem with the mouse itself, in which case a new mouse would fix it, but more likely it is the drivers.
I don't see the mouse drivers on your HP support page. I see the original install date for Windows was 5/2/2010, so I suspect your computer is still under warranty. I suggest contacting their tech support and telling them your mouse or its drivers is causing BSODs.
Maybe it is a problem with the mouse itself, in which case a new mouse would fix it, but more likely it is the drivers.
Ok, got SPTD removed. I went into device manager and tried to update the mouse but it seems it was up to date.
I hope this helps with the two drivers.
GEARAspiWDM.sys Mon May 18 08:17:04 2009 - CD-ROM Class Filter Driver by Gear Softwarehttp://www.gearsoftware.com
pssdk42.sys Tue Jun 23 08:11:57 2009 - Packet Sniffer SD, microOLAP Technologies LTD
GEARAspiWDM.sys Mon May 18 08:17:04 2009 - CD-ROM Class Filter Driver by Gear Softwarehttp://www.gearsoftware.com
pssdk42.sys Tue Jun 23 08:11:57 2009 - Packet Sniffer SD, microOLAP Technologies LTD
�� Quote: Originally Posted by pietastesgood 
Ok, got SPTD removed. I went into device manager and tried to update the mouse but it seems it was up to date.
Carl- the question is where to find his mouse drivers.
The BSOD's only happen periodically, and this time, it didn't happen, but that doesn't say much, it might not happen today but a few days from now it might again.
This mouse driver would work, correct? Software & Driver Downloads HP HDX Laser Mouse - HP Customer Care (United States - English) Device Manager has the mouse described as HP HDX Mouse, and that's the only one that comes up.
I've updated the Gear driver but unfortunately haven't been able to find the driver for Packet Sniffer.
Also, if this is helpful, the past two days, when I tried to shutdown the computer it would get stuck at the Shutting down... screen for 30+ minutes, and then it would bluescreen, giving me a Driver State Power Failure, and I'd have to pull the plug and put it back in, get to the login screen, then turn off to get it off successfully. I experimented this morning with shutting down all my background programs in Task Manager before shutting down, and it's worked something like 4, 5 times now. However, just a time or two ago it crashed again, but I'm suspecting Firefox or something didn't close down completely as I'd forgotten to check in Task Manager that time. I can put up the Minidump for that one.
This mouse driver would work, correct? Software & Driver Downloads HP HDX Laser Mouse - HP Customer Care (United States - English) Device Manager has the mouse described as HP HDX Mouse, and that's the only one that comes up.
I've updated the Gear driver but unfortunately haven't been able to find the driver for Packet Sniffer.
Also, if this is helpful, the past two days, when I tried to shutdown the computer it would get stuck at the Shutting down... screen for 30+ minutes, and then it would bluescreen, giving me a Driver State Power Failure, and I'd have to pull the plug and put it back in, get to the login screen, then turn off to get it off successfully. I experimented this morning with shutting down all my background programs in Task Manager before shutting down, and it's worked something like 4, 5 times now. However, just a time or two ago it crashed again, but I'm suspecting Firefox or something didn't close down completely as I'd forgotten to check in Task Manager that time. I can put up the Minidump for that one.
Those drivers are even older than your current ones, so I don't recommend installing them.
I am running the other dumps now, but it appears that your mouse was the cause in all of them. Forget about the other drivers for the time being and concentrate on the mouse. If you have another mouse you can use instead, try it.
I am running the other dumps now, but it appears that your mouse was the cause in all of them. Forget about the other drivers for the time being and concentrate on the mouse. If you have another mouse you can use instead, try it.
Alright, I won't. I unfortunately don't have a spare hanging around anywhere.
So without the spare, what should be my next step?
So without the spare, what should be my next step?
Try uninstalling the mouse in Device Manager, and then rebooting. Let Windows install drivers automatically, do not install any drivers that you download or find on a CD.
Awrighty. Should I have checked delete driver software? I didn't and restarted, no BSOD's thus far.
I can't really say, to be honest. 
If the BSODs continue, try it again and this time tick the box.
Otherwise, I hope it is solved!
If the BSODs continue, try it again and this time tick the box.
Otherwise, I hope it is solved!
Heh, me too. Thanks for all the help! If it does BSOD again, I'll post here again, if it's alright.
Okay, the results of the dumps are in. With the exception of the last one, they were all caused by your mouse drivers. The last one appears to be caused by your firewire driver.
Semantec is mentioned in the last dump, but since so many pointed to the mouse drivers, I wouldn't make a big deal of it. If the BSODs continue, remove Norton with this tool: ftp://ftp.symantec.com/public/englis...moval_Tool.exe
It should be replaced with the free Microsoft Security Essentials.
...Summary of the Dumps:
Semantec is mentioned in the last dump, but since so many pointed to the mouse drivers, I wouldn't make a big deal of it. If the BSODs continue, remove Norton with this tool: ftp://ftp.symantec.com/public/englis...moval_Tool.exe
It should be replaced with the free Microsoft Security Essentials.
...Summary of the Dumps:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jul 22 11:30:08.082 2010 (UTC - 4:00) System Uptime: 0 days 0:01:24.206 BugCheck A, {0, 2, 1, fffff80002c89a88} *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Tue Jul 20 11:02:47.231 2010 (UTC - 4:00) System Uptime: 0 days 0:00:53.340 BugCheck A, {0, 2, 1, fffff80002cd1a88} *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Jul 9 12:00:14.822 2010 (UTC - 4:00) System Uptime: 0 days 0:00:58.819 BugCheck A, {0, 2, 1, fffff80002c8da88} *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Jul 9 12:02:18.362 2010 (UTC - 4:00) System Uptime: 0 days 0:01:11.470 BugCheck A, {0, 2, 1, fffff80002c92a88} *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Jun 18 11:07:31.596 2010 (UTC - 4:00) System Uptime: 0 days 0:00:44.720 BugCheck A, {0, 2, 1, fffff80002cdea88} *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jun 10 15:13:30.451 2010 (UTC - 4:00) System Uptime: 0 days 0:00:45.575 BugCheck A, {0, 2, 1, fffff80002adea88} *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat May 22 11:14:25.479 2010 (UTC - 4:00) System Uptime: 0 days 0:00:34.492 BugCheck A, {0, 2, 1, fffff80002a8aa88} *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jul 29 18:19:20.003 2010 (UTC - 4:00) System Uptime: 0 days 0:00:53.112 BugCheck A, {0, 2, 1, fffff80002c8aa88} *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jul 29 18:21:29.443 2010 (UTC - 4:00) System Uptime: 0 days 0:01:17.567 BugCheck A, {0, 2, 1, fffff80002c91a88} *** WARNING: Unable to verify timestamp for gamingms.sys *** ERROR: Module load completed but symbols could not be loaded for gamingms.sys Probably caused by : gamingms.sys ( gamingms+fdd ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Wed Jul 28 02:37:21.327 2010 (UTC - 4:00) System Uptime: 0 days 15:10:30.435 BugCheck 9F, {3, fffffa8007856060, fffff80000b9c518, fffffa800f78b470} Probably caused by : pci.sys BUGCHECK_STR: 0x9F PROCESS_NAME: System �������������������������������������������������������������������������������������� Yeah, looks like gamingms.sys has been a real bad boy.
Hope it's all good now.
Hope it's all good now.
I hope you have solved your problem.
Alright, well, the BSOD's on startup have ceased. However, the BSOD's on shutdown still continue. I've already deleted the mouse drivers and checked the box as well.
More info about the BSOD's on shutdown:
I shut down, and it stays for 15 minutes on the Shutting Down... screen, and then it BSOD's saying DRIVER STATE POWER FAILURE. The time that I actually let it wait for 15 minutes before shutting down and BSOD was the time that's totally off from everything else, I did that in the evening as opposed to the morning, so I'm guessing Norton is the one that has to do with that one?
More info about the BSOD's on shutdown:
I shut down, and it stays for 15 minutes on the Shutting Down... screen, and then it BSOD's saying DRIVER STATE POWER FAILURE. The time that I actually let it wait for 15 minutes before shutting down and BSOD was the time that's totally off from everything else, I did that in the evening as opposed to the morning, so I'm guessing Norton is the one that has to do with that one?
�� Quote: Originally Posted by pietastesgood Alright, well, the BSOD's on startup have ceased. However, the BSOD's on shutdown still continue. I've already deleted the mouse drivers and checked the box as well.
More info about the BSOD's on shutdown:
I shut down, and it stays for 15 minutes on the Shutting Down... screen, and then it BSOD's saying DRIVER STATE POWER FAILURE. The time that I actually let it wait for 15 minutes before shutting down and BSOD was the time that's totally off from everything else, I did that in the evening as opposed to the morning, so I'm guessing Norton is the one that has to do with that one?
More info about the BSOD's on shutdown:
I shut down, and it stays for 15 minutes on the Shutting Down... screen, and then it BSOD's saying DRIVER STATE POWER FAILURE. The time that I actually let it wait for 15 minutes before shutting down and BSOD was the time that's totally off from everything else, I did that in the evening as opposed to the morning, so I'm guessing Norton is the one that has to do with that one?
I havent been following this thread, but Norton may not have caused this one, or the last one but it may cause the next one. Most of us here recommend removing norton and using something else.
Current wisdom is to use Microsoft security essentials.
Good luck
Ken
Do you have the dump file? If so, please upload it. It could be Norton causing it. Try removing it Norton using the tool Jonathan mentioned. Download and install Microsoft Security Essentials. Reboot and lets see what happens.
Oops, Ken and I were posting at the same time.
Oops, Ken and I were posting at the same time.
Yep, I do, and I've got it attached.
Just a question though, I got Norton online from my ISP, but I had to pay for it, so is there some way that I can back it up somehow, if I ever want to reinstall it?
Also, what are the benefits of Microsoft Security Essentials over Norton? Norton seems to have been doing a pretty good job, blocking virus attacks in real time and all that.
Just a question though, I got Norton online from my ISP, but I had to pay for it, so is there some way that I can back it up somehow, if I ever want to reinstall it?
Also, what are the benefits of Microsoft Security Essentials over Norton? Norton seems to have been doing a pretty good job, blocking virus attacks in real time and all that.
This dump gives an error code of 9F, which is driver related. It blames 1394ohci.sys which is probably not the actual cause. This is a Microsoft driver.
I still find an older driver and sptd.sys on your system. A number of other drivers are involved in the crash including the Realtek audio drivers.
Update this driver:
GEARAspiWDM.sys Mon May 18 08:17:04 2009 - CD-ROM Class Filter Driver by Gear Softwarehttp://www.gearsoftware.com
I also suggest that you remove sptd.sys using this tool > DuplexSecure - Downloads. Use the tool to uninstall it and do not reinstall it while we are troubleshooting.
At this point, you might uninstall Norton and replace it with MSE.
Try these suggestions and lets see what happens.
Quote:
STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE
Usual causes: Device driver
Usual causes: Device driver
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_072710-27565-01.zip\072710-27565-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500? Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e50 Debug session time: Wed Jul 28 02:37:21.327 2010 (GMT-4) System Uptime: 0 days 15:10:30.435 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ..................................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8007856060, fffff80000b9c518, fffffa800f78b470} Probably caused by : 1394ohci.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8007856060, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa800f78b470, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800f78b470 DEVICE_OBJECT: fffffa800b0a7e20 DRIVER_OBJECT: fffffa800b09f9e0 IMAGE_NAME: C DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc30 MODULE_NAME: 1394ohci FAULTING_MODULE: fffff8800576f000 1394ohci CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002ceae23 to fffff80002c7bf00 STACK_TEXT: fffff800`00b9c4c8 fffff800`02ceae23 : 00000000`0000009f 00000000`00000003 fffffa80`07856060 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`02c87fa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330 fffff800`00b9c570 fffff800`02c87326 : fffff800`02e2a700 00000000`00356f68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5e0 fffff800`02c87e7e : 0000007f`3246f82d fffff800`00b9cc58 00000000`00356f68 fffff800`02df7f88 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`02c87697 : 00000022`b21062c1 00000022`00356f68 00000022`b21062ec 00000000`00000068 : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02c846fa : fffff800`02df4e80 fffff800`02e02c40 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_1394ohci.sys BUCKET_ID: X64_0x9F_IMAGE_1394ohci.sys Followup: MachineOwner --------- 0: kd> lmtsmn start end module name fffff880`0576f000 fffff880`057ad000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`01196000 fffff880`011ed000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`04442000 fffff880`044cc000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`050a9000 fffff880`050bf000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`014ab000 fffff880`014b6000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`06d7a000 fffff880`06d9c000 AtiHdmi AtiHdmi.sys Tue Mar 09 05:08:38 2010 (4B961E26) fffff880`050c5000 fffff880`0576f000 atikmdag atikmdag.sys Tue Apr 20 00:58:51 2010 (4BCD348B) fffff880`04f37000 fffff880`04f6d000 atikmpag atikmpag.sys Mon Apr 19 23:23:12 2010 (4BCD1E20) fffff960`00960000 fffff960`009c1000 ATMFD ATMFD.DLL unavailable (00000000) fffff880`03009000 fffff880`03010000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`04e10000 fffff880`04efb000 BHDrvx64 BHDrvx64.sys Tue May 11 20:28:29 2010 (4BE9F62D) fffff880`04de5000 fffff880`04df6000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`04771000 fffff880`0478f000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff880`04c1e000 fffff880`04cba000 ccHPx64 ccHPx64.sys Fri Feb 05 16:05:45 2010 (4B6C8829) fffff960`007d0000 fffff960`007f7000 cdd cdd.dll unavailable (00000000) fffff880`0428e000 fffff880`042b8000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00e67000 fffff880`00f27000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01d1d000 fffff880`01d4d000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00d06000 fffff880`00d64000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00c00000 fffff880`00c73000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`057ea000 fffff880`057fa000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`06d9c000 fffff880`06daa000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`07200000 fffff880`0723d000 CT20XUT CT20XUT.SYS Mon Jul 13 13:36:20 2009 (4A5B7094) fffff880`05000000 fffff880`050a8880 ctaud2k ctaud2k.sys Mon Jul 13 13:35:01 2009 (4A5B7045) fffff880`06c0d000 fffff880`06d71000 CTEXFIFX CTEXFIFX.SYS Mon Jul 13 13:36:14 2009 (4A5B708E) fffff880`07387000 fffff880`073a3000 CTHWIUT CTHWIUT.SYS Mon Jul 13 13:36:24 2009 (4A5B7098) fffff880`04400000 fffff880`04431000 ctoss2k ctoss2k.sys Mon Jul 13 13:30:53 2009 (4A5B6F4D) fffff880`05a56000 fffff880`05a5e000 ctprxy2k ctprxy2k.sys Mon Jul 13 13:35:03 2009 (4A5B7047) fffff880`0629b000 fffff880`062d3000 ctsfm2k ctsfm2k.sys Mon Jul 13 13:30:29 2009 (4A5B6F35) fffff880`04c00000 fffff880`04c1e000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`04dd6000 fffff880`04de5000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01d07000 fffff880`01d1d000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`04f6d000 fffff880`04f8f000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`06daa000 fffff880`06dbd000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`04062000 fffff880`0426a000 dump_iaStor dump_iaStor.sys Fri Oct 02 15:58:50 2009 (4AC65B7A) fffff880`06dbd000 fffff880`06dc9000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`05a72000 fffff880`05b66000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`05b66000 fffff880`05bac000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`04d3b000 fffff880`04db1000 eeCtrl64 eeCtrl64.sys Fri May 21 17:44:45 2010 (4BF6FECD) fffff880`06ba3000 fffff880`06bed000 emupia2k emupia2k.sys Mon Jul 13 13:30:18 2009 (4A5B6F2A) fffff880`073c6000 fffff880`073e6000 ENG64 ENG64.SYS Thu Jul 01 14:11:13 2010 (4C2CDA41) fffff880`04db1000 fffff880`04dd6000 EraserUtilRebootDrv EraserUtilRebootDrv.sys Fri May 21 17:44:45 2010 (4BF6FECD) fffff880`0301e000 fffff880`031d8000 EX64 EX64.SYS Thu Jul 01 14:19:15 2010 (4C2CDC23) fffff880`01570000 fffff880`01584000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`014b6000 fffff880`01502000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`0162b000 fffff880`01635000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01ccd000 fffff880`01d07000 fvevol fvevol.sys Mon Jul 13 19:22:15 2009 (4A5BC1A7) fffff880`01800000 fffff880`0184a000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff880`06de6000 fffff880`06de8880 gamingms gamingms.sys Fri Nov 20 03:00:09 2009 (4B064C89) fffff880`05a64000 fffff880`05a71000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0) fffff880`06a16000 fffff880`06ba3000 ha20x22k ha20x22k.sys Mon Jul 13 13:34:21 2009 (4A5B701D) fffff800`031e7000 fffff800`03230000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`05bac000 fffff880`05bd0000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`05bd0000 fffff880`05be1000 HECIx64 HECIx64.sys Thu Sep 17 15:54:16 2009 (4AB293E8) fffff880`06349000 fffff880`06362000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`06df7000 fffff880`06dff080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`06de9000 fffff880`06df7000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`046a9000 fffff880`04771000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`01cc4000 fffff880`01ccd000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`012a3000 fffff880`014ab000 iaStor iaStor.sys Fri Oct 02 15:58:50 2009 (4AC65B7A) fffff880`0723d000 fffff880`072b3000 IDSvia64 IDSvia64.sys Thu May 27 04:07:18 2010 (4BFE2836) fffff880`04f21000 fffff880`04f37000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`0433e000 fffff880`04365000 Ironx64 Ironx64.SYS Tue Apr 27 20:48:23 2010 (4BD785D7) fffff880`04e00000 fffff880`04e0f000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`06bed000 fffff880`06bfb000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bae000 fffff800`00bb8000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`04f8f000 fffff880`04fd2000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`01600000 fffff880`0161a000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`019a6000 fffff880`019d1000 ksecpkg ksecpkg.sys Mon Jul 13 19:50:34 2009 (4A5BC84A) fffff880`05a5e000 fffff880`05a63200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`063a6000 fffff880`063bb000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`06362000 fffff880`06385000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00cae000 fffff880`00cf2000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`06a00000 fffff880`06a0e000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`04431000 fffff880`04440000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`06c00000 fffff880`06c0d000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00e33000 fffff880`00e4d000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`0478f000 fffff880`047a7000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`047a7000 fffff880`047d3000 mrxsmb mrxsmb.sys Mon Jul 13 19:23:59 2009 (4A5BC20F) fffff880`04600000 fffff880`0464d000 mrxsmb10 mrxsmb10.sys Mon Jul 13 19:24:08 2009 (4A5BC218) fffff880`0464d000 fffff880`04670000 mrxsmb20 mrxsmb20.sys Mon Jul 13 19:24:05 2009 (4A5BC215) fffff880`04000000 fffff880`0400b000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`011ed000 fffff880`011f7000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01200000 fffff880`0125e000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`045f5000 fffff880`04600000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01cb2000 fffff880`01cc4000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01854000 fffff880`01946000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`05bf2000 fffff880`05bfe000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`01dd1000 fffff880`01e00000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`06286000 fffff880`0629b000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`04540000 fffff880`0454f000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`044cc000 fffff880`04511000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01946000 fffff880`019a6000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`0400b000 fffff880`0401c000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`045e9000 fffff880`045f5000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02c0a000 fffff800`031e7000 nt ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600) fffff880`01652000 fffff880`017f5000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`03000000 fffff880`03009000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`0451a000 fffff880`04540000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`0100d000 fffff880`01022000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00e00000 fffff880`00e33000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`0161a000 fffff880`0162b000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`066f5000 fffff880`0679b000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`057ad000 fffff880`057ea000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00cf2000 fffff880`00d06000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`04fd2000 fffff880`04ff6000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`04047000 fffff880`04062000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`01c00000 fffff880`01c21000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`019d1000 fffff880`019eb000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`04598000 fffff880`045e9000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`043e4000 fffff880`043ed000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`043ed000 fffff880`043f6000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`043f6000 fffff880`043ff000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01c78000 fffff880`01cb2000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`063bb000 fffff880`063d3000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`0457e000 fffff880`04598000 SCDEmu SCDEmu.SYS Mon Apr 12 04:52:25 2010 (4BC2DF49) fffff880`01167000 fffff880`01196000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0) fffff880`0679b000 fffff880`067a6000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`01c70000 fffff880`01c78000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`01037000 fffff880`0115e000 sptd sptd.sys Wed Apr 07 21:29:00 2010 (4BBD315C) fffff880`042b8000 fffff880`0433e000 SRTSP64 SRTSP64.SYS Wed Feb 24 18:59:29 2010 (4B85BD61) fffff880`04365000 fffff880`04379000 SRTSPX64 SRTSPX64.SYS Wed Feb 24 18:59:48 2010 (4B85BD74) fffff880`072be000 fffff880`07356000 srv srv.sys Mon Jul 13 19:25:11 2009 (4A5BC257) fffff880`06600000 fffff880`06669000 srv2 srv2.sys Mon Jul 13 19:25:02 2009 (4A5BC24E) fffff880`067a6000 fffff880`067d3000 srvnet srvnet.sys Mon Jul 13 19:24:58 2009 (4A5BC24A) fffff880`05bfe000 fffff880`05bff480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01502000 fffff880`01570000 SYMDS64 SYMDS64.SYS Mon Aug 17 19:35:30 2009 (4A89E942) fffff880`01584000 fffff880`015bf000 SYMEFA64 SYMEFA64.SYS Wed Apr 21 17:47:39 2010 (4BCF727B) fffff880`04379000 fffff880`043af000 SYMEVENT64x86 SYMEVENT64x86.SYS Thu Aug 13 18:28:21 2009 (4A849385) fffff880`01d5b000 fffff880`01dd1000 SYMTDIV SYMTDIV.SYS Tue May 04 00:38:27 2010 (4BDFA4C3) fffff880`01a01000 fffff880`01bfe000 tcpip tcpip.sys Mon Jul 13 19:25:34 2009 (4A5BC26E) fffff880`067d3000 fffff880`067e5000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`0403a000 fffff880`04047000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`0401c000 fffff880`0403a000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`0456a000 fffff880`0457e000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00500000 fffff960`0050a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`04efb000 fffff880`04f21000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`019eb000 fffff880`019fd000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`0632c000 fffff880`06349000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`06de4000 fffff880`06de5f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`05be1000 fffff880`05bf2000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`0622c000 fffff880`06286000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`05a00000 fffff880`05a56000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`06dc9000 fffff880`06de4000 USBSTOR USBSTOR.SYS Mon Jul 13 20:06:34 2009 (4A5BCC0A) fffff880`01000000 fffff880`0100d000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`03010000 fffff880`0301e000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`043af000 fffff880`043d4000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`01022000 fffff880`01037000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00d64000 fffff880`00dc0000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01c24000 fffff880`01c70000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`0454f000 fffff880`0456a000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`043d4000 fffff880`043e4000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00f27000 fffff880`00fcb000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00fcb000 fffff880`00fda000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`04511000 fffff880`0451a000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00030000 fffff960`0033f000 win32k win32k.sys unavailable (00000000) fffff880`0115e000 fffff880`01167000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`06385000 fffff880`063a6000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) fffff880`07356000 fffff880`07387000 WUDFRd WUDFRd.sys Mon Jul 13 20:06:06 2009 (4A5BCBEE) Unloaded modules: fffff880`07387000 fffff880`073c6000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`04cc5000 fffff880`04d3b000 IDSvia64.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`073c6000 fffff880`073e6000 ENG64.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0301e000 fffff880`031d8000 EX64.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0727c000 fffff880`072bb000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0723d000 fffff880`0727c000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`062d3000 fffff880`062ef000 CTHWIUT.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`06c0d000 fffff880`06d71000 CTEXFIFX.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07387000 fffff880`073c4000 CT20XUT.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`06c16000 fffff880`06d7a000 CTEXFIFX.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`062ef000 fffff880`0632c000 CT20XUT.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0727e000 fffff880`072bd000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0723f000 fffff880`0727e000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07200000 fffff880`0723f000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07387000 fffff880`073c6000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0727e000 fffff880`072bd000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0723f000 fffff880`0727e000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`06669000 fffff880`066da000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07200000 fffff880`0723f000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07387000 fffff880`073c6000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0727e000 fffff880`072bd000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0723f000 fffff880`0727e000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07200000 fffff880`0723f000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07387000 fffff880`073c6000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0723f000 fffff880`0725f000 ENG64.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0301e000 fffff880`031d8000 EX64.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0725f000 fffff880`0729e000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07200000 fffff880`0723f000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07387000 fffff880`073c6000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0725f000 fffff880`0729e000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07200000 fffff880`0723f000 Rt64win7.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`031dc000 fffff880`031fc000 ENG64.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`03022000 fffff880`031dc000 EX64.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`07387000 fffff880`073f8000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01d4d000 fffff880`01d5b000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`04073000 fffff880`0427b000 dump_iaStor. Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0427b000 fffff880`0428e000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
Update this driver:
GEARAspiWDM.sys Mon May 18 08:17:04 2009 - CD-ROM Class Filter Driver by Gear Softwarehttp://www.gearsoftware.com
I also suggest that you remove sptd.sys using this tool > DuplexSecure - Downloads. Use the tool to uninstall it and do not reinstall it while we are troubleshooting.
At this point, you might uninstall Norton and replace it with MSE.
Try these suggestions and lets see what happens.
Alrighty, all done. (Wow, it's amazing how much my computer sped up after removing Norton.)
However, I am a little paranoid - is MSE enough? Should I also run AVG or something?
However, I am a little paranoid - is MSE enough? Should I also run AVG or something?
The increase in speed does not surprise me at all. That is is good to hear.
You only need one AV running at a time. Generally speaking, two AV's will conflict causing systems slow downs and even crashes. There is an exception to this. The security experts here say that Avast was designed to work along side of MSE. I have not tried it, myself.
Did you remove sptd with the tool?
You only need one AV running at a time. Generally speaking, two AV's will conflict causing systems slow downs and even crashes. There is an exception to this. The security experts here say that Avast was designed to work along side of MSE. I have not tried it, myself.
Did you remove sptd with the tool?
Yep. I've actually already removed SPTD a few days ago when troubleshooting the mouse problem.
So running Avast with MSE would complement each other?
So running Avast with MSE would complement each other?
I still saw sptd in the latest dump you uploaded.
Apparently they will according to the security folks here. As I said, I have not tried it myself. I don't really see the need considering how I operate. After you get your system running smoothly, give it a try. But first, lets make sure your problem is solved.
Apparently they will according to the security folks here. As I said, I have not tried it myself. I don't really see the need considering how I operate. After you get your system running smoothly, give it a try. But first, lets make sure your problem is solved.
Yeah, that dump was from before I'd started troubleshooting, which explains the SPTD, since I didn't start trying to fix the problem until the next day or so. Well, I hope it works this time, and thanks for all the help! 
Ah, that explains it. OK, run your system and if you get another BSOD, upload it. If you don't post back in a couple of days and let us know how your system is doing.
Ugh, it wouldn't shut down again last night, so I just let it BSOD this morning and here are the dump reports. Popup (saved as text), minidump, and the system log temp file, zipped up here.
The jcgriff-formatted BSOD report has also been put up.
The jcgriff-formatted BSOD report has also been put up.
Hmm...now we're getting somewhere. It looks like your Creative Sound Blaster drivers are the cause, from the latest dump. They appear to be the default Windows 7 drivers, so you should be able to find an update.
Creative Worldwide Support > Sound Blaster
...Summary of the Dumps:
Creative Worldwide Support > Sound Blaster
...Summary of the Dumps:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Aug 6 12:10:57.357 2010 (UTC - 4:00) System Uptime: 0 days 0:10:37.481 BugCheck 9F, {3, fffffa80077e6a20, fffff8000418c518, fffffa800d785c60} Probably caused by : pci.sys BUGCHECK_STR: 0x9F PROCESS_NAME: System �������������������������������������������������������������������������������������� Oh man, I hope this time the drivers won't mess up my computer. Last time, I updated from Windows Update and it totally blew up my machine. 
On the other hand, in Device Manager, there are yellow exclamation points next to all of my portable devices. This just happened today. Could this also be causing a problem?
On the other hand, in Device Manager, there are yellow exclamation points next to all of my portable devices. This just happened today. Could this also be causing a problem?
If you right-click on the devices and select Properties, what does the explanation of the error mean?
If you are concerned, be sure to create a restore point before installing the drivers. That way you can restore if need be.
System Restore Point - Create
If you are concerned, be sure to create a restore point before installing the drivers. That way you can restore if need be.
System Restore Point - Create
Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)
It says that for all five of the devices.
It says that for all five of the devices.
You might just reboot and see if the problem goes away. Are the devices all USB?
Updated the drivers, rebooted, and the problem's still there. But at least it was able to reboot without BSOD'ing, so I guess that's something.
I just realized, I don't actually have any devices in 4 of the 5 slots. Only one of the slots is occupied, and that's my flash drive, which still works fine. Weird.
Perhaps this will help:
My main drive is C, my W7 restore image is D, my DVD drive is E, and I have empty spots from F to I, all of which have exclamation points in Device Manager. J is my external, I have nothing in K, and L is my flash drive, which also had an exclamation point. I uninstalled the device and reinserted it but the only change was that now there's nothing at all in the L drive of Device Manager. Nevertheless, the flash drive still works. Should I just go ahead and uninstall the devices for F to I, since there's actually nothing in there?
I just realized, I don't actually have any devices in 4 of the 5 slots. Only one of the slots is occupied, and that's my flash drive, which still works fine. Weird.
Perhaps this will help:
My main drive is C, my W7 restore image is D, my DVD drive is E, and I have empty spots from F to I, all of which have exclamation points in Device Manager. J is my external, I have nothing in K, and L is my flash drive, which also had an exclamation point. I uninstalled the device and reinserted it but the only change was that now there's nothing at all in the L drive of Device Manager. Nevertheless, the flash drive still works. Should I just go ahead and uninstall the devices for F to I, since there's actually nothing in there?
Just bumping this, if it's alright.
Try removing the drive letters for those empty drives.
http://www.sevenforums.com/tutorials...ndows-7-a.html
Go ahead and uninstall the devices if that doesn't do the trick for you.
http://www.sevenforums.com/tutorials...ndows-7-a.html
Go ahead and uninstall the devices if that doesn't do the trick for you.
Alright, done. Now, I just hope it'll return to normal shutdown...
I hope it does, too. Let us know.
Well, it's been shutting down normally the past week, and I hope it stays that way! Thanks for all the help, guys!
Thanks for the update! Glad to hear it. 
If you need anything else, be sure to post.
If you need anything else, be sure to post.
�� Quote: Originally Posted by pietastesgood Well, it's been shutting down normally the past week, and I hope it stays that way! Thanks for all the help, guys!
Không có nhận xét nào:
Đăng nhận xét