BSOD when restarting windows after exteneded user session.

Anonymous
2014-01-30T10:12:20+00:00

My PC has BSOD'ed on me several times when I tell it to restart windows. It keeps giving the DRIVER_POWER_STATE_FAILURE error in the BSOD.

I have traced the problem back to NTOSKRNL.EXE. the address in the stack is ntoskrnl,exe+78a8a. both times windows crashed during during the shutdown phase of a windows restart.

Full error:

ntoskrnl.exe ntoskrnl.exe+78a8a fffff80003408000 fffff800039ed000 0x005e5000 0x521ea035 8/28/2013 5:13:25 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.18247 (win7sp1_gdr.130828-1532) Microsoft Corporation C:\windows\system32\ntoskrnl.exe 

Bug Check Code: 0x1000009f

I am not sure why my system is BSOD'ing on me, much less why ntoskrnl.exe is causing it. I'm not running or doing anything strange on my machine. Just BIONC (Seti@Home), games and the occasional document. I have already run SFC, as well as chkdsk, and the checksur utility, but nothing was found wrong. I ran a full scan using MSE and Malwarebytes, and came up clean there too. I want to know if this error's cause lies in the hardware or if windows is just complaining because I have had it running fro so long with out a restart.

If someone wants to look at the minidump files made by my system, let me know and I will post them to my skydrive. when I examined the minidumps using bluescreenview, only ntoskrnl.exe was highlighted in red. I can discern no other cause of this problem.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

58 answers

Sort by: Newest
  1. Anonymous
    2014-01-30T21:41:43+00:00

    Hi,

    BlueScreenView is not as accurate for the cause as WinDBG. However it is excellent for checking

    the driver information in the lower panel.

    Check with Nvidia and the other device makers - as suggested above run DriverView - set VIEW

    to Hide Microsoft drivers - update those without Dump in their names. There are likely to be a

    lot of them available which are not at Toshiba. This is a Toshiba laptop I am on now.

    As Patrick indicated DiskKeeper has been known to cause issues. I doubt it is causing this one

    however it is possible.

    My general feeling is the real issue is the video hardware just can't play some games which is

    normal for most laptops not actually built specifically for gaming.

    After you do all the driver updates run Driver Verifier as Patrick and I have both suggested.

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-01-30T21:30:27+00:00

    Thanks for the DMP files!

    As Rob mentioned, the attached DMP files of the DRIVER_POWER_STATE_FAILURE (9f) bug check.

    *This bug check indicates that the driver is in an inconsistent or invalid power state.*As opposed to your traditional *9F bug check that contains a blocked IRP on the 4th parameter of the bug check held by a driver, this *9F indicates that there is a lock being caused by a driver.

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

    1. sptd.sys is not a system driver, I don't know where you got that information from. sptd.sys is listed and loaded in your modules list; SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win 7 and 8). Please remove it ASAP with the uninstaller tool - http://www.duplexsecure.com/en/downloads
    2. Diskeeper is known to cause crashes, please remove it for troubleshooting purposes.
    3. regi.sys - Mon Apr 16 11:19:10 2007

    ^^ InterVideo regi.sys driver, dated from 2007. Fairly dated, so please go ahead and remove Intervideo for troubleshooting purposes.

    1. Enable Driver Verifier if you're crashing after all of the above so we can get more information:

    Driver Verifier:

    What is Driver Verifier?

    Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

    Before enabling Driver Verifier, it is recommended to create a System Restore Point:

    Vista - START | type rstrui - create a restore point

    Windows 7 - START | type create | select "Create a Restore Point"

    Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

    How to enable Driver Verifier:

    Start > type "verifier" without the quotes > Select the following options -

    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    • Special Pool
    • Pool Tracking
    • Force IRQL Checking
    • Deadlock Detection
    • Security Checks (Windows 7 & 8)
    • DDI compliance checking (Windows 8)
    • Miscellaneous Checks
    1. Select  - "Select driver names from a list"
    2. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    3. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
    4. Click on Finish.
    5. Restart.

    Important information regarding Driver Verifier:

    • If Driver Verifier finds a violation, the system will BSOD.
    • After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

    If this happens, do not panic, do the following:

    • Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    • Once in Safe Mode - Start > Search > type "cmd" without the quotes.
    • To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

    ・    Restart and boot into normal Windows.

    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

    • Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    • Once in Safe Mode - Start > type "system restore" without the quotes.
    • Choose the restore point you created earlier.

    How long should I keep Driver Verifier enabled for?

    It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

    My system BSOD'd, where can I find the crash dumps?

    They will be located in %systemroot%\Minidump

    Any other questions can most likely be answered by this article:

    http://support.microsoft.com/kb/244617

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-01-30T20:26:10+00:00

    I AM NOT overclocking at all, unless you count the i7's built-in turboboost feature as overclocking.


    SPTD.SYS is a system driver. description is SCSI Pass through Direct Host. driver is by Duplex Secure Ltd.


    I do not have Daemon Tool or Alcohol installed.

    bluescreenview (as I already stated) indicates ntoskrnl.exe as the only cause of the crash not ntkrnlmp.exe

    My laptop runs a wide variety of games just fine with out any issues what so ever. this is due to the fact that my unit has a discrete (dedicated) video card with it's own separate memory (although upto 1768Mb of memory can be dynamically shared from system memory using NVidia turbocache )

    My bios and drivers are up to date. there may or may not be issues with my bios, but Toshiba is no longer releasing updating bios/drivers for my unit (even though it is less than 4 years old)

    as the error only occurs after windows has been booted for an extended period when I try to restart, clean booting will not help.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-01-30T20:00:46+00:00

    my computer is a Toshiba P500-ST6844

    I have uploaded the requested files, here is the link

    https://skydrive.live.com/redir?resid=FB6B5D18D0D968B!7738&authkey=!ADxKK5IC_9gKNIU&ithint=folder%2c

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-01-30T19:00:54+00:00

    Hi,

    If you are over-clocking anything STOP!

    A laptop might not be able to play some intense games as it just does not have the video

    horsepower (or other hardware).

    Both minidumps were essentially the same.

    BugCheck 1000009F, {4, 258, fffffa8006d26040, fffff80004d5a510}

    Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )

    ntkrnlmp.exe is a Windows component which means something else drove it into Fault.

    Since there is no definitive help in the minidump you will need to take a broad approach

    and do everything you can to eliminate the issue. What you have already done is a good

    start.

    1. You are running Daemon Tool or Alcohol and SPTD.sys has been known to cause such

    issues. Uninstall them and Remove/Disable SPTD.sys.

    Disable/Remove SPTD.sys

    http://www.duplexsecure.com/en/faq


    2. Check with Toshiba Support, their on-line documentation and drivers, and ask in their

    forums about any known issues. Check for updates to the BIOS, low level chipset drivers,

    and the major on-board and separate device drivers (see driver update methods below).

    BiosVersion = 2.90   

    BiosReleaseDate = 12/15/2010 <- check for updates to the BIOS, low level chipset drivers,

    and the major on-board and separate device drivers.

    SystemManufacturer = TOSHIBA

    SystemProductName = Satellite P500

    SystemVersion = PSPGSU-0Q2012

    BaseBoardManufacturer = TOSHIBA

    BaseBoardProduct = Satellite P500

    Toshiba - Forums

    http://laptopforums.toshiba.com/

    Toshiba - Contacts

    http://www.csd.toshiba.com/cgi-bin/tais/support/jsp/navShell.jsp?cf=su\_contact

    Toshiba - Drivers - navigate to your model

    http://www.csd.toshiba.com/cgi-bin/tais/support/jsp/home.jsp?nav=Download

    Toshiba - Support

    http://www.csd.toshiba.com/cgi-bin/tais/support/jsp/home.jsp


    3. Use the other methods in the troubleshooters below.


    4. AFTER ALL the above if the issue continues run Driver Verifier to see if it can indicate a

    CAUSE (see Driver Verifier methods below - do not run this until after you have done all

    the possible updates and methods previously suggested.)

    =========================================================

    Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't start Windows.

    http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7 

    Check this thread for information using BlueScreenView, MyEventViewer and other methods

    to troubleshoot BlueScreens - top 3 replies.

    http://answers.microsoft.com/en-us/windows/forum/windows\_7-system/sometimes-i-get-a-blue-screen-when-using-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990


    Check with these utilities to see if any information can be gathered : (Be sure to run this since there

    may well be other Bug_Check codes.)

    This is an excellent tool for posting Blue Screen Error Information

    BlueScreenView - Free - scans all your minidump files created during 'blue screen of death' crashes,

    and displays the information about all crashes in one table.

    http://www.nirsoft.net/utils/blue\_screen\_view.html


    MyEventViewer can be checked at the time of the BlueScreen (BSOD) to within a second or so of the

    time of the BSOD to provide more information as to possible cause - see TIP.

    MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.

    TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file -

    set it to a bit before and after the time of the BSOD.

    http://www.nirsoft.net/utils/my\_event\_viewer.html


    AppCrashView - Free - a small utility for Windows Vista and Windows 7 that displays the details of all

    application crashes occurred in your system. The crashes information is extracted from the .wer

    files created by the Windows Error Reporting (WER) component of the operating system every

    time that a crash is occurred. AppCrashView also allows you to easily save the crashes list to

    text/csv/html/xml file.

    http://www.nirsoft.net/utils/app\_crash\_view.html

    ================================

    ================================

    **References to Vista also apply to Windows 7.**This "could" be a power supply problem though it is not the most common cause.

    9f is likely a driver issue. Antivirus/antispware/security programs can also cause these issues.

    Have you added devices lately or updated drivers - be sure to check in Windows Updates to see

    if a driver was updated prior to this occurring. This could also be caused by a loose card or cable

    and even a weak power supply.

    That error means a driver is not handling the power state properly. Check in Control Panel - Device

    Manager to be sure major drivers are not shut off during sleep - double click Display Adapter - NIC

    and WIFI - Sound and others - Power Management tab - uncheck Allow computer to turn off power.

    Maybe only one has an issue.

    Start - type in Search box - MSCONFIG  find at top - Right Click - RUN AS ADMINGeneral Tab - check Diagnostic Start  - APPLY / OK  -  REBOOTTry it now. If it still blue screens think Video Driver. If not think NIC, Wifi, Sound, or......(and it still could be video interacting with something else). See troubleshooter linkabove for my generic driver update methods.MSDN - Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE <-- read this linkhttp://msdn.microsoft.com/en-us/library/ff559329(v=VS.85).aspx

    **** BCCode: 9F  0x0000009F  <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/DRIVER-POWER-STATE-FAILURE-0x0000009F-\*1167.html?order=date


    Driver Verifier can help find some BSOD issues :

    Using Driver Verifier to identify issues with Windows drivers for advanced users

    http://support.microsoft.com/kb/244617 

    How To Troubleshoot Driver Problems in Windows Vista or 7.

    http://www.winvistaclub.com/t79.html 

    Using Driver Verifier

    http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx 

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=\_VwIDD9xngM

    Driver Verifier

    http://www.techsupportforum.com/2110308-post3.html

    Using Driver Verifier

    http://www.faultwire.com/solutions/using\_driver\_verifier.php 

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issues

    http://www.youtube.com/watch?v=\_VwIDD9xngM 

    You can disable Driver Verifier

    http://support.microsoft.com/kb/244617 

    Start - type in Search box -> verifier /reset      hit enter to disable

    Use BlueScreenView to see if there is a driver specified in the error message. Also check with

    MyEventViewer at the time of the BlueScreen.

    If DriverVerifier creates a minidump upload it and post the link here so we can analyze it.


    This is my generic how to for proper driver updates : (update your major drivers and BIOS)

    This utility makes it easy to see which versions are loaded : Run DriverView - set VIEW to HIDE

    Microsoft drivers - update those without Dump in their names (also update BIOS and chipset

    drivers at Toshiba.)

    DriverView - Free - utility displays the list of all device drivers currently loaded on your system.

    For each driver in the list, additional useful information is displayed: load address of the driver,

    description, version, product name, company that created the driver, and more.

    http://www.nirsoft.net/utils/driverview.html

    For Drivers check System Maker as fallbacks and Device Maker's which are the most current.

    Control Panel - Device Manager - Display Adapter - write down the make and complete model

    of your video adapter - double click - Driver's tab - write down the version info. Now click UPdate

    Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click -

    Uninstall - REBOOT this will refresh the driver stack.

    Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party

    with their own software and drivers and any other major device drivers you have.

    Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device

    Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for

    BIOS, Chipset and software updates at System Maker's site while there.)

    Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after

    each installation.

    Always check in Device Manager - Drivers tab to be sure the version you are installing actually

    shows up. This is because some drivers rollback before the latest is installed (sound drivers

    particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as

    needed.

    Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check

    manually by model.

    Manually look at manufacturer's sites for drivers - and Device Maker's sites.

    http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

    Installing and updating drivers in 7 (updating drivers manually using the methods above is preferred

    to ensure the latest drivers from System maker and Device makers are found)

    http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

    If you update drivers manually then it is a good idea to disable Driver Installations in Windows

    Updates, this leaves Windows Updates ON however it will not install drivers which will usually be

    older and cause issues. If Updates suggests a new driver then HIDE it (Right Click on it) and then

    go look for new ones manually if you wish.

    How to stop Windows 7 automatically installing drivers

    http://support.microsoft.com/kb/2500967

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.

    Was this answer helpful?

    0 comments No comments