Bsod: Driver_power_state_failure

KeithJB · 20 Mar 2020

This has started happening repeatedly on my friends computer. It might be connected to a TPLINK Archer T4U USB WiFi adapter i recently installed for her. Its an older i3 system and only had 2.4Ghz Wireless.

Another point of note is that she bought this in Panama where she lives and it originally had Windows in Spanish on it. A friend of hers somehow installed an English version of Win10 Pro on it but that could be suspect too in my opinion.

I would be very grateful for any insights.

Keith

MrPepka · 20 Mar 2020

Update Intel Rapid Storage driver - Downloads for Intel(R) Rapid Storage Technology (Intel(R) RST)
Update BIOS - https://support.hp.com/us-en/drivers.../model/5298229

KeithJB · 20 Mar 2020

Wow, that's quick. Thank you! Can you say more about why those updates?

MrPepka · 20 Mar 2020

Because according to the crash dumps, the driver from the Intel RAID controller is to blame. And as for the BIOS update, I recommend to perform it just in case

zbook · 20 Mar 2020

The logs displayed the following problems / findings:

a) Out of date BIOS
b) one misbehaving driver
c) hibernation failure
d) drive file system corruption

Please perform the following steps:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
10) wmic recoveros get autoreboot
11) wmic recoveros get DebugInfoType
12) powercfg -h off
13) bcdedit /enum {badmemory}

14) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

15) Sometimes there are problems in the bios that produce BSOD.

The BIOS: Version/Date AMI Lar_806, 8/17/2012

Upgrade the BIOS: 806 > 815
https://support.hp.com/us-en/drivers...-2?sku=H3X57AA

16) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
Backup and Restore with Macrium Reflect

17) Create a brand new restore point.
Create System Restore Point in Windows 10

18) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

19) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

20) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

21) Update: iaStorA.sys
Intel chipset drivers

https://answers.microsoft.com/en-us/...0-8d22254aa1c1

https://support.hp.com/us-en/drivers...-1?sku=H3X57AA

22) Perform Window updates

23) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

24) Download and install HP UEFI hardware diagnostics: (left side of the webpage)
https://www8.hp.com/us/en/campaigns/.../pc-diags.html

25) Find a camera or smartphone camera to take pictures

26) Lunch the application > system > extensive > loop until error > run overnight > the next day if there have been two or more loops click esc > take pictures and post images of the tests performed with results into the thread

Code:

Name	Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller
Manufacturer	Intel Corporation
Status	OK
PNP Device ID	PCI\VEN_8086&DEV_1C02&SUBSYS_2AE5103C&REV_05\3&11583659&0&FA
I/O Port	0x0000F0B0-0x0000F0B7
I/O Port	0x0000F0A0-0x0000F0A3
I/O Port	0x0000F090-0x0000F097
I/O Port	0x0000F080-0x0000F083
I/O Port	0x0000F060-0x0000F07F
Memory Address	0xF7F06000-0xF7F067FF
IRQ Channel	IRQ 4294967294
Driver	C:\WINDOWS\SYSTEM32\DRIVERS\IASTORA.SYS (12.9.0.1001, 617.35 KB (632,168 bytes), 12/5/2019 4:05 AM)

Code:

iaStorA.sys  Mon Oct 28 16:15:26 2013 (526ED3EE)

Code:

iastora	iaStorA	c:\windows\system32\drivers\iastora.sys	Kernel Driver	Yes	Boot	Running	OK	Normal	No	Yes

KeithJB · 20 Mar 2020

I ran the powershell script and here is the output. Note that there was a syntax error in the bcdedit command:

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell Installing PowerShell - PowerShell | Microsoft Docs

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
PS C:\WINDOWS\system32> dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.720

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.720

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32> chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
402944 file records processed.
File verification completed.
18355 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
85171 reparse records processed.
557452 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
85171 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
77255 data files processed.
CHKDSK is verifying Usn Journal...
41775864 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

445750271 KB total disk space.
40929092 KB in 306240 files.
211848 KB in 77256 indexes.
0 KB in bad sectors.
534483 KB in use by the system.
65536 KB occupied by the log file.
404074848 KB available on disk.

4096 bytes in each allocation unit.
111437567 total allocation units on disk.
101018712 allocation units available on disk.
PS C:\WINDOWS\system32> wmic recoveros set autoreboot = false
Updating property(s) of '\\DEBORAH-DESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
PS C:\WINDOWS\system32> wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DEBORAH-DESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
PS C:\WINDOWS\system32> wmic recoveros get autoreboot
AutoReboot
FALSE

PS C:\WINDOWS\system32> wmic recoveros get DebugInfoType
DebugInfoType
7

PS C:\WINDOWS\system32> powercfg -h off
PS C:\WINDOWS\system32> bcdedit /enum {badmemory}
Invalid command line switch: /encodedCommand
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
PS C:\WINDOWS\system32> bcdedit /enum

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale es-MX
inherit {globalsettings}
default {current}
resumeobject {44f7a5dc-3dc8-11ea-8f05-b916b2cc1adc}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale es-MX
inherit {bootloadersettings}
recoverysequence {44f7a5de-3dc8-11ea-8f05-b916b2cc1adc}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {44f7a5dc-3dc8-11ea-8f05-b916b2cc1adc}
nx OptIn
bootmenupolicy Standard
PS C:\WINDOWS\system32>

zbook · 20 Mar 2020

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

There are commands that work in administrative command prompt that do not work in PS.
The instructions were to use administrative command prompt.
Run bcdedit /enum {badmemory} using administrative command prompt.

KeithJB · 20 Mar 2020

Sorry, I missed the Command prompt part. Here's what I got:

Microsoft Windows [Version 10.0.18363.720]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>

zbook · 20 Mar 2020

ok.

KeithJB · 20 Mar 2020

I tried to do the BIOS update and the firmware update utility ran and then froze at "verifying flash 83%" and the system seems to be totally locked up. CTRL ALT DEL doesn't work. I think I will have to power cycle it.