Share via

WONT SWITCH ON AFTER THIS / Stop code: SYSTEM_ THREAD_EXCEPTION NOT_HANDLED (0x7E) What failed middinkm-sys

Timasen97 0 Reputation points
2026-03-21T07:12:42.35+00:00

IMG_8281

Windows for home | Other | Performance and system failures
0 comments No comments

2 answers

Sort by: Most helpful
  1. DaveM121 864.5K Reputation points Independent Advisor
    2026-03-21T07:47:50.4+00:00

    Your screenshot indicates it is the Nvidia graphics driver (nvlddmkm.sys) causing the black scree.

    Try this method to access Safe Mode to uninstall the Nvidia drivers to see if Windows will then boot up correctly.

    Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

    Do this twice

    On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

    Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Upon restart, press 5 to enter Safe Mode

    Once in Safe Mode, right click your Start Button and open Device Manager.

    Expand the Display Adapters section.

    Right click and uninstall the Nvidia drivers.

    Restart your PC to see if Windows will start normally.


  2. Q&A Assist
    2026-03-21T07:12:59.7133333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The stop code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E) means a system thread raised an exception that Windows couldn’t handle. In the message, middinkm.sys is the driver that failed.

    For this kind of 0x7E crash, the driver named in the bug check is usually the root cause. Typical resolutions are:

    1. Boot into Windows Recovery Environment (WinRE) and remove or disable the problematic driver or related software.
      • Power on the PC and as soon as the Windows or manufacturer logo appears, hold the power button to force it off.
      • Repeat this power‑on / forced‑off cycle three times so that Automatic Repair starts.
      • Select Advanced optionsTroubleshootAdvanced options.
      • From here, either:
        • Use Startup Settings → restart → choose Safe Mode and, once booted, uninstall the software that installed middinkm.sys (for example, a third‑party driver, security, or tuning tool), or
        • Use System Restore to roll back to a restore point from before the problem started.
    2. If the system still cannot start normally, use WinRE again and choose TroubleshootReset this PC.
      • Prefer Keep my files to preserve personal data while removing apps and drivers that may include middinkm.sys.
    3. If access to a debugger and the dump file is available, the failing driver can be confirmed by analyzing the memory dump:
      • Use WinDbg and the !analyze extension on the crash dump to verify that middinkm.sys is the module causing bug check 0x7E and to see the exception code and call stack.
      • The second parameter of the bug check (address where the exception occurred) will point into the failing driver.

    If debugging shows a different underlying driver or component, disable or update that specific driver instead. If no suitable update exists and removal is not possible, a full reset or clean installation of Windows may be required.


    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.