Share via

Windows 11 BSOD and crashes (0x000000ef, 0x0000004e, 0x0000003b, 0x00000050, 0x0000013a)

VeselinB 0 Reputation points
2026-04-27T10:45:50.94+00:00

My PC crashes/restarts from time to time with the BSOD and I'm continuing to use it as normal butI'm worried about the crashes. Here are the last 3 crashes and as you can see from the dates/time it can happen up to 2 times per day and around 7-8 times per month. Idk, thats just from the info I have.

Here's one of the crashes, you can see more on the image:
042726-6953-01.dmp 27.4.2026 г. 13:15:35 PFN_LIST_CORRUPT 0x0000004e 0000000000000099 0000000000f1f239 0000000000000002 14aa38000034aa38 ntoskrnl.exe ntoskrnl.exe+4fa330 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.26100.8246 (WinBuild.160101.0800) x64 ntoskrnl.exe+4fa330 C:\WINDOWS\Minidump\042726-6953-01.dmp 32 15 26100 3 045 747 27.4.2026 г. 13:16:00

My specs are the following:
ASRock B760 Pro RS
Intel Core i9-14900kf
Total 64GB RAM - 2x Kingston FURY Beast 32GB (2x16GB) DDR5 5600MHz KF556C36BBEK2-32 RAM
(I have the XMP enabled at 5600MT/s, idk if this can cause the crashes or not)
NVIDIA 5060ti 16GB
image

User's image

Windows for home | Windows 11 | Performance and system failures
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lucus-V 7,570 Reputation points Microsoft External Staff Moderator
    2026-04-28T18:06:38.8633333+00:00

    Hi VeselinB,

    Since this is a public forum, we will hide your personal identifiable information, and I have sent that image of yours containing your personal identifiable information in a private message so we can work together to resolve the issue. Also, please check your private message in case you want to share another screenshot to avoid leaking your PII by click on the Private Message button right under your first post.

    Your system was either crashed by ntoskrnl.exe (System Kernel) or dxgmm2.sys (Graphics rendering system driver), which commonly point to faulty drivers, memory corruption, or other low‑level issues.

    The issue with 13th and 14th generation Intel CPUs has been reported by many users. Please navigate to your laptop support page and make sure you have the latest BIOS version.

    Additionally, you may try some workarounds from vgk.sys Error Troubleshooting (13th and 14th generation Intel CPUs), especially increasing Vcore part that ensures your CPU has enough power during load.

    Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate and safe information. Watch out for ads on the site that may advertise products frequently classified as PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it. If you have further information, please feel free to let me know.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. DaveM121 883.8K Reputation points Independent Advisor
    2026-04-27T11:20:58.4+00:00

    Please upload any minidump files you have, 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.

    Was this answer helpful?

    1 person found this answer helpful.

  3. AI answer

    2026-04-27T10:46:30.6+00:00

    The bug checks shown (CRITICAL_PROCESS_DIED 0xEF, PFN_LIST_CORRUPT 0x4E, SYSTEM_SERVICE_EXCEPTION 0x3B, PAGE_FAULT_IN_NONPAGED_AREA 0x50, 0x13A) are all kernel stop errors that commonly point to faulty drivers, memory corruption, or other low‑level issues. With multiple different codes on a new high‑end system, the most likely causes are:

    • Unstable or incompatible drivers (GPU, storage, chipset, firmware tools, etc.)
    • Unstable RAM configuration (XMP overclock, mismatched kits, or bad DIMM)
    • Less commonly, disk or system file corruption, malware, or BIOS/firmware issues

    Start with the basic Windows 11 blue‑screen troubleshooting steps, then move to more advanced checks.

    1. Remove or disable recent hardware or tuning tools
      • If any hardware was added shortly before the BSODs started, shut down, remove it, and test.
      • If any vendor “optimization” or overclocking utilities are installed (for example, motherboard or GPU tuning suites similar to Armoury Crate in other cases), uninstall or disable them and test stability. A clean reinstall without such tools has resolved repeated BSODs in similar scenarios.
    2. Boot into Safe Mode and test
      • Use Safe Mode to see if crashes still occur with minimal drivers loaded. Instructions are in Start your PC in safe mode in Windows 11.
      • If the system is stable in Safe Mode, that strongly suggests a third‑party driver or service.
    3. Check Device Manager for driver issues
      • Right‑click Start → Device Manager.
      • Look for any device with an exclamation mark (!).
      • For each such device, choose Update driver. If that does not help, disable or uninstall the device and test.
    4. Test RAM and XMP
      • Because PFN_LIST_CORRUPT and PAGE_FAULT_IN_NONPAGED_AREA often indicate memory corruption, temporarily disable XMP in BIOS so the RAM runs at JEDEC defaults, then test for a few days.
      • If BSODs stop with XMP off, either keep it off or try a more conservative memory profile.
      • If crashes continue, test each RAM kit or DIMM separately to see if one module or slot is faulty.
    5. Ensure sufficient free disk space
      • Keep at least 10–15% of the system drive free so Windows can create paging and crash‑dump files and operate reliably.
    6. Install the latest Windows updates
      • Go to Start → Settings → Windows Update → Check for updates and install everything offered. This can include fixes for kernel, driver, and stability issues.
    7. Scan and repair system files
      • Open an elevated Command Prompt and run:
        • sfc /scannow
      • If SFC reports it repaired files, reboot and monitor for further BSODs.
    8. Check Event Viewer and minidumps for patterns
      • Look in Event Viewer → Windows Logs → System for critical errors around the time of each BSOD to see whether a particular driver or device is repeatedly mentioned.
    9. If crashes persist, use advanced debugging
      • For IT‑pro/advanced scenarios, follow the advanced bug‑check troubleshooting guidance for CRITICAL_PROCESS_DIED and other stop codes to analyze dumps with the Windows debugger and identify the exact driver or module causing corruption.
    10. As a last resort, use Windows recovery options
    • If none of the above resolves the issue, use a system restore point or one of the recovery options in Windows 11 to repair or reset the installation while keeping data where possible.

    These steps systematically rule out new hardware, unstable RAM settings, faulty drivers, and system file corruption, which are the most common root causes of the mix of stop codes shown.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.

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.