Hi,
Having an issue on my custom build PC whereby after a short time of playing games the PC completely freezes and have to turn the PC off by the power button.
I am running an AMD FX processor and when checking the temperature it hits 75/80 degrees when playing a game as opposed to 45-50 when not playing games. This seems very high and the likely cause of the crashes. I have heard other suggestions online such as RAM failure. Can anyone provide any input/suggestions on jow i can be sure this is a CPU issue before i invest in upgrading my CPU fan. I also have 3 cooling fans in the PC which are all functional.
When checking windows event viewer this is the entry wuaueng.dll (852) SUS20ClientDataStore: A request to write to the file "C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log" at offset 266240 (0x0000000000041000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (75 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.
Your help is greatly appreciated!
Cheers
Having an issue on my custom build PC whereby after a short time of playing games the PC completely freezes and have to turn the PC off by the power button.
I am running an AMD FX processor and when checking the temperature it hits 75/80 degrees when playing a game as opposed to 45-50 when not playing games. This seems very high and the likely cause of the crashes. I have heard other suggestions online such as RAM failure. Can anyone provide any input/suggestions on jow i can be sure this is a CPU issue before i invest in upgrading my CPU fan. I also have 3 cooling fans in the PC which are all functional.
When checking windows event viewer this is the entry wuaueng.dll (852) SUS20ClientDataStore: A request to write to the file "C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log" at offset 266240 (0x0000000000041000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (75 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.
Your help is greatly appreciated!
Cheers
Facebook
Twitter
Instagram