This forum provides answers to commonly asked technical support questions. We are continuously adding to and updating this forum to help our customers troubleshoot problems quickly and effectively.

Use key words in the search bar to see if an answer to your question already exists. If you can't find a related answer, use the "New Post" button to ask your question and an engineer will provide an answer as soon as possible. If your problem is urgent and/or too complex for the forum format, email support@optotherm.com to open a support ticket.

This question has been flagged
1 Reply

When running Thermalyze, a few seconds after pressing the Capture Images button, the Windows blue screen error (Figure 1 below) is displayed indicating an error due to DRIVER_VERIFIER_DMA_VOLATION.

Author Best Answer

Disabling Intel Virtualization in the computer BIOS appears to prevent the DMA violation error and resulting blue screen.

To do this:

  1. In the Windows Search bar type “Settings” and open the Settings app.
  2. Click Update & Security.
  3. In the left pane, click Recovery.
  4. In the right pane under Advanced Startup, click Restart now.
  5. In the Choose an option screen, click Troubleshoot.
  6. In the Advanced options screen, click UEFI Firmware Settings.
  7. On the next screen, click the Restart button.
  8. The PC will now restart to the BIOS menu.
  9. On the left, expand Virtualization Support.
  10. Select Virtualization and then uncheck Enable Intel Virtualization Technology.
  11. Select VT for Direct I/O and then uncheck Enable VT for Direct I/O.
  12. Click Apply and when the Apply Settings Confirmation popup window opens, click OK.
  13. Click Exit and the PC will restart.

The problem appears to be caused by a conflict between Thermalyze image capture drivers and a recent Windows update involving Intel Virtualization.  Intel® Virtualization Technology abstracts hardware that allows multiple workloads to share a common set of resources. On shared virtualized hardware, a variety of workloads can co-locate while maintaining full isolation from each other, freely migrate across infrastructures, and scale as needed. This is the only work around currently available, however we are actively working on a solution that allows for Intel Virtualization to be enabled.