I get the warning "The 3D test was interrupted".
This warning can occur when;
- The screen saver starts during the test
- A power saving option such as switching the display off or the PC going into a sleep state occurs
- The screen resolution changes during the test
- The screen mode is changed during the test, e.g. rotating a tablet
- Another 3D application that uses DirectX was launched while the 3D test was running
- The monitor is disconnected during the test
- A KVM is used and switched to another system
- The user presses Ctrl-Alt-Delete on the keyboard
- The user runs an application with elevated administrator privileges
- Windows Aero theme is switched on/off during the test
- The video card device driver crashes and restarts. In this case you'll often get a messages in the Window's system tray, saying, "Display driver stopped responding and has recovered"
Things you can try to narrow down the issue;
- We have had feedback that a Microsoft bug may cause this problem, please patch your system with KB 2979265 (if applicable) and retry.
- Check you are using the latest device driver for your video card.
- Check that the screen saver has been turned off
- Don't Ctrl-Alt-Delete on the keyboard during the test
- Don't run an application with elevated administrator privileges during the test
- Check that power saving options have been turned off. Including options like "Turn off display after X minutes".
- Don't use a KVM switch.
- Check the windows event logs for any video device driver crashes around the time that the test was interrupted. From Windows Vista there is also a specific event when Windows restarts the device driver.
- Try running without the RAM test (low memory conditions can cause Windows to turn Aero theme off automatically)
- Change the Windows Aero theme to basic before starting the test
- We have had a report that testing on unactivated versions of Windows can lead to notifications that interrupt the 3D test. If you have this issue and have not activated Windows, and have tried all the above, then we suggest either activating Windows or disabling all pop-up notifications.
Example driver crash window
Intel Haswell iGPU
After receiving quite a few reports of this issue on the Intel Haswell iGPU we have investigated further. We were able to reproduce the problem on a Haswell CPU/iGPU (i7-4770/Intel(R) HD Graphics 4600) desktop running 64-bit Windows 7 with older Intel HD Graphics drivers. This issue appears to be resolved with Intel HD Graphics driver for Windows 22.214.171.124.4080 (10.18.10.4080) - it is recommended this be the minimum driver version used.
In addition to the reasons shown above, we have found in our testing that this issue is caused by the Intel graphics card device driver timing out and recovering. This occurs with the driver 10.18.10.3958, and it seems to occur more frequently with an older driver. We could not reproduce the problem with driver 10.18.10.4080.
For reference, the following is a desciption of the problem when using driver 10.18.10.3958:
The System and Application event logs should be checked around the time of the event. To view the events, open Event Viewer, expand "Windows Logs" and select "Application", look for "Desktop Window Manager" and "Windows Error Reporting" events around the time the 3D test was interrupted event occurred (see example from our test lab below). Then select "System" events and look for "Display" Warning events (e.g. Display driver igfx stopped responding and has been successfully recovered).
In our testing, the following occurred when running just the BurnInTest PRO v8.0.1031 3D test:
- The Application event log shows a "Desktop Windows Manager" “A request to disable the Desktop Window Manager was made by process (4)”, (i.e. by the Operating System).
- The Application event log shows a "Windows Error Reporting" event and the crash dump produced by Windows Error Reporting shows a timeout in igdkmd64.sys (VIDEO_TDR_TIMEOUT_DETECTED (117) - The display driver failed to respond in timely fashion.)
- The System event log showed a "Display" Warning event ("Display driver igfx stopped responding and has been successfully recovered").
These events caused the "3D test was interrupted" reported by the BurnInTest 3D test.
Event viewer screenshots for reference
1. Application event log
2. Application event log
3. System event log