HELP GETTING BSOD dpc watchdog violation ntoskrnl.exe+2036f7

Toggle sidebar Toggle sidebar
G

garnet2boots

Oct 6, 2018
13
0
10
Help been getting an occasional freezing and then a BSOD recently whenever coming from a fresh boot up. But after the restart the pc seem to ran fine.

I did a nvidia driver update, flash the bios with the latest firmware, and also change the IDE ATA/ATAPI Controllers to Standard SATA AHCI Controller.

Still the same problem

https://i.imgur.com/ZIHihCB.png here is a screenshot of the minidump

Here is the minidump file https://drive.google.com/file/d/1zlPDDiWpSvnlljiegk71RmdXkXeqLmnQ/view?usp=sharing

Please help 🙁 I am at my wits end with this freezing

UPDATE: Someone suggested to me it might be malwarebytes so i uninstalled it.

got the BSOD again. here is the new minidump file

https://drive.google.com/file/d/1PARalo5DQVLwSmGUTQeo3hTaSzcceORS/view?usp=sharing

It seems to happen when your turn it on from a successful shutdown then induced it by playing a youtube video. When it crashes and either it auto restarts or i force shutdown it and then turn it on, it never happens then.

 
Sort by date Sort by votes
looks like windows updated only a part of your graphics driver on oct 1
nvlddmkm.sys Mon Oct 1 22:26:43 2018

the other part of the graphics driver is from june.

basically the bugcheck is cause be the graphics driver. you should go to the nvidia website and directly update teh gpu driver and is gpu sound support.
(reboot before after you install the driver, to prevent problems with windows updated having pending installs)
-----------------
it is unexpected that you would be running this driver:
EldoS Corporation RawDisk Driver
C:\WINDOWS\system32\drivers\rsdrvx64.sys Thu Feb 12 05:01:49 2009
https://carrona.org/drivers/driver.php?id=rsdrvx64.sys

or even this one (very old)
\SystemRoot\system32\pwdrvio.sys Mon Jun 15 18:43:45 2009
https://carrona.org/drivers/driver.php?id=pwdrvio.sys

old driver:
\SystemRoot\System32\Drivers\PxHlpa64.sys Tue Apr 24 10:26:29 2012
https://carrona.org/drivers/driver.php?id=PxHlpa64.sys

I would check for a update to
Gigabyte Easy Saver - mobo power utility driver
C:\Windows\gdrv.sys Wed Jul 3 21:27:55 2013


machine info:
Manufacturer Gigabyte Technology Co., Ltd.
Product Z170X-Gaming 7
Processor Version Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Processor Voltage 8bh - 1.1V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 3900MHz
 
Upvote 0 Downvote


THANK YOU VERY MUCH FOR THE INFO!

I did a clean uninstall and reinstall of the driver following this guide https://www.wagnardsoft.com/content/ddu-guide-tutorial

will also check try checking updates for:
Gigabyte Easy Saver - mobo power utility driver
C:\Windows\gdrv.sys Wed Jul 3 21:27:55 2013

is it ok to ignore the following three you mentioned? The ones below:
EldoS Corporation RawDisk Driver
C:\WINDOWS\system32\drivers\rsdrvx64.sys Thu Feb 12 05:01:49 2009
https://carrona.org/drivers/driver.php?id=rsdrvx64.sys

\SystemRoot\system32\pwdrvio.sys Mon Jun 15 18:43:45 2009
https://carrona.org/drivers/driver.php?id=pwdrvio.sys

\SystemRoot\System32\Drivers\PxHlpa64.sys Tue Apr 24 10:26:29 2012
https://carrona.org/drivers/driver.php?id=PxHlpa64.sys



 
Upvote 0 Downvote
I was going to sugest a clean install just because of all of the old programs.
when you do the install you want to take care with the windows updates. the windows updates for the Gpu requires a reboot while if you update with the nvidia software it does not require one. Main problem is the mix between the two install methods. just make sure you reboot before you install then nvidia gpu setup program.






 
Upvote 0 Downvote


Yep I did a clean uninstallation of the nvidia drivers while in safe mode and not connected to the internet. Already downloaded the driver installer by that time.

After uninstallation i did a reboot into normal mode while still not connected to the internet then did a driver install, after reinstalling the latest driver I did a reboot one more time and connected to the internet. Will let you know how it goes if it creeps up asap!
 
Upvote 0 Downvote
the stack for nvlddmkm.sys is corrupted.

the driver is dated oct 1 2018 and was pushed out by microsoft. I would read this and see if it is related to your isssue. (new driver that requires a firmware update to the gpu if you use displayport connection)
http://www.tomshardware.com/forum/id-3788495/warning-nvidia-driver-411-bsod-displayport.html

if this is not related i would go in and turn off all audio sources that do not have a speaker connected to them.
you might even roll back the video driver but since it is in the hidden driver store you will have to use this
google "how to remove drivers from the driver store" it involves using the pnputil.exe
to remove the driver package so it does not automatally get reinstalled.
I would also run microsoft update to see if they removed the update.

-------------
system still shows old drivers being installed.



nVidia HDMI Audio Device (nForce chipset driver)
\SystemRoot\system32\drivers\nvhda64v.sys Tue Jun 26 01:22:26 2018

\SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_54bd1f10ac116cd5\nvlddmkm.sys Mon Oct 1 22:26:43 2018
 
Upvote 0 Downvote
Hi johnbl, I opened up the installer and yes it showed this window which means that this could be the fix hopefully. Since my main monitor is hock up via display port.

https://i.imgur.com/Tqy1Q0S.png

Will also take a look at what you suggested in removing the driver from the driver store if the above update still doesn't fix this.
 
Upvote 0 Downvote


Is it safe to just delete the driver store files related to nvlddmkm.sys since reading its directory location its just a place wwhere windows store older driver versions, in this case an older nvidia drivers
 
Upvote 0 Downvote
driverstore was implemented to restore a driver that gets deleted manually or updated without being placed in the driverstore. ie if you boot up and delete a driver or update it , then when you reboot the system detects the file is missing or changed and gets a copy from the driverstore and places it back. if you delete the package from the store, you want to install a new driver first. I think the windows plug and play will detect that you don't have a driver and will go up to the internet and download the Microsoft default driver. (not sure, have not looked at how it works in years)
you might download the nvidia setup package, unplug your network connection or stop windows plug and play service, then remove the driver package from the driverstore, then install the nvidia package and turn on plug and play and plug your network cable back in.


the stack was corrupted, maybe because the driver did not respond and more calls were made until the stack overflowed. (or a audio driver responded when it should not have and overflowed the gpu sound driver)



 
Upvote 0 Downvote
So i will just delete it? no need to reinstall the nvidia driver since I just recently installed a fresh one? I will probably do this if the firmware display port update still doesn't fixed this.

Thanks again johnbl
 
Upvote 0 Downvote


Ok i did a completely clean of the driver using DDU https://www.wagnardsoft.com/content/display-driver-uninstaller-ddu-v18002-released

I check the directory where that file nvlddmkm.sys resides \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_54bd1f10ac116cd5\ and it has been deleted as well as other nvidia related stuff folders

I did a the following command dism /online /get-drivers /format:table > c:\tmp\drivers.txt to dump a list of the drivers installed and this is the results https://docs.google.com/document/d/1KLkApnbZljP5uDc_3vHFm1hyu7mLqIG6-8fW0eZfQHQ/edit?usp=sharing it has removed any driver that is nvidia related.

I did an install of the driver again from the recent nvidia driver installer. I checked the directory where it temporary stores it contents and I found nvlddmkm.sys in it.

After installation of driver when i check back at \SystemRoot\System32\DriverStore\FileRepository\ I now see the folder nv_dispi.inf_amd64_54bd1f10ac116cd5 again with the same contents including nvlddmkm.sys

I did a another test dump to see the drivers installed and here are the results. https://docs.google.com/document/d/1byQ1H4z1tGeV9fU16o7y-XDtfb_GRUEEs-GjbgmbERo/edit?usp=sharing

I did this all the while was never connected to the internet.

 
Upvote 0 Downvote
take a look at this tool, https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
select the hide microsoft entries option and it should show the drivers that are loaded as well as the timestamp.
you can also uncheck drivers to prevent them from loading when you reboot. or delete driver entries you never want to load.



 
Upvote 0 Downvote
start with running memtest from a usb stick make sure your ram is good and not damaging windows. in the bios check the power supply voltage make sure the 12v rail is at 12v. in windows use hardware info set it to logging and sensor make sure the power supply rails are holding. on the mb make sure it has the newest bios file and xmp profile for the ram is on and ram speed is set right.
 
Upvote 0 Downvote


Dm9p2ZV.png
Here is an image showing the 2 items invovled? Is it safe to unchecked these johnbl 🙁 kinda worried something might happen
 
Upvote 0 Downvote
I would uninstall any feature nvidia features i was not using.
like the streaming, uninstall if you don't stream to another device, I would uninstall the nvidia telementry, and then run autoruns to see what is left. IE to make sure nvidia items were removed from the task scheduler.
the nvidia streaming software can break due to bugs in your network driver. when it breaks it crashes the GPU driver.
i don't see why you would have multible copies of the telemetry software scheduled to run. most likely just a bug in the installer if it is run several times. it looks like it would only report bugs to nvidia anyway. Microsoft windows error reporting reports the bugs to Microsoft then hands the collected data to nvidia so you would be covered.
I would turn off the nvidia error reporting and streaming just because it uses a limited network resource (tcp/ip connections. when the connections are maxed out they go into a 300 second wait period before you get to reuse the connection.
you can see the state of the connections by starting powershell.exe or cmd.exe as an admin then run the command
netstat.exe /b

it shows the active connections and the name of the binary program that made them.
close_wait is a 300 second timeout state





 
Upvote 0 Downvote


Hi johnbl i got a recent BSOD here is my latest dump https://drive.google.com/file/d/1OKSWdniqYrB0MPTfp8c5cgBKuZgjtkD-/view?usp=sharing I haven't yet disabled anything. I might try to disable the sound from nvidia
 
Upvote 0 Downvote
maybe some malware running on your graphics card?
the graphics driver jump execution to some location in kernel mode memory, it just runs and fills up the stack and jumps back into the graphic driver. At some point it takes too long and a timer expires and the bugchek is called because the system thinks the gpu is not responding (within 2 seconds)

it could be a bug in one of the nvidia addon drivers but normally the kernel memory in the raw stack dump would be associated with the driver.
the raw stack just had huge number of kernel mode address in it that were not part of a listed driver. it could be malware:
I think there is malware that does bitcoin mining on the GPU now. if the malware takes over 2 seconds before giving control back to the gpu driver you will get this bugcheck.

------------------------

i would also look into why a machine with a bios date 03/09/2018
has this driver installed:
Gigabyte Easy Saver - mobo power utility driver (from 2013)
EldoS Corporation RawDisk Driver from 2009 ?





 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom