New
#1
Crashes with Kernel-Power as the source in Event Viewer
I am running Windows 10 Home version 22H2 and have experienced crashes WITHOUT the blue screen, just system freezing while the computer seems to try and keep running (disks still spinning and fans still blazing).
I ran the script in the BSOD instructions and here is the output file: DESKTOP-R7Q9A1Q-(2024-03-28_12-10-27).zip - Google Drive
I also have pasted the memory.dmp file here:
Microsoft (R) Windows Debugger Version 10.0.27553.1004 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:
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
WARNING: Mismatch between nt!KdDebuggerDataBlock and nt!KdVersionBlock - KernBase (Kernel Base Address)
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff802`4f600000 PsLoadedModuleList = 0xfffff802`5022a730
Debug session time: Thu Mar 28 10:50:41.989 2024 (UTC - 7:00)
System Uptime: 0 days 3:36:58.067
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Loading Kernel Symbols
Missing image name, possible paged-out or corrupt data.
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - HRESULT 0x80004002
WARNING: .reload failed, module list may be incomplete
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
For analysis of this file, run !analyze -v
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
No flat address for current instruction
?? ???
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
and finally, when I view the critical errors in Event Viewer, here is the output:
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331c3b3a-2005-44c2-ac5e-77220c37d6b4}
EventID 41
Version 8
Level 1
Task 63
Opcode 0
Keywords 0x8000400000000002
- TimeCreated
[ SystemTime] 2024-03-28T18:01:46.0488865Z
EventRecordID 94843
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer DESKTOP-R7Q9A1Q
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 278
BugcheckParameter1 0xffffe60292f24050
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI true
CheckpointStatus 0
CsEntryScenarioInstanceIdV2 0
LongPowerButtonPressDetected false
Can anyone tell me what the issue is? I have had the problem before from an out-of-date Nvidia driver, but I updated that and it persists. I also recently replaced the PSU which seemed to decrease the frequency of this crash, but I recently installed Helldivers 2 and it started happening over and over. I have uninstalled it now but the problem persists.