F5F Stay Refreshed Hardware Desktop Help requested regarding DPC Watchdog violation #133.

Help requested regarding DPC Watchdog violation #133.

Help requested regarding DPC Watchdog violation #133.

L
Lazy1534
Junior Member
Find
5
03-07-2024, 10:31 AM
#1
Before I get started, here is some info on my system Ryzen 5950z Asrock X570 Taichi (Latest Bios) WD SN850 4 tb (Windows) 4 - 32 GB 3600mhz Patriot Viper (2 2x32 GB kits purchased at the same time) 2 - Crucial MX500 4 TB Evga 3090 FTW3 Seasonic 850W Power Supply (purchased Jan 2019) Multiple HDD (Have HD Sentiental installed and not seeing any errors) 280mm AIO Windows 11 pro (installed Feb 2023) Latest AMD Chipset and Latest Nvidia drivers installed. For the past few weeks, I've been having reboot issues (reboot, a couple of days later reboot again). This would be during non intensive tasks (just a bunch of Google Chrome tabs open and a few spreadsheets) Initially I removed 2 sticks of ram (didn't test at the time) and really no change. About a week ago, the reboot became more frequent, so i decided to run memtest86 on the two sticks I had left in the machine. Having XMP turned off, and mem speed set to 3400mhz and dram voltage set to 1.42v, it threw about 55 errors in the first 10 minutes so. After that, I had stopped it, and decided to try testing with speed set to 360 mhz (XMP turned off) and it run thru the full 4 tests and the memory came back fine. Since it gave the 55 errors, I decided to swap the 2 sticks and put in the other set and try using that. It worked for a while then it decided to reboot. Up to this point, there hasn't been any BSOD, just reboot. When I look at the Event viewer, it shows Event 41 Kernel power and the one item that would always be in the event viewer was File system filter.npsvctrig. Next I decided to use DDU and remove the latest Nvidia driver in safe mode. Once that was completed, I rebooted to regular mode and let Windows install the default Nvidia driver. After a few days, didn't seem to have any issues and decided to try a Nvidia driver from July '23. At this point, I also set the system to capture a full dump (since I wasn't getting any BSOD). At this point, I decide to run memtest86 on both sticks and both passed. At this point it seemed everything was going fine. I decided to try installing the latest Nvidia driver (Usually I select custom and select "clean install" and haven't had any issues. At this point, I started to get BSOD DPC_Watchdog Violation (seems like every 10 minutes or so). What's interesting is that it will show BSOD on 1st screen, but I'll see Windows and the application on the 2nd screen. Yesterday, I pulled out one stick and run memtest86 (XMP turned on, speed set to 3600mhz and dram voltage set to 1.39v). Ran and passed all 4 tests. Rebooted into Windows and left. Came back a few hours later and computer was locked up, but there was no BSOD, nor was there any reboot. I went and bumped up the voltage to 1.43v. I'm hoping someone can't point me to which item is the issue. here is a link to the Mini Dump Here is a link to Memory.dmp I'm in the process of running PerfMon /report, but it's taking longer than 60 seconds (how long does it take to run this?) When I look at BluesceenView, it says A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps: Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need. If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode. Technical Information: *** STOP: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8068331d340, 0x0000000000000000) *** ntoskrnl.exe - Address 0xfffff80682a12740 base at 0xfffff80682600000 DateStamp 0x7d02613e This is what WindDbg shows when I view "memory.dmp" ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true AllowNugetMSCredentialProviderInstall : true 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.125 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36 Microsoft ® Windows Debugger Version 10.0.25921.1001 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Full address space is available Primary dump contents written successfully Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (32 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951 Kernel base = 0xfffff806`82600000 PsLoadedModuleList = 0xfffff806`832130c0 Debug session time: Wed Oct 11 16:21:51.353 2023 (UTC - 7:00) System Uptime: 0 days 3:00:00.000 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................................. Loading User Symbols ................................................................ ............... Loading unloaded module list ............................................................................................ +------------------------------------------------------------------------+ | This target supports Hardware-enforced Stack Protection. A HW based | | "Shadow Stack" may be available to assist in debugging and analysis. | | See aka.ms/userhsp for more info. | | | | dps @ssp | | | +------------------------------------------------------------------------+ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff806`82a12740 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa880`99ceb9f0=0000000000000133 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. Arg2: 0000000000001e00, The watchdog period (in ticks). Arg3: fffff8068331d340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000 Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: TickPeriods *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3484 Key : Analysis.Elapsed.mSec Value: 3889 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 264 Key : Analysis.Init.Elapsed.mSec Value: 8691 Key : Analysis.Memory.CommitPeak.Mb Value: 200 Key : Bugcheck.Code.KiBugCheckData Value: 0x133 Key : Bugcheck.Code.LegacyAPI Value: 0x133 Key : Dump.Attributes.AsUlong Value: 1800 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 100 Key : Failure.Bucket Value: 0x133_ISR_nt!KeAccumulateTicks Key : Failure.Hash Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Key : Hypervisor.Enlightenments.ValueHex Value: 1497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 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: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 4853999 Key : Hypervisor.Flags.ValueHex Value: 4a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 3f7 Key : SecureKernel.HalpHvciEnabled Value: 1 Key : WER.OS.Branch Value: ni_release_svc_prod3 Key : WER.OS.Version Value: 10.0.22621.1928 BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff8068331d340 BUGCHECK_P4: 0 FILE_IN_CAB: MEMORY.DMP TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1800 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: ffffd38bb2546a10 -- (.trap 0xffffd38bb2546a10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=15d95aae93280000 rdx=ffffa88099cd1180 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80682908030 rsp=ffffd38bb2546ba0 rbp=ffffffffffffffff r8=00000000000c00e1 r9=00000000000000e1 r10=0000fffff8068296 r11=ffff987ef2200000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!KiIpiStallOnPacketTargetsPrcb+0x10: fffff806`82908030 8b87802d0000 mov eax,dword ptr [rdi+2D80h] ds:00000000`00002d80=???????? Resetting default scope BLACKBOXBSD: 1 ( !blackboxbsd ) BLACKBOXNTFS: 1 ( !blackboxntfs ) BLACKBOXPNP: 1 ( !blackboxpnp ) BLACKBOXWINLOGON: 1 PROCESS_NAME: WmiPrvSE.exe STACK_TEXT: ffffa880`99ceb9e8 fffff806`82828859 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`8331d340 : nt!KeBugCheckEx ffffa880`99ceb9f0 fffff806`828280c1 : 00002177`d8f61300 ffffa880`99cd1180 00000000`000a8bff 00000000`00000000 : nt!KeAccumulateTicks+0x239 ffffa880`99ceba50 fffff806`828256cf : 00000000`00000020 00000000`00001388 00000000`000a8c00 00000000`00064953 : nt!KiUpdateRunTime+0xd1 ffffa880`99cebc00 fffff806`828262b8 : 00000000`00000000 ffffa880`9ccfb900 ffffa880`99cd1180 00000000`00000000 : nt!KiUpdateTime+0x63f ffffa880`99cebea0 fffff806`82825b7a : fffff806`832600c8 ffffa880`9ccfb970 ffffa880`9ccfb970 00000000`0000000c : nt!KeClockInterruptNotify+0x228 ffffa880`99cebf40 fffff806`828ae6dc : 00000019`25505854 ffff9188`37566e60 ffff9188`37566f10 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a ffffa880`99cebf70 fffff806`82a1489a : ffffd38b`b2546a90 ffff9188`37566e60 ffffa880`99cd1180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c ffffa880`99cebfb0 fffff806`82a15107 : ffffd38b`b2546a90 ffffa880`99cd1180 00000000`00000001 00000000`7efadb9d : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffffd38b`b2546a10 fffff806`82908030 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`828f8880 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffffd38b`b2546ba0 fffff806`82907e45 : 00000000`00000000 fffff806`82941d01 ffffd38b`b2546c28 ffffd38b`b2546c20 : nt!KiIpiStallOnPacketTargetsPrcb+0x10 ffffd38b`b2546bd0 fffff806`82c8589c : 00000000`00000000 ffffd38b`b2547b20 00000000`00000000 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0xd9 ffffd38b`b2546c20 fffff806`82db598a : 00000000`00000000 00000000`00008000 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x17c ffffd38b`b2547230 fffff806`82db4bbd : 00000000`00000801 00000290`29bf1180 00000000`00000000 00000000`00000401 : nt!ExpQuerySystemInformation+0xd6a ffffd38b`b2547a60 fffff806`82a274e8 : ffff9188`665f0000 ffff9188`50cc5080 00000000`00000000 ffff9188`00000000 : nt!NtQuerySystemInformation+0x5d ffffd38b`b2547aa0 00007ffd`bc6cfab4 : 00007ffd`8e417983 00000000`00000000 00007ffd`8e5d56e0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 000000c5`93a7dc08 00007ffd`8e417983 : 00000000`00000000 00007ffd`8e5d56e0 00000000`00000000 00000000`00000000 : ntdll!NtQuerySystemInformation+0x14 000000c5`93a7dc10 00007ffd`8e4231e3 : 00007ffd`8e5d56e0 00007ffd`8e5d56e0 00000000`00000000 00007ffd`b9c83b7f : cimwin32!Process::GetProcessBlocks+0x63 000000c5`93a7dc70 00007ffd`ae21a826 : ffffffff`0222001a 000000c5`93a7e080 00007ffd`8e5d56e0 00000290`29d03380 : cimwin32!Process::Enumerate+0x73 000000c5`93a7df40 00007ffd`ae21a63b : 00000000`00000000 00000000`00000001 00000000`00000000 00007ffd`bb54ae2d : framedynos!Provider::CreateInstanceEnum+0x56 000000c5`93a7df70 00007ff6`3af10067 : 00000290`2dd309c0 00000290`27c6b720 00000290`2dd309b0 00000290`26f13f60 : framedynos!CWbemProviderGlue::CreateInstanceEnumAsync+0x1ab 000000c5`93a7e530 00007ff6`3af0fc25 : 00000000`00000000 000000c5`93a7e630 00000290`2809c970 00007ffd`bb5aed52 : wmiprvse!CInterceptor_IWbemSyncProvider::Helper_CreateInstanceEnumAsync+0x2e7 000000c5`93a7e5c0 00007ffd`bb9f7e23 : 00000290`00000000 00000000`00000005 00000290`280a16f8 00000290`2809c970 : wmiprvse!CInterceptor_IWbemSyncProvider::CreateInstanceEnumAsync+0x165 000000c5`93a7e660 00007ffd`bb9f6bac : 00007ffd`a73a85b2 00000290`26f15300 00000000`00000000 00000290`280a15b0 : RPCRT4!Invoke+0x73 000000c5`93a7e6d0 00007ffd`bb9d1eea : 00000290`26f15300 00000290`26f14cf0 00000290`2dd9f5b0 000000c5`93a7ea00 : RPCRT4!NdrStubCall2Heap+0x3bc 000000c5`93a7e990 00007ffd`bb5b358d : 00000000`00000000 000000c5`93a7eb90 00000290`26f15300 00000000`00000000 : RPCRT4!NdrStubCall2+0x3a 000000c5`93a7e9c0 00007ffd`bb99aba5 : 00000000`00000001 00000290`26f14cf0 00000290`2994cd48 00007ffd`bb52f835 : combase!CStdStubBuffer_Invoke+0xbd [onecore\com\combase\ndr\ndrole\stub.cxx @ 1479] 000000c5`93a7ea00 00007ffd`bb58c0ad : 00000290`2dd9f5b0 00000290`27dddd10 000024d9`a7a48f85 00000000`00000000 : RPCRT4!CStdStubBuffer_Invoke+0x45 000000c5`93a7ea30 00007ffd`bb58be38 : 00000000`26f14b00 000000c5`93a7eb20 000000c5`93a7ead8 00000000`00000000 : combase!ObjectMethodExceptionHandlingAction<<lambda_c9f3956a20c9da92a64affc24fdd69ec> >+0x4d [onecore\com\combase\dcomrem\excepn.hxx @ 94] 000000c5`93a7ea90 00007ffd`bb5b7c81 : 00000000`00000000 00007ffd`a740605f 00000290`26ebadc8 00000290`2994cd20 : combase!DefaultStubInvoke+0x268 [onecore\com\combase\dcomrem\channelb.cxx @ 1218] 000000c5`93a7ebe0 00007ffd`bb58ee67 : 000000c5`93a7ed20 00000290`2dd9f180 00000290`26ebadc8 00000290`2dd9f180 : combase!SyncServerCall::StubInvoke+0x41 [onecore\com\combase\dcomrem\ServerCall.hpp @ 791] 000000c5`93a7ec20 00007ffd`bb5948e9 : 00000000`00000060 00000000`00000000 00000000`00000000 00000290`26f14cf0 : combase!ServerCall::ContextInvoke+0x517 [onecore\com\combase\dcomrem\ctxchnl.cxx @ 1421] 000000c5`93a7ef50 00007ffd`bb590de3 : 00000290`27d3ec10 00000290`26f11ca4 00000290`27c55d30 00000290`27dddd90 : combase!ComInvokeWithLockAndIPID+0x9a9 [onecore\com\combase\dcomrem\channelb.cxx @ 2152] 000000c5`93a7f240 00007ffd`bb997b72 : 00000290`27d3ed60 00000000`00000000 00000000`00000001 00000000`ffffff00 : combase!ThreadInvoke+0x193 [onecore\com\combase\dcomrem\channelb.cxx @ 7040] 000000c5`93a7f300 00007ffd`bb9c2b74 : 000000c5`93a7f540 00007ffd`bc69309e 000000c5`93a7f534 000000c5`93a7f450 : RPCRT4!DispatchToStubInCNoAvrf+0x22 000000c5`93a7f350 00007ffd`bb9c27c8 : 00000290`26f11c50 00000000`00000000 00000000`00000002 00000000`00000000 : RPCRT4!RPC_INTERFACE:Big GrinispatchToStubWorker+0x1b4 000000c5`93a7f430 00007ffd`bb9ce8fc : 00000290`00000000 00000000`00000004 00000290`2e4133a0 00000000`00000000 : RPCRT4!RPC_INTERFACE:Big GrinispatchToStubWithObject+0x188 000000c5`93a7f4d0 00007ffd`bb9cdf76 : 000000c5`00000000 00000000`00000000 00000000`00000000 00000000`000f2fb4 : RPCRT4!LRPC_SCALL:Big GrinispatchRequest+0x14c 000000c5`93a7f5a0 00007ffd`bb9cd523 : 00000000`00000000 00000290`27d93670 00000290`00000001 00000000`00000000 : RPCRT4!LRPC_SCALL::HandleRequest+0x996 000000c5`93a7f6c0 00007ffd`bb9cd17c : 00000000`00000000 00000290`27d936a0 00000000`00000000 00000000`00000003 : RPCRT4!LRPC_SASSOCIATION::HandleRequest+0x2c3 000000c5`93a7f740 00007ffd`bb9ccda9 : 00000290`26ed2840 000000c5`93a7f8e0 00000000`00000001 00000290`27d93670 : RPCRT4!LRPC_ADDRESS::HandleRequest+0x17c 000000c5`93a7f7e0 00007ffd`bb9d0079 : 00000000`00000002 00000290`2940ee20 00000290`26ed2948 000000c5`93a7fb68 : RPCRT4!LRPC_ADDRESS:TonguerocessIO+0x939 000000c5`93a7f930 00007ffd`bc67ee67 : 00000000`00000000 00000000`00000000 00000290`283890b0 000000c5`93a7fb68 : RPCRT4!LrpcIoComplete+0x109 000000c5`93a7f9c0 00007ffd`bc6657ac : 00000290`26ea0c50 00000000`00000000 00000000`00000000 00000290`26ea0c50 : ntdll!TppAlpcpExecuteCallback+0x157 000000c5`93a7fa10 00007ffd`ba99257d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x72c 000000c5`93a7fcf0 00007ffd`bc68aa78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x1d 000000c5`93a7fd20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28 SYMBOL_NAME: nt!KeAccumulateTicks+239 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 239 FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks OS_VERSION: 10.0.22621.1928 BUILDLAB_STR: ni_release_svc_prod3 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Followup: MachineOwner ---------
Reply
Reply
L
Lazy1534
03-07-2024, 10:31 AM #1

Before I get started, here is some info on my system Ryzen 5950z Asrock X570 Taichi (Latest Bios) WD SN850 4 tb (Windows) 4 - 32 GB 3600mhz Patriot Viper (2 2x32 GB kits purchased at the same time) 2 - Crucial MX500 4 TB Evga 3090 FTW3 Seasonic 850W Power Supply (purchased Jan 2019) Multiple HDD (Have HD Sentiental installed and not seeing any errors) 280mm AIO Windows 11 pro (installed Feb 2023) Latest AMD Chipset and Latest Nvidia drivers installed. For the past few weeks, I've been having reboot issues (reboot, a couple of days later reboot again). This would be during non intensive tasks (just a bunch of Google Chrome tabs open and a few spreadsheets) Initially I removed 2 sticks of ram (didn't test at the time) and really no change. About a week ago, the reboot became more frequent, so i decided to run memtest86 on the two sticks I had left in the machine. Having XMP turned off, and mem speed set to 3400mhz and dram voltage set to 1.42v, it threw about 55 errors in the first 10 minutes so. After that, I had stopped it, and decided to try testing with speed set to 360 mhz (XMP turned off) and it run thru the full 4 tests and the memory came back fine. Since it gave the 55 errors, I decided to swap the 2 sticks and put in the other set and try using that. It worked for a while then it decided to reboot. Up to this point, there hasn't been any BSOD, just reboot. When I look at the Event viewer, it shows Event 41 Kernel power and the one item that would always be in the event viewer was File system filter.npsvctrig. Next I decided to use DDU and remove the latest Nvidia driver in safe mode. Once that was completed, I rebooted to regular mode and let Windows install the default Nvidia driver. After a few days, didn't seem to have any issues and decided to try a Nvidia driver from July '23. At this point, I also set the system to capture a full dump (since I wasn't getting any BSOD). At this point, I decide to run memtest86 on both sticks and both passed. At this point it seemed everything was going fine. I decided to try installing the latest Nvidia driver (Usually I select custom and select "clean install" and haven't had any issues. At this point, I started to get BSOD DPC_Watchdog Violation (seems like every 10 minutes or so). What's interesting is that it will show BSOD on 1st screen, but I'll see Windows and the application on the 2nd screen. Yesterday, I pulled out one stick and run memtest86 (XMP turned on, speed set to 3600mhz and dram voltage set to 1.39v). Ran and passed all 4 tests. Rebooted into Windows and left. Came back a few hours later and computer was locked up, but there was no BSOD, nor was there any reboot. I went and bumped up the voltage to 1.43v. I'm hoping someone can't point me to which item is the issue. here is a link to the Mini Dump Here is a link to Memory.dmp I'm in the process of running PerfMon /report, but it's taking longer than 60 seconds (how long does it take to run this?) When I look at BluesceenView, it says A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps: Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need. If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode. Technical Information: *** STOP: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8068331d340, 0x0000000000000000) *** ntoskrnl.exe - Address 0xfffff80682a12740 base at 0xfffff80682600000 DateStamp 0x7d02613e This is what WindDbg shows when I view "memory.dmp" ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true AllowNugetMSCredentialProviderInstall : true 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.125 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36 Microsoft ® Windows Debugger Version 10.0.25921.1001 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Full address space is available Primary dump contents written successfully Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (32 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951 Kernel base = 0xfffff806`82600000 PsLoadedModuleList = 0xfffff806`832130c0 Debug session time: Wed Oct 11 16:21:51.353 2023 (UTC - 7:00) System Uptime: 0 days 3:00:00.000 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................................. Loading User Symbols ................................................................ ............... Loading unloaded module list ............................................................................................ +------------------------------------------------------------------------+ | This target supports Hardware-enforced Stack Protection. A HW based | | "Shadow Stack" may be available to assist in debugging and analysis. | | See aka.ms/userhsp for more info. | | | | dps @ssp | | | +------------------------------------------------------------------------+ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff806`82a12740 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa880`99ceb9f0=0000000000000133 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. Arg2: 0000000000001e00, The watchdog period (in ticks). Arg3: fffff8068331d340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000 Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: TickPeriods *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3484 Key : Analysis.Elapsed.mSec Value: 3889 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 264 Key : Analysis.Init.Elapsed.mSec Value: 8691 Key : Analysis.Memory.CommitPeak.Mb Value: 200 Key : Bugcheck.Code.KiBugCheckData Value: 0x133 Key : Bugcheck.Code.LegacyAPI Value: 0x133 Key : Dump.Attributes.AsUlong Value: 1800 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 100 Key : Failure.Bucket Value: 0x133_ISR_nt!KeAccumulateTicks Key : Failure.Hash Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Key : Hypervisor.Enlightenments.ValueHex Value: 1497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 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: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 4853999 Key : Hypervisor.Flags.ValueHex Value: 4a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 3f7 Key : SecureKernel.HalpHvciEnabled Value: 1 Key : WER.OS.Branch Value: ni_release_svc_prod3 Key : WER.OS.Version Value: 10.0.22621.1928 BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff8068331d340 BUGCHECK_P4: 0 FILE_IN_CAB: MEMORY.DMP TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1800 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: ffffd38bb2546a10 -- (.trap 0xffffd38bb2546a10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=15d95aae93280000 rdx=ffffa88099cd1180 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80682908030 rsp=ffffd38bb2546ba0 rbp=ffffffffffffffff r8=00000000000c00e1 r9=00000000000000e1 r10=0000fffff8068296 r11=ffff987ef2200000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!KiIpiStallOnPacketTargetsPrcb+0x10: fffff806`82908030 8b87802d0000 mov eax,dword ptr [rdi+2D80h] ds:00000000`00002d80=???????? Resetting default scope BLACKBOXBSD: 1 ( !blackboxbsd ) BLACKBOXNTFS: 1 ( !blackboxntfs ) BLACKBOXPNP: 1 ( !blackboxpnp ) BLACKBOXWINLOGON: 1 PROCESS_NAME: WmiPrvSE.exe STACK_TEXT: ffffa880`99ceb9e8 fffff806`82828859 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`8331d340 : nt!KeBugCheckEx ffffa880`99ceb9f0 fffff806`828280c1 : 00002177`d8f61300 ffffa880`99cd1180 00000000`000a8bff 00000000`00000000 : nt!KeAccumulateTicks+0x239 ffffa880`99ceba50 fffff806`828256cf : 00000000`00000020 00000000`00001388 00000000`000a8c00 00000000`00064953 : nt!KiUpdateRunTime+0xd1 ffffa880`99cebc00 fffff806`828262b8 : 00000000`00000000 ffffa880`9ccfb900 ffffa880`99cd1180 00000000`00000000 : nt!KiUpdateTime+0x63f ffffa880`99cebea0 fffff806`82825b7a : fffff806`832600c8 ffffa880`9ccfb970 ffffa880`9ccfb970 00000000`0000000c : nt!KeClockInterruptNotify+0x228 ffffa880`99cebf40 fffff806`828ae6dc : 00000019`25505854 ffff9188`37566e60 ffff9188`37566f10 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a ffffa880`99cebf70 fffff806`82a1489a : ffffd38b`b2546a90 ffff9188`37566e60 ffffa880`99cd1180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c ffffa880`99cebfb0 fffff806`82a15107 : ffffd38b`b2546a90 ffffa880`99cd1180 00000000`00000001 00000000`7efadb9d : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffffd38b`b2546a10 fffff806`82908030 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`828f8880 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffffd38b`b2546ba0 fffff806`82907e45 : 00000000`00000000 fffff806`82941d01 ffffd38b`b2546c28 ffffd38b`b2546c20 : nt!KiIpiStallOnPacketTargetsPrcb+0x10 ffffd38b`b2546bd0 fffff806`82c8589c : 00000000`00000000 ffffd38b`b2547b20 00000000`00000000 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0xd9 ffffd38b`b2546c20 fffff806`82db598a : 00000000`00000000 00000000`00008000 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x17c ffffd38b`b2547230 fffff806`82db4bbd : 00000000`00000801 00000290`29bf1180 00000000`00000000 00000000`00000401 : nt!ExpQuerySystemInformation+0xd6a ffffd38b`b2547a60 fffff806`82a274e8 : ffff9188`665f0000 ffff9188`50cc5080 00000000`00000000 ffff9188`00000000 : nt!NtQuerySystemInformation+0x5d ffffd38b`b2547aa0 00007ffd`bc6cfab4 : 00007ffd`8e417983 00000000`00000000 00007ffd`8e5d56e0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 000000c5`93a7dc08 00007ffd`8e417983 : 00000000`00000000 00007ffd`8e5d56e0 00000000`00000000 00000000`00000000 : ntdll!NtQuerySystemInformation+0x14 000000c5`93a7dc10 00007ffd`8e4231e3 : 00007ffd`8e5d56e0 00007ffd`8e5d56e0 00000000`00000000 00007ffd`b9c83b7f : cimwin32!Process::GetProcessBlocks+0x63 000000c5`93a7dc70 00007ffd`ae21a826 : ffffffff`0222001a 000000c5`93a7e080 00007ffd`8e5d56e0 00000290`29d03380 : cimwin32!Process::Enumerate+0x73 000000c5`93a7df40 00007ffd`ae21a63b : 00000000`00000000 00000000`00000001 00000000`00000000 00007ffd`bb54ae2d : framedynos!Provider::CreateInstanceEnum+0x56 000000c5`93a7df70 00007ff6`3af10067 : 00000290`2dd309c0 00000290`27c6b720 00000290`2dd309b0 00000290`26f13f60 : framedynos!CWbemProviderGlue::CreateInstanceEnumAsync+0x1ab 000000c5`93a7e530 00007ff6`3af0fc25 : 00000000`00000000 000000c5`93a7e630 00000290`2809c970 00007ffd`bb5aed52 : wmiprvse!CInterceptor_IWbemSyncProvider::Helper_CreateInstanceEnumAsync+0x2e7 000000c5`93a7e5c0 00007ffd`bb9f7e23 : 00000290`00000000 00000000`00000005 00000290`280a16f8 00000290`2809c970 : wmiprvse!CInterceptor_IWbemSyncProvider::CreateInstanceEnumAsync+0x165 000000c5`93a7e660 00007ffd`bb9f6bac : 00007ffd`a73a85b2 00000290`26f15300 00000000`00000000 00000290`280a15b0 : RPCRT4!Invoke+0x73 000000c5`93a7e6d0 00007ffd`bb9d1eea : 00000290`26f15300 00000290`26f14cf0 00000290`2dd9f5b0 000000c5`93a7ea00 : RPCRT4!NdrStubCall2Heap+0x3bc 000000c5`93a7e990 00007ffd`bb5b358d : 00000000`00000000 000000c5`93a7eb90 00000290`26f15300 00000000`00000000 : RPCRT4!NdrStubCall2+0x3a 000000c5`93a7e9c0 00007ffd`bb99aba5 : 00000000`00000001 00000290`26f14cf0 00000290`2994cd48 00007ffd`bb52f835 : combase!CStdStubBuffer_Invoke+0xbd [onecore\com\combase\ndr\ndrole\stub.cxx @ 1479] 000000c5`93a7ea00 00007ffd`bb58c0ad : 00000290`2dd9f5b0 00000290`27dddd10 000024d9`a7a48f85 00000000`00000000 : RPCRT4!CStdStubBuffer_Invoke+0x45 000000c5`93a7ea30 00007ffd`bb58be38 : 00000000`26f14b00 000000c5`93a7eb20 000000c5`93a7ead8 00000000`00000000 : combase!ObjectMethodExceptionHandlingAction<<lambda_c9f3956a20c9da92a64affc24fdd69ec> >+0x4d [onecore\com\combase\dcomrem\excepn.hxx @ 94] 000000c5`93a7ea90 00007ffd`bb5b7c81 : 00000000`00000000 00007ffd`a740605f 00000290`26ebadc8 00000290`2994cd20 : combase!DefaultStubInvoke+0x268 [onecore\com\combase\dcomrem\channelb.cxx @ 1218] 000000c5`93a7ebe0 00007ffd`bb58ee67 : 000000c5`93a7ed20 00000290`2dd9f180 00000290`26ebadc8 00000290`2dd9f180 : combase!SyncServerCall::StubInvoke+0x41 [onecore\com\combase\dcomrem\ServerCall.hpp @ 791] 000000c5`93a7ec20 00007ffd`bb5948e9 : 00000000`00000060 00000000`00000000 00000000`00000000 00000290`26f14cf0 : combase!ServerCall::ContextInvoke+0x517 [onecore\com\combase\dcomrem\ctxchnl.cxx @ 1421] 000000c5`93a7ef50 00007ffd`bb590de3 : 00000290`27d3ec10 00000290`26f11ca4 00000290`27c55d30 00000290`27dddd90 : combase!ComInvokeWithLockAndIPID+0x9a9 [onecore\com\combase\dcomrem\channelb.cxx @ 2152] 000000c5`93a7f240 00007ffd`bb997b72 : 00000290`27d3ed60 00000000`00000000 00000000`00000001 00000000`ffffff00 : combase!ThreadInvoke+0x193 [onecore\com\combase\dcomrem\channelb.cxx @ 7040] 000000c5`93a7f300 00007ffd`bb9c2b74 : 000000c5`93a7f540 00007ffd`bc69309e 000000c5`93a7f534 000000c5`93a7f450 : RPCRT4!DispatchToStubInCNoAvrf+0x22 000000c5`93a7f350 00007ffd`bb9c27c8 : 00000290`26f11c50 00000000`00000000 00000000`00000002 00000000`00000000 : RPCRT4!RPC_INTERFACE:Big GrinispatchToStubWorker+0x1b4 000000c5`93a7f430 00007ffd`bb9ce8fc : 00000290`00000000 00000000`00000004 00000290`2e4133a0 00000000`00000000 : RPCRT4!RPC_INTERFACE:Big GrinispatchToStubWithObject+0x188 000000c5`93a7f4d0 00007ffd`bb9cdf76 : 000000c5`00000000 00000000`00000000 00000000`00000000 00000000`000f2fb4 : RPCRT4!LRPC_SCALL:Big GrinispatchRequest+0x14c 000000c5`93a7f5a0 00007ffd`bb9cd523 : 00000000`00000000 00000290`27d93670 00000290`00000001 00000000`00000000 : RPCRT4!LRPC_SCALL::HandleRequest+0x996 000000c5`93a7f6c0 00007ffd`bb9cd17c : 00000000`00000000 00000290`27d936a0 00000000`00000000 00000000`00000003 : RPCRT4!LRPC_SASSOCIATION::HandleRequest+0x2c3 000000c5`93a7f740 00007ffd`bb9ccda9 : 00000290`26ed2840 000000c5`93a7f8e0 00000000`00000001 00000290`27d93670 : RPCRT4!LRPC_ADDRESS::HandleRequest+0x17c 000000c5`93a7f7e0 00007ffd`bb9d0079 : 00000000`00000002 00000290`2940ee20 00000290`26ed2948 000000c5`93a7fb68 : RPCRT4!LRPC_ADDRESS:TonguerocessIO+0x939 000000c5`93a7f930 00007ffd`bc67ee67 : 00000000`00000000 00000000`00000000 00000290`283890b0 000000c5`93a7fb68 : RPCRT4!LrpcIoComplete+0x109 000000c5`93a7f9c0 00007ffd`bc6657ac : 00000290`26ea0c50 00000000`00000000 00000000`00000000 00000290`26ea0c50 : ntdll!TppAlpcpExecuteCallback+0x157 000000c5`93a7fa10 00007ffd`ba99257d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x72c 000000c5`93a7fcf0 00007ffd`bc68aa78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x1d 000000c5`93a7fd20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28 SYMBOL_NAME: nt!KeAccumulateTicks+239 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 239 FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks OS_VERSION: 10.0.22621.1928 BUILDLAB_STR: ni_release_svc_prod3 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Followup: MachineOwner ---------

Reply
Reply
R
Rolan
Junior Member
Find
11
03-07-2024, 10:31 AM
#2
The minidumps offered limited helpful details. The crash itself (the same as the memory.dmp you shared from windbg) complicates determining which driver was responsible. I reviewed the pending and active DPCs in the minidumps to look for overlaps, but nothing stood out except Processor Power Management, which appears in about 85% of these files for this error. The output didn’t reference any drivers, only indicated a DPC check and crash initiation. I’m downloading the kernel dump now, though it’s taking time, so I’ll refer to the output instead. Checking DPCs and pending ones needs additional commands, so I’ll update this post or add a follow-up comment once possible. This appears to be from the stack trace. I recorded everything before examining the stack, and it seems the issue involves .dll files sending commands, not drivers. To clarify, the minidumps don’t list any .dll files—just commands. EDIT: The absence of .dll files compared to drivers is notable because many .dlls can load. I observed that the active process in the kernel dump was WmiPrvSE.exe, the WMI Provider Host. Are you running any WMI-related software? Did you install workplace or school applications? Or is this a managed workstation handled by IT?
Reply
Reply
R
Rolan
03-07-2024, 10:31 AM #2

The minidumps offered limited helpful details. The crash itself (the same as the memory.dmp you shared from windbg) complicates determining which driver was responsible. I reviewed the pending and active DPCs in the minidumps to look for overlaps, but nothing stood out except Processor Power Management, which appears in about 85% of these files for this error. The output didn’t reference any drivers, only indicated a DPC check and crash initiation. I’m downloading the kernel dump now, though it’s taking time, so I’ll refer to the output instead. Checking DPCs and pending ones needs additional commands, so I’ll update this post or add a follow-up comment once possible. This appears to be from the stack trace. I recorded everything before examining the stack, and it seems the issue involves .dll files sending commands, not drivers. To clarify, the minidumps don’t list any .dll files—just commands. EDIT: The absence of .dll files compared to drivers is notable because many .dlls can load. I observed that the active process in the kernel dump was WmiPrvSE.exe, the WMI Provider Host. Are you running any WMI-related software? Did you install workplace or school applications? Or is this a managed workstation handled by IT?

Reply
Reply
Y
yamistar65
Junior Member
Find
4
03-07-2024, 10:31 AM
#3
I've successfully obtained the kernel dump file (it was quite large). The stack trace I discussed earlier doesn't provide much detail. Examining the pending and active DPCs reveals a timeout for the tcpip.sys driver. This is Windows' network driver, working alongside your network card's driver—it isn't a generic card driver. I also notice pending DPCs from vmswitch.sys, which is a network component for virtual machines. I don't interact with VMs myself, but the docs suggest it connects to the actual network, likely enabling VM connectivity. Are you running a virtual machine? Have you experienced crashes while running one? If yes, I'd recommend checking your network card drivers first. It's possible the VM is interfering or using WMI in a way that triggers crashes. Unfortunately, there aren't clear solutions right now, but I hope this gives you a better direction. Feel free to share more files or ask further questions.
Reply
Reply
Y
yamistar65
03-07-2024, 10:31 AM #3

I've successfully obtained the kernel dump file (it was quite large). The stack trace I discussed earlier doesn't provide much detail. Examining the pending and active DPCs reveals a timeout for the tcpip.sys driver. This is Windows' network driver, working alongside your network card's driver—it isn't a generic card driver. I also notice pending DPCs from vmswitch.sys, which is a network component for virtual machines. I don't interact with VMs myself, but the docs suggest it connects to the actual network, likely enabling VM connectivity. Are you running a virtual machine? Have you experienced crashes while running one? If yes, I'd recommend checking your network card drivers first. It's possible the VM is interfering or using WMI in a way that triggers crashes. Unfortunately, there aren't clear solutions right now, but I hope this gives you a better direction. Feel free to share more files or ask further questions.

Reply
Reply
H
hyperdrive57
Member
Find
67
03-07-2024, 10:31 AM
#4
Thank you for your message. I noticed you enabled Hyper-V during installation and set up a VM on Windows 10 or 11. Since I recall seeing "Hypervision" in the memory file, I thought it might be related. Last night you removed Hyper-V from the app list and restarted the system. This morning it appeared unresponsive, showing a time that was 6 hours behind. Before considering your advice, I tried replacing the memory card with another one you bought earlier to check for problems. You also mentioned network drivers—my system has a 2.5 Gbit Ethernet adapter, and I assume the latest driver is installed. In the BIOS you have Ethernet disabled by default.
Reply
Reply
H
hyperdrive57
03-07-2024, 10:31 AM #4

Thank you for your message. I noticed you enabled Hyper-V during installation and set up a VM on Windows 10 or 11. Since I recall seeing "Hypervision" in the memory file, I thought it might be related. Last night you removed Hyper-V from the app list and restarted the system. This morning it appeared unresponsive, showing a time that was 6 hours behind. Before considering your advice, I tried replacing the memory card with another one you bought earlier to check for problems. You also mentioned network drivers—my system has a 2.5 Gbit Ethernet adapter, and I assume the latest driver is installed. In the BIOS you have Ethernet disabled by default.

Reply
Reply
M
miknes123
Senior Member
Find
646
03-07-2024, 10:31 AM
#5
These are DPC_Watchdog_Violation crashes that can be challenging to troubleshoot because Windows sometimes can't identify the exact faulty driver. The best approach is configuring event tracing in Windows, enabling kernel dumps, and then analyzing those dumps with event traces. I haven't set this up before and don't have much experience with debugging dump files. If anyone knows how to do it, it would be helpful. Locating someone with this expertise is difficult. Usually these crashes stem from software issues, so if you're really stuck, formatting and reinstalling Windows might be the easiest solution.
Reply
Reply
M
miknes123
03-07-2024, 10:31 AM #5

These are DPC_Watchdog_Violation crashes that can be challenging to troubleshoot because Windows sometimes can't identify the exact faulty driver. The best approach is configuring event tracing in Windows, enabling kernel dumps, and then analyzing those dumps with event traces. I haven't set this up before and don't have much experience with debugging dump files. If anyone knows how to do it, it would be helpful. Locating someone with this expertise is difficult. Usually these crashes stem from software issues, so if you're really stuck, formatting and reinstalling Windows might be the easiest solution.

Reply
Reply