BSOD Driver_Power_State_Failure on cloned computer

[manix500]

Hello, i cloned my windows partition with imaging software (Macrium Reflect) and restored it on a similar computer(touch systems) and today I got a BSOD Driver_Power_State_Failure error on the second computer.
The computers are running Windows Embedded Standard 7 with the same software and drivers installed.

Is this a hardware or software issue?

 

[axe0]

0x9F crashes are usually driver issues, but I'd need some files that are missing.
Please run the DM Log Collector again and upload a new zip.

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.
How to fill in your system specs:

 

[manix500]

I run the tool again.
The zip seems have more files this time.

 

[axe0]

Please search for "msinfo32" (without quotes) and press enter,

• save it as msinfo32.nfo,
• in explorer go to the directory where it is saved,
• right click the msinfo32.nfo file,
• choose 'send to' or 'copy to',
• choose 'compressed (zipped) folder',
• upload the zip file.

 

[manix500]

I uploaded the requested file.
I hope there is enough data now to locate the problem.

Thanks

 

[axe0]

This is what I suspected, but isn't something you can find in a dump file hence the reason why I asked to run the DM Log Collector again and the msinfo since the second attempt also didn't had it.

The Atheros network adapter driver is the cause of the crash, however it seems to be the USB network adapter because every other network device is from Windows or the LAN device driver from Realtek.
My suggestion would be to see if there are driver updates available for the USB adapter, if there aren't you better remove it to prevent it from causing problems in the future.

0: kd> lmvm athur
Browse full module list
start    end        module name
93622000 937a6000   athur    T (no symbols)           
    Loaded symbol image file: athur.sys
    Image path: athur.sys
    Image name: athur.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR="Red"]Wed Apr 20 12:05:59 2011[/COLOR] (4DAEB007)
    CheckSum:         0018C064
    ImageSize:        00184000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

[COLOR="red"]Atheros AR9271 Wireless Network Adapter Service[/COLOR]	c:\windows\system32\drivers\[COLOR="Red"]athur[/COLOR].sys

Name	[00000012] TP-LINK Wireless USB Adapter
Adapter Type	Not Available
Product Type	TP-LINK Wireless USB Adapter
Installed	Yes
PNP Device ID	Not Available
Last Reset	27-Apr-16 13:50
Index	12
Service Name	[COLOR="red"]athur[/COLOR]
IP Address	Not Available
IP Subnet	Not Available
Default IP Gateway	Not Available
DHCP Enabled	Yes
DHCP Server	Not Available
DHCP Lease Expires	Not Available
DHCP Lease Obtained	Not Available
MAC Address	Not Available

 

[Layback Bear]

Just a thought.

The odds of a clone from one computer to a different computer working properly are slim to none.

The needed drivers will not match.
The activation COA key will not match.


In my opinion a clone is/was design to use on the same computer that the clone was made from.
It was not designed to move from the cloned computer to other computers.