Time Spy crashed on CPU Test : 3DMark General Discussions


Very unusual. Do Sky Diver and Fire Strike CPU tests work normally?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? Yes, every other benchmark works and finishes. I have 8 events from the 8 crashes just saying the system rebooted without shutting down properly. Do you have latest BIOS on it Mobo, and what graphics card are you using? Also is your PSU sufficient? MSI GTX 1080 SeaHawkBios is up to date and yes the PSU is 850w Platinum Same issue. Time Spy CPU Bench does not work. “3DMark Time Spy Windows Workload funktioniert nicht mehr”. All other Benchmarks are working.3DMark support is not very helpful too.Latest BIOS, Drivers etc.Phenom II X4 965Gigabyte RX480 G1 4GB8 GB Ram (4×2)ASRock 970m Pro3 Same issue. Time Spy CPU Bench does not work. “3DMark Time Spy Windows Workload funktioniert nicht mehr”. All other Benchmarks are working.3DMark support is not very helpful too.Latest BIOS, Drivers etc.Phenom II X4 965Gigabyte RX480 G1 4GB8 GB Ram (4×2)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. Sorry, Phenom IIs are not supported by Time Spy (lack of SSSE3 commands) Yes, every other benchmark works and finishes. I have 8 events from the 8 crashes just saying the system rebooted without shutting down properly. 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. check your vccio and system agent voltage, some mobos dont run well on auto Yes, every other benchmark works and finishes. I have 8 events from the 8 crashes just saying the system rebooted without shutting down properly. 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 z170AWhen 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? More like “that motherboard/CPU is not fully stable without extra volts”. The test is indeed quite heavy on the CPU, but it should work on that hardware without manual adjustments. I’ve swapped over to a Gigabyte Gaming 6 Z170X will update with results later.

Source

Leave a Reply

Your email address will not be published. Required fields are marked *