Windows 10: INTERNAL_POWER_ERROR 0xA0 after Win7 to Win10 upgrade

After my upgrade to Win10, started getting BSOD with this error. Some searching indicated maybe graphics card. My ob board one wasn't officially supported by AMD for Win10 so I bought a new one. Same thing. Disabled Windows Update auto driver install, and installed both Catalyst 15.7 and 15.7.1, no good. Made sure my chipset drivers were up to date, no good. I looked at the dumps and thought maybe it wasn't graphics card but not sure where to go next.

It's totally random. Computer being used, or not, eventually BSOD.

:)

 

windows10 INTERNAL_POWER_ERROR

I have upgraded the win10 form win8.1 and I m getting the error (INTERNAL_POWER_ERROR) sometimes

how to solve this problem ?

please me !!

 

ual boot system upgrade to windows 10

Thanks Jessen for the hint. I was expecting a yes or no answer, since I already have a dual boot system(xp+win7), and if I upgrade win10 from win7 boot, would win7 be replaced by win10 and becomes a (xp+win10) dual boot system?

But it looks more complicated than I thought, should I check current system has xp and win7 are installed in DIFFERENT partitions, otherwise xp would be gone after win7 is upgraded to win10 if xp and win7 are in SAME partition?

 

amdxata.sys is being mentioned in all the dumps I've checked, It seems to be an AMD storage controller, see if you can find a new or other driver for it.

Driver Reference Table - amdxata.sys

 

That's what I was thinking but not sure where. It does have an old date but I think it may be the latest.

 

Attachment 30417 I'm in the same boat here running an AMD 4100 on an ASRock MB. My blue screens and forced reboots happen every 30-70 minutes, and are sometimes prompted by events such as turning on the printer, plugging in a camera, etc.
ASRock's website told me to install the AsMedia 106x SATA Controller, which I did last night, leaving the AMD SATA Controller and it's possibly miscreat amdxata.sys file. Dare I disable the AMD SATA, now that I have the AsMedia?

This is my first post here, so I hope I'm doing everything correctly. thanks!!!

 

So you have the ASMedia 106X on your mobo? I bought an add-in card with this chipset so I could get 6GB/s. I'm wondering if this has something to do with it. I was thinking of taking the card out and putting my hard drive just into the mobo, which uses a different chipset and see if the BSOD goes away.

Does your ASMedia show up in your Device Manager? I don't see it at all or I'm looking in the wrong place.

 

When I got bought two SSDs last year, one of my two AMD motherboards had the ASMedia 106X, and one didn't. I use one more, so I made sure it had the 106x. I went through the step of enabling AHCI on both. The second computer runs "slower Sata", but its hard to tell any difference - it hasn't had any Win10 blue screens yet.
I thought I'd installed all the drivers for the computer with the 106x last year, but I don't remember seeing it show up in the device manager under IDE ATA/ATAPI controllers until I took this step a couple days ago:
- I downloaded it from the ASRock website <although I think it's the same 2012 version (1.3.4.0) as on their install DVD>
- I navigated the menu down to Driver VistaLater x64
- there were 4 files there - I right-clicked on the .inf file and selected install
The ASMedia readme file is long and technical - installing SATA controllers is apparently a bit tricky.

After taking this step, the crashes seem less frequent. So back to my question - in Device Manager, can I disable or delete the entry for AMD SATA controller - does it duplicate the 106x? If no one here knows the answer, I guess I'll go ahead and try that this weekend....can't mess things up too badly......

 

Since mine is an add in card, I found it listed under Storage Controllers and it has the latest drivers I could find but according to my crash dumps, that is not the problem. It's the onboard AMD Sata Controller under IDE/ATAPI controllers. I had no problem with Win7 so, hmmmm. Maybe what I try is just use the ASMedia card and see what happens.

 

The 2nd computer shows AMD SATA as the only SATA in the Device Driver. It's two driver files are amdsata.sys and amdxata.sys. .......And it seems just as quick as the computer with the ASMedia controller.......is 6 GB/s overrated? :-/

 

what's the version\date on your amdxata.sys?

 

Drilling down into System32 drivers shows that my amdxata.sys is version 1.2.0.025 dated 4/27/2009. I just went ahead and played with renaming it to amdxata.OLD, disabling AMD SATA in device driver, and rebooting, and it didn't seem to affect how this computer boots up and runs - I don't think I'll leave it that way, though.

 

I bet some of your SATA ports are on the ASMedia controller and some are on the AMD controller.

Update: I don't have anything plugged into the mobo SATA ports and the computer didn't crash at all last night. I didn't disable the AMD controller. I wonder if it's a specific device, HDD, DVD, etc.

That's the same version as my amdxata.sys too.

 

I downloaded and installed a different version of amdxata.sys last night and no crashes so far. It's the top result of a Google Search "amdxata.sys download" - version 1.1.4.6 ......knock on wood........... :-/

 

Update: Last night I rolled back the AMD SATA Controller driver to the MS one and plugged in my two DVD drives into the mobo ports, no crashes overnight.

I did some reading yesterday and the issue may be with power management. I'm going to run with the MS driver for now but maybe I'll try messing with the power stuff. Here's a couple threads.

http://www.tomshardware.com/forum/93...al-power-error

http://www.sevenforums.com/tutorials...hipm-dipm.html