Is my computer crashing a lot?
Is my computer crashing a lot?
My PC crashes regularly. Sometimes daily. Just today it crashed twice within 30 minutes. I get the blue screen that reads "Your PC ran into a problem and needs to restart". I tried looking through the logs in Even Viewer, but I'll admit that I'm not very familiar with that. I was able to find 2 critical messages that match up with the times that my PC crashed but these are just messages that say that my PC rebooted after a crash. They don't give any info regarding the actual problem that caused the crash. If you guys can help me locate the crash logs, I'll be happy to share them with you. This has become so frustrating, never knowing when it will crash next. I'll add that this a custom build and the problem has been happening since the day I built it. I have done fresh re-installs of Windows three times to see if that would help, but nothing changes. OS: Windows 11 Pro Mobo: AsRock B550M-C CPU: AMD Ryzen 5 3600 Ram: 16gb DDR4 3200 GPU: XFX RX-580 8GB SSD: Kingston NVME 1TB PSU: Corsair CX600 CPU Cooler: Thermaltake UX100 3 case fans plus cpu fan with proper fan control setup
It's just a guess since we don't know which error codes were on board when things broke. But crashes like this usually mean your memory is broken or doesn't talk well with other parts of it. Before, I had regular crashes that made no sense because the CPU and memory didn't match up properly. Your crash files should be in "C:\Windows\Minidump". You can also check Event Viewer under Critical events to see what happened there, where you'll find the error code details. I know you said you weren't familiar with finding those things, and unfortunately I don't remember how to do it anymore.
I don't use any overclocking tricks right now. My computer has an older BIOS version that looks a bit like the new ones coming out every few months. It's actually in beta test mode, just like what I'm running today. Should I bother updating it? After my first step (scanning health), it said no parts were corrupted. Then when I ran scannow, Windows said nothing was broken either.
this is what i got: ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 43 Microsoft ® Windows Debugger Version 10.0.27793.1000 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041125-5968-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 26100 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff800`c7400000 PsLoadedModuleList = 0xfffff800`c82f49c0 Debug session time: Fri Apr 11 18:05:28.288 2025 (UTC - 5:00) System Uptime: 0 days 0:34:09.984 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................. Loading User Symbols PEB is paged out (Peb.Ldr = 00000000`0039f018). Type ".hh dbgerr001" for details Loading unloaded module list ......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800`c78b5520 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`5b41ab50=0000000000000101 0: 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: ffffdb092b7722f4, memory referenced Arg2: 00000000000000ff, IRQL Arg3: 0000000000000091, 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: fffff800c772e983, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1593 Key : Analysis.Elapsed.mSec Value: 2596 Key : Analysis.IO.Other.Mb Value: 10 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 23 Key : Analysis.Init.CPU.mSec Value: 593 Key : Analysis.Init.Elapsed.mSec Value: 40614 Key : Analysis.Memory.CommitPeak.Mb Value: 88 Key : Analysis.Version.DbgEng Value: 10.0.27793.1000 Key : Analysis.Version.Description Value: 10.2410.02.02 amd64fre Key : Analysis.Version.Ext Value: 1.2410.2.2 Key : Bugcheck.Code.LegacyAPI Value: 0xa Key : Bugcheck.Code.TargetModel Value: 0xa Key : Dump.Attributes.AsUlong Value: 0x21008 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0x0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: AV_nt!KeAccumulateTicks Key : Failure.Exception.IP.Address Value: 0xfffff800c772e983 Key : Failure.Exception.IP.Module Value: nt Key : Failure.Exception.IP.Offset Value: 0x32e983 Key : Failure.Hash Value: {bdd44265-f411-b02a-f0e6-95fb2512e2b8} Key : Stack.Pointer Value: ISR BUGCHECK_CODE: a BUGCHECK_P1: ffffdb092b7722f4 BUGCHECK_P2: ff BUGCHECK_P3: 91 BUGCHECK_P4: fffff800c772e983 FILE_IN_CAB: 041125-5968-01.dmp DUMP_FILE_ATTRIBUTES: 0x21008 Kernel Generated Triage Dump FAULTING_THREAD: ffffdb083b62d080 WRITE_ADDRESS: fffff800c83c34c0: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse ffffdb092b7722f4 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: hid.exe STACK_TEXT: fffff800`5b41ab48 fffff800`c772f018 : 00000000`00000101 00000000`00000010 00000000`00000000 ffff9281`2bfb4180 : nt!KeBugCheckEx fffff800`5b41ab50 fffff800`c77a44a1 : 00000000`00000000 00000000`0000000c 00000000`00000000 00000000`0002007e : nt!KeAccumulateTicks+0x6d8 fffff800`5b41abc0 fffff800`c77a4065 : 00000000`00013178 00000000`00000000 00000004`c5e2d14c 00000000`0000000d : nt!KiUpdateRunTime+0xc9 fffff800`5b41ac40 fffff800`c768573e : 00000000`0000000d 00000000`00000000 fffff800`5725f810 fffff800`c83207f8 : nt!KiUpdateTime+0x2b5 fffff800`5b41add0 fffff800`c76870ed : fffff800`c8210a40 00000000`00000000 fffff800`c8210af0 fffff800`c838e150 : nt!KeClockInterruptNotify+0x66e fffff800`5b41af50 fffff800`c7a7dade : 00000000`20b6020c fffff800`c8210a40 ffffb406`5fecce30 00000004`c5f97bf4 : nt!KiCallInterruptServiceRoutine+0x2ed fffff800`5b41afb0 fffff800`c7a7e2ec : 00000004`c5f96860 ffffb406`5fecceb0 00000004`c5f96869 000006b3`0f590a91 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e ffffb406`5fecce30 fffff800`c773d41c : 00000000`00000050 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c ffffb406`5feccfc0 fffff800`c773d38b : 00000000`00000001 00000000`00000000 00000000`00000001 ffffdb08`2bc5cd01 : nt!KiIpiStallOnPacketTargetsPrcb+0x2c ffffb406`5feccff0 fffff800`c7c9c31d : 00000000`00000000 ffffb406`5fecdb60 00000000`00000000 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0x10f ffffb406`5fecd050 fffff800`c7db372e : ffffdb08`3b62d080 ffffb406`00010400 00000000`00870000 00000000`00000000 : nt!ExpGetProcessInformation+0x18d ffffb406`5fecd6c0 fffff800`c7db25fe : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`003a1000 : nt!ExpQuerySystemInformation+0xfce ffffb406`5fecdaa0 fffff800`c7a8ef58 : ffffdb08`3b620000 ffffdb08`3b62d080 ffffdb08`3b62d080 00000000`003a1000 : nt!NtQuerySystemInformation+0x3e ffffb406`5fecdae0 00007ffc`fdbbc684 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 00000000`0009e048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`fdbbc684 SYMBOL_NAME: nt!KeAccumulateTicks+43 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.26100.3775 STACK_COMMAND: .process /r /p 0xffffdb083b62c080; .thread 0xffffdb083b62d080 ; kb BUCKET_ID_FUNC_OFFSET: 43 FAILURE_BUCKET_ID: AV_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {bdd44265-f411-b02a-f0e6-95fb2512e2b8} Followup: MachineOwner ---------
It's probably not going to help if you just update the BIOS. It looks like this might be about your RAM sticks. Do you have some spare ones that work fine? You could also run a memory test, but even if those tests pass easily, they don't always make sure the RAM isn't the cause of the issue. I know it from experience. You might try Driver Verifier instead. Maybe someone smarter can give better advice later.
Ok so I updated my BIOS too. Also, I just ran a memory check and nothing was wrong with it. In the meantime, I'm going to look at the supported RAM list for my motherboard and try to find sticks that work on it. This might take a while. I'll tell you back when I get it started and test it out then.
I wouldn't buy new RAM chips right now just when we aren't sure what's really wrong. You should probably wait until someone with more experience looks at the crash logs to see if something else is causing the issue. It could also be a problem with your hard drive, Windows programs (drivers), or maybe even something completely different. Which memory test did you run? Are all of your RAM sticks from the exact same type and kit? And do all the minidump files show that same error code, or are any of them different?
I talked to Microsoft people and they said the problem is with the memory (RAM). My two sticks were the same and worked great on another computer. It sounds like something else went wrong here, maybe my motherboard or the processor doesn't play nice with these sticks anymore on this new PC.
I used to have some RAM that worked great on my Ryzen 3200G all day long. Then I started swapping to a 5600X, and suddenly crashes were happening almost every single time. Just changing the RAM kit stopped it right away. It's really strange stuff here. I don't get why this would happen sometimes but not other times. If the issue is actually the RAM, at least it was pretty easy to fix. But if you bought new RAM just because something went wrong with your old one and the problem stays, that would be a real no-no.