F5F Stay Refreshed Hardware Desktop App on GeForce NOW triggers system failure and restart (BugCheck 0x13A) when user interacts with mouse or keyboard.

App on GeForce NOW triggers system failure and restart (BugCheck 0x13A) when user interacts with mouse or keyboard.

App on GeForce NOW triggers system failure and restart (BugCheck 0x13A) when user interacts with mouse or keyboard.

X
XxGrenidierXx
Posting Freak
Find
813
07-31-2025, 02:45 AM
#1
Hello everyone, I’m facing a serious problem with the GeForce NOW desktop app on my main PC. Whenever I start a game and use the mouse or keyboard, the screen displays “No Signal” and the whole system restarts shortly afterward. It seems the controller works fine, but the crash happens only when using the browser version (Chrome) or during local play. The same app functions perfectly on my second PC (Minisforum UM760mini), using the same account and network connection.

System details: Windows 11 Enterprise N 24H2 (OS Build 26120.3863), AMD Ryzen 5 3600, NVIDIA GeForce RTX 2060 Super LG 24GN650 (1080p, 144Hz, G-Sync compatible).

What I’ve tried without success:
- Fully reinstalled the NVIDIA driver via DDU
- Tested several older NVIDIA drivers (537.58, 531.79, etc.)
- Adjusted registry values (TdrDelay, TdrDdiDelay)
- Reinstalled Media Feature Pack; disabled G-Sync, HDR, fullscreen, hardware acceleration, and set resolution to 144Hz
- Switched between DisplayPort and HDMI
- Used older versions of the GeForce NOW app (2.0.36, 2.0.37 – no longer supported)
- Reached out to NVIDIA support – no help received

Recent troubleshooting:
- Ran a full crash analysis via Minidump → found BugCheck 0x13A (KERNEL_MODE_HEAP_CORRUPTION) caused by mouse input event, specifically in HMAllocObjectEx inside the kernel input stack
- Completely uninstalled Razer Synapse and all related drivers
- Used only basic mouse and keyboard, no special software
- Disabled Hyper-V via bcdedit /set hypervisorlaunchtype off
- Confirmed Memory Integrity (VBS) was already disabled
- Performed a Clean Boot (only Microsoft services running)

I’m open to suggestions. Have anyone encountered something similar, especially with an RTX 2060 Super on Windows 11?
Reply
Reply
X
XxGrenidierXx
07-31-2025, 02:45 AM #1

Hello everyone, I’m facing a serious problem with the GeForce NOW desktop app on my main PC. Whenever I start a game and use the mouse or keyboard, the screen displays “No Signal” and the whole system restarts shortly afterward. It seems the controller works fine, but the crash happens only when using the browser version (Chrome) or during local play. The same app functions perfectly on my second PC (Minisforum UM760mini), using the same account and network connection.

System details: Windows 11 Enterprise N 24H2 (OS Build 26120.3863), AMD Ryzen 5 3600, NVIDIA GeForce RTX 2060 Super LG 24GN650 (1080p, 144Hz, G-Sync compatible).

What I’ve tried without success:
- Fully reinstalled the NVIDIA driver via DDU
- Tested several older NVIDIA drivers (537.58, 531.79, etc.)
- Adjusted registry values (TdrDelay, TdrDdiDelay)
- Reinstalled Media Feature Pack; disabled G-Sync, HDR, fullscreen, hardware acceleration, and set resolution to 144Hz
- Switched between DisplayPort and HDMI
- Used older versions of the GeForce NOW app (2.0.36, 2.0.37 – no longer supported)
- Reached out to NVIDIA support – no help received

Recent troubleshooting:
- Ran a full crash analysis via Minidump → found BugCheck 0x13A (KERNEL_MODE_HEAP_CORRUPTION) caused by mouse input event, specifically in HMAllocObjectEx inside the kernel input stack
- Completely uninstalled Razer Synapse and all related drivers
- Used only basic mouse and keyboard, no special software
- Disabled Hyper-V via bcdedit /set hypervisorlaunchtype off
- Confirmed Memory Integrity (VBS) was already disabled
- Performed a Clean Boot (only Microsoft services running)

I’m open to suggestions. Have anyone encountered something similar, especially with an RTX 2060 Super on Windows 11?

Reply
Reply
P
Proplayer321
Junior Member
Find
5
07-31-2025, 02:45 AM
#2
Here are some alternative suggestions:
•Consider turning off pointer precision in settings
•Adjust lower polling rates for keyboard or mouse
•Switch to a different Windows profile
•Go back to an earlier Windows update, possibly 23H2
Reply
Reply
P
Proplayer321
07-31-2025, 02:45 AM #2

Here are some alternative suggestions:
•Consider turning off pointer precision in settings
•Adjust lower polling rates for keyboard or mouse
•Switch to a different Windows profile
•Go back to an earlier Windows update, possibly 23H2

Reply
Reply