DRIVER POWER STATE FAILURE Windows 7

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.

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

Thank you, Dave.

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: https://www.sevenforums.com/crashes-d...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.

Code:

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

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