F5F Stay Refreshed Software Operating Systems Understanding how to read a Windows 11 dump file

Understanding how to read a Windows 11 dump file

Understanding how to read a Windows 11 dump file

J
jjsoini
Posting Freak
Find
809
04-25-2021, 06:09 PM
#1
Hello, im in desperate need of finding the cause of my pc bluescreening every 30 minutes when playing BeamNG.Drive. I'm not sure why it's happening. Only errors i get in event manager are some gaming services not responding errors, and only critical errors i get are because of sudden system shutdown. I'm not sure if it's even software issue or is it hardware itself. It also might be crucial info that, today my pc bsod'ed 8 times, and stop codes were:
- KMODE EXCEPTION NOT HANDLED
- CRITICAL PROCESS DIED
- UNEXPECTED STORE EXCEPTION
\
\
\
\
\
I would really appreciate helping me read my dump file since i have no clue on how to do that.
My dump file:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToV8JsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.047 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.265 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 29
Microsoft ® Windows Debugger Version 10.0.26100.4654 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available
Symbol search path is: srv*
Executable search path is:
Unable to read PsLoadedModuleList
WARNING: Mismatch between nt!KdDebuggerDataBlock and nt!KdVersionBlock - KernBase (Kernel Base Address)
WARNING: Mismatch between nt!KdDebuggerDataBlock and nt!KdVersionBlock - PsLoadedModuleList (Kernel Loaded Module List)
KiProcessorBlock[0] could not be read.
KiProcessorBlock[1] could not be read.
KiProcessorBlock[2] could not be read.
KiProcessorBlock[3] could not be read.
KiProcessorBlock[4] could not be read.
KiProcessorBlock[5] could not be read.
KiProcessorBlock[6] could not be read.
KiProcessorBlock[7] could not be read.
KiProcessorBlock[8] could not be read.
KiProcessorBlock[9] could not be read.
KiProcessorBlock[10] could not be read.
KiProcessorBlock[11] could not be read.
Windows 10 Kernel Version 26100 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff805`ca000000 PsLoadedModuleList = 0xfffff805`caef4c40
Debug session time: Fri Jul 25 19:06:44.971 2025 (UTC + 2:00)
System Uptime: 0 days 0:28:16.712
Unable to read PsLoadedModuleList
Loading Kernel Symbols
Unable to read PsLoadedModuleList
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
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Reply
Reply
J
jjsoini
04-25-2021, 06:09 PM #1

Hello, im in desperate need of finding the cause of my pc bluescreening every 30 minutes when playing BeamNG.Drive. I'm not sure why it's happening. Only errors i get in event manager are some gaming services not responding errors, and only critical errors i get are because of sudden system shutdown. I'm not sure if it's even software issue or is it hardware itself. It also might be crucial info that, today my pc bsod'ed 8 times, and stop codes were:
- KMODE EXCEPTION NOT HANDLED
- CRITICAL PROCESS DIED
- UNEXPECTED STORE EXCEPTION
\
\
\
\
\
I would really appreciate helping me read my dump file since i have no clue on how to do that.
My dump file:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToV8JsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.047 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.265 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 29
Microsoft ® Windows Debugger Version 10.0.26100.4654 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available
Symbol search path is: srv*
Executable search path is:
Unable to read PsLoadedModuleList
WARNING: Mismatch between nt!KdDebuggerDataBlock and nt!KdVersionBlock - KernBase (Kernel Base Address)
WARNING: Mismatch between nt!KdDebuggerDataBlock and nt!KdVersionBlock - PsLoadedModuleList (Kernel Loaded Module List)
KiProcessorBlock[0] could not be read.
KiProcessorBlock[1] could not be read.
KiProcessorBlock[2] could not be read.
KiProcessorBlock[3] could not be read.
KiProcessorBlock[4] could not be read.
KiProcessorBlock[5] could not be read.
KiProcessorBlock[6] could not be read.
KiProcessorBlock[7] could not be read.
KiProcessorBlock[8] could not be read.
KiProcessorBlock[9] could not be read.
KiProcessorBlock[10] could not be read.
KiProcessorBlock[11] could not be read.
Windows 10 Kernel Version 26100 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff805`ca000000 PsLoadedModuleList = 0xfffff805`caef4c40
Debug session time: Fri Jul 25 19:06:44.971 2025 (UTC + 2:00)
System Uptime: 0 days 0:28:16.712
Unable to read PsLoadedModuleList
Loading Kernel Symbols
Unable to read PsLoadedModuleList
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
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

Reply
Reply
N
NuDimon
Member
Find
77
04-25-2021, 07:37 PM
#2
I attempted to resolve the gaming services error and even prevented my Xbox app from launching the diagnostic tool.
Also, I tried executing the "DISM /Online /Cleanup-Image /RestoreHealth" command on my PC, but it failed—no scans were performed.
Reply
Reply
N
NuDimon
04-25-2021, 07:37 PM #2

I attempted to resolve the gaming services error and even prevented my Xbox app from launching the diagnostic tool.
Also, I tried executing the "DISM /Online /Cleanup-Image /RestoreHealth" command on my PC, but it failed—no scans were performed.

Reply
Reply
F
Freedom_Men
Member
Find
211
05-02-2021, 12:27 AM
#3
Please upload the actual dump file. The analyze -v oputput you posted is garbage because you don't have the correct windbg symbols loaded.
Reply
Reply
F
Freedom_Men
05-02-2021, 12:27 AM #3

Please upload the actual dump file. The analyze -v oputput you posted is garbage because you don't have the correct windbg symbols loaded.

Reply
Reply
N
NANANANABatman
Junior Member
Find
3
05-02-2021, 01:35 AM
#4
Error code: (NTSTATUS) 0xd0000147 (3489661255) - No paging file specified. The system did not find a paging file in its settings.
You may need to enable Windows virtual memory to generate a proper minidump.
Windows runs as a paging OS; if c:\pagefile.sys is missing, it creates a small pagefile in RAM.
Search for "how to create a windows pagefile" for guidance.
Potential issues include KMODE EXCEPTION NOT HANDLED, CRITICAL PROCESS DIED, and UNEXPECTED STORE EXCEPTION. These often stem from faulty RAM timings.
Typically, update the BIOS or reset it to default, disable overclocking, restart into Windows, and remove any overclocking drivers.
Running memtest86 is recommended to verify memory timings.
If the test passes, submit memory dumps for analysis to identify driver-related corruption or other problems.
Reply
Reply
N
NANANANABatman
05-02-2021, 01:35 AM #4

Error code: (NTSTATUS) 0xd0000147 (3489661255) - No paging file specified. The system did not find a paging file in its settings.
You may need to enable Windows virtual memory to generate a proper minidump.
Windows runs as a paging OS; if c:\pagefile.sys is missing, it creates a small pagefile in RAM.
Search for "how to create a windows pagefile" for guidance.
Potential issues include KMODE EXCEPTION NOT HANDLED, CRITICAL PROCESS DIED, and UNEXPECTED STORE EXCEPTION. These often stem from faulty RAM timings.
Typically, update the BIOS or reset it to default, disable overclocking, restart into Windows, and remove any overclocking drivers.
Running memtest86 is recommended to verify memory timings.
If the test passes, submit memory dumps for analysis to identify driver-related corruption or other problems.

Reply
Reply