L
LiveUndead
Laptop: MSI GT73RE Titan (Windows 10 Pro x64 1909) GeForce GTX 1070
As of recently (last week) will not go in to hibernate. After a restart, it usually will the first time or two. But after that, the screen will shut off, the power and GPU buttonswill still be lit, and the PC will effectively hang. After 5 minutes orso, the PC will shut off. When you turn it back on, it is indeed booting up from a cold boot. nothing that I had open was saved.
I have disabled virtually everything that was running at startup. I've disabled any third party modifications . I have run SFC scannow and repaired/restarted, I've checked and troubleshot power settings. I ran CHKDSK/f, restarted. I never use Fast Startup (and double checked it), so that's irrelevant. Nothing works. I checked Event Viewer, and get a "Windows failed to resume from hibernate with error status 0XC00000001" error. I Googled that, but didn't come across anything especially helpful, besides the "Probably a driver causing it" response.
The timestamp is 5 minutes after I attempted hibernate. This would indicate that it fails to enter hibernate after five minutes, and BSODs. But this is all with the screen having shut off, so I don't see it.
I ran whoCrashed, and the most recent crashes indicate the same error: DRIVER_POWER_STATE_FAILURE in the NTOSKRNL.EXE file. It is coming from the kernel, of course. I will post the output here, but it does not indicate any specific hardware driver that is causing it. just a generic kernel panic.
This week, I've had both an NVidia GeForce driver update, and a Windows update on this PC. I clean uninstalled, and reinstalled a previous NVidia driver, but that didn't work. And the WhoCrashed analysis said that no offending third party drivers were found. I was wondering if anyone had any other advice, or knew of this problem.
WhoCrashed output:
On Sat 2/8/2020 16:57:22 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\020820-7046-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0) Bugcheck code: 0x9F (0x3, 0xFFFFC00F6AA55060, 0xFFFFE3069123F7B0, 0xFFFFC0005A46BDE0) Error: DRIVER_POWER_STATE_FAILURE file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time. This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------
On Sat 2/8/2020 16:39:07 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020820-7031-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0) Bugcheck code: 0x9F (0x3, 0xFFFFAB0EEC5CA570, 0xFFFFE68A84E4F7B0, 0xFFFFAB0EF37CB8A0)
Error: DRIVER_POWER_STATE_FAILURE file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Event Viewer:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff81044a04e060, 0xffffef85b868f7b0, 0xffff81044f12c3b0). A dump was saved in: C:\WINDOWS\Minidump\021020-7000-01.dmp. Report Id: c94f0eb4-453f-4540-a344-91932048b186.
Results of Minidump:
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021020-7000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802`5e000000 PsLoadedModuleList = 0xfffff802`5e448150
Debug session time: Mon Feb 10 02:28:35.627 2020 (UTC - 5:00)
System Uptime: 0 days 1:08:43.411
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffff81044a04e060, Physical Device Object of the stack
Arg3: ffffef85b868f7b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff81044f12c3b0, The blocked IRP
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.628 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.
SYSTEM_PRODUCT_NAME: GT73VR 7RE
SYSTEM_SKU: 17A1.3
SYSTEM_VERSION: REV:1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: E17A1IMS.325
BIOS_DATE: 03/12/2018
BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.
BASEBOARD_PRODUCT: MS-17A1
BASEBOARD_VERSION: REV:1.0
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffff81044a04e060
BUGCHECK_P3: ffffef85b868f7b0
BUGCHECK_P4: ffff81044f12c3b0
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: pci
FAULTING_MODULE: fffff80263130000 pci
CPU_COUNT: 8
CPU_MHZ: b58
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: B4'00000000 (cache) B4'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST:
ANALYSIS_SESSION_TIME: 02-10-2020 02:31:07.0878
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
STACK_TEXT:
ffffef85`b868f778 fffff802`5e2ee3d7 : 00000000`0000009f 00000000`00000003 ffff8104`4a04e060 ffffef85`b868f7b0 : nt!KeBugCheckEx
ffffef85`b868f780 fffff802`5e2ee2e1 : ffff8105`388a0210 ffff8104`4fd891b0 ffffc680`4f2c0100 ffffc680`4f2c0180 : nt!PopIrpWatchdogBugcheck+0xef
ffffef85`b868f7f0 fffff802`5e06ba89 : ffff8105`388a0248 00000000`00000080 00000000`00000002 ffff8104`00000002 : nt!PopIrpWatchdog+0x31
ffffef85`b868f840 fffff802`5e06a7e9 : 00000000`0000000c 00000000`00989680 00000000`0002666f 00000000`00000087 : nt!KiProcessExpiredTimerList+0x169
ffffef85`b868f930 fffff802`5e1c5024 : 00000000`00000000 ffffc680`4f2c0180 ffffc680`4f2d1240 ffff8104`54d03080 : nt!KiRetireDpcList+0x4e9
ffffef85`b868fb60 00000000`00000000 : ffffef85`b8690000 ffffef85`b8689000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84
THREAD_SHA1_HASH_MOD_FUNC: 418dcf5cc7a95525fe8ac8ffec7980c508fac304
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 380ee536789d4b77d82e9ab3a599c8d978e0118f
THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 10.0.18362.628
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_e2xw10x64_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_POWER_DOWN_e2xw10x64_IMAGE_pci.sys
PRIMARY_PROBLEM_CLASS: 0x9F_3_POWER_DOWN_e2xw10x64_IMAGE_pci.sys
TARGET_TIME: 2020-02-10T07:28:35.000Z
OSBUILD: 18362
OSSERVICEPACK: 628
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 1991-11-30 00:21:39
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.628
ANALYSIS_SESSION_ELAPSED_TIME: 1080
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_e2xw10x64_image_pci.sys
FAILURE_ID_HASH: {4e9d0212-3878-3d83-28f5-ae5c37341dff}
Followup: MachineOwner
---------
Continue reading...
As of recently (last week) will not go in to hibernate. After a restart, it usually will the first time or two. But after that, the screen will shut off, the power and GPU buttonswill still be lit, and the PC will effectively hang. After 5 minutes orso, the PC will shut off. When you turn it back on, it is indeed booting up from a cold boot. nothing that I had open was saved.
I have disabled virtually everything that was running at startup. I've disabled any third party modifications . I have run SFC scannow and repaired/restarted, I've checked and troubleshot power settings. I ran CHKDSK/f, restarted. I never use Fast Startup (and double checked it), so that's irrelevant. Nothing works. I checked Event Viewer, and get a "Windows failed to resume from hibernate with error status 0XC00000001" error. I Googled that, but didn't come across anything especially helpful, besides the "Probably a driver causing it" response.
The timestamp is 5 minutes after I attempted hibernate. This would indicate that it fails to enter hibernate after five minutes, and BSODs. But this is all with the screen having shut off, so I don't see it.
I ran whoCrashed, and the most recent crashes indicate the same error: DRIVER_POWER_STATE_FAILURE in the NTOSKRNL.EXE file. It is coming from the kernel, of course. I will post the output here, but it does not indicate any specific hardware driver that is causing it. just a generic kernel panic.
This week, I've had both an NVidia GeForce driver update, and a Windows update on this PC. I clean uninstalled, and reinstalled a previous NVidia driver, but that didn't work. And the WhoCrashed analysis said that no offending third party drivers were found. I was wondering if anyone had any other advice, or knew of this problem.
WhoCrashed output:
On Sat 2/8/2020 16:57:22 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\020820-7046-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0) Bugcheck code: 0x9F (0x3, 0xFFFFC00F6AA55060, 0xFFFFE3069123F7B0, 0xFFFFC0005A46BDE0) Error: DRIVER_POWER_STATE_FAILURE file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time. This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------
On Sat 2/8/2020 16:39:07 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020820-7031-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0) Bugcheck code: 0x9F (0x3, 0xFFFFAB0EEC5CA570, 0xFFFFE68A84E4F7B0, 0xFFFFAB0EF37CB8A0)
Error: DRIVER_POWER_STATE_FAILURE file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Event Viewer:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff81044a04e060, 0xffffef85b868f7b0, 0xffff81044f12c3b0). A dump was saved in: C:\WINDOWS\Minidump\021020-7000-01.dmp. Report Id: c94f0eb4-453f-4540-a344-91932048b186.
Results of Minidump:
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021020-7000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802`5e000000 PsLoadedModuleList = 0xfffff802`5e448150
Debug session time: Mon Feb 10 02:28:35.627 2020 (UTC - 5:00)
System Uptime: 0 days 1:08:43.411
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffff81044a04e060, Physical Device Object of the stack
Arg3: ffffef85b868f7b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff81044f12c3b0, The blocked IRP
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.628 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.
SYSTEM_PRODUCT_NAME: GT73VR 7RE
SYSTEM_SKU: 17A1.3
SYSTEM_VERSION: REV:1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: E17A1IMS.325
BIOS_DATE: 03/12/2018
BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.
BASEBOARD_PRODUCT: MS-17A1
BASEBOARD_VERSION: REV:1.0
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffff81044a04e060
BUGCHECK_P3: ffffef85b868f7b0
BUGCHECK_P4: ffff81044f12c3b0
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: pci
FAULTING_MODULE: fffff80263130000 pci
CPU_COUNT: 8
CPU_MHZ: b58
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: B4'00000000 (cache) B4'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST:
ANALYSIS_SESSION_TIME: 02-10-2020 02:31:07.0878
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
STACK_TEXT:
ffffef85`b868f778 fffff802`5e2ee3d7 : 00000000`0000009f 00000000`00000003 ffff8104`4a04e060 ffffef85`b868f7b0 : nt!KeBugCheckEx
ffffef85`b868f780 fffff802`5e2ee2e1 : ffff8105`388a0210 ffff8104`4fd891b0 ffffc680`4f2c0100 ffffc680`4f2c0180 : nt!PopIrpWatchdogBugcheck+0xef
ffffef85`b868f7f0 fffff802`5e06ba89 : ffff8105`388a0248 00000000`00000080 00000000`00000002 ffff8104`00000002 : nt!PopIrpWatchdog+0x31
ffffef85`b868f840 fffff802`5e06a7e9 : 00000000`0000000c 00000000`00989680 00000000`0002666f 00000000`00000087 : nt!KiProcessExpiredTimerList+0x169
ffffef85`b868f930 fffff802`5e1c5024 : 00000000`00000000 ffffc680`4f2c0180 ffffc680`4f2d1240 ffff8104`54d03080 : nt!KiRetireDpcList+0x4e9
ffffef85`b868fb60 00000000`00000000 : ffffef85`b8690000 ffffef85`b8689000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84
THREAD_SHA1_HASH_MOD_FUNC: 418dcf5cc7a95525fe8ac8ffec7980c508fac304
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 380ee536789d4b77d82e9ab3a599c8d978e0118f
THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 10.0.18362.628
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_e2xw10x64_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_POWER_DOWN_e2xw10x64_IMAGE_pci.sys
PRIMARY_PROBLEM_CLASS: 0x9F_3_POWER_DOWN_e2xw10x64_IMAGE_pci.sys
TARGET_TIME: 2020-02-10T07:28:35.000Z
OSBUILD: 18362
OSSERVICEPACK: 628
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 1991-11-30 00:21:39
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.628
ANALYSIS_SESSION_ELAPSED_TIME: 1080
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_e2xw10x64_image_pci.sys
FAILURE_ID_HASH: {4e9d0212-3878-3d83-28f5-ae5c37341dff}
Followup: MachineOwner
---------
Continue reading...