Error of blue screen

Question

Loading Dump File [C:\Windows\Minidump\071221-8750-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff80551400000 PsLoadedModuleList = 0xfffff8055202a230
Debug session time: Mon Jul 12 12:45:27.374 2021 (UTC + 8:00)
System Uptime: 0 days 9:12:52.166
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805517f6c20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8f897d8174f0=0000000000000018
3: kd> !analyze -v

*
Bugcheck Analysis *
*

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

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 6655

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 18

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9383dc423050

BUGCHECK_P3: 10

BUGCHECK_P4: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

LOCK_ADDRESS: fffff805520449e0 -- (!locks fffff805520449e0)
Cannot get _ERESOURCE type

Resource @ nt!PiEngineLock (0xfffff805520449e0) Available
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff805520449e0
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

STACK_TEXT:
ffff8f897d8174e8 fffff80551814d52 : 0000000000000018 0000000000000000 ffff9383dc423050 0000000000000010 : nt!KeBugCheckEx
ffff8f897d8174f0 fffff80551671946 : ffff9383dc423050 0000000069706e50 0000000000001001 0000000000000fff : nt!ObfReferenceObjectWithTag+0xf5422
ffff8f897d817530 fffff80551a39c3b : 00000000c00000bb ffff8f897d817600 0000000000000054 0000000000000000 : nt!IoGetAttachedDeviceReferenceWithTag+0x36
ffff8f897d817560 fffff80551b50746 : 00000000c00000bb ffff9383c0558c60 ffff8f897d8177a8 ffff9383c0558a70 : nt!IopSynchronousCall+0x3f
ffff8f897d8175d0 fffff80551b50624 : ffff9383c0558c60 ffff8f897d8177a8 ffff9383dba6c380 fffff805519d80ce : nt!PnpIrpQueryID+0x56
ffff8f897d817660 fffff80551b2447d : ffff9383c0558c60 ffff8f897d8177c0 0000000000000000 0000000000000000 : nt!PnpQueryID+0x34
ffff8f897d8176c0 fffff80551b26d40 : ffff9383c0558c60 ffff9383c0558c60 0000000000000001 0000000000000000 : nt!PiProcessNewDeviceNode+0x11d
ffff8f897d817890 fffff80551b215b6 : ffff9383c0558c00 ffff9383eb5a5401 ffff8f897d8179b0 fffff80500000000 : nt!PipProcessDevNodeTree+0x380
ffff8f897d817960 fffff8055176dffa : 0000000100000003 ffff9383c0558c60 0000000000000000 ffff9383eb5a5420 : nt!PiRestartDevice+0xba
ffff8f897d8179b0 fffff80551741225 : ffff9383dba6c380 ffff9383c049fce0 fffff80552043380 fffff80500000000 : nt!PnpDeviceActionWorker+0x46a
ffff8f897d817a70 fffff805516f53b5 : ffff9383dba6c380 0000000000000080 ffff9383c05120c0 000fa4efbd9bbfff : nt!ExpWorkerThread+0x105
ffff8f897d817b10 fffff805517fe278 : fffff8054d7df180 ffff9383dba6c380 fffff805516f5360 0000000000000000 : nt!PspSystemThreadStartup+0x55
ffff8f897d817b60 0000000000000000 : ffff8f897d818000 ffff8f897d811000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nt!ObfReferenceObjectWithTag+f5422

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1052

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: f5422

FAILURE_BUCKET_ID: 0x18_nt!ObfReferenceObjectWithTag

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b6b47bfd-ed1b-fc56-3b01-ddc037f9c59f}

Followup: MachineOwner

This is one of the minidump, can anyone help me to check about the problem and tell me ho to solve it?

Answer

Hi,
Rreference_by_pointer BSoD error (also known as MSDN bugcheck reference_by_pointer 0x00000018). This is a BSOD error that can indicate a driver or software issue.
For the dump information, it refers to ntkrnlmp.exe. This is usually a kernel error with no valid information pointing to the file that might be causing the problem.
Few steps we could try to check:
1.Perform a clean boot and uninstall security software temporarily to check.
https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd
2.Update install your video card driver from the manufacturer's official website to check.
3.Reset BIOS settings.
https://www.wikihow.com/Reset-Your-BIOS
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

Error of blue screen

1 answer