Question Kernel 41 Error while idle and gaming ?

[RushGemsHorizon]

I think I've had enough of this error. I've tried everything already, from running memtest to changing power plans, but it looks like the issue still persists.

Luckily, this time my PC decided to create dump log errors.

Can anyone help me with this? I don't know how memory dumps work.

Here my spec:
Device name DESKTOP-P73PJL0
Processor AMD Ryzen 5 5600G with Radeon Graphics 3.90 GHz
Installed RAM 16,0 GB (15,4 GB usable)
Device ID C6E1286D-A90C-4AF3-B6C5-35081F501378

Here the dump:
091524-26312-01.dmp

091524-26312-01

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

Edited 15-09-2024:
Here is the latest analyst memory dump (I was playing NIKKE when the reboot occurred)

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000b2, MmMapLockedPages called on an MDL having incorrect flags.
For example, calling MmMapLockedPages for an MDL
that is already mapped to a system address is incorrect.
Arg2: ffffae0c78828fc0, MDL address.
Arg3: 0000000000000004, MDL flags.
Arg4: 0000000000000004, Incorrect MDL flags.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2171

Key : Analysis.Elapsed.mSec
Value: 3902

Key : Analysis.IO.Other.Mb
Value: 1

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 6

Key : Analysis.Init.CPU.mSec
Value: 452

Key : Analysis.Init.Elapsed.mSec
Value: 13491

Key : Analysis.Memory.CommitPeak.Mb
Value: 91

Key : Bugcheck.Code.LegacyAPI
Value: 0xc4

Key : Bugcheck.Code.TargetModel
Value: 0xc4

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: 0xc4_b2_ACE_BASE!unknown_function

Key : Failure.Hash
Value: {2f5e91cf-4b49-d06f-3c30-03808e67014f}


BUGCHECK_CODE: c4

BUGCHECK_P1: b2

BUGCHECK_P2: ffffae0c78828fc0

BUGCHECK_P3: 4

BUGCHECK_P4: 4

FILE_IN_CAB: 091524-26015-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

FAULTING_THREAD: ffffae0c079340c0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: SGuard64.exe

STACK_TEXT:
fffffe8c`885be808 fffff802`2f1e1e44 : 00000000`000000c4 00000000`000000b2 ffffae0c`78828fc0 00000000`00000004 : nt!KeBugCheckEx
fffffe8c`885be810 fffff802`2f1f862f : ffffae0c`78828fc0 00000000`00000000 00000000`c0000001 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xe0
fffffe8c`885be850 fffff802`2f1f7c23 : ffffae0c`78828fc0 fffff802`2f1f76ab ffffae0c`78828fc0 00000000`00000000 : nt!ViMmMapLockedPagesSanityChecks+0xa7
fffffe8c`885be890 fffff804`e094923d : ffffae0c`78828fc0 00000000`00000000 00000000`c0000001 fffff802`2f1e60a5 : nt!VerifierMmMapLockedPagesSpecifyCache+0x33
fffffe8c`885be8e0 ffffae0c`78828fc0 : 00000000`00000000 00000000`c0000001 fffff802`2f1e60a5 00000000`00000000 : ACE_BASE+0x5923d
fffffe8c`885be8e8 00000000`00000000 : 00000000`c0000001 fffff802`2f1e60a5 00000000`00000000 00000000`00000010 : 0xffffae0c`78828fc0


SYMBOL_NAME: ACE_BASE+5923d

MODULE_NAME: ACE_BASE

IMAGE_NAME: ACE-BASE.sys

STACK_COMMAND: .process /r /p 0xffffae0c5871c080; .thread 0xffffae0c079340c0 ; kb

BUCKET_ID_FUNC_OFFSET: 5923d

FAILURE_BUCKET_ID: 0xc4_b2_ACE_BASE!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2f5e91cf-4b49-d06f-3c30-03808e67014f}

Followup: MachineOwner
---------

 

[Roland Of Gilead]

Hey there,

Kernal 41 means that the system lost power unexpectedly.

Can you list your full PC specs please? Including mobo and PSU make and model.

 

[RushGemsHorizon]

Asrock B450M Steel Legend
Vurrion ARC Series 550 Froze Edition | PSU 80+ RGB 550W

I updated my driver, and apparently, it was the latest version. I'll be back to report whether the Kernel 41 issue is still there or not. As for the recent error, it seems that Nikke's anti-cheat was the problem, so I removed it. Everything was fine until the Kernel 41 issue happened again. I'm not sure what went wrong, as my PC isn't writing dump files for the recent events.

 

[RushGemsHorizon]

There is still a Kernel 41 error. I was playing ZZZ when my PC rebooted itself in the middle of the game. Once again, I checked the event log and saw the Kernel 41 error. It always appears after Event 6, and the sound device seems to disappear after the reboot.

No memory dump, just the good old Kernel 41.

https://imgur.com/NC8Y27d

 

[RushGemsHorizon]

Update 9/21/2024:
I have finished reinstalling the OS to Ubuntu. The issue still persists, but I think it may be related to a driver problem.

 

[buggerlugs_52]

Try unplugging your power and HDD activity LED's from the motherboard. Mine was resolved by doing this. Cheap chinese high power LED's fitted to PC cases is causing this issue. (Was in mine!)