J
JosipTica
Hi,
I have a 2020 MBAir with Windows 10 pro 19041.630 installed via bootcamp.
After hibernation in Windows OS (MacOS does not have this issue) I usually immediately or after 10-15 minutes end up with BSOD. It does not happen after sleep, only after hibernation.
Actually, I get unreadable blue screen, but I assume that it is BSOD due to Windbg report - BSODs is never readable, I just get blue screen with scrambled lines and zero text and computer restarts after that by itself.
Dump file is attached below.
Thanking you,
jt
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`6d400000 PsLoadedModuleList = 0xfffff804`6e02a3b0
Debug session time: Sat Dec 5 17:36:22.322 2020 (UTC + 1:00)
System Uptime: 2 days 3:14:08.248
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
...................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`6d7f5210 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd80c`e6c1f4b0=00000000000000a0
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000901, A driver has enabled/disabled kernel APCs while handling a
power IRP.
Arg2: ffff9d857de934b0, DEVICE_OBJECT
Arg3: ffff9d857bb1b7a0, IRP
Arg4: 000000000000ffff, The thread's APC disable count
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2593
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on MBAI716GB
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 7139
Key : Analysis.Memory.CommitPeak.Mb
Value: 78
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a0
BUGCHECK_P1: 901
BUGCHECK_P2: ffff9d857de934b0
BUGCHECK_P3: ffff9d857bb1b7a0
BUGCHECK_P4: ffff
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd80c`e6c1f4a8 fffff804`6d89f4e2 : 00000000`000000a0 00000000`00000901 ffff9d85`7de934b0 ffff9d85`7bb1b7a0 : nt!KeBugCheckEx
ffffd80c`e6c1f4b0 fffff804`6d6a29a5 : 00000000`00000000 fffff804`6d79c350 00000000`00000000 00000000`000000b4 : nt!PopIrpWorker+0x103192
ffffd80c`e6c1f550 fffff804`6d7fc868 : ffffc700`79884180 ffff9d85`704b1040 fffff804`6d6a2950 058aff95`3816e800 : nt!PspSystemThreadStartup+0x55
ffffd80c`e6c1f5a0 00000000`00000000 : ffffd80c`e6c20000 ffffd80c`e6c19000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!PopIrpWorker+103192
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 103192
FAILURE_BUCKET_ID: 0xa0_901_nt!PopIrpWorker
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8bab41ba-fdcc-37e3-a8f6-bbec8a9193cf}
Followup: MachineOwner
---------
Continue reading...
I have a 2020 MBAir with Windows 10 pro 19041.630 installed via bootcamp.
After hibernation in Windows OS (MacOS does not have this issue) I usually immediately or after 10-15 minutes end up with BSOD. It does not happen after sleep, only after hibernation.
Actually, I get unreadable blue screen, but I assume that it is BSOD due to Windbg report - BSODs is never readable, I just get blue screen with scrambled lines and zero text and computer restarts after that by itself.
Dump file is attached below.
Thanking you,
jt
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`6d400000 PsLoadedModuleList = 0xfffff804`6e02a3b0
Debug session time: Sat Dec 5 17:36:22.322 2020 (UTC + 1:00)
System Uptime: 2 days 3:14:08.248
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
...................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`6d7f5210 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd80c`e6c1f4b0=00000000000000a0
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000901, A driver has enabled/disabled kernel APCs while handling a
power IRP.
Arg2: ffff9d857de934b0, DEVICE_OBJECT
Arg3: ffff9d857bb1b7a0, IRP
Arg4: 000000000000ffff, The thread's APC disable count
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2593
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on MBAI716GB
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 7139
Key : Analysis.Memory.CommitPeak.Mb
Value: 78
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a0
BUGCHECK_P1: 901
BUGCHECK_P2: ffff9d857de934b0
BUGCHECK_P3: ffff9d857bb1b7a0
BUGCHECK_P4: ffff
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd80c`e6c1f4a8 fffff804`6d89f4e2 : 00000000`000000a0 00000000`00000901 ffff9d85`7de934b0 ffff9d85`7bb1b7a0 : nt!KeBugCheckEx
ffffd80c`e6c1f4b0 fffff804`6d6a29a5 : 00000000`00000000 fffff804`6d79c350 00000000`00000000 00000000`000000b4 : nt!PopIrpWorker+0x103192
ffffd80c`e6c1f550 fffff804`6d7fc868 : ffffc700`79884180 ffff9d85`704b1040 fffff804`6d6a2950 058aff95`3816e800 : nt!PspSystemThreadStartup+0x55
ffffd80c`e6c1f5a0 00000000`00000000 : ffffd80c`e6c20000 ffffd80c`e6c19000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!PopIrpWorker+103192
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 103192
FAILURE_BUCKET_ID: 0xa0_901_nt!PopIrpWorker
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8bab41ba-fdcc-37e3-a8f6-bbec8a9193cf}
Followup: MachineOwner
---------
Continue reading...