Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Only major difference to those is that the Time spy CPU tests uses some newer CPU commands not used in the older tests. A problem with the CPU that only exhibits itself when those commands are used could in theory be the cause.
Is there any kind of error in Windows Event Log related to the system restart?
Bios is up to date and yes the PSU is 850w Platinum
3DMark support is not very helpful too.
Latest BIOS, Drivers etc.
Phenom II X4 965
Gigabyte RX480 G1 4GB
8 GB Ram (4x2)
ASRock 970m Pro3
From what i've gathered looking into this... It doesn't work for you because it doesn't support your AMD Processor which lacks SSSE function or something like that.
If system reboots or hangs like that, it is almost always some kind of hardware problem. If it were actual software problem, there would be a crash notification in the event log.
At this point... Faulty CPUs are exceedingly rare, but it is not impossible. I *doubt* that is the reason here, but I can't rule it out. In theory it could also be some kind of motherboard issue (ie. system hangs/reboots when power draw on the CPU rises enough). Of course if this was the issue, it should also happen in Fire Strike CPU test as well. If you are using Advanced Edition, you could try running Fire Strike CPU test repeatedly to see if you can get similar issue with that - which would pretty much confirm a hardware problem.
I was able to recreate the problem and Brettwallace seems to be right.
Processor: i7 6700K
MOBO: MSI Krait 3X z170A
When the test began to load the system crashed, when I went into bios following the crash I went down to voltage which was set to "AUTO" but indicated it ran at 1.488v. So for some reason this test wanted that many volts?