question

RyanTran-6605 avatar image
0 Votes"
RyanTran-6605 asked JennyFeng-MSFT commented

BSOD caused by ntoskrnl.exe

Hi eveyrone,

I'm getting sporadic BSOD causing mostly by ntoskml.exe. I tried few things to troubleshoot the issue; However to no avai.

Things that I tried:

  • clean reinstall of GPU drivers and some motherboard drivers

  • run sfc/ scannow

  • check disk with "chkdsk"

116774-image.png
116777-2021-07-21-10-49-01-clipboard.png

Above is the spec of my PC and I also include the Mini dumps below as well


https://1drv.ms/u/s!Al01zzrLyom4gbAsqDMUnBwy2Syd9w?e=X72YA0

Thank you,

windows-10-general
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@RyanTran-6605
Hi,

Just checking in to see if the information provided was helpful.

If the reply helped you, please remember to accept as answer.
If no, please reply and tell us the current situation in order to provide further help.

0 Votes 0 ·
Docs-4663 avatar image
0 Votes"
Docs-4663 answered

1) Please run V2 and post a share link into this thread:

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

2) Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are run in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified



https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html
https://support.microsoft.com/en-us/windows/start-your-pc-in-safe-mode-in-windows-10-92c27cff-db89-8644-1ce4-b3e5e56fe234
https://www.tenforums.com/tutorials/2304-boot-into-safe-mode-windows-10-a.html



.
.
.
.
.

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: Vote = a helpful post
.
.
.
.
.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RyanTran-6605 avatar image
0 Votes"
RyanTran-6605 answered

Thanks for quick help. I forgot to mention that I already tried driver verifier for non Microsoft drivers and run it for 2 days without BSOD.

On V2 collector. Is there anywhere else I can download the tool? since I don't have account with Eleven

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
0 Votes"
Docs-4663 answered

When were each of these RAM modules installed:

CMW16GX4M2C3200C16
CMW32GX4M2D3600C18


CMW16GX4M2C3200C16 was seen on the QVL.

CMW32GX4M2D3600C18 was not seen on the QVL.


Remove the CMW32GX4M2D3600C18 modules > monitor for computer stability / instability.


V2 is available on these websites:
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html
https://www.windowsq.com/resources/v2-log-collector.8/
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: Vote = a helpful post
.
.
.
.
.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RyanTran-6605 avatar image
0 Votes"
RyanTran-6605 answered

@Docs-4663 Thank again!

The CMW32GX4M2D3600C18 modules installed recently but the BSOD occurred prior to that as well. It is just a 16 GB version of CMW16GX4M2C3200C16 (8GB). Should I still try to remove and monitor again?

Below is V2 collector output:

https://1drv.ms/u/s!Al01zzrLyom4gbAy_WB_HHVEtngXoA?e=lLkIyY

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
1 Vote"
Docs-4663 answered

The prior BSOD bugchecks were consistent with incompatible or malfunctioning hardware.

Incompatible and / or malfunctioning RAM needs to be evaluated.

1) View the owners manual to see if there is an optimal DIMM or DIMMS when using each one or two RAM modules
2) Remove all RAM modules
3) Only test RAM modules displayed on the QVL
4) Test one module at a time
5) Post a new V2 for any BSOD


.
.
.
.
.

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: Vote = a helpful post
.
.
.
.
.






5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JennyFeng-MSFT avatar image
0 Votes"
JennyFeng-MSFT answered

@RyanTran-6605
Hi,
ntoskrnl.exe is a Windows component which means something else drove it into Fault.
When did the BSOD start to occur? Before the issue happened, did you do any modifications? Or install any updates?

It seems that you have done a series of troubleshooting operations.
If there is no problem with the driver and system files, then the hardware may also be one of the causes of this problem

A failing RAM module or Solid State Drive (SSD) could be the cause of the error you are dealing with. Your RAM and local storage may be inadequate in keeping up with the activities you carry out on your computer. This leads to frequent freezing, and subsequently to the Ntoskrnl.exe error.
Replace your hard sticks and see if the issue will be resolved.

Please understand due to security policy and from our professional level, we do not provide dump/log analysis.
You could install WinDbg from Microsoft website and analyze crash dump files.
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools

Hope above information can help you.

============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.