Code 193 on Windows: Causes and Fixes
Open Device Manager, expand Display adapters, and identify the device or devices listed there if the crash pattern points to the display stack. The dump file indicates a problem with the graphics drivers, and it seems to indicate it is integrated graphics drivers. Use that as the starting point when the screen goes black, the PC hangs, or the display recovers after a failure.
What is code 193?
Likely causes
The provided evidence points to the graphics drivers, including integrated graphics drivers. In practice, that means the first place to look is the display adapter and its driver version.
- Graphics driver trouble, including integrated graphics or NVIDIA display drivers.
What usually causes it first?
The display driver is the first thing to test when the failure shows up as a black screen, a hang, or a wake problem. Start there before making broader changes.
Say your laptop sleeps with the lid closed and then refuses to wake, but the power light stays on. That pattern belongs with the graphics path first.
Graphics path
- Open Device Manager > Display adapters and note every adapter listed there.
- If the system uses NVIDIA, completely remove the current NVIDIA device driver using the widely available free DDU utility, then restart.
- Restart your PC and go to the Nvidia website to download and install a couple of slightly older version of the NVIDIA device driver.
- If the first retry does not help, try a couple of other versions of the drivers they provide for your graphics card model.
Validation
After each graphics change, do the exact action that failed before: sleep, wake, idle, or reconnect the monitor. If the event no longer returns and the display stays stable across one full repeat of the same action, stop there.
Can a graphics driver cause code 193?
Yes. The dump file indicates a problem with the graphics drivers, and the source material also says it seems to indicate integrated graphics drivers. If the symptom matches the display stack, a driver test is the right first step.
Graphics rollback test
- Open Device Manager > Display adapters.
- Right-click the NVIDIA device, choose Uninstall device, then use DDU to completely remove the current NVIDIA device driver.
- Restart the PC and install a slightly older NVIDIA driver, or try another available version for the same card model.
- Test the same black-screen or wake path again before changing any other driver.
If the issue began right after a display update, compare it against the last stable driver version first. Keep the rest of the system unchanged during that test.
Is the Wi-Fi or chipset driver the problem?
The supplied facts do not support Wi-Fi, chipset, VPN, peripheral, or system-file causes here, so do not start with those paths. Keep the focus on the display adapter and the graphics driver versions available for that device.
Wi-Fi and chipset checks
- Open Device Manager > Display adapters and identify the graphics device.
- Update or roll back the graphics driver using the vendor package that matches the device.
- If you attached a new peripheral or external drive before the crash started, unplug it and test the same display action again.
- Use standard Windows troubleshooting only if a separate hardware issue is clearly tied to that device, such as Hardware and Devices troubleshooter.
Do one driver path at a time. If the symptom changes after the graphics update, keep other drivers untouched until you know which change mattered.
Could NordVPN or another app be involved?
The provided facts do not support NordVPN or another app as the cause here. Keep the test plan centered on the graphics driver and its installed version.
Software conflict test
- Leave recently installed apps out of the first round of testing.
- Restart the PC and repeat the same sleep, wake, or idle action that failed before.
- If the event stops, keep the working graphics driver version in place.
- If nothing changes, continue with another graphics driver version rather than shifting to unrelated software changes.
A common first-timer mistake is changing several things at once. Change one thing, then retest the same action.
LiveKernelEvent 193 decision matrix
| Symptom pattern | Most likely subsystem | First test | Second test | Stop condition |
|---|---|---|---|---|
| Black screen, monitor goes out and on again | Graphics driver | Device Manager > Display adapters > identify the active adapter | DDU removal, then install a slightly older NVIDIA driver | Event no longer returns after the same display action |
| Hangs after being idle for a few minutes | Graphics driver | Graphics driver rollback or update | Try another available driver version for the same GPU | System survives idle without a repeat event |
| Wake failure after sleep | Graphics driver | Test the display driver version that was stable before | Try another approved driver version for the same GPU | PC wakes normally twice in a row |
Validation checklist
- Repeat the exact action that used to trigger the event.
- Confirm the screen stays on through one full sleep or wake cycle.
- Check Reliability Monitor to see whether the same event returns.
- Change only one graphics driver version before testing again.
- Stop when the trigger no longer reproduces.
How do I fix code 193 on Windows 11?
On Windows 11, start with the graphics driver that matches the failure. If the system uses NVIDIA, remove the current driver with DDU, then install a slightly older version from Nvidia and test again. If that does not hold, try a couple of other versions of the drivers they provide for your graphics card model.
Windows 11 repair ladder
- Test the display driver path first if the failure is a black screen or failed wake.
- Open Device Manager > Display adapters and identify the graphics device.
- Remove the current NVIDIA driver with DDU if the device is NVIDIA.
- Install a slightly older NVIDIA driver, then try another version if needed.
If that still does not hold, continue testing other graphics driver versions for the same card model.
Does code 193 mean a hardware problem?
Not necessarily. The dump file points to the graphics drivers, so the first step is to test the driver path before assuming a failed part.
When to escalate
- Open Device Manager > Display adapters.
- Remove the current NVIDIA driver with DDU if applicable.
- Try a slightly older NVIDIA driver version.
- Try a couple of other driver versions for the same graphics card model if needed.
Still not working?
If the same event keeps returning after the graphics driver tests, keep comparing different supported driver versions for the same adapter. If a new external device was attached right before the crashes began, disconnect it and retest the same display action.
Keep the working driver version noted somewhere after a stable fix.
Frequently asked questions
What does LiveKernelEvent 193 mean in Reliability Monitor?
It is a Windows event label that you can use to line up the failure time with the display action that triggered it. Start by checking the graphics driver version and the adapters listed in Device Manager.
Why does my monitor go black and then recover with code 193?
That pattern usually points to the graphics stack. Start with Device Manager > Display adapters, then update or roll back the active display driver.
Should I reinstall or roll back the driver for code 193?
Rollback or try a slightly older supported version first when the event began after a driver change. If needed, try a couple of other versions for the same graphics card model.
