BSOD issues

Question

Getting a lot of BSOD issues lately. My minidump is below, any help would be great. I believe its a CPU issue but the CPU is still quite new. I have reseated it and temps are within the threshold so overheating isn't the issue.

*******************************************************************************
*                                                                             *
*                        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: fffff8042a5115a9, Address of the instruction which caused the BugCheck
Arg3: ffffbd813dd32900, 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: 1421

    Key  : Analysis.Elapsed.mSec
    Value: 4492

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_nt!KiWakeQueueWaiter

    Key  : Failure.Hash
    Value: {89a3d14f-3238-5523-6cfb-56792bd502eb}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    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

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8042a5115a9

BUGCHECK_P3: ffffbd813dd32900

BUGCHECK_P4: 0

FILE_IN_CAB:  100823-10625-01.dmp

DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

CONTEXT:  ffffbd813dd32900 -- (.cxr 0xffffbd813dd32900)
rax=0000000000000001 rbx=ffff9585053aa080 rcx=7fff95850d379d40
rdx=ffff95850d379d40 rsi=ffff95850d379d00 rdi=ffff9585053aa1c0
rip=fffff8042a5115a9 rsp=ffffb808731479c0 rbp=ffffbd813dd11180
 r8=ffff95850b029b40  r9=fffff8042a200000 r10=0000fffff8042a00
r11=0000000000000001 r12=ffff95850b029b40 r13=0000000000000000
r14=ffff95850bcc5200 r15=ffff95850d379d48
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!KiWakeQueueWaiter+0x99:
fffff804`2a5115a9 0fb601          movzx   eax,byte ptr [rcx] ds:002b:7fff9585`0d379d40=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  SystemSettings

STACK_TEXT:  
ffffb808`731479c0 fffff804`2a511914     : ffff9585`0d379d40 ffff9585`00000000 ffffffff`fffebb37 00000000`00000000 : nt!KiWakeQueueWaiter+0x99
ffffb808`73147a20 fffff804`2a6273e8     : ffff9585`0d674080 ffff9585`0d72a680 00000000`00000000 ffffffff`ffffffff : nt!NtReleaseWorkerFactoryWorker+0x204
ffffb808`73147aa0 00007ffa`f1fb21d4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000099`560bf378 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`f1fb21d4

SYMBOL_NAME:  nt!KiWakeQueueWaiter+99

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.2361

STACK_COMMAND:  .cxr 0xffffbd813dd32900 ; kb

BUCKET_ID_FUNC_OFFSET:  99

FAILURE_BUCKET_ID:  AV_nt!KiWakeQueueWaiter

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {89a3d14f-3238-5523-6cfb-56792bd502eb}

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

Answer 1

However, please check your RAM modes (voltage, frequency, timings) are in compliance with numbers in the motherboard compatibility list for your RAM model, especially if you have Ryzen CPU.

Share your minidumps to OneDrive, maybe they will give some clues.

Answer 2

Its 100% not RAM I have confirmed this by switching to 2 working sticks of RAM. It crashes whether I have my Corsair Vengeance Pro RAM or my older Corsair LPX RAM.

I assumed it could have been RAM earlier so switched and the exact same issue happens either way.

Answer 3

Driver verifier slows computer down but should not do this so significantly. This may mean some problem with your drivers.

Please run Windows memory diagnostic tool and switch it to extended mode when it starts (F1 key). Note, test hang at ~21% for more than 2-3 hours means memory error too.

Turn off XMP mode in BIOS if it is turned on.

And if your PC is home assembled, please check your RAM modes (voltage, frequency, timings) are in compliance with numbers in the motherboard compatibility list for your RAM model.

You may share your minidumps to OneDrive, maybe I will see some useful information.

And see the Remark section of https://learn.microsoft.com/en-us/windows-hardw...

Answer 4

Hello, thanks for the response but when I run driver verifier and my system restarts its so slow its unusable.

Like literally opening chrome takes 15 minutes. How can I find out anything using this? Plus I had to reinstall windows last time I used it as I couldn't get rid and made my system unstable. This is not too much of a problem if I am just testing something but as my PC crashes are infrequent and usually while playing a game this isn't gonna help.

Answer 5

Hi,

My name is Igor, it's a pleasure for me to help others and I'll do all my best to help you.

Please use driver verifier to gather additional information.

https://support.microsoft.com/en-us/help/244617...

Run verifier /standard /all /bootmode resetonbootfail command, reboot PC and use it as usual. If blue screen happens please share memory minidumps to OneDrive for analysis.