Share via

I've been having this issue for around 3 days; I've repaired the system files yet I'm still getting that BSOD. I'll even share the analysis of the recent minidump file. I'm stuck on windows 10.

DN 0 Reputation points
2026-05-06T02:16:03.3766667+00:00 
  •                                                                         *

  •                    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: fffff80632534add, Address of the instruction which caused the BugCheck

Arg3: fffff684f1e9ee30, 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: 4921

Key  : Analysis.Elapsed.mSec

Value: 17998

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 0

Key  : Analysis.Init.CPU.mSec

Value: 2468

Key  : Analysis.Init.Elapsed.mSec

Value: 13029

Key  : Analysis.Memory.CommitPeak.Mb

Value: 96

Key  : Analysis.Version.DbgEng

Value: 10.0.29547.1002

Key  : Analysis.Version.Description

Value: 10.2602.27.2 amd64fre

Key  : Analysis.Version.Ext

Value: 1.2602.27.2

Key  : Bugcheck.Code.LegacyAPI

Value: 0x3b

Key  : Bugcheck.Code.TargetModel

Value: 0x3b

Key  : Failure.Bucket

Value: AV_acpitime!WaHandleAcpiGetRealTime

Key  : Failure.Exception.IP.Address

Value: 0xfffff80632534add

Key  : Failure.Exception.IP.Module

Value: ACPI

Key  : Failure.Exception.IP.Offset

Value: 0x24add

Key  : Failure.Hash

Value: {aeadc4bf-3223-d972-c07c-d821bbb88289}

Key  : Faulting.IP.Type

Value: Paged

Key  : Hypervisor.Enlightenments.Value

Value: 77582238

Key  : Hypervisor.Enlightenments.ValueHex

Value: 0x49fcf9e

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: 0

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: 4722927

Key  : Hypervisor.Flags.ValueHex

Value: 0x4810ef

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: 0x3f7

Key  : WER.OS.Branch

Value: vb_release

Key  : WER.OS.Version

Value: 10.0.19041.1

Key  : WER.System.BIOSRevision

Value: 15.70.0.0

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80632534add

BUGCHECK_P3: fffff684f1e9ee30

BUGCHECK_P4: 0

FILE_IN_CAB: 050426-20031-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

FAULTING_THREAD: ffffc50301fa9080

CONTEXT: fffff684f1e9ee30 -- (.cxr 0xfffff684f1e9ee30)

rax=ffffaf812ddeaa98 rbx=0000000000000001 rcx=0000000000000001

rdx=0000000000000000 rsi=0000000000000000 rdi=ffffaf812ddeaa98

rip=fffff80632534add rsp=fffff684f1e9f830 rbp=fffff684f1e9f8a9

r8=00000000f8000000 r9=fffff684f1e9f7d8 r10=fffff78380003054

r11=0000000000000001 r12=0000000000000001 r13=ffffc502f8479488

r14=00000000000000ff r15=0000000000000001

iopl=0 nv up ei pl nz na po nc

cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010202

ACPI!WriteSystemMem+0xa9:

fffff80632534add 881f mov byte ptr [rdi],bl ds:002b:ffffaf812ddeaa98=??

Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

IP_IN_PAGED_CODE:

ACPI!WriteSystemMem+a9

fffff806`32534add 881f mov byte ptr [rdi],bl

STACK_TEXT:

fffff684f1e9f830 fffff80632511c2a : fffff57abd58a060 fffff57abd5eac50 8a0000002fe5eb63 fffff80633f0114e : ACPI!WriteSystemMem+0xa9

fffff684f1e9f910 fffff80632541fda : ffffc5030958c010 ffffc50306dde100 00000000000000ff 00000000000000ff : ACPI!AccessBaseField+0x2ba

fffff684f1e9f9c0 fffff8063253468a : ffffc50306dde118 ffffc502f8479488 ffffc5030958c010 0000000000000001 : ACPI!AccessFieldData+0x15e

fffff684f1e9fa10 fffff80632514fbf : ffffc5030958c010 fffff684f1e9fb39 0000000000000000 0000000000000000 : ACPI!WriteFieldObj+0x10a

fffff684f1e9fa70 fffff80632514a45 : 0000000000000000 ffffc5030958c010 0000000000000000 000000000000004d : ACPI!RunContext+0x1ef

fffff684f1e9fba0 fffff806325163be : 0000000000000000 fffff684f1e9fd00 0000000000000000 ffffc5030958c1f0 : ACPI!InsertReadyQueue+0x2a5

fffff684f1e9fc00 fffff806325146c8 : 0000000000000001 0000000000000049 000000000032c000 ffffc502f847aa20 : ACPI!AsyncEvalObject+0xb2e

fffff684f1e9fd40 fffff8063251bd49 : fffff68400000000 ffffc502f847aa20 0000000000000000 000000000032c004 : ACPI!SyncEvalObject+0x238

fffff684f1e9fdf0 fffff8063251bb6a : 0000000000000000 ffff9f0e3649c4d0 0000000000000000 0000000000000000 : ACPI!AMLIEvalNameSpaceObject+0xa9

fffff684f1e9fe50 fffff8063251ba27 : ffffc503043dcdf0 fffff80600000000 ffff9f0e3649c4d0 ffffc502f847aa98 : ACPI!ACPIIoctlEvalControlMethod+0xa6

fffff684f1e9fee0 fffff806325110d5 : ffffc502f79c8410 0000000000000007 ffffc503043dcec0 fffff80633f1db01 : ACPI!ACPIIrpDispatchDeviceControl+0x187

fffff684f1e9ff20 fffff80633ed21c5 : 0000000000000007 0000000000000001 fffff684f1ea0079 fffff684f1ea0170 : ACPI!ACPIDispatchIrp+0xc5

fffff684f1e9ffa0 fffff806323b35a7 : 0000000000000010 0000000000000000 fffff684f1ea0170 fffff684f1ea0079 : nt!IofCallDriver+0x55

fffff684f1e9ffe0 fffff806323b1eb2 : 000000000a3dd800 0000000000000001 0000000000000000 0000000000000001 : Wdf01000!FxIoTarget::Send+0x17

fffff684f1ea0010 fffff806323c7ae7 : 0000000000000000 fffff684f1ea0100 fffff68400000000 0000000000000000 : Wdf01000!FxIoTarget::SubmitSync+0x1a2

fffff684f1ea00e0 fffff806323c7958 : ffffc502faafe230 ffffc5030a63e2c0 fffff684f1ea0500 0000000000001030 : Wdf01000!FxIoTargetSendIoctl+0x183

fffff684f1ea0380 fffff80636bf6cf5 : ffffc502fab75b30 0000000000000010 0000000000000000 0000fffff80636bf : Wdf01000!imp_WdfIoTargetSendIoctlSynchronously+0x48

fffff684f1ea03e0 fffff80636bf68d8 : 0000000000000010 ffffc502faba80e0 00003afd05457f18 0000000000000000 : acpitime!WaHandleAcpiGetRealTime+0x139

fffff684f1ea04d0 fffff806323b9032 : ffffc50306d2e230 0000000000294210 ffffc502fab76d30 00003afd05457f18 : acpitime!WaIoDeviceControl+0x208

(Inline Function) ---------------- : ---------------- ---------------- ---------------- --------`-------- : Wdf01000!FxIoQueueIoDeviceControl::Invoke+0x41

fffff684f1ea0540 fffff806323b8a00 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x162

fffff684f1ea05e0 fffff806323b5dee : ffffc502faba80e0 ffffc502faba8000 0000000000000000 ffffc502fab75cf0 : Wdf01000!FxIoQueue::DispatchEvents+0x520

fffff684f1ea06b0 fffff806323b7877 : 0000000000000000 ffffc50306d2e230 0000000000000000 ffffc502faba80e0 : Wdf01000!FxIoQueue::QueueRequest+0xae

(Inline Function) ---------------- : ---------------- ---------------- ---------------- --------`-------- : Wdf01000!FxPkgIo::DispatchStep2+0x5ac

fffff684f1ea0720 fffff806323b723d : ffffc50300000000 ffffc50306505a20 ffffc50306d2e230 0000000000000000 : Wdf01000!FxPkgIo::DispatchStep1+0x627

fffff684f1ea07e0 fffff806323ba906 : ffffc50306505a20 fffff684f1ea09a0 fffff806323b2f70 ffffc502faba6c20 : Wdf01000!FxPkgIo::Dispatch+0x5d

(Inline Function) ---------------- : ---------------- ---------------- ---------------- --------`-------- : Wdf01000!DispatchWorker+0x6a

(Inline Function) ---------------- : ---------------- ---------------- ---------------- --------`-------- : Wdf01000!FxDevice::Dispatch+0x88

fffff684f1ea0840 fffff80633ed21c5 : 0000000000000080 000000000000003e 0000000000000001 fffff684f1ea09e0 : Wdf01000!FxDevice::DispatchWithLock+0x156

fffff684f1ea08a0 fffff80634463ef6 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IofCallDriver+0x55

fffff684f1ea08e0 fffff8063446405f : fffff684f1ea09e0 fffff806340cc2c3 0000000000000001 000000000000003e : nt!HalpQueryAcpiRealTimeClock+0x9a

fffff684f1ea0970 fffff806340b6be9 : 0000000000000001 0000000000000000 0000000000000000 0000000000000000 : nt!HalpUtcTimeToAcpiRealTime+0x3b

fffff684f1ea09b0 fffff806345a5b1c : 00000083a287f900 00000083a287f900 0000000000000101 fffff80634309526 : nt!HalSetRealTimeClock+0x159

fffff684f1ea0a20 fffff8063454bdc5 : 00000083a287f9f0 0000000000000101 00000083a287f9e0 01dcdc3fc68b8d5e : nt!ExpSetSystemTime+0xcb64

fffff684f1ea0a70 fffff80634011d0b : ffffc50301fa9080 0000000000000100 0000008300000000 ffffc50300000000 : nt!NtSetSystemTime+0x145

fffff684f1ea0b00 00007ffdc4370b57 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x41f

00000083a287f998 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd`c4370b57

SYMBOL_NAME: acpitime!WaHandleAcpiGetRealTime+139

MODULE_NAME: acpitime

IMAGE_NAME: acpitime.sys

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .cxr 0xfffff684f1e9ee30 ; kb

BUCKET_ID_FUNC_OFFSET: 139

FAILURE_BUCKET_ID: AV_acpitime!WaHandleAcpiGetRealTime

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {aeadc4bf-3223-d972-c07c-d821bbb88289}

Followup: MachineOwner

Windows for home | Windows 10 | Performance and system failures
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. DaveM121 (2) 13,715 Reputation points Volunteer Moderator
    2026-05-06T06:06:05.8466667+00:00

    That minidump file analysis does not indicate the underlying cause of the system crashes.

    Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Please do not upload a very large Memory.dmp file.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so I can take a look for you.

    0 comments
  2. Q&A Assist
    2026-05-06T02:16:21.9566667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The minidump shows a SYSTEM_SERVICE_EXCEPTION (0x3B) with exception code 0xC0000005 (STATUS_ACCESS_VIOLATION). The faulting code is inside the ACPI driver path (ACPI!WriteSystemMem, called from acpitime.sys in WaHandleAcpiGetRealTime), which is part of the kernel’s ACPI/time stack. This indicates a kernel‑mode access violation while ACPI is writing to system memory, typically caused by a faulty/buggy driver, firmware/BIOS issue, or memory/data corruption rather than corrupt system files.

    From the bug check documentation:

    • 0x3B occurs when an exception happens while executing a system service routine.
    • Common cause is a NULL pointer dereference or access to an incorrect/random address, often due to prematurely freed memory or data structure corruption.

    Given that the stack clearly shows ACPI and acpitime.sys, focus should be on:

    1. Firmware/BIOS and chipset/ACPI‑related drivers.
    2. Recently added or updated device drivers or system services.
    3. General driver/memory issues that can corrupt kernel data.

    Actionable steps based on the bug check guidance:

    1. Check for problematic or recently changed drivers
    • In Device Manager, look for any devices with an exclamation mark and review their Events tab for errors around the time of the BSOD.
    • If any device drivers or system utilities were added/updated in the last few days (especially power management, motherboard utilities, overclocking tools, or virtualization tools), remove or roll them back and test.
    1. Review Event Viewer
    • Open Event Viewer → Windows Logs → System.
    • Look for critical or error events that occur at the same time as the BSOD. These can help pinpoint which device or driver is triggering the ACPI/time call that leads to the crash.
    1. Use Driver Verifier for driver issues
    • Since the crash is in the ACPI/time path, use Driver Verifier to stress drivers and catch misuse of memory or IRPs:
      • Run verifier from an elevated command prompt.
      • Configure it to verify non‑Microsoft drivers first (to avoid over‑stressing core OS components).
      • Reboot and use the system until it crashes again.
      • Analyze the new dump; if Driver Verifier flags a specific third‑party driver, update or remove that driver.
      • Note: Driver Verifier adds overhead and can itself cause more frequent crashes while testing; disable it once finished.
    1. Analyze multiple dumps if available
    • If there are several minidumps, compare them to see if the same ACPI/acpitime path appears each time or if another third‑party driver shows up in the stack.
    • Use !error on parameter 1 (0xC0000005) to confirm the access violation, and examine the stack text around ACPI/acpitime for any recurring third‑party modules.
    1. General bug check troubleshooting
    • If any new hardware was added recently (RAM, storage, PCIe cards, etc.), temporarily remove or replace it and test.
    • Ensure all motherboard/chipset and storage drivers are the latest versions from the system or motherboard vendor.
    • If the issue started immediately after a specific Windows update, and only that update is new, consider uninstalling that update and testing, then re‑applying once a fixed build is available.

    If comfortable with WinDbg, further debugging can follow the documented approach:

    • Use .cxr with parameter 3 (0xfffff684f1e9ee30) then kb to inspect the context and stack in more detail.
    • Use lm t n to list loaded modules and check for any non‑Microsoft drivers involved near the ACPI/acpitime calls.

    If after updating/removing suspect drivers and checking firmware the crashes persist, the next step is to treat this as a deeper driver/firmware interaction problem and continue with Driver Verifier and vendor support (motherboard/system manufacturer) for ACPI/BIOS updates.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.