BSOD Sleep 0x0000000A (INTERNAL_POWER_ERROR)

[BigJohn52]

I have a problem with a system that I built at Christmas on which I loaded Windows 7 Professional and it seems to work fine except that it crashes when I try to make it SLEEP.

If it tries to go into sleep automatically, or I try to put it into sleep mode manually then the monitor goes off, the PC doesn't power off and after a few minutes it crashes with a BSOD. The message is as follows:
INTERNAL_POWER_ERROR
STOP: 0x0000000A (0x00000009, 0xC0000001, 0x00000001, 0x00000000)

I've looked on the internet and have tried a few things, but I still have the problem:
1) checked graphics driver up to date
2) tried SLEEP after clean boot
3) wanted to try from safe mode but sleep option not available
4) powercfg /hibernate /size 100
5) checked that TRIM is enabled.
6) checked that the SSD drivers are up to date.

I did read somewhere that running Windows 7 with SSD disks has a problem with going into sleep mode but I've not been able to find any more info.

I've disabled the system going into sleep mode automatically for now but I'd really like a fix to this problem.

 

[Arc]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

 

[BigJohn52]

Dump File Not Created

I've tried following the instructions in attempt to get a minidump file but without success. I've even tried creating te directory: C:\Windows\MiniDump and that's empty after the crash.

The crash happens every time I push the "Sleep" key on my keyboard. The exact chain of events is:

1. Push "Sleep" key
2. After a little more that 6 minutes, the system crashes with the following messages:
   STOP 0x000000A0 (0x00000009 0xC0000001 0x00000001)
   Collecting Data for Crash Sump
   Initialising disk for Crash Dump...
3. After a further 6 mins the system powers off.
4. After rebooting, there's no sign of anything in the minidump folder and no .dmp files anywhere on the C drive.

I've checked that there's a paging file on the C: drive.

I've checked the registry vales under path
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl]
and everything seems to be set the same as in the Create_Minidump_on_BSOD.reg file.

What would you suggest?

 

[Arc]

1. STOP 0x000000A0 (0x00000009 0xC0000001 0x00000001)

There should be one more number/series series in the bracket, but still what we have is somehow meaningful.

Stop 0xA0 means INTERNAL_POWER_ERROR. Here teh second parameter is the ntstatus code. In this case, 0xC0000001 means unsuccessful operation.

{Operation Failed} The requested operation was unsuccessful.

That means, the computer failed to go to sleep.

In absence of a crash dump I am not very sure on which we should concentrate, but .... there is one startup item there .....

VIAxHCUtl    c:\via_xhci\usb3monitor.exe    Public    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

I think you should think about it.

One more thing is in my suspects list. ..... Silicon Image SiI 3114 SoftRaid 5 Controller. Because it is not present in the drivers exported list. And RAID is always problematic.

 

[BigJohn52]

The missing number in the brackets was a final value of 0.

Although I've been working in software development for many years, my Windows system skills are somewhat rusty, so am in need in some guidance as to the way forward... So, what do you suggest?

1) I'm not sure why I'm not getting a crash dump. Is this something that's worth investigating and feasible?

2) I did check the via_xhci driver and I believe that that's up to date. What else should be checked here? Could this driver be disabled so as to eliminate it from the equation?

3) What's the best thing to do about the Raid controller? What's the significance of it not appearing in the exported list? Would it be worth breaking the raid set and even possibly replacing the SSDs by a spinning drive?

Sorry for all the questions - I wasn't expecting all these problems...

Thanks

John

 

[Arc]

Hi John.

It was a long time I checked your issue, and the gap in between made it out from my brain. So I took another look at your issue, and is is this, simple.

So you can have a workaround. As it is a desktop PC, then you can disable hibernate without any issue. Hibernate etc are mainly for portable computers running on stored battery power; it helps to preserve the battery charge. If you disable hibernate, the issue will no longer be there. Plus, Some SSDs dont like the hibernation thing on them.

If you dont like to go with that, then only read the following.

One thing you need to check at first, that is the size of the size of the hiberfile.sys in C:\windows. It must not be more than 4 GB, the size of your RAM.

The hibernate file, that is hiberfile.sys is prepared when you put your computer to hibernate. That file is a copy of the state of RAM to the HDD. So there may be a chance of an issue from the part of the storage device or storage controller. And, the storage controller (Silicon Image Raid) is too old to work properly with windows 7.

21/11/2008 07:32:08    C:\Windows\system32\drivers\Si3114r5.sys

Search for any possible update Silicon Image SiI 3114 SoftRaid 5 Controller in http://www.siliconimage.com/support/. If available, update it and see how it goes.

If nothing changed, we will plan to break the RAID and to install windows with SCSI controller.
[FONT=&quot]
[/FONT]