Question The bugcheck was: 0x0000003b

[ToNiX21]

Hello, i need some help. I have started getting this random BSOD while playing this new game Delta Force which has an kernel level anticheat. i have already updated my chipset drivers and bios. Im running all default only XMP enabled. AMD 5600x, MSI MPG b550 gaming plus, nvidia RTX 3070

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80323ac2d00, 0xffffb580ddbe0920, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\022625-6421-01.dmp. Report Id: 00bb07ef-1cf9-4994-910c-e4cfa229ba43.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80323ac2d00, Address of the instruction which caused the BugCheck
Arg3: ffffb580ddbe0920, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1078

Key : Analysis.Elapsed.mSec
Value: 6746

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x3b

Key : Bugcheck.Code.TargetModel
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: AV_ACE_BASE!unknown_function

Key : Failure.Hash
Value: {2a7f67f1-b324-eb93-e618-e903b45ded5c}

Key : Hypervisor.Enlightenments.Value
Value: 77057948

Key : Hypervisor.Enlightenments.ValueHex
Value: 497cf9c

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 1

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 4a10ef

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key : Stack.Pointer
Value: PRCBException


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80323ac2d00

BUGCHECK_P3: ffffb580ddbe0920

BUGCHECK_P4: 0

FILE_IN_CAB: 022625-6421-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

FAULTING_THREAD: ffff8a855cc5c080

CONTEXT: ffffb580ddbe0920 -- (.cxr 0xffffb580ddbe0920)
rax=ffffb580f7adc000 rbx=0000000000000002 rcx=ffffc6805135a880
rdx=ffffef00a6781788 rsi=0000000000000000 rdi=ffffc6805135a808
rip=fffff80323ac2d00 rsp=ffffc6805135a768 rbp=ffff8a855d797100
r8=0000000000000008 r9=0000000000000001 r10=0000000000000001
r11=ffffc6805135a878 r12=0000000000000000 r13=ffff8a855f8cce10
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050212
ACE_BASE+0xc2d00:
fffff803`23ac2d00 488b440af8 mov rax,qword ptr [rdx+rcx-8] ds:002b:ffffb580`f7adc000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: DeltaForceClie

STACK_TEXT:
ffffc680`5135a768 fffff803`23a87c2a : ffff81da`c07bd6e0 00000000`00000008 00000001`a0be86e0 fffff803`23a99cd1 : ACE_BASE+0xc2d00
ffffc680`5135a770 ffff81da`c07bd6e0 : 00000000`00000008 00000001`a0be86e0 fffff803`23a99cd1 00000001`00000001 : ACE_BASE+0x87c2a
ffffc680`5135a778 00000000`00000008 : 00000001`a0be86e0 fffff803`23a99cd1 00000001`00000001 00000000`008b1101 : 0xffff81da`c07bd6e0
ffffc680`5135a780 00000001`a0be86e0 : fffff803`23a99cd1 00000001`00000001 00000000`008b1101 ffff81da`c07bd6e0 : 0x8
ffffc680`5135a788 fffff803`23a99cd1 : 00000001`00000001 00000000`008b1101 ffff81da`c07bd6e0 00000000`00000000 : 0x00000001`a0be86e0
ffffc680`5135a790 00000001`00000001 : 00000000`008b1101 ffff81da`c07bd6e0 00000000`00000000 ffffb580`f7adc000 : ACE_BASE+0x99cd1
ffffc680`5135a798 00000000`008b1101 : ffff81da`c07bd6e0 00000000`00000000 ffffb580`f7adc000 fffff803`23a99da7 : 0x00000001`00000001
ffffc680`5135a7a0 ffff81da`c07bd6e0 : 00000000`00000000 ffffb580`f7adc000 fffff803`23a99da7 00000001`a0be86e0 : 0x8b1101
ffffc680`5135a7a8 00000000`00000000 : ffffb580`f7adc000 fffff803`23a99da7 00000001`a0be86e0 fffff803`23a88326 : 0xffff81da`c07bd6e0


SYMBOL_NAME: ACE_BASE+c2d00

MODULE_NAME: ACE_BASE

IMAGE_NAME: ACE-BASE.sys

STACK_COMMAND: .cxr 0xffffb580ddbe0920 ; kb

BUCKET_ID_FUNC_OFFSET: c2d00

FAILURE_BUCKET_ID: AV_ACE_BASE!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2a7f67f1-b324-eb93-e618-e903b45ded5c}

Followup: MachineOwner

 

[johnbl]

access violation. can not determine why the address is bad
you should put the memory dump on a server, share it for public access so someone with a windows debugger can take a look.
this command lmiftsm
will list your drivers in order. It makes it easy to see old or common drivers with bugs.
for a access violation it can be a bug or a hardware issue.

when you see error code c0000005 it is a bad memory address
I tend to think of corruption caused by the app, or a bad driver corrupting memory and storing it in a pagefile.sys.

most people would run memtest86 to confirm your memory timings. you might also consider deletion of your virtual memory (pagefile.sys) rebooting and creating a new pagefile.sys

other than that I would look at the drivers in windbg and look for known bad drivers.

also, looking at a series of memory dumps can help. most drivers corrupt their own data, some corrupt other drivers data.
ssd firmware can have bugs, bad spots show up in pagefile.sys
lots of reasons

some devices like mice have firmware that talks to a installed service. you can get corruption if you update the mouse firmware but not the mouse service software. pretty common for mice service software to corrupt memory due to bad programing assumptions. (update software in those cases)