BSOD - dump file attached

Question

Hello,

My pc is having BSOD often, and I have no idea why.

The memory dump is this:

Microsoft (R) Windows Debugger Version 10.0.22473.1005 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_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
* ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine 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
Machine Name:
Kernel base = 0xfffff8005e800000 PsLoadedModuleList = 0xfffff8005f42a2d0
Debug session time: Sat Nov 27 20:33:23.300 2021 (UTC - 3:00)
System Uptime: 0 days 2:09:29.096
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
* ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
Missing image name, possible paged-out or corrupt data.
.Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
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

What could be the root cause?

Thanks in advance!

Answer 1

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive:

https://www.windowsq.com/t/bsod-posting-instructions.17/
https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

.
.
.
.
.

Answer 2

Please make the share link available without logon.

Answer 3

Please perform the following steps:

1) Search for C:\windows\memory.dmp
11/28/2021 7:54:12 PM 1694.43 C:\WINDOWS\MEMORY.DMP
Save to the downloads folder > zip > post a share link into this thread with only the dump file

2) The BIOS: Version/Date Insyde Corp. V1.02, 4/15/2019
Upgrade the BIOS: 1.02 > 1.12
https://www.acer.com/ac/en/US/content/support-product/7983?b=1&pn=NH.Q54SV.002&sn=NHQ54SV002920061DB2600

3) Increase the free space on C:
https://support.microsoft.com/en-us/windows/free-up-drive-space-in-windows-a18fae02-a0fa-8df9-9838-8970f9939de4
https://www.tenforums.com/tutorials/83441-free-up-drive-space-windows-10-a.html

4) Run Memtest86 for 4 passes (free version)

https://www.memtest86.com/

Repeat the test so that there are a total of 8 passes.

Testing can be performed overnight.

Find a camera or smartphone camera to take pictures and post images into this thread.

Memtest86 has a feature to create text files.

Please include the text files with images when posting the share link results.

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

.
.
.
.
.

Answer 4

1) the dump file was partially corrupt

2) ok

3) free space is important so that Windows does not automatically delete memory dump files

4) high on the list for the cause of the BSOD

5) For any new BSOD:
a) post a new V2 share link
b) post a separate zipped memory.dmp share link

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

.
.
.
.
.

Answer 5

Hi @Fabio Sakiyama

The minidump in one way directs to the corrupted system files.
Corrupted system files are one of the possible reasons why this issue is happening.

Press F8 while booting your computer to access System Recovery options.
Click Troubleshoot.
Select Command Prompt.
Enter the following commands below, then press Enter after each command:

chkdsk c: /f  
bootrec /fixmbr  
bootrec /fixboot  
bootrec /rebuildbcd  
bcdboot c:\windows /s c:  

Once done with the above commands, restart your computer and see if the problem is fixed.

--------
--If the reply is helpful, please Upvote and Accept it as an answer--