F5F Stay Refreshed Power Users Overclocking i7 3770K experiencing hot BSOD while idling or running

i7 3770K experiencing hot BSOD while idling or running

i7 3770K experiencing hot BSOD while idling or running

Pages (2): Previous 1 2
Z
ZeroBruh
Junior Member
3
10-12-2016, 05:14 PM
#11
Intel CPU diagnostic link provided.
Prime95 + Core Temp test used for worst-case CPU temperature, around 105degC Tjmax; normal scenarios should stay at 75degC or less, which should be fine even at 90degC in Prime95.
So...
*The "srttrail.txt" appears to be a frequent problem. I’m unsure what the real issue is since no good solutions seem available. It seems like a LOG file, but it doesn’t help much.
I’m still confused about the second hard drive test. Was this a CLEAN INSTALL of Windows? If not, it’s not very informative (for example, if you cloned the drive). If yes, then it’s puzzling because a CPU failure usually brings more problems like specific BSODs.
It looks like data corruption might be the cause. If you haven’t done a CLEAN INSTALL, I recommend doing so.
I think there could be some driver or software issues, but I don’t have any useful details to share.
Other possible steps are:
a) Scannow (sfc /scannow), and
b) Checkdisk (chckdsk C: /f )*
Z
ZeroBruh
10-12-2016, 05:14 PM #11

Intel CPU diagnostic link provided.
Prime95 + Core Temp test used for worst-case CPU temperature, around 105degC Tjmax; normal scenarios should stay at 75degC or less, which should be fine even at 90degC in Prime95.
So...
*The "srttrail.txt" appears to be a frequent problem. I’m unsure what the real issue is since no good solutions seem available. It seems like a LOG file, but it doesn’t help much.
I’m still confused about the second hard drive test. Was this a CLEAN INSTALL of Windows? If not, it’s not very informative (for example, if you cloned the drive). If yes, then it’s puzzling because a CPU failure usually brings more problems like specific BSODs.
It looks like data corruption might be the cause. If you haven’t done a CLEAN INSTALL, I recommend doing so.
I think there could be some driver or software issues, but I don’t have any useful details to share.
Other possible steps are:
a) Scannow (sfc /scannow), and
b) Checkdisk (chckdsk C: /f )*

Pages (2): Previous 1 2