Question I got a REFERENCE_BY_POINTER BSOD

[JJLopera]

I was on a meet reunion when this BSOD appeared, then I checked my minidump file and got this:
||1:7: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: ffffd60fda8e4070, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 12e3ea2300582255, 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: 1484

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on TW3

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 1479

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 18

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd60fda8e4070

BUGCHECK_P3: 1

BUGCHECK_P4: 12e3ea2300582255

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: chrome.exe

STACK_TEXT:
ffff9984336c56d8 fffff80761c329bc : 0000000000000018 0000000000000000 ffffd60fda8e4070 0000000000000001 : nt!KeBugCheckEx
ffff9984336c56e0 fffff80761a6119e : ffffd60fda8e4070 ffffd60fd7c96d00 ffffd60fd7c96d00 ffff9984336c5770 : nt!ObfDereferenceObjectWithTag+0x1d180c
ffff9984336c5720 fffff80761e476fe : ffffd60f00000001 ffffd60f00000000 ffffd60fd7c96d00 ffffd60fdb129de0 : nt!HalPutDmaAdapter+0xe
ffff9984336c5750 fffff80761e4759d : ffffd60fda8e4070 ffffd60fd7c96d00 ffffd60fdb129de0 ffffe6815f5450b0 : nt!AlpcpDispatchCloseMessage+0x12a
ffff9984336c57b0 fffff80761e468ee : ffffd60fdb129de0 ffff9984336c5939 0000000000000000 ffff9984336c5939 : nt!AlpcpSendCloseMessage+0xe9
ffff9984336c5820 fffff80761e2882c : 0000000000000001 fffff80700000000 ffffffff00000000 ffffffffffffffff : nt!AlpcpClosePort+0x5e
ffff9984336c5850 fffff80761e2c4fc : 0000000000000c40 0000000000000000 0000000000000000 0000000000000000 : nt!ObCloseHandleTableEntry+0x24c
ffff9984336c5990 fffff80761c071b5 : ffffd60fdb951000 ffffd60fda7cda70 ffff9984336c5a80 ffffd60f00000000 : nt!NtClose+0xec
ffff9984336c5a00 00007ffe1d18c194 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000cc80fff368 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe1d18c194 SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+1d180c MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 1d180c FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fa6b3516-71cb-1e92-b987-b8bebd3458ac} Followup: MachineOwner --------- ||1:7: kd> lmvm nt Browse full module list start end module name fffff80761800000 fffff80762846000 nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\3D4400784115718818EFC898413F36C41\ntkrnlmp.pdb Loaded symbol image file: ntkrnlmp.exe Mapped memory image file: C:\ProgramData\Dbg\sym\ntoskrnl.exe\F516CD761046000\ntoskrnl.exe Image path: ntkrnlmp.exe Image name: ntkrnlmp.exe Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: F516CD76 (This is a reproducible build file hash, not a timestamp) CheckSum: 00A5F4B4 ImageSize: 01046000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables: ||1:7: kd> lmvm nt Browse full module list start end module name fffff80761800000 fffff807`62846000 nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\3D4400784115718818EFC898413F36C41\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\ProgramData\Dbg\sym\ntoskrnl.exe\F516CD761046000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: F516CD76 (This is a reproducible build file hash, not a timestamp)
CheckSum: 00A5F4B4
ImageSize: 01046000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:


What conclusion can i get from this?

 

[kerberos_20]

thats a driver issue, nothing conclusive

try this command in kd
!object ffffd60fda8e4070

 

[JJLopera]

When i put that it says "Could not read ObjectType address"
what should i do?

 

[kerberos_20]

When i put that it says "Could not read ObjectType address"
what should i do?

that adress is comming from argument2 in your first post

Arg2: ffffd60fda8e4070, Object whose reference count is being lowered

try upload your dmp here