Stability issues when running loop testing and get error about display res firestrike

[litwicki22]

Hello i have a problem with 3dmark 13 Firestrike test. Firestrike is crashing on loop setting with no GPU crash and no Driver crash. It just showing "Window focus lost during benchmark run - display resolution had changed" or "Dx init error".
I can loop for 10 hours without issue, but generally it crash after 11 hours. I check system event viewer and this is not driver crash. Simply random crash ""Window focus lost during benchmark run - display resolution had changed." or "Dx init error".
I can loop easily Firestrike for example 10 hours without crash. But sometimes it crash after 11-12 hour. Weird, why after such many hours?

Is this something with my card or system? My card is Gtx 980 Ti reference, no OC. I am using drivers 353.38 HOTFIX.

rest pc:
4790k stock
8gb ram
Corsair 750 RM

I dont have any background programs, only GPUZ installed thats all.


Infraction issued for Trolling and defying moderator warnings of repeat posts.

-Rvenger

 

[LTC8K6]

I'm having stability issues when running loop testing and get error about display resolution changing

While the loop tickbox in Custom tab does disable most of the anti-tampering checks, when loop testing for hours in full screen mode, the run can be interrupted if some background application draws a popup or task bar notification as it causes a switch back to the desktop view. 3DMark cannot recover from such display mode change.

For very long stability stress tests we recommend testing using the windowed mode. Windowed mode is not interrupted by task bar popups or other interrupts from background applications, only actual driver crashes or general system instability will stop the test. When looping all parts of a test, there are loading screens with light load between each part. For maximum load set the stress test loop to loop a single part of a test - Fire Strike Game Test 1, for example - and the loop will be continous without loading screens. Note that when looping, the run will never produce a score.

Also we recommend disabling Scan Systeminfo from the help tab for loop testing - you are not going to get a result file anyway, so there is little point in gathering hardware data and in very long loops the hardware monitoring dataset (temperatures, clock frequencies etc.) can be so large that it could in theory cause stability problems.

http://www.futuremark.com/support/3dmark

 

[litwicki22]

yes but i dont have any background programs. Only gpuz

 

[myocardia]

yes but i dont have any background programs. Only gpuz

His post to you said, "Stop running 3DMark in fullscreen mode."

 

[Phynaz]

Again! You just got a thread locked.

As the mods said then, Google it.

Reported. Hopefully you get more than a warning this time.

 

[Spanners]

GPU Munchausen syndrome.

 

[Subyman]

Rvenger already locked your other 3DMark stability thread. Do not make another one.
Moderator Subyman