NTOSKRNL.exe Causing BSOD

Prophesy · 04 Sep 2018

About 4 months ago I noticed that at least once a day my computer would restart when it tried to go into a sleep/idle state. So far it has never crashed while I was working/gaming. I've tried memtest for 8 passes (all good, i actually did this twice), updated all drivers I could, and updated my Bios. I thought I knocked it out with the bios update but I noticed it happened again last night. Any help would be greatly appreciated, I'm out of my depth here.Attachment 202407

Ztruker · 04 Sep 2018

Dump indicates a problem with nvlddmkm.sys.

Code:

fffff608`19ff6968  fffff800`05994ae4Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f5be1f8d25335236\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x924ae4

Driver Description: nVidia Video drivers
Driver Update Site: http://www.nvidia.com/Download/index.aspx

You have the most recent driver available. I would suggest the following.

Remove and install latest Nvidia drivers:

I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode. Then download the latest driver for your Nvidia card from here again: NVIDIA Driver Downloads

Then do a custom install of only the NVidia graphics driver and the PhysX driver.

See if that gets rid of the problem.

ALso, please run the Beta log collector. It's at the bottom of the BSOD posting instruction page, with help on how to use it. It collects additional data that may help to further identify what is happening.

Prophesy · 04 Sep 2018

Attachment 202420
I will do a clean install of the Nvidia drivers as you suggested as well, I went ahead and included the beta log. Thank you

Prophesy · 05 Sep 2018

Apologize, not trying to bump, but had another bsod and wanted to include that beta log.Attachment 202637

cwsink · 05 Sep 2018

Hi Prophesy,

Does EVGA Precision X have a Periodic polling option? If so, can you try disabling it and see if the problem continues? I get the impression EVGA Precision X is HWiNFO64 reskinned so I'm wondering if the suggestion in this thread might apply to your situation.

Ztruker · 05 Sep 2018

Also use Samsung Magician to check if you have the latest Firmware for your Samsung SSD 850 EVO 1TB. If not update.

Prophesy · 05 Sep 2018

cwsink said:

Hi Prophesy,

Does EVGA Precision X have a Periodic polling option? If so, can you try disabling it and see if the problem continues? I get the impression EVGA Precision X is HWiNFO64 reskinned so I'm wondering if the suggestion in this thread might apply to your situation.

There is a "polling period" that can be adjusted, currently its default is 1000 ms, I'm assuming I could set it to 0 and see if that stops it, but I don't see the option to disable it. Also ran Samsung Magician, I'm running the latest firmware.

cwsink · 05 Sep 2018

Prophesy said:

There is a "polling period" that can be adjusted, currently its default is 1000 ms, I'm assuming I could set it to 0 and see if that stops it, but I don't see the option to disable it. Also ran Samsung Magician, I'm running the latest firmware.

Hmmm... it's worth a try although I'd be worried that could set the polling as constant. If that doesn't work can you try setting the rate to -1?

edit: If I'm correct about it being HWiNFO64 with a different skin perhaps another thing to try would be removing EVGA Precision X and trying HWiNFO64 to see if it has the same features. A new version of HWiNFO64 was released in the last few days.

Prophesy · 05 Sep 2018

I'll gladly remove Precision if that is causing the issues. Out of curiosity do the newest logs show anything different from my other crash logs?

cwsink · 05 Sep 2018

Both dumps were generated when a thread owned by PrecisionX_x64.exe crashed due to an access violation with both having the same bugcheck code and parameters: BugCheck D1, {0, 2, 8, 0}. The raw callstacks look very much the same as well. My interpretation would be that an older version of the utilities is calling newer versions of the Nvidia drivers in a way that makes the calls sometimes invalid.

This reddit post seems to be by someone experiencing the same issue recently. I haven't heard back as to whether uninstalling HWiNFO64 fixed the problem, yet. Same bugcheck code with the same parameters, HWiNFO64.exe process, and the raw callstack looks virtually identical to yours.