DRIVER_POWER_STATE_FAILURE 00000000'00000003

Hi all

I try everything I install windows 7 and 8 and 8.1 same problem I try to also update same driver problem

Toshiba L50T-A

I think that this problem of material

DRIVER_POWER_STATE_FAILURE ntoskrnl.exe

DRIVER_POWER_STATE_FAILURE 00000000'00000003

101413 58187 - 01.dmp 14/10/2013-09:43:06 00000000'00000003 ffffe000 "013b01c0 fffff801" 0x0000009f DRIVER_POWER_STATE_FAILURE 546e5960 ffffe000'00f9ec50 ntoskrnl.exe ntoskrnl.exe + 1500 has a 1500 0 C:\Windows\Minidump\101413-58187-01.dmp 9600 + 0 x 64 ntoskrnl.exe 15 8 1 043 760 10/14/2013 09:45:02

dumfiles

https://SkyDrive.live.com/redir?RESID=18BA779B1B55F962! 3306 & authkey =! AKzuMlPiUWHvjOs

Info

https://SkyDrive.live.com/redir?RESID=18BA779B1B55F962! 3307 & authkey =! AAhN15P5WE0sAqQ

Hello

Please follow my recommendation above and activate the driver verifier.

Kind regards

Patrick

Tags: Windows

Similar Questions

DRIVER_POWER_STATE_FAILURE 00000000'00000004 leaving mode standby

I worked on for 00000000'00000004 DRIVER_POWER_STATE_FAILURE bsod

It always happens when the device out of standby/sleep (user closed the lid). User closes the lid to put to sleep. Does not occur when the lid closing and opening upward in short periods of time, it occurs when the lid is closed and let him sleep all night

I have updated the BIOS, video drivers, Wifi + NIC drivers.

The SCEP Protocol has no virus detected

Hibernation is disabled for sleep in the advanced power settings.

I ran/f/r chkdsk and sfc/scannow and not found anything

I used bluescreenview and Windbg, but I can't find a specific driver as the cause.

Before you start pulling the machine, I would like to know definitely its no driver or setting or something to another number

the memory.dmp and minidump with system information are to the

https://onedrive.live.com/redir?RESID=E97F581991DC7D7C! 188 & authkey =! AHFzxhgmpKIfpA4&ithint=file%2c.zip

The initial system is

Name of the operating system Microsoft Windows 7 Enterprise
Version 6.1.7601 Service Pack 1 Build 7601
Another Description of the OS is not available
Manufacturer of operating system Microsoft Corporation
US31777 system name
System manufacturer Dell Inc.
System model Latitude E6430
System Type x 64-based PC
Intel Core processor i5 - 3320M CPU @ 2.60 GHz, 2601 Mhz, 2 Lossnay, 4 logical processors
A15 BIOS Version/Date Dell Inc., 29/05/2014
SMBIOS Version 2.7

It is solved with:

'Uninstalled the current video driver, rebooted, installed more recent site of dell for the video driver. Also check the settings for PCI express links and AC and battery have been updated with Maximum energy saving. Changed both to moderate"

Thanks for all help

BSOD "DRIVER_POWER_STATE_FAILURE" (BlueScreenView said it was nvbridge.kmd)

I got a BSOD recently for the first time in years. I used a tool called 'BlueScreenView' to see what was going on with the dump file, the dump quite well said

Mini113011 - 01.dmp 30/11/2011-05:16:03 DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000 00000003' fffffa80 ' 09742060 fffffa80' 09742060 fffffa80'0440 has 680 nvBridge.kmd nvBridge.kmd + 58c5060 x 64 + C:\Windows\Minidump\Mini113011-01.dmp 2 15 6001 279 768 55410 ntoskrnl.exe

What should I do? BlueScreenView is useful? I found the "nvBridge.kmd" and removed as well as more experienced my NVIDIA drivers and reinstall the last a. IM in SafeMode right now so this type because normal mode for some reason, I'm very slow and some programs just hanging out or will not open, I would like a link this problem to the recent BSOD.

In any case, I decided to Skydrive my dump files in the hope of getting an answer from someone more intelligence tech to help me with my current problem of why my computer is extremely slow/laggy and unresponsive at times.

https://SkyDrive.live.com/redir.aspx?CID=5a4d69e1cd2517c5&RESID=5A4D69E1CD2517C5! 117 & Thierry = 5A4D69E1CD2517C5! 115

I set myself, I had to rename the nvlddmkm.sys in the system32/drivers nvlddmkm.sys.old and let it update automatically on reboot and then I downloaded the new beta drivers and all is well.

DRIVER_POWER_STATE_FAILURE on new HP Probook 450 G2 problems and a Wi - Fi connection

Hello

I am running Windows 7 64 bit on a laptop HP HP Probook 450 G2 and I get a BSOD per day during the recovery of sleep/wake. I have the latest drivers from HP, updating the BIOS and Windows updated with Win Update.

122615-7784 - 01.dmp

26.12.2015 10:59:47

DRIVER_POWER_STATE_FAILURE

0x0000009F

00000000'00000003

fffffa80'077bea10

fffff800'00b9a3d8

fffffa80'0f571810

Ntoskrnl.exe

Ntoskrnl.exe + 73c40

Microsoft® Windows® operating system Microsoft Corporation 6.1.7601.19045 (win7sp1_gdr.151019 - 1254) x 64

Link to minidump https://www.dropbox.com/s/t72xvj8k1nh5oqb/122615-7784-01.dmp?dl=0

Also, my Wi - Fi Realtek RTL8723BE 802.11 adapter b/g/n gives me a headache, it is connected to the router, but my Internet connection is lost on a daily basis, and I have to turn the adapter wi - fi for it to work again (router is ok, I use other devices to connect to the net without frequent problems like that).

Usually, I see this in the event handler:

-Event 1014 name resolution for the name dns.msftncsi.com timed out after none of the servers configured DNS responded.

-Event 4001 WLAN auto configuration service has stopped successfully. (not really a problem, I read)

-Event 10002 Module WLAN Extensibility stopped. Path of the module: C:\Windows\system32\Rtlihvs.dll (solved by editing the registry)

I tried to disable in the BIOS of the LAN device, camera, microphone, etc. but still the BSOD and wi - fi connectivity issues.

Help, please!

The gold standard for the diagnosis of ASD BSOD is called Windows Debugger. While it's not rocket science there is a steep learning curve when all first start using it if you simply want your diagnose your best best is to let a more experienced analyst to make your

Bluescreens ~ 15 min interval... 0X0000009F DRIVER_POWER_STATE_FAILURE

Hi I'm Philipp,

and I hope you can help me with this problem:

My system is a Win7 64 bit old for two months on a Toshiba Tecra Notebook z50. During the first-updates Windows appears the first Bluescreen.

I tried to solve the problem 0x0000009f DRIVER_POWER_STATE_FAILURE, but actually I get stuck.

I trie to identify the driver, which seems to cause the problem.

The Dumpfile indicates the following:

==================================================
Dump file: 060315-10764 - 01.dmp
Time of the accident: 03.06.2015 15:34:29
Bug Check String: DRIVER_POWER_STATE_FAILURE
Bug check code: 0x0000009f
Parameter 1: 00000000'00000003
Parameter 2: fffffa80 107 c 0970
Parameter 3: fffff800'00b9e3d8
Parameter 4: fffffa80'0d88fc60
Caused by the driver: ntoskrnl.exe
Caused by the address: ntoskrnl.exe + 75bc0
File description: NT kernel & system
Product name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File version: 6.1.7601.18409 (win7sp1_gdr.140303 - 2144)
CPU: x 64
Plant address: ntoskrnl.exe + 75bc0
Stack address 1:
The stack address 2:
Address 3 the battery:
Computer name:
Full path: C:\Windows\Minidump\060315-10764-01.dmp
Number of processors: 4
Main version: 15
Minor Version: 7601
Empty the file size: 1.027.896
Dump of file time: 03.06.2015 15:35:27
==================================================

Thanks for your support,

Regards Philipp

Also the link to the minidump and MSinfo32:

https://onedrive.live.com/redir?RESID=9F39027DBFE5299D! 109 & authkey =! ACdpcx4LGKdn_1k & ithint = the file % 2czip

They are all connected to iusb3hub.sys driver hub USB 3.0 of Intel Corporation. Remove the driver current completely and install the latest driver available.

BSOD ntoskrnl.exe + 72 0x0000009f DRIVER_POWER_STATE_FAILURE has 40

I almost brand new HP ProBOOK 450 G2 with Windows 7 Enterprise, just noticed today the first Memory Dump, thought then to ask... like the laptop is under warranty... laptop computer is on battery power and the battery is dead so saw the light flashing 'orange' and he got the memory dump and he came down, the battery was finished It happened... but its still not the right way to go then... I have through the app "BlueScreenView" about something, but he could not say exactly... searched thing many error BSOD here in the office, but none had the same error, sharing so if someone is kind enough to help.

Dump file 050415-21028 - 01.dmp
Time of the accident 04/05/2015-11:01:32
Bug Check String DRIVER_POWER_STATE_FAILURE
Bug check code 0x0000009f
Parameter 1 00000000'00000003
Parameter 2 fffffa80'07f37a10
Parameter 3 fffff800'048943 d 8
Parameter 4 fffffa80'08da0010
Caused by the driver Ntoskrnl.exe
Caused by the address ntoskrnl.exe + 72 has 40

DMP file: http://1drv.ms/1K9FKRC

Thanks in advance

ONE

This phenomenon was related to rtlane.sys NDIS Driver of Realtek Semiconductor Corporation. I remove the current driver and install the latest driver available.

DRIVER_POWER_STATE_FAILURE ntoskrnl.exe e58d2

I'm the blockages of the system and this is the error I get: driver_power_state_failure ntoskrnl.exe e58d2

Here is a paste of bluescreenview log:

==================================================
Dump file: 111914-29234 - 01.dmp
Crash time: 19/11/2014-15:39:27
Bug Check String: DRIVER_POWER_STATE_FAILURE
Bug check code: 0x0000009f
Parameter 1: 00000000'00000003
Parameter 2: fffffa80'07581680
Parameter 3: fffff800'04895748
Parameter 4: fffffa80 12854 c. 60
Caused by the driver: ntoskrnl.exe
Caused by the address: ntoskrnl.exe + 75bc0
File description: NT kernel & system
Product name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File version: 6.1.7601.18409 (win7sp1_gdr.140303 - 2144)
CPU: x 64
Plant address: ntoskrnl.exe + 75bc0
Stack address 1:
The stack address 2:
Address 3 the battery:
Computer name:
Full path: C:\Windows\Minidump\111914-29234-01.dmp
Number of processors: 8
Main version: 15
Minor Version: 7601
Size of the dump file: 1 475 032
Dump of file time: 19/11/2014-15:41:49
==================================================

Someone has an idea of what is causing this crash? Let me know what I can provide. I'm stumped on this one.

Shaun

I don't know your config so can suggest only you remove the current driver and then install a new one without having to reboot. You can also contact the computer manufacturer for information about the procedure to update.

Win 7 DRIVER_POWER_STATE_FAILURE (9f)

For the last week, I was constantly doing a BSOD every time I try to put my computer to sleep or into hibernation. I did a system restore, and I still find it. I don't know what is the cause.

I have had this computer of Gateway Office since 2008 and improved from Vista to Win 7 a few years ago. Intel Core 2 Quad - 8 GB of Ram - 64 bit

Any help trying to figure, what is the cause would be greatly appreciated.

Here's the WinDbg dump file:

*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************

9F error checking, {3, fffffa8006cd1a10, fffff80004942518, fffffa800b12e010}

Probably caused by: pci.sys

Follow-up: 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
Arg2: fffffa8006cd1a10, physical device from the stack object
Arg3: fffff80004942518, functional device object of the stack
Arg4: fffffa800b12e010, blocked IRP

Debugging information:
------------------

DRVPOWERSTATE_SUBCODE: 3

Nom_image: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000d6a000 pci

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0X9F

Nom_processus: System

CURRENT_IRQL: 2

STACK_TEXT:
"fffff800 ' 049424 c 8 fffff800 ' 0334d8d2: 00000000'00000003 fffffa80 00000000' 0000009f'06cd1a10 fffff800'04942518: nt! KeBugCheckEx
"fffff800 ' 049424 d 0 fffff800 ' 032e885c: fffff800 '04942600 fffff800' 04942600 00000000'00000000 00000000'00000001: nt! : FNODOBFM: 'string' + 0x33af0
fffff800 ' 04942570 fffff800' 032e86f6: fffff800 '0348e140 00000000' 0002665d 00000000'00000000 00000000' 0000073c: nt! KiProcessTimerDpcTable + 0x6c
"fffff800 '049425e0 fffff800' 032e85de: 00000005' b66df7d6 fffff800'04942 58 00000000 ' 0002665 c d fffff800 ' 0345be28: nt! KiProcessExpiredTimerList + 0xc6
"fffff800 ' 04942 c 30 fffff800 ' 032e83c7: 00000001' 00000001'0002665 d 00000001'55f9db3f 00000000'0000005 d 55f9dbc1: nt! KiTimerExpiration + 0x1be
fffff800 ' 04942 cd 0 fffff800' 032d58ca: fffff800'03458e80 fffff800 '03466cc0 00000000 00000000' fffff880' 0f203354: nt! KiRetireDpcList + 0 x 277
fffff800'04942 d 80 00000000 00000000': fffff800 ' 04943000 fffff800 '0493 d 000 fffff800' 04942d 40 00000000 00000000': nt! KiIdleLoop + 0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_e1e6232e_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_e1e6232e_IMAGE_pci.sys

Follow-up: MachineOwner
---------

0: kd > lmvm pci
start end module name
fffff880 '00d6a000 fffff880' 00d9d000 pci (PDB symbols) c:\symbols\pci.pdb\CB76D2E9B4BD4058A1AD2452855153671\pci.pdb
Loaded symbol image file: pci.sys
Mapped memory image file: c:\symbols\pci.sys\4CE7928F33000\pci.sys
Image path: \SystemRoot\system32\drivers\pci.sys
Image name: pci.sys
Timestamp: Sat, Nov 20 02:19:11 2010 (4CE7928F)
CheckSum: 00033150
ImageSize: 00033000
File version: 6.1.7601.17514
Product version: 6.1.7601.17514
Flags of the file: 0 (mask 3F)
Folder OS: 40004 NT Win32
File type: Dll 2.0
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: pci.sys
OriginalFilename: pci.sys
ProductVersion: 6.1.7601.17514
FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119 - 1850)
FileDescription: NT Plug - and - Play PCI enumerator
LegalCopyright: © Microsoft Corporation. All rights reserved.

Thank you very much!

The attached file of the DMP is to bug checking DRIVER_POWER_STATE_FAILURE (9f) .

This bug check indicates that the driver is in an inconsistent or invalid power state.

By default, the driver being blamed for blocking an IRP for too long is pci.sys, but it is not the real cause. If we run one! IRP on the 4th parameter of the verification of bug:

> [16, 2] e1 0 fffffa8008fd6050 fffff8000352a210-fffffa800aff3580 00000000 success error cancel pending
ERROR: Module load completed but symbols can be loaded for e1e6232e.sys
\Driver\e1express nt! PopSystemIrpCompletion

The real cause is e1e6232e.sys , which is the driver Intel (r) PRO/1000 PCI Express Network Connection.

------------------------------------

The reason why that this driver is the fault behind the accident is due to the fact that you are using a Modem Conexant. Device for this modem drivers are nearly 8 years, so it is not compatible with the operating system, and he can't go to sleep > wake States correctly.

Alone (unhappy) / workaround is to be replaced by a method of internet connection was updated.

Kind regards

Patrick

DRIVER_POWER_STATE_FAILURE - 0x0000009f - c:\windows\system32\drivers\sptd.sys

DRIVER_POWER_STATE_FAILURE

0x0000009F

Parameter 1: 00000000'00000003

Parameter 2: fffffa80'059 c 0880

Parameter 3: fffff880'02ece7f0

Parameter 4: fffffa80'080 c 7670

Caused by the driver: c:\windows\system32\drivers\sptd.sys

Caused by the address: c:\windows\system32\drivers\sptd.sys + 1dc3c

CPU: x 64

Plant address: ntoskrnl.exe + 5 has 540

Then view the last dump using BlueScreenView file

on the lower panel. I see two entries with a red nail... namely

ntosknrl.exe and c:\windows\system32\drivers\sptd.sys

This BSOD occur usually when I try to use my secondary video card... a Nvidia Geforce 610 m. I tried updating the driver, put it back, for a newer version or even an older version supplied by the manufacturer of the laptop. But the BSOD stop then re - occurring when the system restarts after a few attempts also. and I look in Device Manager and I see that my other card video (nvidia) is missing from the list. but then returns after a few stops more or less.

ASUS k55

all stock, nothing has changed...

Hello

c:\windows\system32\drivers\sptd.sys is pass it through Direct host SCSI - Daemon Tools (called BSOD issues). Please remove it as soon as POSSIBLE with the uninstall tool - http://www.duplexsecure.com/en/downloads

Kind regards

Patrick

Dealing with DRIVER_POWER_STATE_FAILURE BSOD

After playing with some new display monitors, everything has been fine up until a few weeks ago, when I noticed that whenever I want to restart my computer, it would display the restart of the screen for about 10 minutes, then it would display a BSOD with the error being 'DRIVER_POWER_STATE_FAILURE.

Fortunately, after it seems, the system will re-start very well on its own.

Dump file:

http://download1513.mediafire.com/7c4dcdr53qrg/hbru16n6y7i9vzo/040414-38796-01.dmp

Any help and information on why this happens is greatly appreciated.

-Ben

Thank you very much!

9F, {4, 12 c, fffffa8014fb35c0, fffff80402351810} error checking

1 = 0x4

2nd = 12 (time-out in seconds)

Execute! locks to see what is happening:

0: kd >! locks
DUMP OF ALL RESOURCE OBJECTS *.
KD: Scanning of locks which took place...

Resource @ nt! IopDeviceTreeLock (0xfffff80400f47600) shared 1-wire owners
Contention count = 12
Discussions: fffffa8014fb35c0-01<*>
KD: Scanning of locks which took place.

Resource @ nt! PiEngineLock (0xfffff80400f47700) the exclusive property
Contention count = 44
NumberOfExclusiveWaiters = 1
Discussions: fffffa8014fb35c0-01<*>
Threads waiting on exclusive access:
fffffa800ed20a00

0: kd >! thread fffffa8014fb35c0
WIRE Cid 0004.42f0 Teb fffffa8014fb35c0: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) core criticism
Mutant fffffa8009379db8 - owning thread fffffa8014516080
The IRP list:
fffffa8013c0d2c0: (0006, 03e8) flags: Mdl 00000000: 00000000
Borrow not identity
DeviceMap fffff8a00000c2e0
Owning process fffffa8008499040 Image: System
Joint process s/o Image: n/a
Wait start TickCount 1036025 ticks: 19201 (0:00:05:00.015)
Context switch count 302 IdealProcessor: 1 NoStackSwap
Get_user_time 00:00:00.000
KernelTime 00:00:00.000
Win32 Start address nt! ExpWorkerThread (0xfffff80400d07160)
Stack Init fffff880321b1c90 current fffff880321b1040
Basic fffff880321b2000 limit fffff880321ac000 dial 0
Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP RetAddr: Args to child: call Site
fffff880 '321b 1080 fffff804' 00d0c7cb: fffffa80'00000001 00000000'00000000 00000000'00000001 00000000'00000000: nt! KiSwapContext + 0 x 76
fffff880 '321b11c0 fffff804' 00d0b60f: 00000001' fffff880 '022f12e0 00000000' fffff804 00000000' 00000000 00ca 5412: nt! KiCommitThreadWait + 0x23b
fffff880 '321b 1280 fffff880' 023b18dd: fffffa80'09379db8 fffff880 ' fffffa80 00000000' 11022100 00000000' 6f6d4400: nt! KeWaitForSingleObject + 0x1cf
fffff880 '321b 1310 fffff880' 023b7ac5: fffffa80'09379 c 50 fffff880 '321b 1400 fffffa80' 137c0df0 00000000' 00000000: ndis! ndisUnbindProtocol + 0 x 95
"fffff880 '321b 1430 fffff880' 023b943e: fffffa80 ' 11022101 fffffa80'1103 d 101 fffffa80 ' 110221a 0 fffffa80'1103 020 d: ndis! ndisCloseMiniportBindings + 0 x 225
fffff880'321b14f0 fffff880'0239 c 940: fffffa80'110221 has 0 fffffa80 '110221-0 fffffa80' 13c0d2c0 fffffa80'11022050: ndis! ndisPnPRemoveDevice + 0x21e
"fffff880 '321b 1680 fffff880' 0239c6f5: fffffa80 '110221-0 fffffa80 ' 11022050 fffff880' 321b 1760 fffffa80 ' 13c0d200: ndis! ndisPnPRemoveDeviceEx + 0 x 84
fffff880 '321b16b0 fffff880' 023ab685: fffffa80'13c0d2c0 fffff880 '321b 1720 fffffa80' 110221a 0 00000000 00000000': ndis! ndisPnPIrpSurpriseRemoval + 0 x 109
"fffff880 '321b16f0 fffff804' 0105b8f7: fffffa80'11022001 fffffa80 ' 11022050 00000000 00000001' fffff880 ' 009aa180: ndis! ndisPnPDispatch + 0x2ee49
"fffff880'321 b 1750'01177 fffff804 39 d: 00000000 ' 00000017 fffff880 '321b 1819 fffffa80' 0ece6bd0 fffffa80 ' 1103fa10: nt! IopSynchronousCall + 0xc7
"fffff880 '321b17c0 fffff804' 011775e6: fffff8a0 ' 173883 c 0 00000000'00000088 fffffa80 ' 1103fa10 00000000' 00000000: nt! IopRemoveDevice + 0xd9
fffff880'321 b 1880'01177501 fffff804: fffffa80'0ece6bd0 00000000 00000000' fffff8a0 '05dbac01 fffff880' b 321, 1930: nt! PnpSurpriseRemoveLockedDeviceNode + 0xaa
fffff880'321b18d0 fffff804'01177468: 00000000'00000000 00000000'00000000 fffff8a0 '05dbacd0 fffffa80' 0ece6bd0: nt! PnpDeleteLockedDeviceNode + 0x5d
fffff880 '321b 1910 fffff804' 01176bcb: 00000000 00000000' fffff880 '321b1a70 fffff8a0' 06dfed00 00000000'00000003: nt! PnpDeleteLockedDeviceNodes + 0 x 98
fffff880 '321b 1970 fffff804' 010062e5: fffff880'321b1b88 00000000 00000000' fffff8a0 ' 16893700 fffff8a0' 00000000: nt! PnpProcessQueryRemoveAndEject + 0x2c3
fffff880'321b1ae0 fffff804'01069346: fffff8a0 173883 c 0 00000000'00000000 00000000'00000001 00000580'00000000: nt! PnpProcessTargetDeviceEvent + 0x9d
"fffff880 '321b1b20 fffff804' 00d072a1: fffffa80 '14fb35c0 fffff8a0' 06dfed00 fffff804 ' c 0106905 fffffa80 ' 14126ca 0: nt! PnpDeviceEventWorker + 0x2ea
fffff880 '321b1b80 fffff804' 00c9bfd9: fffffa80 ' 14a3e630 00000000'00000080 fffff804'00 d 07160 fffffa80 ' 14fb35c0: nt! ExpWorkerThread + 0 x 142
fffff880 '321b1c10 fffff804' 00d507e6: fffff880'009aa180 fffffa80 '14fb35c0 fffffa80' 08495b 00 fffffa80'08499040: nt! PspSystemThreadStartup + 0 x 59
fffff880'321b1c60 00000000' 00000000: fffff880 '321b 2000 fffff880' 321ac000 00000000'00000000 00000000'00000000: nt! KiStartSystemThread + 0x16

We have a list of the IORP and a bit of a more informative text in the stack. We can see some NDIS calls, so this may indicate that we are dealing with something of associated network. The driver Interface specification NDIS (Network) is an application programming interface (API) for network (NIC) interface cards. The NDIS form the logical link control sublayer (LLC), which is the top layer of the OSI (Layer 2) data link layer. Therefore, the NDIS acting as interface between the sublayer Media Access Control (MAC), which is the bottom layer of the data link layer, and the network layer (Layer 3).

The NDIS is a library of functions often referred to as a "wrapper" that hides the underlying complexity of the NIC hardware and serves as a standard interface for pilots of level 3 network protocol and at the hardware level MAC drivers. Another common LLC is the Data-Link Interface ODI (Open).

Let's go and take a look at the IRP in the discussion thread:

0: kd >! fffffa8013c0d2c0 PRI 7
IRP is active with 3 batteries 3 is current (= 0xfffffa8013c0d420)
No Mdl: No system buffer only: thread fffffa8014fb35c0: Irp stack trace.
Flags = 00000000
ThreadListEntry.Flink = fffffa8014fb3990
ThreadListEntry.Blink = fffffa8014fb3990
IoStatus.Status = 00000000
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = fffff880321b1780
UserEvent = fffff880321b1790
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000
UserBuffer = 00000000
& Tail.Overlay.DeviceQueueEntry = fffffa8013c0d338
Tail.Overlay.Thread = fffffa8014fb35c0
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = 00000000
Tail.Overlay.ListEntry.Blink = 00000000
Tail.Overlay.CurrentStackLocation = fffffa8013c0d420
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
cmd flg cl device file completion-context
[0, 0] 0 0 00000000 00000000 00000000 - 00000000

Args: 00000000 00000000 00000000 00000000
[0, 0] 0 0 00000000 00000000 00000000 - 00000000

Args: 00000000 00000000 00000000 00000000
> [1B, 17] 0 fffffa8011022050 0 00000000 00000000 - 00000000
\Driver\vwifimp
Args: 00000000 00000000 00000000 00000000
IO to check information:
No information available - the auditor is probably disabled

^^ Microsoft Virtual WiFi Miniport driver.

We will now go ahead and start! devstack the address pinned to vwifimp.sys:

0: kd >! devstack fffffa8011022050
! DevObj! DrvObj! DevExt ObjectName
> fffffa8011022050 \Driver\vwifimp fffffa80110221a0 NDMP22
fffffa801103fa10 \Driver\vwifibus fffffa8011057c40 00000090
! DevNode fffffa800ece6bd0:
DeviceInst is ' {5d624f94-8850-40c3-a3fa-a4fd2080baf3} \vwifimp_wfd\5&2032a077&0&02»
ServiceName is "vwifimp".

^^ Here we see also mention of virtual WiFi Bus driver.

-------------------

1. with all this said, please remove and replace Kaspersky with 8 built-in Windows Defender for purposes of troubleshooting Windows temporary, as it is most likely originally NETBIOS conflicts:

Kaspersky - remove http://support.Kaspersky.com/common/service.aspx?El=1464

Windows Defender (how put on after the withdrawal)- http://www.eightforums.com/tutorials/21962-Windows-Defender-turn-off-Windows-8-a.html

2 in your list of drivers loaded, dtsoftbus01.sys figure who is the driver for Daemon Tools. Daemon Tools is a very popular cause of BSOD in 7/8 base systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Kind regards

Patrick

DRIVER_POWER_STATE_FAILURE BSOD when running low on battery and out of hibernation

I have 13 Duo Sony laptop and Windows 8 gives BSOD when it hibernates after critical battery action and I try to turn it on by connecting the power adapter. I suspect a driver is a problem. Can someone identify the driver from the memory dump?

Here is the address in the dump file: http://sdrv.ms/18jx5ss

Hello

The attached file of the DMP is to bug checking DRIVER_POWER_STATE_FAILURE (9f) .

This bug check indicates that the driver is in an inconsistent or invalid power state.

By default it is failing pci.sys (NT Plug - and - Play PCI enumerator) that is NOT the real cause and is being blamed by something else.

If we run one! IRP on the 4th parameter of the bug check (IRP address blocked), we get the following:

[16, 0] 0 fffffa8007f09060 0 fffff88003826c48 00000000-fffff880009869f0
ERROR: Module load completed but symbols can be loaded for c:\windows\system32\drivers\sptd.sys
\Driver\pci dxgkrnl! DpiFdoPowerCompletionRoutine
Args: 00000000 00000000 00000000 00000003
> [16, 2] e1 0 fffffa8008dbb040 fffff80247fac830-fffffa8017f3af08 00000000 success error cancel pending
ERROR: The symbol file is not found. Defaulted to export symbols for igdkmd64.sys -.
\Driver\igfx nt! PopRequestCompletion

From the above, we can see three things. For me, it is very problematic and we will address as soon as POSSIBLE. However, the other two are small and may not even be a contributing factor, but let's take care of it without worrying.

c:\windows\system32\drivers\sptd.sys is pass it through the Direct SCSI host - Daemon Tools (BSOD problems with Win 7 and 8 in particular.

Remove as soon as POSSIBLE with the uninstaller - http://www.duplexsecure.com/en/downloads

dxgkrnl.sys is the core of DirectX and works hand in hand with next igdkmd64.sys which is Intel Graphics driver.

Make sure you have the latest video card drivers. If you are already on the latest graphics card drivers, uninstall and install a version or a few versions behind the last to make sure this isn't a last number one driver. If you have already experienced with the driver of the card later and earlier versions, please try the driver beta for your card.

Kind regards

Patrick

DRIVER_POWER_STATE_FAILURE - 0x0000009f - ntoskrnl.exe

I am facing to the BSOD a couple times a day. Each time the blue screen appears the laptop shows "DRIVER_POWER_STATE_FAILURE" then restarts again, once rebooted everything looks normal as usual.

The system is Windows 8, X 64. The properties of the dmp is illustrated below:

Chain: DRIVER_POWER_STATE_FAILURE checking bug

The bug check code: 0x0000009f

Parameter 1: 00000000'00000003

Parameter 2: fffffa80'04df9880

Parameter 3: fffff803'fc5d2b40

Parameter 4: fffffa80'05ad4290

Plant address: ntoskrnl.exe + 5 has 440

And my minidump link is

https://SkyDrive.live.com/redir?RESID=F8ACA593B484724A! 1437 & authkey =! AI3q_oKn6TnvVOQ

Hello

The attached file of the DMP is to bug checking DRIVER_POWER_STATE_FAILURE (9f) .

This bug check indicates that the driver is in an inconsistent or invalid power state.

If we run one! IRP on the 4th parameter of the bug check (IRP address blocked), we get the following:

> [16, 2] e1 0 fffffa8006d36040 fffff803fd551830-fffffa800a43e690 00000000 success error cancel pending
\Driver\nvlddmkm nt! PopRequestCompletion

nvlddmkm nvlddmkm.sys = which is the video driver nVidia.

Make sure you have the latest video card drivers. If you are already on the latest graphics card drivers, uninstall and install a version or a few versions behind the last to make sure this isn't a last number one driver. If you have already experienced with the driver of the card later and earlier versions, please try the driver beta for your card.

Kind regards

Patrick

Windows 8 blue screen - DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe

I have a new Sony Vaio Pro and have experienced outages of system 3 times. All the accidents that happened after I've restored from hibernation and were related to the bug check DRIVER_POWER_STATE_FAILURE. After the first two accidents, I ran Sony diagnostics on the memory and hard drive SSD and they passed the test. I even sent my Vaio Pro to the repair depot to Sony for a test on the memory, hard drive and other hardware and they all passed.

I found my Vaio Pro last Wednesday and updated the Windows 8 from scratch. This morning, after the resumption of hibernation, I realized my Bluetooth mouse did not work. So I stop the laptop hoping a restart could solve the problem. However, it took almost 5 minutes before they would stop and restart Windows gave a warning:

"Experienced problem with closed Windows. Your PC fell on problem. This problem case your PC to restart.

BlueScreen Viewer it pointing DRIVER_POWER_STATE_FAILURE caused by driver ntoskrnl.exe.

BlueScreen details as follows:

A problem has been detected and Windows has shut down to prevent damage to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

DRIVER_POWER_STATE_FAILURE

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is installed correctly.

If it is a new installation, ask your hardware manufacturer or software, the Windows updates, you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable the BIOS memory options such as implementing caching or shading.

If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options and then

select Safe Mode.

Technical information:

STOP: 0X0000009F (0X000000000000012C, 0XFFFFFA80196707C0, 0 X 0000000000000004, 0XFFFFF880009EC810)

Ntoskrnl.exe - address 0xfffff80189072106 base at 0xfffff8018901e000 DateStamp

0x51a966cd

Here's my minidump file:

https://DL.dropboxusercontent.com/u/1928780/093013-7531-01.dmp

File Msinfo32.NFO:

https://DL.dropboxusercontent.com/u/1928780/Msinfo32.nfo

Dump file memory (do not know why this file is nearby big 550MO):

https://DL.dropboxusercontent.com/u/1928780/memory.dmp

p.s. I think this may have something to do with my Bluetooth driver I had experienced many times the Bluetooth driver has been disabled by Windows and the event viewer reported "the Local Bluetooth is not indeterminate way and will not be used. The driver has been unloaded. "

Thanks in advance,

William

Hi William,.

The attached file of the DMP is the error checking DRIVER_POWER_STATE_FAILURE (9f) .

This bug check indicates that the driver is in an inconsistent or invalid power state.

9F, {4, 12 c, fffffa80196707c0, fffff880009ec810} error checking

Parameter 1 of the bugcheck is 4 , which indicates that the transition of power over waiting to synchronize with the Pnp subsystem.

The 2nd setting is 12 c , which indicates that it is exceeded for a total of 12 seconds.

By default, the crash dump is failing UsbHub3.sys who is the pilot of HUB-USB3 (System driver and not the true cause, and is due to the fault by something else).

If we look further into the dump:

ERROR: Module load completed but symbols could not be loaded for btmhsf.sys

FAILURE_BUCKET_ID: 0x9F_4_btmhsf_IMAGE_UsbHub3.sys

Implicit thread is now fffffa80 196707 c 0

^^ If we run one! thread on the address fffffa80 196707 c 0:

Child-SP RetAddr: Args to child: call Site
fffff880 '20b42f20 fffff801' 890bb7cb: fffffa80'00000001 00000000'00000000 00000000'00000003 00000000'00000000: nt! KiSwapContext + 0 x 76
fffff880 '20b 43060 fffff801' 890ba60f: fffffa80'18b23ef8 fffff880 '0115a 178 00000000 00000000' fffff880' 0622a 202: nt! KiCommitThreadWait + 0x23b
fffff880'20 b 43120 fffff880'06114700: fffffa80 '16115fd8 fffff880' 00000001 00000000' 00000000 00000000'00000000: nt! KeWaitForSingleObject + 0x1cf
"fffff880 '20b431b0 fffff880' 06117ef0: 00000000 ' 00000018 fffff880 ' 0622a2f8 00000000'00000000 00000000'00000018: btmhsf+ 0 x 33700
fffff880 '20b431f0 fffff880' 060fb1e4: fffffa80'17 has 00030 fffff880 '20b433b0 fffff880' 0622a2f8 00000000' 00000000: btmhsf+ 0x36ef0
fffff880 '20b 43260 fffff880' 060e2b84: 0000057f 'e9eaddd8 00000000' 00000127 fffff880 '0622a2f8 fffff880' 0115 has 178: btmhsf+ 0x1a1e4
fffff880 '20b432b0 fffff880' 060e2cce: 00000000'00000008 fffff880 '20b 43370 00000000'00000008 fffff880' 20b 43378: btmhsf+ 0x1b84
fffff880 '20b432e0 fffff880' 0114ecb0: fffffa80'16153860 00000000 00000000' fffff8a0 '04c3a748 fffff801' 89403cfe: btmhsf+ 0x1cce
"fffff880 '20b 43310 fffff880' 010e881d: 00000000 ' 00000127 fffff880 ' 20b433b0 00000000'00000119 fffffa80'16153860: Wdf01000! FxPkgPnp::PnpEventSurpriseRemoveIoStarted + 0x2c
"fffff880 '20b 43340 fffff880' 010e9032: fffffa80 ' 16153980 fffffa80' 16153988 fffffa80 ' 16153860 fffff880 ' 20b434c0: Wdf01000! FxPkgPnp::PnpEnterNewState + 0x1a1
"fffff880 '20b433e0 fffff880' 010e8cdd: 00000000 ' 00000000 fffff880 ' 20b434c0 fffffa80 ' 16153970 fffffa80' 16153860: Wdf01000! FxPkgPnp::PnpProcessEventInner + 0 x 122
fffff880'20 b 43450 fffff880'0114 701 d: 00000000 00000000' fffffa80 '16153860 fffff880' 00000000 00000000 00000000': Wdf01000! FxPkgPnp::PnpProcessEvent + 0x18d
fffff880 '20b434f0 fffff880' 010d1ecf: fffffa80'16141 b 30 fffff880 '20b 43570 00000000 00000000' fffffa80' 1615d1d0: Wdf01000! FxPkgFdo::_PnpSurpriseRemoval + 0 x 25
fffff880 '20b 43520 fffff880' 010c99da: fffffa80'197 b 9010 fffffa80 '197b 9010 fffffa80' 197b 9010 00000000 00000000': Wdf01000! FxPkgPnp::Dispatch + 0x18f
"fffff880 '20b 43580 fffff880' 010c9aa6: fffffa80' 197b 9010 00000000'00000005 fffffa80 ' 161531 c 0 fffff880 ' 062fca20: Wdf01000! FxDevice::Dispatch + 0x19a
fffff880 '20b435c0 fffff880' 062e3cbe: fffffa80 '197b 9010 00000000 00000005' fffffa80' 1615e190 00000000' 00000000: Wdf01000! FxDevice::DispatchWithLock + 0xa6
fffff880 '20b 43600 fffff880' 062e3484: fffffa80 '197b 9010 00000000 00000000' fffffa80' 1615e190 00000000' 00000000: bthport! BthDefaultPnpHandler + 0x2a
fffff880 '20b 43630 fffff880' 062e2cc1: fffffa80 ' 1615e190 fffff880 '062fca17 fffffa80' 1615e190 fffffa80 ' 197b 9010: bthport! BthHandleSurpriseRemoval + 0xc4
fffff880 '20b436b0 fffff880' 062e2b04: fffffa80' 197b 9010 00000000'00000701 fffff880 '062fca20 fffff880' 20b 43800: bthport! BthHandlePnp + 0x16d
fffff880 '20b 43700 fffff801' 8940a8f7: fffffa80 '1615e040 00000000' c00000bb 00000000 00000000' fffff880' 00a 82180: bthport! BthDispatchPnp + 0 x 68
"fffff880'20 b 43750 89526 fffff801 39 d: 00000000 ' 00000017 fffff880 ' 20b 43819 fffffa80 ' 16137710 fffffa80' 16137060: nt! IopSynchronousCall + 0xc7
fffff880 '20b437c0 fffff801' 895265e6: fffff8a0 ' 04069710 00000000'00000308 fffffa80' 16137060 00000000 00000000': nt! IopRemoveDevice + 0xd9
fffff880'20 b 43880 fffff801'89526501: fffffa80'16137710 00000000 00000000' fffff8a0 '0c432a01 fffff880' 20b 43930: nt! PnpSurpriseRemoveLockedDeviceNode + 0xaa
fffff880'20b438d0 fffff801'89526468: fffff8a0 00000000'00000000 00000000'00000000 ' 0c432a70 fffffa80'16137710: nt! PnpDeleteLockedDeviceNode + 0x5d
fffff880 '20b 43910 fffff801' 89525bcb: 00000000 00000000' fffff880 '20b43a70 fffff8a0' 0b89e6f0 00000000'00000005: nt! PnpDeleteLockedDeviceNodes + 0 x 98
fffff880 '20b 43970 fffff801' 893b52e5: fffff880'20b43b88 00000000 00000000' fffff8a0 ' 05764100 fffff8a0' 00000000: nt! PnpProcessQueryRemoveAndEject + 0x2c3
fffff880'20b43ae0 fffff801'89418346: fffff8a0'04069710 00000000'00000000 00000000'00000001 00000000'00000000: nt! PnpProcessTargetDeviceEvent + 0x9d
"fffff880 '20b43b20 fffff801' 890b62a1: fffffa80 ' 196707 c 0 fffff8a0 ' 0b89e6f0 fffff801 ' 8941805 c fffffa80' 16748130: nt! PnpDeviceEventWorker + 0x2ea
"fffff880 '20b43b80 fffff801' 8904afd9: fffffa80 ' 00180000 00000000 00000080' fffff801 ' b 890, 6160 fffffa80 196707 c 0: nt! ExpWorkerThread + 0 x 142
fffff880 '20b43c10 fffff801' 890ff7e6: fffff880 ' 00a 82180 fffffa80 ' 196707 c 0 fffffa80 ' 06741b 00 fffffa80' 06765940: nt! PspSystemThreadStartup + 0 x 59
fffff880'20b43c60 00000000' 00000000: fffff880 '20b 44000 fffff880' 20b3e000 00000000'00000000 00000000'00000000: nt! KiStartSystemThread + 0x16

We can see the various routine calls BTHUSB Device bthport.sys (Bus Bluetooth driver) who then finally enter various before btmhsf.sys some error checking.

btmhsf.sys is the Intel Proset Bluetooth HighSpeed filter driver and probably the culprit here. Update this driver ASAP - http://downloadcenter.intel.com/default.aspx?iid=gg_support-EN_01+home_downloadctr
or uninstall it if you do not plan to use BlueTooth.

---------------------------------------------------------------------

If after doing the above, you are still blocked, remove and replace AVG with built-in Windows Defender from Windows 8 for temporary troubleshooting purposes:

-AVG removal tool http://www.Avg.com/us-en/utilities

In addition, to answer your question as to why the MEMORY. DPM is so important because it's a dump of memory rather than a small kernel. Kernel memory dumps contain all the kernel memory was working with and that was in use at the time of the accident, that is why it is larger and provides much more information.

Kind regards

Patrick

BSOD on Satellite L850

Hi guys,.
I'm having these BSOD with bug check code "DRIVER_POWER_STATE_FAILURE", I tried to update my BIOS and other pilots, but the guys at Microsoft say that I need to update my driver of power, but I can't find them in
"toshiba - tro.de.
My specs are:
Toshiba Satellite L850 - B452 (PSKG8V) with Intel core i7-3630QM.
This is one of the mini dumps, the rest are in this zip file:
https://www.mediafire.com/?qhvafd91r34awzx
==================================================
Dump file: 042614-58609 - 01.dmp
Crash time: 26/04/2014 11:39:18
Bug Check String: DRIVER_POWER_STATE_FAILURE
Bug check code: 0x0000009f
Parameter 1: 00000000'00000003
Parameter 2: ffffe001'eff448e0
Parameter 3: fffff801'61193930
Parameter 4: ffffe001'dbff9550
Caused by the driver: ntoskrnl.exe
Caused by the address: ntoskrnl.exe + 153fa0
File description: NT kernel & system
Product name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File version: 6.3.9600.17041 (winblue_gdr.140305 - 1710)
CPU: x 64
Plant address: ntoskrnl.exe + 153fa0
Stack address 1:
The stack address 2:
Address 3 the battery:
Computer name:
Full path: C:\WINDOWS\Minidump\042614-58609-01.dmp
Number of processors: 8
Main version: 15
Minor Version: 9600
Size of the dump file: 251 790
Dump of file time: 26/04/2014 11:40:17
==================================================

Hello

All the drivers for your model mobile, you can find on http://www.toshibamea.com/en/Download-Files

Your model of PSKG8V is in the list. Maybe this silly now, but I do not know what is the conductor of electricity. If your laptop comes with original preinstalled OS I recommend you set the BIOS to default settings and install original recovery image.
After doing this, you can test the functionality with the factory settings.

Post comments please.

BSOD on shutdown/reboot bug check 9f

I get d BSOD saying DRIVER_POWER_STATE_FAILURE
all d minidumps are in given link
I've updated all my drivers for a version more recent but problem still persits
Product F2C09PA #ACJ number

Operating system: Windows 8.1 64bits

Report Viewer blue screen:

062814-35812 - 01.dmp 2014/06/28 02:14:47 DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000 00000003' ffffe001 '46cbe730 fffff802' e7dfe930 ffffe001'4e104250 ntoskrnl.exe ntoskrnl.exe + x 64 ntoskrnl.exe 153fa0 + 153fa0 C:\WINDOWS\Minidump\062814-35812-01.dmp 4 15 9600 706 528 2014/06/28 09:25:09
062714-36859 - 01.dmp 2014/06/27 20:20:55 ffffe000 'eb7ed060 ffffd001' 00000000'00000003 0x0000009f DRIVER_POWER_STATE_FAILURE c0fec930 ffffe000'fabc76f0 ntoskrnl.exe ntoskrnl.exe + x 64 ntoskrnl.exe 153fa0 + 153fa0 C:\WINDOWS\Minidump\062714-36859-01.dmp 4 15 9600 722 816 2014/06/27 21:42:43
062614-49375 - 01.dmp 26/06/2014-15:12:54 fffff802 '5249ce70 fffff802' 00000000'00000008 0x0000007f UNEXPECTED_KERNEL_MODE_TRAP 5248df40 fffff802'4f6ece94 ntoskrnl.exe ntoskrnl.exe + x 64 ntoskrnl.exe 153fa0 + 153fa0 C:\WINDOWS\Minidump\062614-49375-01.dmp 4 15 9600 288 768 26/06/2014-15:14:45
062614-46765 - 01.dmp 26/06/2014-15:06:15 UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000'00000008 '28df5e70 fffff803' fffff803 28ddff60 fffff803'26ef3f2c werkernel.sys werkernel.sys + a238fe70 x 64 ntoskrnl.exe + 153fa0 C:\WINDOWS\Minidump\062614-46765-01.dmp 4 15 9600 289 632 26/06/2014-15:07:58

Minidump:

Debug version of Microsoft Windows (R) 6.3.9600.17029 X 86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading dump file [E:\ImageDiags_1.8.56.0\Minidumps\062614-41046-01.dmp]
The mini kernel dump file: only registers and the trace of the stack are available

Symbol search path is: * invalid *.
****************************************************************************
* Loading of the symbol may be unreliable without a symbol search path. *
* Use .symfix to get the debugger to choose a symbol path. *
* After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
* *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable. *
* using the argument y < symbol_path > then to start the debugger. *
* using the .sympath and .sympath + *.
*********************************************************************
Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (4 procs) free x 64
Product: WinNt, suite: TerminalServer personal TerminalServer
By: 9600.17085.amd64fre.winblue_gdr.140330 - 1035
Computer name:
Kernel base = 0xfffff800 '48a7f000 PsLoadedModuleList = 0xfffff800' 48d492d0
The debugging session: Thu Jun 26 19:28:32.858 2014 (UTC + 05:30)
System Uptime: 0 days 0:57:48.770
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
* *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable. *
* using the argument y < symbol_path > then to start the debugger. *
* using the .sympath and .sympath + *.
*********************************************************************
Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Loading the kernel symbols
...............................................................
................................................................
............................................................
Loading user symbols
Loading unloaded module list
...........

Summary of the symbol load error *.
Name of the module error
Ntoskrnl the system cannot find the specified file

You can solve most symbol related issues by turning the symbol loading diagnostics (! sym noisy) and repeating the command that caused the symbols to load.
You should also check that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************

Use! analyze - v to obtain detailed debugging information.

9F error checking, {3, ffffe001b66a2060, ffffd000c51e1930, ffffe001ca506790}

The kernel symbols are FALSE. Correct symbols to do the analysis.

*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: NT! _DEVICE_OBJECT *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! TRIAGE_9F_POWER *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _IO_STACK_LOCATION *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _DEVICE_OBJECT *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
Probably caused by: ntoskrnl.exe (nt + 153fa0)

Follow-up: MachineOwner
---------

Rather you should mention that I don't have symbols told me how to get them

and this link Forum called youtube video and youtube video was useless by itself it did not show how to solve my problem.

But in any case I solved it and here is how I did it

1. restored by computer laptop to an earlier time of the first restore point was himself on the day where the problem started, but nevertheless I did

2 uninstalled all my network drivers and all tha application uses internet (Hotspot service as conectify) except of WEb browsers

3. in the event viewer WIndows stopped all service ontenet which appear to come from a third party application or so.

4. voila it worked

5. thanks for your useless highly appreciated <

DRIVER_POWER_STATE_FAILURE 00000000'00000003

Similar Questions

Maybe you are looking for