Question Please Analyse This BSOD. Help me figure out what caused this. I have text file from Windows Debugger.

[Only a noob]

System specs: windows 11 from 10, 12700k, 3090, cl14-3600 4 x 16gb dominator, msi pro z690 wifi ddr 4, watercooled

Guys here is the report that was produced:

Spoiler

Microsoft (R) Windows Debugger Version 10.0.22621.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Dump completed successfully, progress percentage: 100


Path validation summary *
Response Time (ms) Location
Deferred SRVC:\Windows\symbol_cache

Symbol information

Symbol search path is: SRVC:\Windows\symbol_cache

Symbol information

Executable search path is:
Windows 10 Kernel Version 22000 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff80368c00000 PsLoadedModuleList = 0xfffff80369829650
Debug session time: Fri Jul 8 19:35:51.193 2022 (UTC - 7:00)
System Uptime: 0 days 1:12:04.824
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000001d129df018). Type ".hh dbgerr001" for details Loading unloaded module list ......... For analysis of this file, run !analyze -v 10: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* REFERENCE_BY_POINTER (18) Arguments: Arg1: ffff97879d5d6da0, Object type of the object whose reference count is being lowered Arg2: ffff9787bba0ea30, Object whose reference count is being lowered Arg3: 0000000000000001, Reserved Arg4: ffffffffffffffff, Reserved The reference count of an object is illegal for the current state of the object. Each time a driver uses a pointer to an object the driver calls a kernel routine to increment the reference count of the object. When the driver is done with the pointer the driver calls another kernel routine to decrement the reference count. Drivers must match calls to the increment and decrement routines. This BugCheck can occur because an object's reference count goes to zero while there are still open handles to the object, in which case the fourth parameter indicates the number of opened handles. It may also occur when the object's reference count drops below zero whether or not there are open handles to the object, and in that case the fourth parameter contains the actual value of the pointer references count. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1202 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1156 Key : Analysis.Init.CPU.mSec Value: 4515 Key : Analysis.Init.Elapsed.mSec Value: 183449 Key : Analysis.Memory.CommitPeak.Mb Value: 149 Key : WER.OS.Branch Value: co_release Key : WER.OS.Timestamp Value: 2021-06-04T16:28:00Z Key : WER.OS.Version Value: 10.0.22000.1 FILE_IN_CAB: MEMORY.DMP DUMP_FILE_ATTRIBUTES: 0x1000 BUGCHECK_CODE: 18 BUGCHECK_P1: ffff97879d5d6da0 BUGCHECK_P2: ffff9787bba0ea30 BUGCHECK_P3: 1 BUGCHECK_P4: ffffffffffffffff BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: dwm.exe STACK_TEXT: ffffb982ea3a6888 fffff803690741ce : 0000000000000018 ffff97879d5d6da0 ffff9787bba0ea30 0000000000000001 : nt!KeBugCheckEx ffffb982ea3a6890 fffff8036927da0d : 0000000000000000 ffff9787bba0ea00 ffff9787bba0ea00 ffff978700000001 : nt!ObfDereferenceObjectWithTag+0x22050e ffffb982ea3a68d0 fffff8036927c1d9 : 0000000000000000 00000173f8c5e490 00000000000012a0 0000000000000000 : nt!ObpCloseHandle+0x2dd ffffb982ea3a69f0 fffff80369029b75 : ffff9787ad369080 ffff9787ad7a3ce0 ffffb98200000000 ffff978700000000 : nt!NtClose+0x39 ffffb982ea3a6a20 00007ff839dc40f4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 0000001d127bf3a8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff839dc40f4


SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+22050e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 22050e

FAILURE_BUCKET_ID: 0x18_OVER_DEREFERENCE_nt!ObfDereferenceObjectWithTag

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4139309c-4e9f-52f0-ac5e-4041e7a86a20}

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

 

[Colif]

one clue is the victim. Its Desktop WIndows Manager. It sits between Applications & GPU drivers

run ddu in safe mode, uninstall Nvidia drivers, and when back in normal mode reinstall Nvidia drivers

How To - How to perform a CLEAN install of your video card drivers.

Updated 9-19-19 How to do a CLEAN install of your graphics card drivers using the Wagnard tools Display Driver Uninstaller A major issue on many systems is the presence of multiple graphics card drivers or drivers that have been incompletely uninstalled followed by the installation of...

forums.tomshardware.com

In case it continues,
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

 

[johnbl]

you actually need to put the minidump file on a cloud server, share the file for public access and post a link.