Question My PC crashes almost daily

Toggle sidebar Toggle sidebar
H

Hunter Camper

May 29, 2024
15
2
15
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
 
Sort by date Sort by votes
Without knowing what error codes were associated with the crashes, it's just a guess, but these kinds of crashes can be caused by faulty memory or memory compatibility issues. I had regular crashes like this before that boiled down to inexplicable CPU-memory incompatibility.

Your crash dump files should be located at "C:\Windows\Minidump". You should also be able to find Windows crash events using Event Viewer under Critical events, and there the error code information can be found. I know you said you weren't very familiar with that, though, and unfortunately I can't remember the specifics of how to find that information.
 
Last edited:
Upvote 0 Downvote
COLGeek said:
Is your motherboard BIOS fully updated? https://www.asrock.com/mb/AMD/B550M-C/index.us.asp#BIOS

Are you trying to overclock anything (CPU, GPU, memory)?

Have you run DISM and SFC to verify the health of Windows?

https://support.microsoft.com/en-us...-windows-365e0031-36b1-6031-f804-8fd86e0ef4ca
Click to expand...
No overclocking whatsoever.
I have the 2nd to last bios version. It looks like a newer version came out a few months ago. It's a beta, just like the one that I'm currently running. Should I update?
After running the 1st step (scanhealth) it says "No component store corruption detected."
After running scannow, it says "Windows Resource Protection did not find any integrity violations."
 
Upvote 0 Downvote
ThereAndBackAgain said:
Without knowing what error codes were associated with the crashes, it's just a guess, but these kinds of crashes can be caused by faulty memory or memory compatibility issues. I had regular crashes like this before that boiled down to inexplicable CPU-memory incompatibility.

Your crash dump files should be located at "C:\Windows\Minidump". You should also be able to find Windows crash events using Event Viewer under Critical events, and there the error code information can be found.
Click to expand...
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 (R) Windows Debugger Version 10.0.27793.1000 AMD64
Copyright (c) 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
---------
 
Upvote 0 Downvote
Hunter Camper said:
Should I update?
Click to expand...
It's doubtful that updating the BIOS will fix the problem.
Hunter Camper said:
IRQL_NOT_LESS_OR_EQUAL (a)
Click to expand...
https://learn.microsoft.com/en-us/w...ebugger/bug-check-0xa--irql-not-less-or-equal
I'm not an expert, but that looks like it could be related to memory. Do you have spare known-working memory sticks you could test? You could also try running a memory test, but unfortunately even if those pass with flying colors, that doesn't guarantee the RAM isn't part of the problem. I know this from experience.

You may also want to try running Driver Verifier. Perhaps someone more knowledgeable will come along and offer better/more specific advice though.
 
Upvote 0 Downvote
Ok so I updated BIOS anyway. Also, I just ran a memory test and it didn't find any issues. In the mean time, I'm going to go through the supported RAM list for my mobo and try to get sticks from that list. This could take some time. I'll report back when I get it and test it.
 
Upvote 0 Downvote
Hunter Camper said:
Ok so I updated BIOS anyway. Also, I just ran a memory test and it didn't find any issues. In the mean time, I'm going to go through the supported RAM list for my mobo and try to get sticks from that list. This could take some time. I'll report back when I get it and test it.
Click to expand...
I wouldn't buy new sticks of RAM just yet when we're not sure yet that that's the problem. You should probably wait for someone with more experience to analyze the crash dumps to see if there's another source of the problem. It could also be an issue with a disk drive, with Windows drivers, or something else entirely.

Which memory test did you run? Also, are all your RAM sticks from the same kit?

And do all of the minidump files have that same bugcheck, or are there any that are different?
 
Last edited:
Upvote 0 Downvote
ThereAndBackAgain said:
I wouldn't buy new sticks of RAM just yet when we're not sure yet that that's the problem. You should probably wait for someone with more experience to analyze the crash dumps to see if there's another source of the problem. It could also be an issue with a disk drive, with Windows drivers, or something else entirely.

Which memory test did you run? Also, are all your RAM sticks from the same kit?

And do all of the minidump files have that same bugcheck, or are there any that are different?
Click to expand...
I was able to get Microsoft support to look at the log and they agreed that it's an issue with RAM. Both of my sticks are matched and they work perfectly fine on my other PC. I guess for some reason they are just incompatible with my mobo or cpu or both on this new machine.
 
Upvote 0 Downvote
Hunter Camper said:
I was able to get Microsoft support to look at the log and they agreed that it's an issue with RAM. Both of my sticks are matched and they work perfectly fine on my other PC. I guess for some reason they are just incompatible with my mobo or cpu or both on this new machine.
Click to expand...
I had a set of RAM that worked just fine on my Ryzen 3200G for a long time, but as soon as I changed to a 5600X, it was crashes almost daily. Switching out the RAM for a different kit fixed it. It's so weird. I don't understand why it can be so finnicky.

If it is the RAM, at least it's a relatively easy fix. But it'd be unfortunate if you bought a different kit only for the problem to remain.
 
  • Like
Reactions: Hunter Camper
Upvote 0 Downvote
normally for this problem I would be looking for a device driver that is taking too long to respond.
general fix would be to update the bios to the current version then install the various mother board drivers and retest. I would also remove any overclocking drivers. if you get a memory dump you should put it on a server so someone with a debugger can take a quick look.
errors flushing buffers can be for a drive or a error in the cpu RAM cache. ie ram inside the cpu chip rather than the motherboard RAM sticks.
 
Upvote 0 Downvote
johnbl said:
normally for this problem I would be looking for a device driver that is taking too long to respond.
general fix would be to update the bios to the current version then install the various mother board drivers and retest. I would also remove any overclocking drivers. if you get a memory dump you should put it on a server so someone with a debugger can take a quick look.
errors flushing buffers can be for a drive or a error in the cpu RAM cache. ie ram inside the cpu chip rather than the motherboard RAM sticks.
Click to expand...
the microsoft support tech did mention issues with drivers also. he wasn't very specific and said it was not a windows problem. I've already updated bios. So you're saying to re-install all mobo drivers? i'm not familiar with memory dumps or how to put them on a server.
 
Upvote 0 Downvote
Hunter Camper said:
the microsoft support tech did mention issues with drivers also. he wasn't very specific and said it was not a windows problem. I've already updated bios. So you're saying to re-install all mobo drivers? i'm not familiar with memory dumps or how to put them on a server.
Click to expand...
Just upload some of the recent minidump files somewhere like DropBox or Google Drive where you could share them with users on the forum using a link. I won't be able to help with advanced analysis of dump files, but some people here can.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom