Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Troubleshooting Blue Screen (BSOD) Crashes on WATCHPAX and Display Servers

A Windows Blue Screen of Death (BSOD) on a WATCHPAX or display server causes an immediate show interruption. The unit either restarts automatically or gets stuck on the blue screen. This article covers the most common causes identified from support cases.

Common Causes

1. Failing SSD
Frequency: Most common cause on older WATCHPAX 40/60 units. Symptom: Random BSODs with varying stop codes, or the unit fails to boot entirely after a BSOD. Solution:

  • Contact Dataton Support to arrange an SSD replacement (requires returning the unit).

  • On custom-built servers, replace the SSD and re-image.

Multiple WATCHPAX 40 units from a specific production batch required SSD swaps. If you have a WP40 from 2019-2020 experiencing random BSODs, this is the most likely cause.

2. GPU Driver Crash
Symptom: BSOD referencing nvlddmkm.sys (NVIDIA) or atikmdag.sys (AMD). Solution:

  • Install the Dataton-recommended NVIDIA driver version (check the WATCHOUT release notes for the tested driver).

  • Avoid using the absolute latest NVIDIA driver — it may not be tested with WATCHOUT.

  • On WATCHPAX units, GPU drivers are pre-installed and should not be changed without guidance from Support.

3. Windows Update Conflict
Symptom: BSOD starts occurring after a Windows Update. Solution:

  • On WATCHPAX units, automatic Windows Update should be disabled by default. If it was re-enabled, roll back the update.

  • On custom servers, defer feature updates and test cumulative updates before deploying to production machines.

4. Overheating
Symptom: BSOD under heavy load (multiple 4K outputs, many layers). Unit is hot to the touch. Solution:

  • Ensure adequate ventilation. WATCHPAX units need at least 5 cm clearance on all sides.

  • In rack installations, ensure proper airflow. Do not stack WATCHPAX units without spacing.

  • Check that internal fans are running (listen for fan noise on startup).

5. External Hardware Conflict
Symptom: BSOD related to USB or third-party hardware drivers. Solution:

  • Disconnect all non-essential USB devices.

  • Remove any third-party capture cards, audio interfaces, or adapters temporarily to isolate the cause.

Gathering Diagnostic Information

After a BSOD, Windows writes a minidump file:

  1. Navigate to C:\Windows\Minidump\.

  2. Copy the most recent .dmp file(s).

  3. Send them to Dataton Support along with the BSOD stop code (e.g. DRIVER_IRQL_NOT_LESS_OR_EQUAL).

For WO7, also create a Feedback Report (Producer → Help → Create Feedback Report) if the system is bootable after the crash.

Last updated: 30 March 2026 · Dataton Support