Computer crashes during gaming sessions

M

mornon

Member
Joined
Jun 11, 2016
Posts
6
Location
Italy
Hi,

I'm experiencing this issue while gaming on my pc. Sounds get stucked and the screen go black. No way to close the application, I always need to restart.

Here's the log I find in Event Viewer:

svchost (1660) Terminating process due to non-recoverable failure: PV: 10.0.10586.0 SV: 10.0.10586.0 GLE: 0 ERR: -1603(fucb.cxx:359): dllentry.cxx(103) (ESENT[10.0.10586.0] RETAIL RTM MBCS)

and

Faulting application name: svchost.exe, version: 10.0.10586.0, time stamp: 0x5632d7ba
Faulting module name: ESENT.dll, version: 10.0.10586.212, time stamp: 0x56fa1686
Exception code: 0xc0000602
Fault offset: 0x000000000022885f
Faulting process id: 0x67c
Faulting application start time: 0x01d1c41fa94f0346
Faulting application path: C:\WINDOWS\system32\svchost.exe
Faulting module path: c:\windows\system32\ESENT.dll
Report Id: dc697834-6688-449b-ad4c-97f34c0a7509
Faulting package full name:
Faulting package-relative application ID:


Thanks for your help!:banghead:
 
Hi mornon ... and welcome to the forums ...


If this problem started just recently, try using System Restore to return the system files to a previous, workable, condition.

System Restore in Windows 10


1) Right-click the Windows Start Menu icon
2) Select System
3) Select System Protection (a blue link in the upper left-hand corner)
4) Select System Restore
5) Choose a restore point from before the current trouble started.

Some users experienced an error similar to yours after a Cumulative Update in April. The two updates associated with the error were KB3147458 and KB3147461. You also have the option to try and uninstall the update. It's possible that when the updates re-install as part of your next automatically scheduled Windows Updates, the versions will be newer and less troublesome.
_______________

You could also check for updates/patches for the game(s) that you are running when the crash occurs, especially if it happens only for some games, and not all.

The esent.dll module is part of the "Extensible Storage Engine for Microsoft Windows", and is a system file - a part of Windows.

Let us know if this doesn't help.
 
Hi Gary, and thanks for your reply!

There are no restore points since I made a reset of my pc a week ago.

And there's no trace of the two updates you quoted, here's my installed updates folder.

updates.jpg

Game is up to date, just checked on Steam.

If you have any other advice I'd be grateful :)
 
Gaming is very demanding and stressful on computers. So whenever problems occurring during heavy game play, but the computer works fine otherwise, I always suspect (1) heat, (2) power and (3) RAM. So you need to make sure your computer is clean of heat trapping dust and all fans are spinning, then monitor your temps. I use CoreTemp to monitor my CPU temps. I also like Speccy (from the makers of CCleaner) which provides much more "System Information" and now has a system tray applet too. HWiNFO64 is also very (if not too) informative.

Speccy and HWiNFO64 will also report your voltages. The +12, +5 and +3.3VDC should be within ±5%. While these programs are not conclusive, the are pretty good. If they report voltages are missing or way off, that is most likely a mis-reading and should be ignored. And none of these programs test for ripple and other anomalies that affect computer stability. The only way a "normal" user can verify voltages conclusively is by having the PSU tested by a professional, or by swapping in a known good PSU.

And for testing your RAM, I recommend MemTest86. Allow the diagnostics to run for several passes or even overnight. You should have no reported errors.

Alternatively, Windows 7, 8 and 10 users can use the built in Windows Memory Diagnostics Tool (though I prefer MemTest86).

Note, however, that software based RAM diagnostic tools are good, but none are conclusive. To conclusively test your RAM, you need to use sophisticated and very expensive test equipment, like this $4,000 Eureka Express DDR3 DIMM Memory Module Tester. So you might try running with just a single RAM module to see if it fails. Repeat process with remaining modules, hopefully identifying the bad stick through a process of elimination. Just be sure to unplug the computer from the wall and touch bare metal of the case interior BEFORE reaching in to discharge any destructive static in your body.

There are no restore points since I made a reset of my pc a week ago.
Click to expand...
Why did you reset the computer? And some system specs might help. At this point, we don't even know if this is a PC or a notebook.
 
Digerati said:
Gaming is very demanding and stressful on computers. So whenever problems occurring during heavy game play, but the computer works fine otherwise, I always suspect (1) heat, (2) power and (3) RAM. So you need to make sure your computer is clean of heat trapping dust and all fans are spinning, then monitor your temps. I use CoreTemp to monitor my CPU temps. I also like Speccy (from the makers of CCleaner) which provides much more "System Information" and now has a system tray applet too. HWiNFO64 is also very (if not too) informative.

Speccy and HWiNFO64 will also report your voltages. The +12, +5 and +3.3VDC should be within ±5%. While these programs are not conclusive, the are pretty good. If they report voltages are missing or way off, that is most likely a mis-reading and should be ignored. And none of these programs test for ripple and other anomalies that affect computer stability. The only way a "normal" user can verify voltages conclusively is by having the PSU tested by a professional, or by swapping in a known good PSU.

And for testing your RAM, I recommend MemTest86. Allow the diagnostics to run for several passes or even overnight. You should have no reported errors.

Alternatively, Windows 7, 8 and 10 users can use the built in Windows Memory Diagnostics Tool (though I prefer MemTest86).

Note, however, that software based RAM diagnostic tools are good, but none are conclusive. To conclusively test your RAM, you need to use sophisticated and very expensive test equipment, like this $4,000 Eureka Express DDR3 DIMM Memory Module Tester. So you might try running with just a single RAM module to see if it fails. Repeat process with remaining modules, hopefully identifying the bad stick through a process of elimination. Just be sure to unplug the computer from the wall and touch bare metal of the case interior BEFORE reaching in to discharge any destructive static in your body.

There are no restore points since I made a reset of my pc a week ago.
Click to expand...
Why did you reset the computer? And some system specs might help. At this point, we don't even know if this is a PC or a notebook.
Click to expand...

First of all thank you for your help.

I reset my desktop pc a week ago because I wanted to get rid of this esent error. In this way I avoided to install the supposed culprit (April cumulative update), but it seems the error is occuring also with the may update.

Regarding my configuration, here's some details:

CPU i5 2500K
MoBo ASUS P8P67-EVO
RAM 16GB Corsair Vengeance LP - 1333
GPU GeForce GTX 670
SDD Corsair Force GT 120GB x2
PSU Corsair 700W (don't remember the exact model)
OS Windows 10 Pro Edition - upgraded from Win 7 Ultimate Edition

And in the end, the test you suggested me.

I checked my CPU and GPU temperature. While doing nothing CPU stays around 37/38°, about 60° when stressed (during gaming). GPU stays between 30-40° during normal use, reaching 75° under stress.
There was a minor presence of dust in the case, I removed it with no sensible difference output about temp.
Honestly I didn't find where to check voltage on HWiNFO64 and I don't have a spare PSU to swap with the one currently installed, when I come back home this evening I'll check again on HWiNF.

I let MemTest86 run all night long and it found no error with my RAM.

I still have to remove my RAM modules one by one and then try to stress them with some benchmark.

What could I try if an hardware defect is not the answer?
 
Sadly, you found out why resetting Windows (or formatting and reinstalling) should always be a last resort option - it frequently does not help and often destroys clues to the real problem along the way.

You have to click the Sensors button to see the voltages listed under your motherboard in HWiNFO. It takes a minute for that data to appear - in fact, on my system, it even reports HWiNFO is not responding, then suddenly the new window opens.

Other than that, I am afraid I am out of my element. I cannot find any information on "602" ESENT errors. Possible solutions I am finding are running sfc /scannow and re-registering esent.dll but it seem resetting W10 should have taken care of that. Hopefully OldGrayGary will have some more ideas or another Windows expert will stop by.
 
Yesterday I run an sfc /scannow and it found a lot of things to repair. None of them was related to esent.dll thou.
I restarted my pc and run it again, no error was found.
This evening I'll play for a couple of hours and keep the thread updated if the esent nightmare will occur again.

Thanks again!
 
Hi all (and thanks to Digerati for helping!) ....


Sorry I've been away so long .... (lots of local repairs here in Southern California! .... keeping this old man busy...)

Glad that the System File Checker worked so well for you so far! (sfc = system file checker). If sfc finished successfully, it might have been able to fix your esent.dll issues. If sfc finished with the words "found but could not repair" some corruptions, and if the errors come back - let us know. There is a tool called "DISM" that can work to restore the system files to a healthy condition. DISM can sometimes help complete the repair when sfc isn't able to fix all of the trouble.

If it's all fixed: congratulations on your good work!
 
A fast update: yesterday I installed June cumulative update and then I played for 3 hours in a row without any issue. Anyway I'll keep my fingers crossed, just in case... :)

Thank you guys for your priceless advices!

Have a nice day!
 
A fast update: yesterday I installed June cumulative update and then I played for 3 hours in a row without any issue.
Click to expand...
Great! Not sure why a Windows reset failed to fix the problem but running sfc /scannow appears to have done the trick. Anyway, still a good idea to keep an eye on your temps (I keep CoreTemp running in my system tray full time) and to verify your voltages are good too.

Sorry too for my delay in responding. We've had some above average temps here and of course, my AC went out. The darn cooling fan motor for the compressor outside seized so I put an old box fan that's been in the garage for the last 25 years on top of the unit and tied the hose nozzle to a stake spraying a very fine mist on the coil fins and that seems to be doing the trick! At least enough to hold me over until the new motor comes in. But I was worried about some thunderstorms coming through getting this fan wet so I went out and bought a new Lasko Weather Shield Fan yesterday. Worked great - for about 3 hours then that motor seized! :banghead:

So now I'm back to the 25-year old box fan again with an old plastic shower curtain hung over it in case it rains again. 9:10AM and already 86.3°F outside, but holding at 74° indoors - so fingers crossed.

Anyway, glad again your system is working and thanks for the followup.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top