Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041122-7890-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* 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 Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff801`50200000 PsLoadedModuleList = 0xfffff801`50e2a2d0 Debug session time: Mon Apr 11 12:13:34.567 2022 (UTC 8:00) System Uptime: 0 days 0:33:27.429 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................................................... Loading User Symbols Loading unloaded module list ......................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff801`505f7620 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffa902`fbb7a650=0000000000000018 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* REFERENCE_BY_POINTER (18) Arguments: Arg1: 0000000000000000, Object type of the object whose reference count is being lowered Arg2: ffff960509c87050, 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: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4140 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 4200 Key : Analysis.Init.CPU.mSec Value: 280 Key : Analysis.Init.Elapsed.mSec Value: 2554 Key : Analysis.Memory.CommitPeak.Mb Value: 100 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 FILE_IN_CAB: 041122-7890-01.dmp BUGCHECK_CODE: 18 BUGCHECK_P1: 0 BUGCHECK_P2: ffff960509c87050 BUGCHECK_P3: 10 BUGCHECK_P4: 1 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffa902`fbb7a648 fffff801`50615134 : 00000000`00000018 00000000`00000000 ffff9605`09c87050 00000000`00000010 : nt!KeBugCheckEx ffffa902`fbb7a650 fffff801`50471896 : ffff9605`09c87050 00000000`69706e50 ffffca8c`87c00340 ffffca8c`87c01400 : nt!ObfReferenceObjectWithTag 0x17e504 ffffa902`fbb7a690 fffff801`5083b69b : ffff9604`ef207d70 ffffa902`fbb7a7d0 fffff801`50e58740 fffff801`504716fd : nt!IoGetAttachedDeviceReferenceWithTag 0x36 ffffa902`fbb7a6c0 fffff801`50471664 : ffff9604`ef207d70 00000000`00000000 ffffa902`fbb7a860 ffffa902`fbb7a7d0 : nt!IopSynchronousCall 0x3f ffffa902`fbb7a730 fffff801`5092ac59 : 00000000`000000d0 00000000`00000001 ffff9604`ef207d70 fffff801`50932ec3 : nt!PnpSendIrp 0x64 ffffa902`fbb7a7a0 fffff801`50932ab9 : 00000000`00000000 00000000`00000002 00000000`00000002 ffff9604`eee9a5d0 : nt!PnpQueryDeviceRelations 0x51 ffffa902`fbb7a830 fffff801`509326cf : ffffca8c`8ddd5510 ffffca8c`94b7cca0 ffffca8c`00000002 ffffa902`fbb7a938 : nt!PnpProcessRelation 0x105 ffffa902`fbb7a8a0 fffff801`50931e6d : 00000000`00000000 ffffa902`fbb7a959 ffffca8c`9f20df10 00000000`00000002 : nt!PnpBuildRemovalRelationList 0x57 ffffa902`fbb7a8e0 fffff801`5092cd1b : ffffa902`fbb7aa20 ffff9604`eee9a500 ffffa902`fbb7aa00 ffffca8c`00000000 : nt!PnpProcessQueryRemoveAndEject 0xfd ffffa902`fbb7a9c0 fffff801`5084a54e : ffffca8c`9db5a890 ffffca8c`9f20df10 ffff9604`eee87c00 00000000`00000000 : nt!PnpProcessTargetDeviceEvent 0xeb ffffa902`fbb7a9f0 fffff801`504b86d5 : ffff9604`ef1eb040 ffff9604`ef1eb040 ffff9604`eee87c90 ffff9605`0ebf8090 : nt!PnpDeviceEventWorker 0x2ce ffffa902`fbb7aa70 fffff801`50555a15 : ffff9604`ef1eb040 00000000`00000080 ffff9604`eee98040 00000000`00000000 : nt!ExpWorkerThread 0x105 ffffa902`fbb7ab10 fffff801`505fec78 : fffff801`4db0b180 ffff9604`ef1eb040 fffff801`505559c0 00000000`00000000 : nt!PspSystemThreadStartup 0x55 ffffa902`fbb7ab60 00000000`00000000 : ffffa902`fbb7b000 ffffa902`fbb74000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread 0x28 SYMBOL_NAME: nt!ObfReferenceObjectWithTag 17e504 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1586 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 17e504 FAILURE_BUCKET_ID: 0x18_nt!ObfReferenceObjectWithTag OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {b6b47bfd-ed1b-fc56-3b01-ddc037f9c59f} Followup: MachineOwner ---------
HiYourminidumpfilesjustindicatememory(RAM)corruptionnospecificdriverislistedAllyourdevicedriversandBIOSseemtobefullyuptodate.ThebestoptionistodownloadthewidelyavailablefreeutilityMemTest86,thenrunafull4passscanwiththattotestyourRAMforphysicalerrors___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD1人认为此有帮助·此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
HiIamDave,Iwillhelpyouwiththis.PleasechecktoseeifyourPCisproducinganyminidumpfiles,Iwillcheckthosetoseeiftheyprovideanyinsightintoapotentialcauseofthesystemcrashes.PleaseNote,IcannotdownloadfromBaiduCloudDrive,pleaseuseadifferentCloudServicefortheupload.OpenWindowsFileExplorer.NavigatetoC:\Windows\MinidumpCopyanyminidumpfilesontoyourDesktop,thenzipthoseup.UploadthezipfiletotheCloud(OneDrive,DropBox.etc.),thenchoosetosharethoseandgetasharelink.Thenpostthelinkheretothezipfile,sowecantakealookforyou.
thisissharelinkyouwant,thankforyourhelphttps://drive.google.com/file/d/1Ii8wRn20kGIop_O3_dIO52jwqMq2wo4k/view?usp=sharing此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
HiYourminidumpfilesjustindicatememory(RAM)corruptionnospecificdriverislistedAllyourdevicedriversandBIOSseemtobefullyuptodate.ThebestoptionistodownloadthewidelyavailablefreeutilityMemTest86,thenrunafull4passscanwiththattotestyourRAMforphysicalerrors___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD1人认为此有帮助·此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
