Computer Crashes consistently, once a day almost.

[jayric18]

To start things off right, my specs are...
Motherboard: BIOSTAR TA970
Processor: AMD FX(tm)-8320 Eight-Core Processor (3.50 GHz)
Hard Drive: ST3320620AS
SSD: PNY CS1311 240 GB SSD
Graphics Card: Nvidia GeForce GTX 760
Power Supply: CORSAIR TX Series TX750M 750W 80 PLUS Gold Modular Power Supply
RAM: 2 Sticks of DDR3 4GB
Operating System: Windows 10
I am a PC gamer that runs with two separate monitors, since November 2017 I have been noticing that my computer has been completely freezing consistently. It has gotten to the point where I can rely on the fact that it freezes once per day, once every time I start up for a gaming session. Back in December I tried to diagnose this problem and purchased the Powersupply listed in the specifications. This has not resolved my issue. I updated all my drivers, I have the most recent BIOS from the manufacturer of my motherboard, I ran chkdsk, I ran sfc /scannow, and I downloaded MSI afterburner to see the temps of the graphics card as I play games and I modify the fan speed depending on how hot the card is running. I have tested my RAM and it came up with no errors, I have checked both the hard drive and the SSD and defragged the hard drive and optimized both of them. I cleaned my registry and temp files with Advanced SystemCare. When I ran CrystalDiskInfo it told me that I had 1 preallocated sector on my HDD. I am out of options, frustrated, and desperate, please help!

 

[accessrandom]

Have you checked your Windows event viewer to see if there are any clues as to what is causing these crashes (whether it's the game itself, a driver, or something else)?

 

[jayric18]

Under Administrative Events it lists a few errors and warnings but the only thing that is marked as critical is me forcing a restart... The first one is...
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
See https://go.microsoft.com/fwlink/?linkid=832647 for more details.

The second one is...
Certificate for local system with Thumbprint e5 74 47 fb 75 6e a2 5a 6c 28 00 b6 6b af cf d3 a0 81 63 53 is about to expire or already expired.

The third...
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

The last event in the Windows Log under application was
Successfully scheduled Software Protection service for re-start at 2118-01-26T18:33:49Z. Reason: RulesEngine.

The last event in System under Windows Log before the crash was
The access history in hive \??\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-Provisioning-Sequence.dat was cleared updating 0 keys and creating 0 modified pages.

I am not sure what any of this means, Thank you for the response too by the way!

 

[accessrandom]

At first glance, none of the log entries seem to have anything to do with gaming. You could try this link which shows you how to turn off certain programs at startup.

For most games, though, it's a driver problem. Just another thing to try - go into nVidia's control panel and adjust the acceleration settings there. Worst case scenario - disable hardware acceleration as shown here for Windows 10, which will make game performance worse but should be tried as a last resort in the process of elimination.

 

[jayric18]

For now, I changed the setting in the NVIDIA Control panel depicted here... https://gyazo.com/a6388ca0f781698751779a8feb2221ac
The bottom of the three buttons was checked before, and now it should let the application itself decide instead of forcing a certain method onto the card. Whether or not that is sufficient enough to change anything is something that we shall see in the coming days. The setting is described as "Instead of using the 3D hardware-acceleration settings from this control panel, the 3D application will set the values to be used by your graphics card" I attempted to follow the link you sent to disable hardware acceleration through windows but when I looked for the display settings, none of them referenced hardware acceleration at all. Selective Start-Up will be the next attempt, should this not solve my problem. But only time will tell! I will keep you posted and I really appreciate your help!!!!!!

 

[accessrandom]

Good luck. Hopefully that is it. The second website to disable hardware acceleration is toward the bottom of the page, where you need to go into the registry to disable it in Windows 10. That is such an intrusive measure, I'd use that as a last resort.

One more thought - are you gaming on both monitors, or are you browsing/viewing Youtube on one while gaming on the other? If so, I had problems with my PC crashing until I turned off hardware acceleration in Chrome (under Settings -> Advanced).

 

[jayric18]

Today I have not crashed at all so far, once while gaming and watching videos all of my programs stopped responding for a minute, but other than that there have been no problems! I am gaming on the main monitor and browsing the internet/viewing Youtube videos on the second one. As I was typing this message, the game on my primary monitor, in this case, World of Warcraft, stopped responding, and then a little box appeared in the top left of my monitor that was labeled Microsoft Windows at the top, slowly, all of my other programs stopped working and the cursor stopped moving for half a second before all of the running programs resumed responding. Nothing looked out of the ordinary in the task manager as that was happening, nothing out of the ordinary, in the event viewer, this popped up...
A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.
What do you believe may have caused this?
EDIT: This just happened again, this time the box was populated with the error that Microsoft Windows has stopped responding and that it may resume if you wait, it gave me the options to end process or cancel. The event logs are showing three new warnings now...
taskhostw (6308,D,0) WebCacheLocal: A request to write to the file "C:\Users\JayPC\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 225280 (0x0000000000037000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

taskhostw (6308,D,0) WebCacheLocal: A request to write to the file "C:\Users\JayPC\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 225280 (0x0000000000037000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

and

taskhostw (6308,D,0) WebCacheLocal: A request to write to the file "C:\Users\JayPC\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

What do you recommend I do?

 

[accessrandom]

I know you mentioned that you had scanned your hard drives earlier, but can you please try scanning the C: drive for bad blocks and run a SMART test? If you don't have something like HD Tune Pro (which I use), there are free scanning tools out there. Depending on the manufacturer of your SSD or HDD (whichever is the C drive), you can obtain manufacturer-specific scanning tools (like SeaTools).

 

[jayric18]

I used CrystalDiskInfo to see if there were any warnings or cautions given out, and the only one that I saw was not on the C: drive, but on the D: drive, the C: Drive is the PNY SSD CS1311 and there seem to be no problems with it. Windows 10 is installed on the C: Drive, and the only issue with the HDD D: drive is that I have 1 reallocated sector. When I went into the CMD prompt and typed out wmic diskdrive get status, I received a message saying...
Status
OK
OK
A few minutes after start up, I noticed that something stopped responding again, so I checked the Event Viewer and saw...
svchost (14624,D,0) Unistore: A request to write to the file "C:\Users\JayPC\AppData\Local\Comms\UnistoreDB\USS.jtx" at offset 2715648 (0x0000000000297000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

And

svchost (14624,D,0) Unistore: A request to write to the file "C:\Users\JayPC\AppData\Local\Comms\UnistoreDB\USS.jtx" at offset 2715648 (0x0000000000297000) for 32768 (0x00008000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Could there have been a setting that I accidentally disabled somewhere that would cause this error or is it guaranteed a hardware issue? How else would you recommend I proceed? Strange coincidence that the time has consistently been 36 seconds, could that have any significance?

 

[accessrandom]

Whether it's hardware or perhaps a corrupt file system, all the logs point to something on the C drive. Try renaming the files that are indicated in the logs Whatever is writing to those files would then write to another part of the disk. Rename them back if that causes further instability.

Does CrystalDiskInfo do scans of blocks? If it's only a SMART monitor, that may not catch everything. I think you'll need to do a full error scan.

 

[jayric18]

I just gave a download to Hard Disk Sentinel as well and it said my SSD (The C: Drive with Windows on it) is in perfect health...
https://gyazo.com/fc220a72af349780d74d8f58f80d1d0f
The 99% on the HDD (The D: Drive) is because I have 1 reallocated sector.
I tried modifying the name of the file that was giving errors, but it gave me an error because the file is in use.
https://gyazo.com/bd0fe55189b98f01e5eeec772a856cdf
How would you recommend I proceed except by doing a fresh install of windows?

 

[accessrandom]

For the files that are in use, try entering safe mode in Windows 10.

To check the possibility for a corrupt file system, try a chkdsk /f.

Let me know if that helps...

 

[jayric18]

After a several day experiment, to see if my issue persisted, I found my problem not solved. Some surface research connected crashing and windows problems to the Fall Creators update that rolled out a couple of months ago, something that came up in my research as to the cause, or coincidental appearance, of something that shows up in the event log as "DllHost (8288,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000."
There are a few different names before "The beta feature..." coming up but this seems to be a beta feature that rolled out with the update and is causing people problems.
Am I correct in my assumption that this is possibly the cause?
How would you recommend I proceed in solving my crashing/freezing/not responding problem at this point. I did modify the files you suggested. I can confirm that at most, once per day, the system crashes and requires a forced restart.