Computer crashes randomly.

Question

Hi,

I keep having my system crash. Sometimes I get a blue screen and sometimes my mouse cursor just freezes. When that happens I am forced to turn the system off by holding down the power button. I have run a memory tester to make sure I don't have a faulty ram stick and I have also done a reset of my PC, but I am still getting these issues. I will paste a log below that windows created upon one of the latest blue screen crashes, I would love some help to identify the issues with my PC.
************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : false

AllowNugetExeUpdate : false

AllowNugetMSCredentialProviderInstall : false

AllowParallelInitializationOfLocalRepositories : true

-- 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.063 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\liamj\Desktop\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Kernel base = 0xfffff8057cc00000 PsLoadedModuleList = 0xfffff8057d82a770

Debug session time: Wed Feb 21 14:23:32.386 2024 (UTC + 1:00)

System Uptime: 0 days 4:48:27.034

Loading Kernel Symbols

...............................................................

................................................................

.....................Page 19428d not present in the dump file. Type ".hh dbgerr004" for details

..........................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 00000000`0cf04018). Type ".hh dbgerr001" for details

Loading unloaded module list

........

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff8057cffd5b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa40fdd9241d0=000000000000003b

0: kd> !analyze -v

*******************************************************************************

* *

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

Arg3: ffffa40fdd924ad0, Address of the context record for the exception that caused the BugCheck

Arg4: 0000000000000000, zero.

Debugging Details:

---

*** WARNING: Check Image - Checksum mismatch - Dump: 0x6ced5, File: 0x69574 - C:\ProgramData\Dbg\sym\FLTMGR.SYS\BF9EE6586d000\FLTMGR.SYS

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 4218 

Key  : Analysis.Elapsed.mSec 

Value: 5537 

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

Key  : Analysis.Init.Elapsed.mSec 

Value: 5825 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 100 

Key  : Bugcheck.Code.KiBugCheckData 

Value: 0x3b 

Key  : Bugcheck.Code.LegacyAPI 

Value: 0x3b 

Key  : Failure.Bucket 

Value: AV\_FLTMGR!TreeUnlinkMulti 

Key  : Failure.Hash 

Value: {ca6fc98c-5b37-6c44-6983-7e23d46c66bf} 

Key  : Hypervisor.Enlightenments.Value 

Value: 0 

Key  : Hypervisor.Enlightenments.ValueHex 

Value: 0 

Key  : Hypervisor.Flags.AnyHypervisorPresent 

Value: 0 

Key  : Hypervisor.Flags.ApicEnlightened 

Value: 0 

Key  : Hypervisor.Flags.ApicVirtualizationAvailable 

Value: 1 

Key  : Hypervisor.Flags.AsyncMemoryHint 

Value: 0 

Key  : Hypervisor.Flags.CoreSchedulerRequested 

Value: 0 

Key  : Hypervisor.Flags.CpuManager 

Value: 0 

Key  : Hypervisor.Flags.DeprecateAutoEoi 

Value: 0 

Key  : Hypervisor.Flags.DynamicCpuDisabled 

Value: 0 

Key  : Hypervisor.Flags.Epf 

Value: 0 

Key  : Hypervisor.Flags.ExtendedProcessorMasks 

Value: 0 

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

Key  : Hypervisor.Flags.Phase0InitDone 

Value: 0 

Key  : Hypervisor.Flags.PowerSchedulerQos 

Value: 0 

Key  : Hypervisor.Flags.RootScheduler 

Value: 0 

Key  : Hypervisor.Flags.SynicAvailable 

Value: 0 

Key  : Hypervisor.Flags.UseQpcBias 

Value: 0 

Key  : Hypervisor.Flags.Value 

Value: 16908288 

Key  : Hypervisor.Flags.ValueHex 

Value: 1020000 

Key  : Hypervisor.Flags.VpAssistPage 

Value: 0 

Key  : Hypervisor.Flags.VsmAvailable 

Value: 0 

Key  : Hypervisor.RootFlags.AccessStats 

Value: 0 

Key  : Hypervisor.RootFlags.CrashdumpEnlightened 

Value: 0 

Key  : Hypervisor.RootFlags.CreateVirtualProcessor 

Value: 0 

Key  : Hypervisor.RootFlags.DisableHyperthreading 

Value: 0 

Key  : Hypervisor.RootFlags.HostTimelineSync 

Value: 0 

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled 

Value: 0 

Key  : Hypervisor.RootFlags.IsHyperV 

Value: 0 

Key  : Hypervisor.RootFlags.LivedumpEnlightened 

Value: 0 

Key  : Hypervisor.RootFlags.MapDeviceInterrupt 

Value: 0 

Key  : Hypervisor.RootFlags.MceEnlightened 

Value: 0 

Key  : Hypervisor.RootFlags.Nested 

Value: 0 

Key  : Hypervisor.RootFlags.StartLogicalProcessor 

Value: 0 

Key  : Hypervisor.RootFlags.Value 

Value: 0 

Key  : Hypervisor.RootFlags.ValueHex 

Value: 0 

Key  : SecureKernel.HalpHvciEnabled 

Value: 0 

Key  : WER.OS.Branch 

Value: vb\_release 

Key  : WER.OS.Version 

Value: 10.0.19041.1 

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80579488b0b

BUGCHECK_P3: ffffa40fdd924ad0

BUGCHECK_P4: 0

FILE_IN_CAB: MEMORY.DMP

CONTEXT: ffffa40fdd924ad0 -- (.cxr 0xffffa40fdd924ad0)

rax=0000100000000000 rbx=0000000000000000 rcx=ffff94048cab1120

rdx=ffff94048f584ca0 rsi=ffff94048f584ca0 rdi=0000100000000000

rip=fffff80579488b0b rsp=ffffa40fdd9254d0 rbp=ffffa40fdd925649

r8=ffffffffffffffff r9=7fff94048cab1108 r10=fffff8057ce45370

r11=ffffbf89bbfece80 r12=00000000ffff7fff r13=0000000000008000

r14=ffff94048cab1120 r15=ffff94047fa54710

iopl=0 nv up ei pl nz na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206

FLTMGR!TreeUnlinkMulti+0x4b:

fffff80579488b0b 483b7020 cmp rsi,qword ptr [rax+20h] ds:002b:0000100000000020=????????????????

Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

PROCESS_NAME: Discord.exe

STACK_TEXT:

ffffa40fdd9254d0 fffff805794ba7b7 : ffff94048cab10a0 ffff940400000000 ffffa40f00000000 ffff94047fa540a0 : FLTMGR!TreeUnlinkMulti+0x4b

ffffa40fdd925520 fffff805794869fe : ffff94049313e010 ffff94048f584ca0 ffffa40fdd925649 0000000000000000 : FLTMGR!FltpRemoveAllNamesCachedForFileObject+0xb7

ffffa40fdd925590 fffff80579485f7a : ffffa40fdd925700 ffffa40fdd925502 ffff94048f584c00 0000000000000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x89e

ffffa40fdd9256b0 fffff80579485021 : ffffa40fdd926000 ffffa40fdd920000 ffff94049329d9b0 ffffa40fdd9257c0 : FLTMGR!FltpPassThroughInternal+0xca

ffffa40fdd925700 fffff80579484a2b : fffffffffffe7960 0000000000000000 0000000000000001 0000000000000000 : FLTMGR!FltpPassThrough+0x541

ffffa40fdd925790 fffff8057ce35cf5 : ffff94048f584ca0 fffff8057ce346f8 ffff94047f9ca180 0000000000000000 : FLTMGR!FltpDispatch+0x8b

ffffa40fdd9257f0 fffff8057d2420df : ffff94048f584ca0 ffff94047f9ca180 ffff94047a348900 ffff94047a348900 : nt!IofCallDriver+0x55

ffffa40fdd925830 fffff8057d245880 : ffff94047a348980 0000000000000001 ffff94048f584c70 ffff94049329d9b0 : nt!IopDeleteFile+0x14f

ffffa40fdd9258b0 fffff8057ce45c07 : 0000000000000000 0000000000000000 ffffa40fdd925a39 ffff94048f584ca0 : nt!ObpRemoveObjectRoutine+0x80

ffffa40fdd925910 fffff8057d24b0e9 : ffff94048f584c70 0000000000000000 ffffbf8900000000 ffff94048f584c70 : nt!ObfDereferenceObjectWithTag+0xc7

ffffa40fdd925950 fffff8057d245e2c : 000000000000076c 0000000000000000 0000000000000000 000000001141f470 : nt!ObCloseHandleTableEntry+0x6c9

ffffa40fdd925a90 fffff8057d011138 : ffff94048ce87000 ffff94048ed48080 ffffa40fdd925b80 ffff940400000000 : nt!NtClose+0xec

ffffa40fdd925b00 0000000076e91cfc : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28

000000001131efb8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x76e91cfc

SYMBOL_NAME: FLTMGR!TreeUnlinkMulti+4b

MODULE_NAME: FLTMGR

IMAGE_NAME: FLTMGR.SYS

STACK_COMMAND: .cxr 0xffffa40fdd924ad0 ; kb

BUCKET_ID_FUNC_OFFSET: 4b

FAILURE_BUCKET_ID: AV_FLTMGR!TreeUnlinkMulti

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ca6fc98c-5b37-6c44-6983-7e23d46c66bf}

Followup: MachineOwner

---

Answer 1

Hi

Thanks for your reply.

Thank you for sharing your log files. I've reviewed it carefully and identified the following issues: You can try disabling or uninstalling the corresponding software to see if the problem disappears.

Amdfendr.sys are system files associated with AMD Endpoint Security, a security solution provided by AMD to protect endpoints from various cyber threats. This file manages the security features of the AMD Endpoint Security software. It is essential to the proper functioning of the security solution and must not be tampered with or deleted. If you have any issues with this file, we recommend that you contact AMD Support for assistance.

RzCommon.sys file is the driver file associated with the Razer Common Modules. Razer is a popular gaming hardware manufacturer known for its gaming mice, keyboards, and other peripherals. RzCommon.sys file is typically installed when you install Razer Synapse, the software used to manage your Razer device and customize its settings.

Rzdev_0528.sys file is also the driver file associated with your Razer device. It may be a specific driver for a specific Razer device or component. If you experience any issues related to this file, you may need to update your Razer device drivers or reinstall the Razer Synapse software.

Answer 2

Hi,

Thanks you for the hasty response.

I uploaded the three Mini dumps I could find in the folder onto google drive.

https://drive.google.com/drive/folders/1cVdFyiEabtkAmm60bYlyv6PU3j2Z0tut?usp=sharing Thanks!

Br,
Liam

Answer 3

Hi

Welcome to the Microsoft community.

Based on the logs you've provided, it appears that your compatibility conflict blue screen issue is caused by Discord. To better assess your problem, would the issue reoccur if you do not use Discord or uninstall it?

We need you to provide the blue screen log (minidump) to analyze your problem further. Finally, upload the file to a suitable network drive and send the sharing link in the reply. Please make sure to set the sharing link as public and without the need for login or permission.

To find the minidump file in Windows, you can follow these steps:

Open File Explorer by pressing the Windows key + E.

Navigate to the following location: C:\Windows\Minidump (replace C with the drive where Windows is installed if it is different).

If you cannot find the Minidump folder at the specified location, it might be hidden. To show hidden files and folders, click on the "View" tab in the File Explorer, and check the "Hidden items" option.

If the Minidump folder is still not present, it might be because your system is not configured to create Minidump files. To enable this feature, follow these steps:

Press the Windows key + X and select "System".

Click on "Advanced system settings" on the left-hand side.

In the System Properties window, go to the "Advanced" tab and click on the "Settings" button under the "Startup and Recovery" section.

In the Startup and Recovery window, make sure that the "Write debugging information" drop-down menu is set to "Small memory dump (256 KB)" or "Kernel memory dump".

Click "OK" to save the changes.

Restart your computer for the changes to take effect.

Once you have located the Minidump folder, you will find the Minidump files inside it. These files have the .dmp extension and are named with a combination of date and time.

Note: Minidump files are created when your system encounters a blue screen of death (BSOD) or a crash. If you have not experienced any crashes, the Minidump folder may be empty.

Please feel free to let me know if you have any further updates, thanks.

Best regards

Derrick Qian | Microsoft Community Support Specialist