Snipping tool freezing my laptop when using the draw feature?

Hi Pierrau Stefan,

That freezing is a symptom of a render thread deadlock within the Windows display subsystem.

To recover without a hard reboot, use the native Windows command by pressing Windows Key, Ctrl, Shift, and B simultaneously. Your screen will briefly flash black and you will hear a short beep as the system safely discards the current display buffer and restarts the driver running from your local DriverStore directory. This achieves the exact same reset as unplugging a physical monitor and will immediately restore your interface without closing your applications or losing unsaved work.

You're right about the OS build and the graphics driver, as the newer Windows 11 build 22631.6936 contains specific patches targeting Desktop Window Manager stability. Because your device is managed by your company, your best path forward is to submit a request to your IT department to deploy this specific update or push a newer Intel display driver. You can strengthen your IT ticket by navigating to the Windows Event Viewer, opening the Windows Logs folder, and checking the Application log for Event ID 1002 or Event ID 1000 associated with dwm.exe, which provides concrete evidence of the application hang. Until the permanent update is deployed to your machine, the keyboard shortcut workaround will prevent the need for disruptive forced restarts.

Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

VP

Pierrau Stefan

The Event ID 1001 log containing the LiveKernelEvent 1b8 and the WATCHDOG dump file precisely identifies a Video Timeout Detection and Recovery failure. The Windows subsystem detected that your Intel graphics driver took too long to render the Snipping Tool's hardware-accelerated drawing overlay and forcefully intervened. This explains why the keyboard reset shortcut stopped working after the first attempt. Repeated rendering timeouts cause the operating system to lock the software display stack to prevent a complete blue screen crash, leaving your physical monitor detachment as the only hardware interrupt powerful enough to clear the deadlock. The HotKeyServiceUWP event is simply a standard HP background service reacting to the sudden display power state changes and is a symptom rather than the root cause.

Since your operating system and Intel drivers are up to date, the most effective resolution is to disable Multi-Plane Overlay. This is a Windows feature designed to reduce GPU workload, but it has heavily documented synchronization conflicts with Intel integrated graphics during layered window rendering on extended monitors. To apply this fix, open the Registry Editor as an administrator and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm. Inside this location, right-click to create a new DWORD 32-bit value, name it OverlayTestMode, and set its value data to 5.

If the desktop manager still hangs after disabling the overlay, the next step is to increase the timeout threshold so the operating system stops preemptively crashing the graphics process. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers. Create a new DWORD 32-bit value named TdrDelay and set its value data to 8. This adjustment gives your Intel GPU eight seconds to complete the drawing handoff instead of the default two seconds, preventing the Watchdog monitor from prematurely triggering the freeze. Please ensure you restart your laptop after applying these registry modifications for the new configurations to initialize.

Hope this helps :)

VP

Pierrau Stefan

Lowering the power efficiency slider will not disable Panel Self Refresh. That specific slider controls a different feature called Intel Display Power Saving Technology, which dynamically alters your screen brightness and contrast based on the content you are viewing. Panel Self Refresh is a hardware-level protocol that dictates whether the graphics card temporarily stops sending rendering frames to the physical monitor entirely, which is the exact mechanism conflicting with the Windows Ink drawing tools.

The complete absence of the Panel Self Refresh toggle in your interface confirms the complications introduced by the generic Intel driver update. In recent generic driver branches, Intel often hides these advanced power toggles or migrates them to a completely different utility called Intel Arc Control, effectively locking users out of crucial hardware configurations when using the standard Command Center application.

Because the software interface prevents us from manually disabling this power state, we must execute the driver reversion strategy discussed previously. Please open the Windows Device Manager, expand the Display adapters section, right-click your Intel Graphics device, and select Properties to click the Roll Back Driver button. If that button is greyed out, you must visit the official HP support portal, search for your specific EliteBook 640 G11 model, and download their certified Intel Video Driver package. Installing that manufacturer-approved driver will overwrite the generic installation and restore the proper hardware synchronization protocols required to stop the drawing overlay from freezing your system.

VP

Hi Pierrau Stefan,

I suspect the root cause is a specific conflict between your Intel graphics driver and the Windows Presentation Foundation rendering engine. This engine specifically powers the Windows Ink workspace and native drawing overlays exclusively within Microsoft software, which explains why external applications render without issue.

Since modifying the system overlays and timeout thresholds did not resolve the hardware handoff failure, we must force these specific Microsoft frameworks to bypass the GPU entirely and rely on software rendering. You can achieve this by disabling hardware acceleration globally for the Windows Presentation Foundation subsystem. Open the Registry Editor and navigate to HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics. If the Avalon.Graphics folder does not exist, right-click the Microsoft folder to create it as a new key. Inside Avalon.Graphics, create a new DWORD 32-bit value named DisableHWAcceleration and set its value data to 1.

To ensure the Office suite is entirely severed from the failing graphics hooks, you should apply the exact same restriction directly to the Office common registry settings. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Graphics, creating the Graphics key if necessary. Add a new DWORD 32-bit value named DisableHardwareAcceleration and set its value to 1. Restart your computer to initialize these software-only rendering pathways. This will offload the drawing calculations to your CPU, completely bypassing the crashing Intel graphics API calls.

VP