problems on bsod ntskrnl.exe

Question

hello! i have been having these problems for about 1.5 year now. it crashes almost everyday. today when i was playing some games i crashed 2 times.

my pc specs:

16GB RAM

3060Ti

ryzen 5600

Answer 1

Hi Karel Ollema,

Thank you for sharing the details of the issue.

When a BSOD references ntoskrnl.exe, it usually indicates that Windows encountered an unexpected condition at the system level. This is commonly triggered by factors such as memory stability, device drivers, or firmware interactions, rather than the file itself.

Please try the following steps to stabilize your system when experiencing frequent crashes, especially during gaming or high-performance use:

1, Check memory stability

• Enter BIOS settings
• Temporarily disable XMP/DOCP (run RAM at default speed)
• Save changes and test system stability

2, Clean reinstall graphics driver

• Use Display Driver Uninstaller (DDU) in Safe Mode
• Remove all NVIDIA drivers
• Install the latest NVIDIA driver using Clean installation

3, Install AMD chipset drivers

• Download chipset drivers directly from AMD’s official website
• Restart after installation

4, Update system BIOS

• Update to the latest stable BIOS version from the motherboard manufacturer
• Load Optimized Defaults after updating

5, Repair system files

• Open Command Prompt as administrator
• Run: sfc /scannow
• Then run: DISM /Online /Cleanup-Image /RestoreHealth

6, Disconnect non‑essential devices

• Remove external USB devices temporarily
• Test system behavior with only keyboard and mouse connected

If the issue continues - persistent crashes after these steps may point to hardware stability factors such as memory modules or power delivery. At that stage, testing components individually or consulting a local technician can help narrow down the cause.

Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

---

If my response is helpful to you, please click "Accept Answer" and kindly upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

Answer 3

Frequent BSODs that reference ntoskrnl.exe (often shown as ntkrnlmp.exe/ntoskrnl.exe in dumps) usually indicate a kernel‑mode problem such as:

• Faulty or incompatible drivers
• Third‑party system utilities (tuning, overclocking, RGB, OEM control software)
• Hardware issues (RAM, storage, motherboard, etc.)
• In some cases, a Windows kernel bug that is fixed by an update

From the provided context, several similar issues were ultimately traced to:

1. Buggy OEM/overclocking utilities
   On an ASUS ROG laptop with repeated BSODs under light load, the root cause was the ASUS Armory Crate software manipulating CPU frequencies and profiles. After a clean ASUS cloud restore and removing Armory Crate, the system became stable and BSODs stopped for days. Action:
   • Uninstall OEM tuning/control utilities (e.g., ASUS Armory Crate, OEM “gaming center”, overclocking tools, fan control tools) and test stability for several days.
2. Driver and kernel bugs fixed by updates
   Multiple Microsoft KB articles in the context show that specific ntoskrnl.exe builds caused crashes or Stop errors and were fixed by updated kernel binaries. Examples:
   • Windows 8 / Windows Server 2012: SQL Server or other apps crashing due to ntdll.dll / ntoskrnl.exe bugs, fixed by updated files Ntdll.dll 6.2.9200.20975 and Ntoskrnl.exe 6.2.9200.20975.
   • Stop errors 0x133, 0x101, 0x9E, and 0x0000000A on older Windows versions, all resolved by updated ntoskrnl.exe builds.
   Action on Windows 11:
   • Ensure Windows Update is fully up to date (all cumulative and optional quality updates installed). Kernel‑level fixes are delivered this way.
3. Storage/SSD or controller issues leading to deep corruption and BSODs
   A complex case with repeated BSODs, WinSxS corruption, and strange DISM/SFC behavior was ultimately traced to an SSD hardware problem (“drive’s 406 SRAM error” on a Phison‑based NVMe). Replacing the SSD resolved the issue. Action:
   • Run vendor diagnostics for SSD/NVMe (or use the OEM’s SSD tool) and check SMART health. If errors are reported, consider testing with a different drive.
4. GPU driver problems causing crashes in games
   For Minecraft for Windows (Bedrock) crashing, the resolution was to use DDU and downgrade GPU drivers, which stopped TDR and unknown crashes. Action:
   • Use Display Driver Uninstaller (DDU) in Safe Mode to clean GPU drivers.
   • Install a known‑stable WHQL driver version (not necessarily the latest) and test games again.
5. Malware or system damage
   One case with many system issues (services failing, Windows Update broken, UI freezes) after running shady software required:
   • Malware removal
   • SFC repairs
   • Ultimately a Reset this PC (keep files) when system damage was too deep.
   Action if malware or heavy system damage is suspected:
   • Run full scans with Windows Security and a reputable antimalware tool.
   • If instability persists, use Settings → System → Recovery → Reset this PC → Keep my files to reinstall Windows while preserving personal data.
6. Collecting more data (minidumps)
   In a Windows 11 DRIVER_POWER_STATE_FAILURE (0x9F) case, the moderator requested minidumps from C:\Windows\Minidump to analyze the exact driver causing the crash. Action:
   • Confirm that minidumps are being created (System Properties → Startup and Recovery → Write debugging information: Small memory dump).
   • When the next BSOD occurs, collect the .dmp files from C:\Windows\Minidump, zip them, and provide them to a support channel capable of debugging them. This will identify the exact driver/module, not just ntoskrnl.exe.

Summary of recommended steps for recurring ntoskrnl.exe BSODs on Windows 11:

1. Fully update Windows (all cumulative/quality updates).
2. Remove OEM tuning/overclocking utilities (e.g., Armory Crate or similar) and any third‑party kernel‑level tools.
3. Clean‑install a stable GPU driver using DDU.
4. Run SSD/NVMe diagnostics; if errors appear, test with another drive.
5. If malware or deep corruption is suspected and persists, perform Reset this PC (Keep my files).
6. Enable and collect minidumps for targeted analysis of the offending driver.

If these steps are followed and crashes continue, minidump analysis is the next required step to identify the specific driver or hardware component behind the ntoskrnl.exe crashes.

---

References:

• SQL Server or another application crashes on a Windows 8-based or Windows Server 2012-based computer
• "0x133", "0x101" Stop error or system stops responding during start
• Stop error 0x9E in Windows Server 2012 or Windows 8
• Error message on a blue screen on a computer that is running Windows 7 or Windows Server 2008 R2: "STOP: 0x0000000A"
• Some software products function incorrectly in Windows
• Troubleshooting Windows unexpected restarts and stop code errors
• Please check my minidumps, BSOD and shutdowns - Microsoft Q&A
• Issue with Driver_Power_State_Failure 0x9F Windows 11 - Microsoft Q&A
• WinSxS Corruptions Despite Numerous Formats to Windows, Silent Corruption and Deletion of Windows Update Files - Microsoft Q&A
• Minecraft for windows is crashing - Microsoft Q&A
• Plethora of issues relating to windows and possibly security. - Microsoft Q&A