Share via

ntoskrnl.exe+3fd5c0 BSOD

Zyrus 0 Reputation points
2026-02-18T10:58:46.27+00:00

I've been reinstalling Windows for days and I still get this BSOD. I run Bluescreen View and it always shows this error.

Here is the minidumps I gathered!

https://drive.google.com/drive/folders/1TPC_EYKRXzAw2Ki8Qi-iQ21w0CNsgYk6?usp=sharing

Windows for home | Windows 10 | Performance and system failures
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. DaveM121 848.8K Reputation points Independent Advisor
    2026-02-18T11:35:23.5866667+00:00

    Your minidump files indicate memory (RAM) corruption and also USB drivers as the cause of the system crashes.

    The best first option because you have re-installed Windows and the BSOD's have survived that, is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors.

    0 comments No comments

  2. Q&A Assist
    2026-02-18T10:58:57.3166667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The BSOD (Blue Screen of Death) error related to ntoskrnl.exe typically indicates a problem with the Windows kernel, which can be caused by various issues such as faulty drivers, hardware problems, or system corruption. Here are some steps you can take to troubleshoot and potentially resolve this issue:

    1. Update Drivers: Ensure that all your device drivers are up to date. You can do this through the Device Manager by right-clicking on each device and selecting "Update driver".
    2. Check Hardware: Run hardware diagnostics to check for any failing components, especially RAM and hard drives. You can use the Windows Memory Diagnostics tool to test your memory.
    3. Review Minidumps: Analyze the minidump files using a tool like WinDbg or BlueScreen View to identify the specific driver or hardware causing the issue. Look for patterns in the errors reported.
    4. System File Check: Run the System File Checker tool by executing sfc /scannow in an elevated Command Prompt to repair any corrupted system files.
    5. Check Event Viewer: Use the Event Viewer to look for any critical errors or warnings that occurred around the time of the BSOD. This can provide additional insight into what might be causing the problem.
    6. Remove Recently Installed Hardware: If you have added new hardware recently, try removing it to see if that resolves the issue.
    7. Restore or Reset Windows: If the problem persists, consider restoring your system to a previous state or performing a reset to reinstall Windows while keeping your files.

    If you continue to experience issues after trying these steps, it may be beneficial to consult with a professional or seek further assistance from Microsoft support.


    References:

    0 comments No comments

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.