System freeze under high load

n00b42

Reputable
Apr 22, 2014
4
0
4,510
Under high load (e.g. gaming) my system freezes after some time (often about half an hour).
Running Prime95 results in a freeze after a few minutes (around 3-5min).
With "Freeze" I mean the display freezes (image still there, but no changes any more), and I can not interact with the system any more. [Hard reset required]

[My system]
Mainboard: Gigabyte GA-990FXA-UD3
CPU: AMD FX-8320
(CPU Cooler: Scythe Mugen 2)
PSU: OCZ Fatal1ty 550W
GPU: Gigabyte Radeon HD 7870 2GB
Memory: 2 x 4GB GeIL EVO POTENZA
HDDS: WD2TB, Samsung 830 (128GB), Samsung 840 (256GB)
OS: Win 8.1

[Gathered information]
Running hwmonitor I checked the temperature until a freeze occured, showing no problem. The CPU stayed at around 40°C, with a max of 41°C; GPU at around 30°C

[Already tried]
* Considered buggy game -> tried Prime95 -> issue occured earlier
* Considered a faulty driver -> run Prime95 in safe mode -> issue occured
* Considered problem with either OS or HDD/SSD -> used Knoppix and run Prime95 -> issue occured
* Considered faulty memory -> run memtest -> multiple passes
* Considered faulty memory -> replaced the 2 modules by different combinations of other modules (1x 2GB, 2x 2GB, 1x 4GB) -> issue occured
* Considered problem with GPU -> switched GPU with old one -> issue occured as well
* Considered problem with CPU -> switched CPU with older one (AMD Phenom II X4 955) -> issue did NOT occur.

Resumee so far: Following my experiments I think the problem is either the CPU, mainboard, or PSU.
The working system with the Phenom II can be explained by the lower power consumption/heat as contrasted with the FX 8320.

Anyone an idea what exactly the problem could be / how to determine which one is the faulty part to sent it in? Any experiences with Gigabyte/AMD customer service?
 

n00b42

Reputable
Apr 22, 2014
4
0
4,510
After replacing every part but the CPU i sent it back to AMD.
After checking they replaced it with an 8350, and now everything works fine.
So either it was an incompatibility (MB<->CPU) or a faulty CPU.