DRIVER POWER STATE FAILURE Windows 7

[SoulPursuer]

Ok so when shutting down my computer it seems to hang at shutting down for ages (time changes) and then I get a BSOD and it says DRIVER POWER STATE FAILURE. It also does this randomly when not shutting down.

I have a Dell XPS, Core i7 (8x 2.67ghz), 8Gigs of RAm, running a legal copy of Windows 7 Home Edition (64bit).

Its fully updated and have previously done a reinstall.

Cant really think what else to do. Oh and when listen to music (most noticable) the sound cuts out and makes horible noises for a half second then plays fine and then does it again later. It seems to only do this after the computer has been on a while though.

I have attached minidumps bellow.

Anything would be helpfull.


Minidump.rar - Windows Live

 

[CarlTR6]

Hi Soulpurser. Sorry you are having problems. Please read this thread and post back. We will be glad to help you.


http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[SoulPursuer]

Ok Ill start afresh and try again.

Window Home Premium

x64
Original OS was Vista but they sent me 7 as a free upgrade
System brought new a week prior to Windows 7 Launching (about a year)
I'm pretty sure the disk is a retail copy.

System (hardware) is about a year old, had a new graphics, card and wifi adapter though, they are about 4months old.
Reinstalled the OS 3 days ago.



and here is the link to the BSOD and Peformance stuff

BSOD and Resource Perform check.rar - Windows Live

 

[CarlTR6]

Thanks much. I looked at all five dumps and they all have the same error code, 9F.

Error code 9F, DRIVER_POWER_STATE_FAILURE. Usual causes: Device driver

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e4ae50
Debug session time: Thu Oct 28 06:10:52.209 2010 (GMT-4)
System Uptime: 0 days 0:51:00.255
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8006d20680, fffff80000b9c510}

Unable to load image \SystemRoot\system32\DRIVERS\connctfy.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for connctfy.sys
*** ERROR: Module load completed but symbols could not be loaded for connctfy.sys
Probably caused by : connctfy.sys ( connctfy+1606 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006d20680, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8006d20680

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c84992 to fffff80002c835da

STACK_TEXT:  
fffff880`03361b80 fffff800`02c84992 : fffffa80`06d20680 fffffa80`06d20680 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`03361cc0 fffff800`02c86cff : fffff6fc`4000ba40 fffffa80`06d20680 fffff880`00000000 00000000`00160077 : nt!KiCommitThreadWait+0x1d2
fffff880`03361d50 fffff880`0169320f : fffffa80`09857600 fffff880`00000000 fffff880`04837000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`03361df0 fffff880`04831606 : fffffa80`0afde720 00000000`00000001 00000000`00000000 fffffa80`0afde8e0 : ndis!NdisWaitEvent+0x3f
fffff880`03361e30 fffffa80`0afde720 : 00000000`00000001 00000000`00000000 fffffa80`0afde8e0 fffff880`00000103 : connctfy+0x1606
fffff880`03361e38 00000000`00000001 : 00000000`00000000 fffffa80`0afde8e0 fffff880`00000103 fffffa80`0996f1a0 : 0xfffffa80`0afde720
fffff880`03361e40 00000000`00000000 : fffffa80`0afde8e0 fffff880`00000103 fffffa80`0996f1a0 fffff880`016d3310 : 0x1


STACK_COMMAND:  .thread 0xfffffa8006d20680 ; kb

FOLLOWUP_IP: 
connctfy+1606
fffff880`04831606 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  connctfy+1606

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: connctfy

IMAGE_NAME:  connctfy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bfe3927

FAILURE_BUCKET_ID:  X64_0x9F_connctfy+1606

BUCKET_ID:  X64_0x9F_connctfy+1606

Followup: MachineOwner
---------

0: kd> lmtsmn
start             end                 module name
fffff880`04387000 fffff880`043c5000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f97000 fffff880`00fee000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`04000000 fffff880`0408a000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`049ea000 fffff880`04a00000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`011cc000 fffff880`011d7000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`06071000 fffff880`0607c000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`04843000 fffff880`049c0000   athrx    athrx.sys    Mon Oct 05 12:33:57 2009 (4ACA1FF5)
fffff880`047a9000 fffff880`047dd000   AVGIDSDriver AVGIDSDriver.Sys Tue Aug 03 18:24:45 2010 (4C58972D)
fffff880`015e6000 fffff880`015f0000   AVGIDSEH AVGIDSEH.Sys Mon Sep 13 18:46:38 2010 (4C8EA9CE)
fffff880`046ad000 fffff880`046b9000   AVGIDSFilter AVGIDSFilter.Sys Tue Aug 03 18:23:21 2010 (4C5896D9)
fffff880`042fc000 fffff880`0434b000   avgldx64 avgldx64.sys Mon Sep 06 20:49:29 2010 (4C858C19)
fffff880`02c3d000 fffff880`02c4c000   avgmfx64 avgmfx64.sys Mon Sep 06 20:49:14 2010 (4C858C0A)
fffff880`0167d000 fffff880`01687000   avgrkx64 avgrkx64.sys Mon Sep 06 20:49:37 2010 (4C858C21)
fffff880`040dc000 fffff880`0413d000   avgtdia  avgtdia.sys  Mon Sep 06 20:52:11 2010 (4C858CBB)
fffff880`02c55000 fffff880`02c5c000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`0108b000 fffff880`0109c000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`03800000 fffff880`0381e000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff880`05bde000 fffff880`05bee000   BthEnum  BthEnum.sys  Mon Jul 13 20:06:52 2009 (4A5BCC1C)
fffff880`02d56000 fffff880`02d76000   bthpan   bthpan.sys   Mon Jul 13 20:07:00 2009 (4A5BCC24)
fffff880`05b52000 fffff880`05bde000   bthport  bthport.sys  Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`05b3a000 fffff880`05b52000   BTHUSB   BTHUSB.sys   Mon Jul 13 20:06:52 2009 (4A5BCC1C)
fffff960`00610000 fffff960`00637000   cdd      cdd.dll      unavailable (00000000)
fffff880`02c13000 fffff880`02c3d000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00cd2000 fffff880`00d92000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`013af000 fffff880`013df000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c74000 fffff880`00cd2000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01482000 fffff880`014f5000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`049da000 fffff880`049ea000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`04830000 fffff880`0483b000   connctfy connctfy.sys Thu May 27 05:19:35 2010 (4BFE3927)
fffff880`04a5a000 fffff880`04a68000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0106d000 fffff880`0108b000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`041f1000 fffff880`04200000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`015d0000 fffff880`015e6000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04bc7000 fffff880`04be9000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`05b27000 fffff880`05b3a000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`05a09000 fffff880`05b27000   dump_iaStorV dump_iaStorV.sys Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`05bee000 fffff880`05bfa000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04200000 fffff880`042f4000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`10b6f000 fffff880`10bb5000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`0fe00000 fffff880`0fe49000   e1y60x64 e1y60x64.sys Mon Aug 18 17:45:05 2008 (48A9ED61)
fffff880`039c4000 fffff880`039fa000   fastfat  fastfat.SYS  Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`0104c000 fffff880`01060000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01000000 fffff880`0104c000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01506000 fffff880`01510000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01596000 fffff880`015d0000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`049cd000 fffff880`049da000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`031e9000 fffff800`03232000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`10bb5000 fffff880`10bd9000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`04b2e000 fffff880`04b8a000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`04a00000 fffff880`04a19000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`04a19000 fffff880`04a21080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`04bef000 fffff880`04bfd000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`038fc000 fffff880`039c4000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`017ef000 fffff880`017f8000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`010ae000 fffff880`011cc000   iaStorV  iaStorV.sys  Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`04371000 fffff880`04387000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`011f1000 fffff880`01200000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04a4c000 fffff880`04a5a000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bcf000 fffff800`00bd9000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`04a6a000 fffff880`04aad000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`01468000 fffff880`01482000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`04be9000 fffff880`04bee200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`02dc8000 fffff880`02ddd000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`02d84000 fffff880`02da7000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c1c000 fffff880`00c60000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`02d76000 fffff880`02d84000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`0109c000 fffff880`010ab000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04a24000 fffff880`04a31000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00d92000 fffff880`00dac000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`0381e000 fffff880`03836000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`0607c000 fffff880`060a4000   mrxdav   mrxdav.sys   Mon Jul 13 19:23:57 2009 (4A5BC20D)
fffff880`03836000 fffff880`03863000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`0463c000 fffff880`0468a000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0468a000 fffff880`046ad000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`02cba000 fffff880`02cc5000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e00000 fffff880`00e0a000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`0140a000 fffff880`01468000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`041e6000 fffff880`041f1000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`017dd000 fffff880`017ef000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0168b000 fffff880`0177d000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04824000 fffff880`04830000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`038c7000 fffff880`038da000   ndisuio  ndisuio.sys  Mon Jul 13 20:09:25 2009 (4A5BCCB5)
fffff880`043c5000 fffff880`043f4000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04b19000 fffff880`04b2e000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`04182000 fffff880`04191000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`0413d000 fffff880`04182000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`0177d000 fffff880`017dd000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`02cc5000 fffff880`02cd6000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`041da000 fffff880`041e6000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c0d000 fffff800`031e9000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`0120c000 fffff880`013af000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`02c4c000 fffff880`02c55000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`10b6d000 fffff880`10b6e180   nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA)
fffff880`0fedb000 fffff880`10b6ce00   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E)
fffff880`03874000 fffff880`038c7000   nwifi    nwifi.sys    Mon Jul 13 20:07:23 2009 (4A5BCC3B)
fffff880`04093000 fffff880`040b9000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00e4a000 fffff880`00e5f000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e0a000 fffff880`00e3d000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`014f5000 fffff880`01506000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`046b9000 fffff880`0475f000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`04b8a000 fffff880`04bc7000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c60000 fffff880`00c74000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`04800000 fffff880`04824000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0febd000 fffff880`0fed8000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`10bd9000 fffff880`10bfa000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`011d7000 fffff880`011f1000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`00dac000 fffff880`00dfd000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`02c9f000 fffff880`02ca8000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02ca8000 fffff880`02cb1000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02cb1000 fffff880`02cba000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0155c000 fffff880`01596000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`02d2a000 fffff880`02d56000   rfcomm   rfcomm.sys   Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`038da000 fffff880`038f2000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`041c0000 fffff880`041da000   SCDEmu   SCDEmu.SYS   Sun Nov 08 22:27:29 2009 (4AF78C21)
fffff880`0475f000 fffff880`0476a000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`01675000 fffff880`0167d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`06110000 fffff880`061a6000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`060a9000 fffff880`06110000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`0476a000 fffff880`04797000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`0483b000 fffff880`0483c480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01800000 fffff880`019fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`04797000 fffff880`047a9000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`01060000 fffff880`0106d000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`013df000 fffff880`013fd000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`041ac000 fffff880`041c0000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00520000 fffff960`0052a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`0434b000 fffff880`04371000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`02cd6000 fffff880`02d2a000   udfs     udfs.sys     Mon Jul 13 19:23:37 2009 (4A5BC1F9)
fffff880`04aad000 fffff880`04abf000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`04a22000 fffff880`04a23f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`0feac000 fffff880`0febd000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04abf000 fffff880`04b19000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`0fe56000 fffff880`0feac000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`04a31000 fffff880`04a4c000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`0fe49000 fffff880`0fe56000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00e3d000 fffff880`00e4a000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`02c5c000 fffff880`02c6a000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`02c6a000 fffff880`02c8f000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e5f000 fffff880`00e74000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e74000 fffff880`00ed0000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01510000 fffff880`0155c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`049c0000 fffff880`049cd000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`040b9000 fffff880`040cf000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`038f2000 fffff880`038fc000   vwifimp  vwifimp.sys  Mon Jul 13 20:07:28 2009 (4A5BCC40)
fffff880`04191000 fffff880`041ac000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02c8f000 fffff880`02c9f000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ee4000 fffff880`00f88000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f88000 fffff880`00f97000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`0408a000 fffff880`04093000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00060000 fffff960`0036f000   win32k   win32k.sys   unavailable (00000000)
fffff880`00fee000 fffff880`00ff7000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`02da7000 fffff880`02dc8000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`061a6000 fffff880`061d7000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`06000000 fffff880`06071000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`015f0000 fffff880`015fe000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02cd8000 fffff880`02df6000   dump_iaStorV
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02c00000 fffff880`02c13000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

To start your troubleshooting, I suggest that you uninstall AVG using this tool: [FONT=&quot]Tool (64 bit). If you have Identity Protection installed, uninstall it with this tool: [/FONT][FONT=&quot]Tool. Download and install Microsoft Security Essentials in its place.

You have two outdated drivers loaded on your system. The one in red font is really out of date. Older drivers can and do cause BSOD's. Update these drivers.

e1y60x64.sys Mon Aug 18 17:45:05 2008 - [/FONT]Intel(R) 82567LM Gigabit Network Connection http://downloadcenter.intel.com/Default.aspx
[FONT=&quot]
iaStorV.sys Wed Apr 08 12:57:17 2009 - [/FONT]Intel Matrix Storage Manager driver (base)http://downloadcenter.intel.com/Default.aspx

Uninstall AVG, update these drivers, reboot and let's see how your system does. If you get another BSOD, upload it to us and we will go from there. Let us know how your system is doing.
[FONT=&quot]
[/FONT]

 

[SoulPursuer]

Ok I done all those, things seems to be fine atmo, but then it has been fine for a day or two before so who knows ill update you.

 

[CarlTR6]

That is good to hear; thank you for reporting back.. Report back again in a couple of days and let us know. I hope your troubles are gone.

 

[SoulPursuer]

Ok so it hasn't crashed yet but it made that weird noise again, so it doesn't look good.

 

[CarlTR6]

I am glad you have not had a crash. I wonder if it is your sound card going bad or if you have have an over heating problem? You can check your temps by downloading and installing Speedfan or CPUZ.

For help with the sound problem, I recommend you start a thread in the Sound & Audio section. There are some very knowledgeable folks there. Please post back here if you have another BSOD. I'm sorry that I cannot help you with the sound. I just have little experience in that area.

 

[SoulPursuer]

heres a link to pic of my temps

http://i235.photobucket.com/albums/ee215/jacob_d_reeves/Untitled-6.png?t=1288383776

this is idle btw (itunes, chrome, skype, and a couple of tiny background apps)

 

[CarlTR6]

Here is your screenshot:

View attachment 109025

What is your Temp1? That looks a little high for idle.

 

[SoulPursuer]

I have no idea where the temp 1 is located but I did think that it was pretty high too, how can I find out where it is?


p.s. My computer hasn't made any noises or crashed yet. Looking good so far.

 

[CarlTR6]

That is good news! Glad to hear you have had not further BSOD's. I will have one of the hardware guys look at this thread; he may be able to tell us what that temp 1 is.

 

[Dave76]

This question is asked alot.

I'm afraid the answer is that they are different on just about every brand, motherboard, OEM model, etc.

All the Speed Fan settings need to be checked when installed, it is not able to get every temp sensor labeled and setup correctly as there are thousands of different systems that require different settings.

Here is the disclaimer from their website:

Disclaimer
This program is aimed at the power user. At those who know what they're doing. I've known of no real problem caused by SpeedFan, but may be it's due to the fact that once it made the PC explode and the user disappeared in the blast, thus being unable to report Anyway: SpeedFan can be extremely useful, but you should first watch its behavior before setting and forgetting it.

Here is some info from SpeedFan:

Which temperature is which?​

​

​

​

There are several ways to label available readings (temperatures, voltages, fan speeds). The first source should be the BIOS. Enter BIOS at boot, write down labels and readings and compare them to those reported by SpeedFan. You can use manufacturer's custom hardware monitors to match readings too. SpeedFan strictly adheres to available datasheets for each sensor chip. Please remember that hardware monitors chips have some pins (small connectors) that should be connected to some additional hardware (temperature probes, thermistors or thermocouples) in order to be able to read temperatures. Only a few hardware monitor chips do label their connectors with "CPU", "System" and the like. Most of them use labels like "Temp1", "Local" or "Remote". Hardware manufacturers connect available pins to different temperature sensors basically according to the physical placement of components on the motherboard. This means that the same chip, an ITE IT8712F, for example, might be connected to a sensor diode measuring CPU temperature on Temp2 and, on a different hardware, it might be connected on Temp1. If you have a "Local" sensor and a "Remote" labeled one, this usually means that "Local" is the temperature of the monitor chip itself and "Remote" is the temperature read from a "remote" probe. When you have properly identified which temperature sensor is which, try to lower the speed of each fan and look at reported speed and temperatures. This way you can match PWM controls (speeds) with fans. Please, note that if you do not allow SpeedFan to change any fan speed and set all the speeds too low, then SpeedFan won't be able to avoid overheating.

Dell XPS has good customer support, from what I remember, I would try and sent them a question.

Temp1 in SpeedFan is TMPIN0 in windows.

Can you give us more info on your system, the XPS xxx model number, etc.?


Found this on the Dell Support Forum, it may or may not be relevent or help.
Have a look and see if you want to try this.

Download the Nvidia System Tools with ESA Support 6.03 by using the link below. If you have the XPS Thermal App running, disable it and don't use it. Why? Because it's junk. The Nvidia tools will allow you to adjust all of your fans, leds, and clocks.​

NVIDIA System Tools with ESA Support 6.03​

 

[CarlTR6]

Thank you, Dave.

 

[SoulPursuer]

I have a:
Studio XPS Desktop 435MT
Service tag is FBPKG4J if that helps.


I added the specs of my system to my profile if you want to have a look there.

 

[SoulPursuer]

Ok still cant find out where my temp 1 is located. I hadnt had a crash in ages though so I forgot about it not even any more strange noises which I still havent had so thats all good I guess, I did just get another BSOD though
It didnt seem to be the same error by the looks of it, saying that though I didnt get that much of a good look as it rebooted to quick.
anyway here is my new mini dump thing:

BSOD report 2nd of nov.rar - Windows Live

 

[CarlTR6]

I looked at your three latest dumps. One blames nvlddmkm.sys, which is a video driver and the other two blame connctfy.sys, Connectify - Turn your Windows 7 laptop into a Wi-Fi Hotspot. There is another thread here where Connectify was the culprit: http://www.sevenforums.com/crashes-debugging/119972-bsod-hibernate.html. However, in all three dumps, LVUSBS64.sys is shown as an unloaded module. This means it was involved the crash, but not necessarily the cause of the crash. This driver is out of date.

Some of my references show that LVUSBS64.sys is a Logitech webcam driver; but people who have disabled it have lost their sound and sound returned upon enabling it again. Read this thread: Problem Driver LVUSBS64.sys (Vista x64) - Logitech Forums. As far as I been able to determine, Logitech has no update for this driver and it has caused many problems.

Error code 116, VIDEO_TDR_FAILURE. Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card.

Error code 9F (2X), DRIVER_POWER_STATE_FAILURE. Usual causes: Device driver.

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50
Debug session time: Tue Nov  2 18:30:11.958 2010 (GMT-4)
System Uptime: 0 days 0:15:21.004
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800738c4e0, fffff88010124cf8, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+119cf8 )

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800738c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010124cf8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+119cf8
fffff880`10124cf8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`039b89c8 fffff880`10cfbef8 : 00000000`00000116 fffffa80`0738c4e0 fffff880`10124cf8 00000000`00000000 : nt!KeBugCheckEx
fffff880`039b89d0 fffff880`10cfbc02 : fffff880`10124cf8 fffffa80`0738c4e0 fffffa80`0b7e7d50 fffffa80`0b7db010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`039b8a10 fffff880`10da2f07 : fffffa80`0738c4e0 00000000`00000000 fffffa80`0b7e7d50 fffffa80`0b7db010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`039b8a40 fffff880`10dccb75 : 00000000`ffffffff 00000000`0000e5c7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`039b8b20 fffff880`10dcb2bb : 00000000`00000102 00000000`00000000 00000000`0000e5c7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`039b8b50 fffff880`10d9e2c6 : ffffffff`ff676980 fffffa80`0b7db010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`039b8bf0 fffff880`10dcae7a : 00000000`00000000 fffffa80`0b873810 00000000`00000080 fffffa80`0b7db010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`039b8d00 fffff800`02f15c06 : 00000000`fffffc32 fffffa80`0b7d1210 fffffa80`06ca99e0 fffffa80`0b7d1210 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`039b8d40 fffff800`02c4fc26 : fffff800`02debe80 fffffa80`0b7d1210 fffff800`02df9c40 fffff880`01630bf0 : nt!PspSystemThreadStartup+0x5a
fffff880`039b8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+119cf8
fffff880`10124cf8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+119cf8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c37918e

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8006d2cb60, fffff800042ae510}

Unable to load image \SystemRoot\system32\DRIVERS\connctfy.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for connctfy.sys
*** ERROR: Module load completed but symbols could not be loaded for connctfy.sys
Probably caused by : connctfy.sys ( connctfy+1606 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006d2cb60, The thread currently holding on to the Pnp lock.
Arg4: fffff800042ae510

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8006d2cb60

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c7a992 to fffff80002c795da

STACK_TEXT:  
fffff880`03584b80 fffff800`02c7a992 : fffffa80`06d2cb60 fffffa80`06d2cb60 00000000`00000000 00000000`0000000a : nt!KiSwapContext+0x7a
fffff880`03584cc0 fffff800`02c7ccff : fffff6fc`4000c978 fffffa80`06d2cb60 fffff880`00000000 00000000`00160077 : nt!KiCommitThreadWait+0x1d2
fffff880`03584d50 fffff880`0187a20f : fffffa80`0a997600 fffff880`00000000 fffff880`04df5000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`03584df0 fffff880`04def606 : fffffa80`0c1ab010 00000000`00000001 00000000`00000000 fffffa80`0c1ab1d0 : ndis!NdisWaitEvent+0x3f
fffff880`03584e30 fffffa80`0c1ab010 : 00000000`00000001 00000000`00000000 fffffa80`0c1ab1d0 fffff880`00000103 : connctfy+0x1606
fffff880`03584e38 00000000`00000001 : 00000000`00000000 fffffa80`0c1ab1d0 fffff880`00000103 fffffa80`0ab6a1a0 : 0xfffffa80`0c1ab010
fffff880`03584e40 00000000`00000000 : fffffa80`0c1ab1d0 fffff880`00000103 fffffa80`0ab6a1a0 fffff880`018ba310 : 0x1


STACK_COMMAND:  .thread 0xfffffa8006d2cb60 ; kb

FOLLOWUP_IP: 
connctfy+1606
fffff880`04def606 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  connctfy+1606

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: connctfy

IMAGE_NAME:  connctfy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bfe3927

FAILURE_BUCKET_ID:  X64_0x9F_connctfy+1606

BUCKET_ID:  X64_0x9F_connctfy+1606

Followup: MachineOwner
---------

I think you may have a couple of problems going on: possible overheating and a driver problem, specifically the LVUSBS64.sys driver. But the LVUSBS64.sys is common in all three dumps.

These outdated drivers are loading on your system. I believe there is an update for iaStorV.sys. Try to find one for LVUSBS64.sys. This driver is really out of date.

LVUSBS64.sys Jul 26 2008 - Logitech USB Monitor Filter, Downloads.

iaStorV.sys Wed Apr 08 12:57:17 2009 - Intel Matrix Storage Manager driver (base)http://downloadcenter.intel.com/Default.aspx

 

[SoulPursuer]

OK thanks I think I missed a driver last time I tried to update, found a new "Intel Matrix Storage Manager driver" and removed Connectify. It did crash before I managed to restart but im going to give it some chance as I hadnt managed to update the intel driver.

Ill let you know how it goes.

UPDATE:
Ok, so I wrote this just before I had finished installing the new Intel driver and when I opened it it told me that I had a newer driver already.

 

[CarlTR6]

Very good and thanks for reporting back. Please let us know how your system does.

 

[SoulPursuer]

Ok its been a good 4 days since I did what you said, it looks to me like its fixed. I haven't had any BSOD's any noises, its working like a charm. I do miss Connectify though, I used that a lot. Oh well, defo worth it.

Thanks guys, you lot are awesome keep the work up. You have made me happy to use my pc again.

SoulPursuer out.