Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Power State Failures


  • Please log in to reply
17 replies to this topic

#1 ky234vell

ky234vell

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 26 February 2018 - 11:20 PM

Been getting driver power state failures for about a month now.  BlueScreenView says caused by driver: ntoskrnl.exe
 
Did a little sleuthing and think perhaps it's due to a corrupted or outdated BIOS device driver?  Wanted to check with an expert before I did something potentially stupid, thanks in advance.
 
 

Attached Files



BC AdBot (Login to Remove)

 


#2 Shellfishclive

Shellfishclive

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:England
  • Local time:12:58 AM

Posted 27 February 2018 - 04:16 AM

Updating your drivers and flashing your BIOS are always good ways to solve a BSOD. I would try that first, unfortunately the ntoskrnl is a very common cause of BSOD so it's hard to actually pin down what is causing it as any power failure is likely to show this message, is there anything in your event log that you could share?



#3 ky234vell

ky234vell
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 27 February 2018 - 04:54 AM

I can tell you that ever since I began using this computer (about 6 months ago) I've been getting event 37 kernel-processor-power warnings.
 
Everything is seemingly running fine, it just hangs on all power state changes where I then must do a forced shutdown.
 
As far as the event logs, I'm not exactly a Windows Event Viewer whisperer (I suspect few are).  Is there a way I can share my Event Viewer logs?


#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:58 PM

Posted 28 February 2018 - 03:19 PM

There weren't any dump files in the uploaded reports. Have you been using a disk cleanup utility like CCleaner? If so, please stop that, it deletes all the dump files. Please see this topic to check if Windows is configured correctly for minidumps: https://www.bleepingcomputer.com/forums/t/576615/bsods-but-no-dump-files/


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 ky234vell

ky234vell
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 28 February 2018 - 11:17 PM

They are there, but I think Windows is overwriting or deleting prior dumps.  Here was my last:

 

On Wed 2/28/2018 9:32:18 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022818-28562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430) 
Bugcheck code: 0x9F (0x3, 0xFFFFB109B13FD060, 0xFFFFF802E505D8F0, 0xFFFFB109B62CCB40)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time. 
This is likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
 
 
 
On Wed 2/28/2018 9:32:18 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!ObIsKernelHandle+0xF77) 
Bugcheck code: 0x9F (0x3, 0xFFFFB109B13FD060, 0xFFFFF802E505D8F0, 0xFFFFB109B62CCB40)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time. 
This is likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


#6 ky234vell

ky234vell
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 01 March 2018 - 03:14 AM

Here's some more information then from one of the minidumps for your viewing pleasure:

 

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffb109b13fd060, Physical Device Object of the stack
Arg3: fffff802e505d8f0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffb109b62ccb40, The blocked IRP
 
Debugging Details:
------------------
 
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
 
DRVPOWERSTATE_SUBCODE:  3
 
IMAGE_NAME:  pci.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  43aeedb9
 
MODULE_NAME: pci
 
FAULTING_MODULE: fffff80a1c2f0000 pci
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  0x9F
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  2
 
STACK_TEXT:  
fffff802`e505d8b8 fffff802`e2e36387 : 00000000`0000009f 00000000`00000003 ffffb109`b13fd060 fffff802`e505d8f0 : nt!KeBugCheckEx
fffff802`e505d8c0 fffff802`e2e36292 : ffffb109`b918ad90 fffff802`e19fd180 00000000`000000a1 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xeb
fffff802`e505d920 fffff802`e2cc48a3 : fffff802`e19fd180 00000000`00000000 fffff802`e505db18 00000000`00000000 : nt!PopIrpWatchdog+0x22
fffff802`e505d970 fffff802`e2cc593d : 00000000`0000001a 00000000`008cb501 00000000`0026a74f fffff802`e19fd180 : nt!KiProcessExpiredTimerList+0x153
fffff802`e505da60 fffff802`e2d78d1a : 00000000`00000000 fffff802`e19fd180 00000000`001a6f79 fffff802`e3019380 : nt!KiRetireDpcList+0x43d
fffff802`e505dc60 00000000`00000000 : fffff802`e505e000 fffff802`e5058000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
FAILURE_BUCKET_ID:  X64_0x9F_3_Netwbw02_IMAGE_pci.sys
 
BUCKET_ID:  X64_0x9F_3_Netwbw02_IMAGE_pci.sys
 
Followup: MachineOwner


#7 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:58 PM

Posted 01 March 2018 - 04:05 PM

Thanks. It would be nice if you can zip and attach the dump file too. :) Nevertheless,

FAILURE_BUCKET_ID:  X64_0x9F_3_Netwbw02_IMAGE_pci.sys

your Intel® Dual Band Wireless-AC 3160 driver appears to be at fault. Hence I would suggest you update it: https://support.toshiba.com/drivers/?locale=en_AU&source=tap This link is for TOSHIBA's support page, you'll have to find and search for the driver yourself as I can't find your model number from SystemInfo. (The model number is usually on a sticker on the bottom of the laptop.)


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#8 ky234vell

ky234vell
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 01 March 2018 - 05:42 PM

I'm assuming this is the driver I need: https://downloadcenter.intel.com/download/27475/Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-10?product=75442  Am I cool using device manager to just update the driver or do I have to uninstall the driver then do a manual install?    



#9 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:58 PM

Posted 01 March 2018 - 05:53 PM

No, you shouldn't use Device Manager to update it; sometimes Window messes up and finds the wrong driver (rarely but it does happen). Where did you get that Intel link for? Try to download the driver from TOSHIBA, as the version listed by them is the "approved" version.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#10 ky234vell

ky234vell
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 01 March 2018 - 06:21 PM

I didn't see that specific driver on Toshiba's website.  This is my satellite # S55T-B5282.  Should I use the driver named Intel Wireless Display? 



#11 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:58 PM

Posted 01 March 2018 - 06:26 PM

use this

 

http://files.ecp.toshiba.com/2016/08/19/1007/54/tca0122900b.exe


Edited by bwv848, 01 March 2018 - 06:27 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#12 ky234vell

ky234vell
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 01 March 2018 - 07:07 PM

When I executed the file a little Intel window popped up and said:

 

Installation Blocked: A newer product version is already installed.



#13 HyperHenry

HyperHenry

  • Members
  • 775 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Iowa (but travel)
  • Local time:06:58 PM

Posted 01 March 2018 - 10:09 PM

Please go back to the Device Manager and uninstall the driver. Then follow the instructions below to manually install it.

 

Let's try this. Go to Control Panel, click on Device Manager, Then on your display adapter, right click and choose Update Driver. Then click on Browse my computer for driver software. Now click Let me pick from a list of available drivers on my computer. You should find the driver you downloaded. Click on it and then Next. This should properly install the driver.



#14 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:58 PM

Posted 01 March 2018 - 11:21 PM

When I executed the file a little Intel window popped up and said:
 
Installation Blocked: A newer product version is already installed.

We'll need to uninstall the old driver first then. Ensure you have the driver installer downloaded to your machine first. Create a system restore point first and go to "Uninstall a program" in the Control Panel (Programs and Features) and uninstall something of the name "Intel PROSet" or similar. (I can't give you the actual name, it may differ from machine to machine.) Reboot and try installing the drivers again.

 

The reason why I'd like us to try an older driver is that network drivers are quite fiddly. I've found that it's best to use the drivers listed on your motherboard's website; sometimes the ones from Intel give trouble.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#15 ky234vell

ky234vell
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 01 March 2018 - 11:51 PM

Okay, I'll try that momentarily, one question though.  Does it matter that my OS (Windows 10) or my laptop's model # isn't listed as being compatible with that driver you provided?  http://www.helpjet.net/Fs-19227902-52205994-92757294.html






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users