Is this question about crashes that happen when programs try to use ntoskrnl.exe or ntkrnlmp.exe?
Is this question about crashes that happen when programs try to use ntoskrnl.exe or ntkrnlmp.exe?
For the past few months i've been having this issue where my PC randomly has a BSOD with either code IRQL_NOT_LESS_OR_EQUAL or KMODE_EXCEPTION_NOT_HANDLED. Before updating to windows 11 i have also stumbled upon the MEMORY_MANAGEMENT error, with the same processes related to them: ntoskrnl.exe or ntkrnlmp.exe. I've tried updating the bios, updating drivers, updating windows, as well as a clean installation. sfc /scannow doesn't show any errors, neither does DISM. When testing using memtest86, no errors are found. I don't know what is causing these errors anymore, i really need help. CPU: Ryzen 5 2400G AMD Stock cooler wraith stealth Motherboard: ASRock A320M-HD P5.40 (initially P4.90 but the issue persists, i don't think i can go beyond 5.40 as ASRock doesn't recommend) RAM: HyperX Fury 2x8GB 2666MHZ (KHX2666C162/8) Storage: ST1000DM010-2EP102 GPU: Radeon RX Vega 11 350W PSU This happens daily, usually when i'm closing an app or when it's just idle. However, it also happens while i'm playing games and it earned me quite a few competitive bans. I scanned the most recent one. The pc was idle with Valorant and Discord both open, it also happens with discord closed so i don't think discord is the issue as the windbg scan of the full dump file says. Code: 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000008, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8026d6ebf2a, address which referenced memory Debugging Details: ------------------ *** WARNING: Check Image - Checksum mismatch - Dump: 0x7dd2, File: 0x159e7 - C:\ProgramData\Dbg\sym\hal.dll\1865382A6000\hal.dll KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4780 Key : Analysis.Elapsed.mSec Value: 5018 Key : Analysis.IO.Other.Mb Value: 27 Key : Analysis.IO.Read.Mb Value: 16 Key : Analysis.IO.Write.Mb Value: 58 Key : Analysis.Init.CPU.mSec Value: 14561 Key : Analysis.Init.Elapsed.mSec Value: 653900 Key : Analysis.Memory.CommitPeak.Mb Value: 269 Key : Bugcheck.Code.KiBugCheckData Value: 0xa Key : Bugcheck.Code.LegacyAPI Value: 0xa Key : Failure.Bucket Value: AV_nt!IopQueueThreadIrp Key : Failure.Hash Value: {8a586314-907b-ce1a-3426-a00962ec3fac} Key : Hypervisor.Enlightenments.Value Value: 0 Key : Hypervisor.Enlightenments.ValueHex Value: 0 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 0 Key : Hypervisor.Flags.ApicEnlightened Value: 0 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 1 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 0 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 0 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 0 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 0 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 0 Key : Hypervisor.Flags.Phase0InitDone Value: 0 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 0 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 16777216 Key : Hypervisor.Flags.ValueHex Value: 1000000 Key : Hypervisor.Flags.VpAssistPage Value: 0 Key : Hypervisor.Flags.VsmAvailable Value: 0 Key : Hypervisor.RootFlags.AccessStats Value: 0 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 0 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 0 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 0 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 0 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 0 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 0 Key : Hypervisor.RootFlags.MceEnlightened Value: 0 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 0 Key : Hypervisor.RootFlags.Value Value: 0 Key : Hypervisor.RootFlags.ValueHex Value: 0 Key : SecureKernel.HalpHvciEnabled Value: 0 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 BUGCHECK_CODE: a BUGCHECK_P1: 8 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8026d6ebf2a FILE_IN_CAB: MEMORY.DMP READ_ADDRESS: 0000000000000008 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: Discord.exe TRAP_FRAME: ffffd68c513b0c70 -- (.trap 0xffffd68c513b0c70) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=ffffc68b2a4c5080 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8026d6ebf2a rsp=ffffd68c513b0e08 rbp=0000000000000000 r8=ffffc68b1af61340 r9=0000000000000005 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!IopQueueThreadIrp+0x6a: fffff802`6d6ebf2a 48397808 cmp qword ptr [rax+8],rdi ds:00000000`00000008=???????????????? Resetting default scope STACK_TEXT: ffffd68c`513b0b28 fffff802`6d82c5e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffd68c`513b0b30 fffff802`6d827b34 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000fff : nt!KiBugCheckDispatch+0x69 ffffd68c`513b0c70 fffff802`6d6ebf2a : 00000000`1e4ef280 00000000`0010001b ffffc68b`293d88fc 00000000`00000001 : nt!KiPageFault+0x474 ffffd68c`513b0e08 fffff802`6dafa3cf : 00000000`00000000 ffffd68c`513b1370 00000000`00000001 ffffc68b`293d88fc : nt!IopQueueThreadIrp+0x6a ffffd68c`513b0e38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryInformationFile+0x35f SYMBOL_NAME: nt!IopQueueThreadIrp+6a MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 6a FAILURE_BUCKET_ID: AV_nt!IopQueueThreadIrp OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {8a586314-907b-ce1a-3426-a00962ec3fac} Followup: MachineOwner ---------
Welcome to the forums! If you're a new person here, your 350W PSU is rated for 350W of power. What makes this unit special? Who made it and when was it first released? You can check if anyone has used another pair of RAM sticks from their friends or neighbors. Try to see if your system works better after that change. If the RAM sticks have X.M.P listed on them, please make sure to turn it on. Your motherboard is an ASRock A320M-HD P5.40 (but maybe try going to a higher version like P4.90 first). Just clear your CMOS carefully as you check if the BIOS was installed correctly before moving forward with the next update until you reach the very latest one. The last update opened up doors so that almost any processor and RAM combo can run on it now.
If you keep seeing BSOD errors, share every single mindump file you can find somewhere safe online. You should put your link up there so we can check them together. Analyzing one file isn't enough; we need to look at everything possible.
here are 3 minidumps from yesterday that happened while i was playing CS2. my computer froze up and the mouse keyboard stopped working after a few seconds too. audio went wrong and the screen turned off completely. but one of those files is big, about 14 gigabytes, so if you want it here just let me know. also, when i looked at my event log, there was an error message right before every crash. It said that a certificate for SCEP failed to start. The code says the authority does not exist. Even though I don't really understand how this works, i'll wait for your answer.
Hello. The PSU is a Bluecase BLU 350-E, it has been more than a year but I don't know the exact age yet. I am going to try turning on XMP and see if that fixes my problem. I have heard other people say about lowering the frequency before, but I tried with 2400MHz back then and the issue still happened. Regarding the RAM, could it be a compatibility issue with the motherboard? If so, wouldn't the PC not even start up? I cannot find my model name on ASRock's website. They don't list every single model though, and they have the same specs as other models that they do support so I might be overthinking it. I also never tried clearing the CMOS so I am a bit scared about breaking the motherboard, not even in time to buy new RAM sticks. I think this motherboard only has one lock for each slot and there is some glue on the other side. The PC was a gift from my brother-in-law and he said the motherboard already had the glue when he bought it. Should I be worried? These are my minidump files: https://drive.google.com/file/d/1Ob-6j-G...sp=sharing
Putting all those four dumps together, it looks like your RAM is the problem. Two of the dumps show errors in the kernel, which means the images on the hard drive are corrupted. This could mean the RAM is bad or the files on your system drive are damaged. The other two dumps also point to the RAM being the main cause of these blue screen crashes. I tell you to test your memory using Memtest86. Download Memtest86 (it's free), then use a tool called imageUSB.exe that came with it to make a bootable USB stick with Memtest86 on it. One gigabyte is enough, so just download the file and put it on your drive. If you can, try doing this on another computer instead of yours right now because you don't trust your current one yet. Then plug in that USB stick onto your PC, and Memtest86 will start running the moment it boots up. If no errors show up after the four rounds of checking thirteen different tests in the free version, restart Memtest86 and run another four rounds. Even one tiny bit error counts as a failure.
I already tried fixing it on my computer. It didn't show any errors when I ran 4 tests. But since you mentioned that, I can't rely on this completely. I'll try something else to check if the memory works. If everything looks okay with these checks, maybe the problem is in the slots where the sticks go?
Was that error code from Event Viewer? Yes, it came from this specific message: "The authority \"amd-keyid-...\" does not exist." The website said HTTP 404 Not Found and gave an error about GETCACaps. This means the computer is trying to check a key but can't find it or cannot reach that server. Do you have any similar errors in your Reliability History? I searched for "GetCACaps" online, but nothing helpful came up. Where was this PC bought originally?
We usually suggest doing two sets of Memtest86, which means running 13 different checks eight times total. If you want a better way to check for memory problems, take one stick out and see if the issues go away when it's gone. It might be that the slots on the motherboard aren't working right, but I don't think that is the most common reason. Just make sure each slot is clean using air from a blower (don't blow with your mouth!). Then look at the RAM sticks to check if the contacts are clean and not broken.