Repeating BSOD pointing on ntoskrnl.exe

Hi, I'm Bernard. I'm happy to help!

Upon analyzing and checking the DMP files, the error you have is hardware_ram, this means there is a problem with the RAM itself or the RAM slot on the motherboard, in this case, I suggest trying to remove all RAM and retain only 1 then repeat all the process to check what RAM is not working fine, however, if the issue persists, I highly suggest contacting a local technician to physically check the device as it is a hardware problem, it might need a RAM replacement or just need to clean the motherboard.

Note: This is a public forum. I may respond shortly, but I apologize in advance for any delays. I am simply a fellow user trying to provide helpful insights and information.

The most relevant guidance in the context shows that repeated BSODs (including those where tools like BlueScreenView highlight ntoskrnl.exe) are often caused by faulty or unstable drivers, OEM utilities, or hardware/firmware issues rather than ntoskrnl.exe itself.

From similar Windows 11 BSOD and crash cases in the context:

1. OEM/overclocking utilities and unstable CPU states
   • One user with frequent BSODs on an ASUS ROG laptop (Windows 11) found that crashes were tied to an OEM tuning/overclocking tool (Armory Crate). The tool caused unstable CPU frequency changes and fan/thermal misbehavior. After doing an OEM cloud restore and completely removing that utility, the system became stable and BSODs stopped.
   • This shows that even if ntoskrnl.exe appears in the crash analysis, the root cause can be a vendor performance/overclocking tool or power-profile manager.
2. Heavy application logs and storage pressure
   • Another user with constant BSODs (including ntoskrnl-related messages) discovered a hidden 200 GB cache/log folder from Adobe Premiere Pro. Removing that large backlog resolved the BSODs. This indicates that disk pressure or large application-generated data can contribute to instability.
3. Faulty CPU or platform hardware
   • A separate case with Windows Error Reporting “Bluescreen” events (without visible BSODs) ended up being caused by a faulty Intel CPU. The user resolved it by replacing the motherboard/CPU platform.
4. General troubleshooting pattern from similar freezes/BSODs
   • Guidance in the context for Windows 11 freezes and crashes includes:
     • Checking Event Viewer (Windows Logs → System) around the time of crashes for recurring error sources (e.g., display, storage, power, or specific driver names).
     • Disabling features that can stress drivers, such as hardware-accelerated GPU scheduling and Fast Startup.
     • Reducing background apps and overlays while gaming.
     • Verifying hardware by reseating RAM/GPU and running memory and hardware diagnostics.

Applied to the described system (Ryzen 5 5600, RTX 4060, 2×16 GB RAM, Windows 11, BSODs during Steam games):

1. Remove or disable any OEM tuning/overclocking utilities
   • If the system uses vendor tools (ASUS/MSI/Gigabyte utilities, auto-overclock, or “gaming mode” software), disable or uninstall them and revert BIOS/UEFI to default (non-overclocked) settings.
   • This mirrors the successful fix where removing Armory Crate and restoring a clean configuration stopped BSODs.
2. Check for large application caches/logs
   • Inspect game launchers (Steam, other stores) and any content-creation tools for very large cache or backup folders on the system drive. Clean them up if found, similar to the 200 GB Premiere Pro backup case that resolved repeated BSODs.
3. Inspect Event Viewer around BSOD times
   • Open Event Viewer → Windows Logs → System and correlate errors/warnings with the BSOD times. Look for recurring driver or hardware-related sources (display, storage, power, etc.) to identify the failing component or driver.
4. Test stability with a clean, default configuration
   • With overclocking disabled and OEM utilities removed, test games again. If BSODs stop, the cause is likely a driver/utility or unstable tuning profile.
   • If BSODs persist, consider hardware diagnostics (RAM tests, GPU tests) and, as in the faulty CPU case, evaluating CPU/motherboard health if other causes are ruled out.

These steps align with the successful resolutions in the provided cases, where the root cause was either OEM tuning software, excessive application data, or faulty hardware, even though ntoskrnl.exe appeared in the crash analysis.

References:

• Please check my minidumps, BSOD and shutdowns - Microsoft Q&A
• Constant BSOD - Microsoft Q&A
• Trying to figure out this Windows Error Reporting 1001 event (Event Name: Bluescreen) - Microsoft Q&A
• My Windows 11 PC Hard Freezes for about 30 seconds to a minute when I play certain games. - Microsoft Q&A