Windows 10: I have a problem as I am trying to wake up my computer.

Microsoft (R) Windows Debugger Version 10.0.18914.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\anath\Desktop\minidump\090119-10593-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802`09800000 PsLoadedModuleList = 0xfffff802`09c46490
Debug session time: Sun Sep 1 00:22:43.849 2019 (UTC + 8:00)
System Uptime: 0 days 5:21:21.838
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`099bfcc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb786`77db7550=00000000000000a0
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000010e, The disk subsystem returned corrupt data while reading from the
hibernation file.
Arg2: 000000000000000a
Arg3: 000000000000d0a7, Incorrect checksum
Arg4: 000000000000b532, Previous disk read's checksum

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.Elapsed.Sec
Value: 2

Key : Analysis.Memory.CommitPeak.Mb
Value: 70


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.18362.295 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0x9
Hiber Crash Dump
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: 10e

BUGCHECK_P2: a

BUGCHECK_P3: d0a7

BUGCHECK_P4: b532

BUGCHECK_STR: 0xa0_10e

CPU_COUNT: c

CPU_MHZ: a20

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-RMS12GD

ANALYSIS_SESSION_TIME: 09-01-2019 11:51:50.0335

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff80209da5480 to fffff802099bfcc0

STACK_TEXT:
ffffb786`77db7548 fffff802`09da5480 : 00000000`000000a0 00000000`0000010e 00000000`0000000a 00000000`0000d0a7 : nt!KeBugCheckEx
ffffb786`77db7550 fffff802`09dad324 : 00000000`00000001 ffffb98f`4350e390 00000003`051b5000 ffffb98f`523f7000 : nt!PopHiberChecksumHiberFileData+0xb570
ffffb786`77db75b0 fffff802`09da497b : 00000001`5287c000 ffffa304`82731858 00000000`00000001 00000000`00000001 : nt!PopRequestRead+0x78
ffffb786`77db7620 fffff802`09d9892e : 000018a6`da41adc0 ffffa304`82731858 00000000`00000000 fffff802`0a2b6848 : nt!PopRestoreHiberContext+0xbcab
ffffb786`77db76b0 fffff802`09d9867a : fffff802`09c67f10 ffffb786`77db7830 fffff802`09c67f10 ffffb98f`4350e390 : nt!PopHandleNextState+0x20e
ffffb786`77db7700 fffff802`09d983ef : 00000000`00000100 00000000`00989680 ffffb98f`4350e390 ffffb98f`4350e390 : nt!PopIssueNextState+0x1a
ffffb786`77db7730 fffff802`09d98c7c : 00000000`00000010 00000000`00040286 00000000`00000000 fffff802`09892f14 : nt!PopInvokeSystemStateHandler+0x35b
ffffb786`77db7930 fffff802`09d9cf8a : ffffffff`ffffffff ffffffff`ffffffff 00000000`00000014 00000000`00000000 : nt!PopEndMirroring+0x1ec
ffffb786`77db79f0 fffff802`09d9ccc5 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : nt!MmDuplicateMemory+0x26e
ffffb786`77db7a80 fffff802`09929e95 : ffffb98f`44e70000 ffffb98f`44e70040 fffff802`09d9cba0 00000000`00000001 : nt!PopTransitionToSleep+0x125
ffffb786`77db7b10 fffff802`099c730a : ffff8e80`e00dc180 ffffb98f`44e70040 fffff802`09929e40 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb786`77db7b60 00000000`00000000 : ffffb786`77db8000 ffffb786`77db1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC: 337d1299c6890b7c6d65ceb358b93db026da4cb1

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3f4204606101825ad0e94e534cb039430fc7d595

THREAD_SHA1_HASH_MOD: dc844b1b94baa204d070855e43bbbd27eee98b94

FOLLOWUP_IP:
nt!PopHiberChecksumHiberFileData+b570
fffff802`09da5480 cc int 3

FAULT_INSTR_CODE: 16b9cccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PopHiberChecksumHiberFileData+b570

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 35707659

IMAGE_VERSION: 10.0.18362.295

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: b570

FAILURE_BUCKET_ID: 0xa0_10e_nt!PopHiberChecksumHiberFileData

BUCKET_ID: 0xa0_10e_nt!PopHiberChecksumHiberFileData

PRIMARY_PROBLEM_CLASS: 0xa0_10e_nt!PopHiberChecksumHiberFileData

TARGET_TIME: 2019-08-31T16:22:43.000Z

OSBUILD: 18362

OSSERVICEPACK: 295

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: 1998-05-31 05:12:57

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.18362.295

ANALYSIS_SESSION_ELAPSED_TIME: 959

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xa0_10e_nt!pophiberchecksumhiberfiledata

FAILURE_ID_HASH: {28ba2091-a476-6f77-2dec-6241bccd4685}

Followup: MachineOwner
---------


:)

 

computer wake-up after sleep

Did all the steps exactly as shown above and "Allow this device to wake the computer" was already selected.

I think you might have miss-understood the problem. It appears that the computer is waking up, but it doesn't re-connect to my display. I have to turn off the display and turn it back on to get my display to to re-connect. This was not a problem prior to
the last Win 10 upgrade.

 

computer wake-up after sleep

Hi Bill,

There's a possibility that the settings that enables your Space bar to wake your computer up from sleep was reset after updating Windows. If this what had happened, we suggest that you just re-set it up. See the steps below on how to do
so:

• Press Windows key and type keyboard in.
• Click on Keyboard option and a pop-up windows should show up.
• From there, go to > Hardware tab > Properties >
  Change settings > Power management > Allow this device to wake the computer >
  OK/Apply.

Try the if the steps did work and let us know any updates.

 

waking up my computer

Hi Virginia,

For us to properly isolate the issue in waking up your computer, we would like to know the following:

• What is the make and model of your computer?
• Were there any changes made on your computer prior to the issue (e.g., updates, software installation)?
• Aside from a hard shut down, to make sure that we have not missed on anything, what other troubleshooting steps have you done so far?

In the meantime, we suggest that you check if the wake on keyboard option is enabled. To check this, open
Device Manager > Keyboards > HID Keyboard Device >
Power Management, and then disable the Allow this device to wake the computer feature (standard value).

We would appreciate it if you could get back to us and provide us your feedback.