New
#11
I was getting bsod every time from sleep mode. Uninstalled the samsung nvme driver and all good now as well.
I was getting bsod every time from sleep mode. Uninstalled the samsung nvme driver and all good now as well.
I also have two Samsung NVME drives, and get BSOD on resuming from sleep after updating to 1809 yesterday.
Word of caution, it does not happen always, if you resume from sleep pretty quickly (when testing), it seems to work (even with NVME driver), so there may be false positives here!
Edit: So far I've tested twice and the fix worked. I removed "Samsung NVM Express driver" using "Add & Remove programs" dialog, and for two times a row, no BSOD, will see how this work further down the road.
Edit: Maybe the topic could be renamed with including Samsung NVME so other people will also see this, if this truly is the problem.
Last edited by Ciantic; 06 Oct 2018 at 10:40.
Now I have a Watchdog Violation while using steam.
yes
Please use the beta log collector from now on.
Looks like you installed the October 2018 upgrade (17763.1 / 1809). Just a FYI that Microsoft has withdrawn the upgrade for now due to some serious problems. It will be re-released sometime in the near future.
The dump shows a problems with nvlddmkm.sys.
You already have the latest Nvidia driver 416.16 dated 10/01/2018. You can try this:Code:BugCheck 133, {1, 1e00, fffff800202d1380, 0} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+1e635d )
Remove and install latest Nvidia drivers:
Completely uninstall the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode. Then get the latest driver for your Nvidia card here: 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 check you setup again and see if there is any over-clocking going on and if there is, set all to normal/default. Also check memory timings and voltages.
Here is the info from the beta version.
Interesting, the mini dump is gone now: C:\Windows\minidump\100718-19390-01.dmp.
It was there when you ran dm_log_collector.exe. Did you delete it or run a hard drive cleanup tool like CCleaner?
Not a problem, just curious since I already have the dump.
No, I didn't run any cleaner. Do you think it is the October update that is causing it since it was pulled by Microsoft?