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

58 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-03-11T19:03:32+00:00

    Hi,

    The Bug_Check was 9F CAUSE Unknown_Image which is of no real help. Further analysis

    also failed to show a direct cause.

    BugCheck 9F, {3, fffffa8006d57a00, fffff80000b9c518, fffffa8013429e50}

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Use the troubleshooter I posted on page 1 of this thread - use ALL of the methods.

    Run Driver View and verify all the drivers are up-to-date (check all the 3rd party sources as well

    as Toshiba).

    If no help run Driver Verifier to see if it can indicate a CAUSE.

    Rob - SpiritX

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-03-11T18:54:02+00:00

    These are the latest Bluetooth drivers according to my search against your model:

    Bluetooth Stack for Windows by Toshiba

    - Posted Date: 2010-08-09 | Version: 7.10.16(T) | Size: 77.02M
    • Bluetooth Stack for Windows XP/Vista/7 (32/64) by Toshiba
      • Posted Date: 2009-11-06 | Version: 7.10.01(T) | Size: 76.53M
    • ConfigFree for Windows 7 (32/64)
      • Posted Date: 2009-10-28 | Version: 8.0.25 | Size: 45.54M

    I would agree that the Windows 7 Upgrade Advisor is only a guide and not totally reliable. By that I mean that it points you to things to look at and does not provide definitive answers. -

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-03-11T18:11:32+00:00

    I am not sure what to make of that. I think it is another case of the upgrade advisor being senile again. I am using the latest Bluetooth drivers that are for my laptop; version 9.10.00T

    I would be willing to bet that if I went back to the Bluetooth drivers that came with my laptop, the upgrade advisor would not have a problem with those drivers v7.10.00(T)

    will autoruns work for x64? I remember that when I first got my laptop, when I went to use some of the software from sysinternals, that I found out that a fair portion of them were not 64-bit friendly

    UPDATE:

    Ok, I see that this particular piece of software has been fairly recently updated. I will run it as instructed and post the link in a bit

    heres the link

    --> http://1drv.ms/1habWFX  <--

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-03-11T17:09:02+00:00

    What have you done about these devices in your Windows Upgrade Advisor report

    Devices Status Details

     Bluetooth RFBUS

    TOSHIBA Not compatible The driver installed for this device is not compatible with Windows 7.

     Bluetooth RFHID

    TOSHIBA Not compatible The driver installed for this device is not compatible with Windows 7.

     BT Port

    TOSHIBA Not compatible The driver installed for this device is not compatible with Windows 7.

    To identify what loads when you boot use Autoruns (freeware from Microsoft).

    http://technet.microsoft.com/en-us/sysinternals/bb963902

    Select File, Save, change the “Save as type” to Text file type using the Scroll to the right and click Save. Please upload the file to your OneDrive as a shared file and post as a link here.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-03-11T14:43:29+00:00

    it is still disabled

    Microsoft  uses a "lite" version of diskkeeper in windows disk defragmenter, so I still don't see how the full feature version could be the problem.

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

    besides that, I have googled my brains out and the last version of Diskeeper that I could find caused BSOD's was Diskeeper 2010, that is two or three version older than what I have. I have found no BSOD issues involving Diskeeper 12 Professional that has been reported online.

    there are some conflicts with Diskeeper and other software, none of which I have installed.

    I did do  a manual defrag last week using diskkeeper, but ifaast, intelliwrite, and automatic defrag remain disabled.

    Was this answer helpful?

    0 comments