BSOD when restarting windows after exteneded user session.

Anonymous

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.

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

Anonymous

2014-03-11T03:24:03+00:00

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

Please review ALL the methods in the previously posted troubleshooters. Do ALL the updates

you can. That means BIOS, chipset drivers, and all major drivers.

A very intermittent BSOD issue is often the program you are running or antivirus. Though it

can be anything those are the most likely causes for very sporadic occurrences.

After ALL of those (and not before) run Driver Verifier to see if it can indicate an issues. See

methods in the previously posted troubleshooter.

Rob - SpiritX
Was this answer helpful?

0 comments No comments
Anonymous

2014-03-11T03:19:38+00:00

using 7-zip I was able to shrink memory.dmp down to 125 MB as opposed to the 234 Mb .ZIP file. is this size and file format acceptable to you? if so, I will upload it immediately.
Was this answer helpful?

0 comments No comments
Anonymous

2014-03-11T03:09:21+00:00

the dump setting was set at kernel dump which is what either Microsoft of Toshiba had set it at.

The error seems to be coming from ntoskrnl.exe, so I don't see how anything but a kernel dump would be helpful. I have now changed the dump setting to small memory dump.

in any case, since this problem is intermittent, it may take a month or more before it happens again. when it does happen again, I will make a new set of files and post them here.
Was this answer helpful?

0 comments No comments
Anonymous

2014-03-11T03:03:22+00:00

the dump was set as kernel dump, which whar either Microsoft or Toshiba set it at. I have changed it to small memory dump. but since the error is occurring with ntoskrnl.exe I don't see how a non kernel dump would help.

in any case, since the problem is intermittent, it may take a month or more before it happens again. when it does happen again, I will make a new set of files and post them here.
Was this answer helpful?

0 comments No comments
Anonymous

2014-03-11T01:24:40+00:00

Hi,

All we need is a minidump. You must have it set for memory.dmp instead which will

be huge and I will not download it. A minidump is only 2 hundred K or so each.

Rob - SpiritX
Was this answer helpful?

0 comments No comments