Counter-Strike 2

Counter-Strike 2

View Stats:
Frosty266 Nov 9, 2015 @ 8:16am
nvd3dum.dll game crash, out of options
Good day all!
Whenever I play CSGO, after about 20-30mins the game crashes to desktop with the message that csgo has stopped working. After looking in event viewer, the same error seems to be the problem every time. The error is as follows :

Faulting application name: csgo.exe, version: 0.0.0.0, time stamp: 0x55ce3d41
Faulting module name: nvd3dum.dll, version: 10.18.13.5850, time stamp: 0x560f31fe
Exception code: 0xc0000005
Fault offset: 0x00443d54
Faulting process id: 0x7c2c
Faulting application start time: 0x01d11634c2ed7ff4
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\csgo.exe
Faulting module path: C:\Windows\system32\nvd3dum.dll
Report Id: 5b1cbb5b-822c-11e5-8d1b-50465d9e1f65

believe the problem is from nvd3dum.dll, but I only recieve this problem with counter strike go, so CSGO has to be the problem.

Things I have tried :
Reinstalled CSGO
Uninstalled and reinstalled NVidia drivers
Using older nvidia drivers
Removed the CFG folder
Playing on different graphics settings
as well as all the administrator settings.

This may not be the place to post this, but Steam support as always is the worst from any game in the world, after 9 days I still have no reply, and I have google'd hours away looking for an answer.


OS: WIndows 7 Proffesional 64bit
CPU : Intel core I7-3770k
Ram : 8Gb DDR 3
Display : NVidia Geforce GTX 560 ti





I would appreciate any and all help!
Thank you to all

Last edited by Frosty266; Nov 9, 2015 @ 8:50am
< >
Showing 1-6 of 6 comments
Pagusse Nordic Apr 7, 2018 @ 2:04pm 
Have you find any solution to this problem? I know its an old post, but muck* this problem. Its driving me crazy. And seems like no1 has any idea how to fix this.
Ancient Oldie Apr 7, 2018 @ 2:06pm 
goto startmenu -> run -> type; sfc /scannow

let it run, try again.
Pagusse Nordic Apr 7, 2018 @ 3:49pm 
I delete my Graphic card via DUD (Display Driver Uninstaller) in safe mode. And did that sfc thing via powershell (elevated). Then started CS:GO. (No problem came up with sfc)

It crashed again but this time the problem is not nvidia. Its something called ESENT in the event viewer. I have'nt found anything about it yet. If so, i will post it here so maybe someone will use it later. :)

Last edited by Pagusse Nordic; Apr 7, 2018 @ 3:50pm
Ancient Oldie Apr 8, 2018 @ 2:44am 
Originally posted by RetardedPuppet:
I delete my Graphic card via DUD (Display Driver Uninstaller) in safe mode. And did that sfc thing via powershell (elevated). Then started CS:GO. (No problem came up with sfc)

It crashed again but this time the problem is not nvidia. Its something called ESENT in the event viewer. I have'nt found anything about it yet. If so, i will post it here so maybe someone will use it later. :)
That's kind of a a hard one to troubleshoot. Personally I would just reinstall the computer because that's a quick solution. Most of these ESENT errors seem to be coming from windows search, but they could be related to certain SSD's too.

Try disabling the windows search service:
start -> run -> type: services.msc
find windows search -> disable it, reboot, try again.
Pagusse Nordic Apr 8, 2018 @ 4:33am 
I think i found the solution. Here is what i did since the beginning...

1. Reinstall Nvidia drivers with DUD (Display driver uninstaller in safe mode)
2. disabled the Superfetch thru services.msc
3. Play with computer's power management and set it on high performance. +set everything on "never" so nothing can turn itself off.
4. and lastly... I have an ssd for my OS and an hdd for my data. My data drive named D. Go to your Computer and select D, then properties. Then there is 2 checkbox at the below. Untick the second one. I don't know what it is in English. My W10 is Turkish... (This makes data reading pretty slow, but you can turn it on after Microsoft release a solution for this.)

Its been 2 competitive match in CS:GO (almost 3 hours.) and it didnt crashed. It was crashing 2-3 times in 1 match before this solution. BTW there is still ESENT info logs coming up in the event viewer.

Let me know if this works for you guys. And please mark it as answer if it is so.

P.S: I don't know which step fixed the issue. I pretty much did all things at the same time and didn't bother to test it.
Ancient Oldie Apr 8, 2018 @ 4:54am 
Originally posted by RetardedPuppet:
I think i found the solution. Here is what i did since the beginning...

4. and lastly... I have an ssd for my OS and an hdd for my data. My data drive named D. Go to your Computer and select D, then properties. Then there is 2 checkbox at the below. Untick the second one. I don't know what it is in English. My W10 is Turkish... (This makes data reading pretty slow, but you can turn it on after Microsoft release a solution for this.)

Great. The 2nd checkbox is the windows indexing from windows Search. So that seemed to be the problem.
< >
Showing 1-6 of 6 comments
Per page: 1530 50

Date Posted: Nov 9, 2015 @ 8:16am
Posts: 6