蓝屏 Blue screen：Probably caused by : ntoskrnl.exe ( nt+2f652c )

Question

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***

---

Symbol loading may be unreliable without a symbol search path.

Use .symfix to have the debugger choose a symbol path.

After setting your symbol path, use .reload to refresh symbol locations.

---

Executable search path is:

---

Symbols can not be loaded because symbol path is not initialized.

**

The Symbol Path can be set by:

using the _NT_SYMBOL_PATH environment variable.

using the -y <symbol_path> argument when starting the debugger.

using .sympath and .sympath+

---

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
WARNING: Unable to verify timestamp for ntoskrnl.exe ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff8020a600000 PsLoadedModuleList = 0xfffff8020b229750
Debug session time: Mon Jan 3 14:13:50.313 2022 (GMT+8)
System Uptime: 0 days 17:16:03.048

---

Symbols can not be loaded because symbol path is not initialized.

**

The Symbol Path can be set by:

using the _NT_SYMBOL_PATH environment variable.

using the -y <symbol_path> argument when starting the debugger.

using .sympath and .sympath+

---

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
WARNING: Unable to verify timestamp for ntoskrnl.exe ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.........................

---

**

Bugcheck Analysis

**

---

Use !analyze -v to get detailed debugging information.

BugCheck A, {31, 2, 0, fffff8020a8f652c}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

---

---

---

Your debugger is not using the correct symbols

---

In order for this command to work properly, your symbol path

must point to .pdb files that have full type information.

---

Certain .pdb files (such as the public OS symbols) do not

contain the required information. Contact the group that

provided you with these symbols if you need this command to

work.

---

Type referenced: nt!_KPRCB

---

---

---

---

---

Your debugger is not using the correct symbols

---

In order for this command to work properly, your symbol path

must point to .pdb files that have full type information.

---

Certain .pdb files (such as the public OS symbols) do not

contain the required information. Contact the group that

provided you with these symbols if you need this command to

work.

---

Type referenced: nt!_KPRCB

---

---

---

---

---

Your debugger is not using the correct symbols

---

In order for this command to work properly, your symbol path

must point to .pdb files that have full type information.

---

Certain .pdb files (such as the public OS symbols) do not

contain the required information. Contact the group that

provided you with these symbols if you need this command to

work.

---

Type referenced: nt!_KPRCB

---

---

---

Symbols can not be loaded because symbol path is not initialized.

**

The Symbol Path can be set by:

using the _NT_SYMBOL_PATH environment variable.

using the -y <symbol_path> argument when starting the debugger.

using .sympath and .sympath+

---

---

Symbols can not be loaded because symbol path is not initialized.

**

The Symbol Path can be set by:

using the _NT_SYMBOL_PATH environment variable.

using the -y <symbol_path> argument when starting the debugger.

using .sympath and .sympath+

---

Probably caused by : ntoskrnl.exe ( nt+2f652c )

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

Answer 1

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

Make sure the default language is English so that logs can be scanned and read.

https://www.tenforums.com/tutorials/3813-add-remove-change-display-language-windows-10-a.html

https://www.tenforums.com/tutorials/136792-change-display-language-windows-10-a.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

.
.
.
.
.

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

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 2

Hello

Thank you for your question and reaching out.

I can understand you are facing issue with BSOD with error code ntoskrnl.exe

Ntoskrnl.exe (Short for Windows NT operating system kernel,) also known as kernel image, provides the kernel and executive layers of the Windows NT kernel space, and is responsible for various system services such as hardware virtualization, process and memory management.

The ntoskrnl.exe BSOD is usually related to memory, possibly caused by a faulty driver. It is suggested that you run the following memory test to verify your memory and find out which driver is causing the problem.

1. Click Start button, then type Windows Memory Diagnostic in the search box and hit Enter.
2. Click Restart now and check for problems(recommended). Be sure to save your work first because your computer will start immediately.
3. Your computer will restart and the Windows Memory Diagnostic Tool screen will appear. Just let it perform the test. You don’t need to stay and watch the test finishes.
4. Your computer will automatically reboot and return to the Windows desktop. The test result will show up after you log in. If the result doesn’t show up automatically, you can check it manually.
5. Press Win+ R at the same time, then type in eventvwr.msc and hit Enter. Click System option under category Windows Logs on the left pane. On the right pane, click Find….
6. Type MemoryDiagnostic in the search box and hit Enter, you will be able to see the result displayed at the bottom of the window.
7. If the result of your memory diagnose shows that there are certain drivers are at fault, or that you see some error, you have bad RAM. It is very likely that you need to get your RAM changed. If you don’t see anything here, your memory is good.

Also it might also be related to a driver related issues. I suggest updating all the drivers on your device. You can also run the troubleshooter for blue screen errors.

https://support.microsoft.com/en-us/sbs/windows/troubleshoot-blue-screen-errors-5c62726c-6489-52da-a372-3f73142c14ad?ui=en-US&rs=en-US&ad=US

---

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