New
#1
CRASH - Windows failed to resume from hibernate with error status 0xC0
- Windows failed to resume from hibernate with error status 0xC0000001.
- The previous system shutdown at 18:31:09 on 31/10/2017 was unexpected.
- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
- The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000000, 0x00000000000000ff, 0x0000000000000001, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b1dc8f46-c5bd-4e0a-902d-5b7d02ae67d1.
The above are the typical System events appearing in my Event Viewer every time I boot from a previous session where the computer was hibernated and then failed to come back from hibernation. It happens at least once a week, I do use my computer daily, its as if I'm cold booting and there is no BSOD or clue something has gone wrong.
I've run WhoCrashed and this is the output from the latest crash today.
On Wed 15/11/2017 00:17:45 your computer crashed
crash dump file: C:\WINDOWS\Minidump\111517-6250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not 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 Wed 15/11/2017 00:17:45 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not 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.
So would really appreciate any guidance on how to track down what is causing the problem.
Quote
