Share via

BSOD ntkrnlmp.exe

Anonymous
2024-10-17T12:11:08+00:00

I've been plagued by blue screens for a long time. Initially, there were random errors with random files. I replaced the SSD with a new one and installed a fresh Windows. The blue screens continued to appear, but now they all referenced ntkrnlmp.exe. I replaced the motherboard, which helped for a while, but by evening I was facing the same blue screens again. In addition to this, games crash after 5-10 minutes of running. It doesn't depend on the load: both simple and demanding games crash.

System specs:

• CPU: AMD Ryzen 5 3600x

• GPU: Radeon rx570

• Motherboard: X470 AORUS ULTRA GAMING

• RAM: 2x8gb HyperX FURY

dumps

I'm starting to get frustrated, I don't understand what's wrong. Please help!

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

11 answers

Sort by: Most helpful
  1. Sakiko 39,240 Reputation points Independent Advisor
    2024-10-19T05:46:41+00:00

    Sure, please keep me updated.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-10-18T09:21:56+00:00

    Thank you for your response. XMP is disabled, and I've never overclocked.

    It's very strange that the problem is with the RAM. The thing is, shortly before using the verifier, I replaced the RAM with a perfectly working one, borrowed from a friend.

    However, I'll run the check now and report the results in the next message.

    Was this answer helpful?

    0 comments No comments
  3. Sakiko 39,240 Reputation points Independent Advisor
    2024-10-18T07:59:56+00:00

    Thanks for the update.

    The information you have provided indicates a memory failure.

    Please make sure XMP or EXPO is turned off, you can press DEL or F12 at power up to enter the BIOS menu (may be other keys depending on different computers, refer to the device manual for details) and adjust it.

    Then try running the Windows Memory Diagnostic tool to test the physical memory. Select the Start button, then Control Panel. In the search box, type "memory" and select "Diagnose memory problems in your computer".

    If the diagnostics are OK, please test the memory for two hours using MemTest64.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-10-17T13:12:04+00:00

    Here is new dumps: new dupms

    Thanks for your patience.

    Was this answer helpful?

    0 comments No comments
  5. Sakiko 39,240 Reputation points Independent Advisor
    2024-10-17T12:44:20+00:00

    Hello, I'm here to help.

    The information you have provided indicates a problem with the system kernel, usually caused by a driver, which we need to verify further. Please first create a restore point for your system, then please refer to this article: https://learn.microsoft.com/en-us/windows-hardw... to enable driver verifier. In the third step select "Automatically select all drivers installed on this computer", wait for a couple of new blue screens and then collect 2-3 new dump files and share the new dump files with me.

    If the computer has any automatic overclocking features enabled (including XMP, PBO, etc.) or manual overclocking, please restore the defaults first.

    Driver verifier puts heavy pressure on the drivers in your system to troubleshoot drivers that are in poor condition or misbehaving. It is normal for your computer to run slowly after driver verifier is turned on. The computer will also crash more frequently and generate dump files during this process.

    If your system fails to boot after driver verifier is turned on or enough dump files are generated, please restore via the restore point.

    Please feel free to reply. This is not a live chat channel and I may be in a different time zone than you. As a result, replies may be delayed and I may respond minutes to hours later.

    Was this answer helpful?

    0 comments No comments