Razer Cortex creating BSOD "Critical_Process_Died" | Razer Insider
Skip to main content

Razer Cortex creating BSOD "Critical_Process_Died"

  • September 6, 2025
  • 2 replies
  • 173 views
polyHarlequinup386

Hello. 
i had the issue that when i stopped a Game and went back to Desktop i had immediatley the BSOD “Critical_Process_Died” 
i had to find out it was caused by Razer Cortex. 
Uninstalled it and now all runs fine. 

First i had so many issues with Razer Hardware, no i have so many issues with Razer Software. 
This Company gives me nighmares.

    2 Replies

    Ekhagim
    • Ekhagim
    • Insider Mini
    • September 12, 2025

    I had been having this same issue a couple weeks ago. Ended up doing a repair version installation of Windows 11 through Windows Update. Then everything was good until the start of the week. Frequent Critical Process Died BSOD when exiting games. Wasn’t every single time, and a couple times it happened on launching, for example, Warhammer 40K Boltgun. I tried everything I could find online, DISM and SFC, Safe Mode, downloaded drivers, used DDU to remove my nVidia drivers, then install fresh. 

     

    Even tried the Windows 11 repair version again. Probably unnecessarily. 

     But on a whim, I checked if there had been such things happening while using Razer Cortex. I decided to uninstall, rather than just turn off auto boost. So far, so good. 

    U
    • UnseenDark
    • Insider Mini
    • September 14, 2025

    Hi,

    This happened to me just today. Im on Windows 11 and automatic update is always on. I got the problem NOT when enabling cortex, but rather disabling it.

    My PC instantly hangs with “Critical_Process_Died” message. I proceed to check on the dump file using Windbg. Heres what I get:

     

    !--startfragment>

    CRITICAL_PROCESS_DIED (ef)        A critical system process diedArguments:Arg1: ffffc587fe99f080, Process object or thread objectArg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.Arg3: ffffc587fe99f080, The process object that initiated the termination.Arg4: 0000000000000000, Additional triage data

    …

    Key  : CriticalProcessDied.ExceptionCode    Value: 0x23adf080    Key  : CriticalProcessDied.Process    Value: svchost.exe

    …

    FAULTING_THREAD:  ffffc58823adf080PROCESS_NAME:  svchost.exeCRITICAL_PROCESS:  svchost.exe

     

    Based on this debug result, it turns out that Cortex has just messed around with SVCHOST.EXE process which is a critical process used by Windows OS and must not be terminated.

    Just steer away from Cortex until they solve the software.

    *UPDATE: IT WORKS fine if I cycle enable/disable when not running any games.

     

    CookiesCookie settingsAccessibility statement