BSOD Windows 10 Windbg not telling me much

malloy993

malloy993

Well-known member
Joined
Sep 12, 2023
Posts
58
Please HELP!

I have a windows 10 device that continually crashes. I have tried to analyze the .DMP file sent to me up but isn't giving me much. What else can I do on the system to try to fix this? I have uploaded the .DMP file here. Bug check analysis below.

DMP FIle upload: https://tinyurl.com/Mini-dump-file

Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PDC_UNEXPECTED_REVOCATION_LIVEDUMP (17d)
An activator has been revoked unexpectedly
(This code can never be used for a real BugCheck; it is used to identify live dumps.)
Arguments:
Arg1: 0000000000000065, The client ID of the revoked activator.
Arg2: ffffe60d357e4b20, The revoked activator client.
Arg3: ffffe60d353579f0, The revoked activation instance.
Arg4: ffff8b0dae8b1530, pdc!_PDC_CLIENT_PROCESS_INFO

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1374

    Key  : Analysis.Elapsed.mSec
    Value: 2005

    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: 265

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x0

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x17d

    Key  : Dump.Attributes.AsUlong
    Value: 10

    Key  : Failure.Bucket
    Value: LKD_0x17D_0x65_pdc!PdcpRevocationLiveDump

    Key  : Failure.Hash
    Value: {69e68e14-f0ca-1a9b-94e0-96617704d912}

    Key  : Hypervisor.Enlightenments.Value
    Value: 8992

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 2320

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 1

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 536584

    Key  : Hypervisor.Flags.ValueHex
    Value: 83008

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0

    Key  : WER.OS.Branch
    Value: rs5_release

    Key  : WER.OS.Version
    Value: 10.0.17763.1


BUGCHECK_CODE:  17d

BUGCHECK_P1: 65

BUGCHECK_P2: ffffe60d357e4b20

BUGCHECK_P3: ffffe60d353579f0

BUGCHECK_P4: ffff8b0dae8b1530

FILE_IN_CAB:  dump.dmp

VIRTUAL_MACHINE:  VMware

DUMP_FILE_ATTRIBUTES: 0x10
  Live Generated Dump

PROCESS_NAME:  System

STACK_TEXT: 
ffff8b0d`ae8b0fd0 fffff801`5ad73452     : ffffffff`ffffffff 00000000`00000011 00000000`00000000 00000000`00000011 : nt!IopLiveDumpEndMirroringCallback+0x7e
ffff8b0d`ae8b1020 fffff801`5ad7f587     : 00000000`00000000 fffff801`00000000 ffffe60d`00000001 00000000`00000001 : nt!MmDuplicateMemory+0x26e
ffff8b0d`ae8b10b0 fffff801`5b026ead     : ffffe60d`49221d40 ffffe60d`49221d40 ffff8b0d`ae8b1378 ffff8b0d`ae8b1378 : nt!IopLiveDumpCaptureMemoryPages+0x7f
ffff8b0d`ae8b1170 fffff801`5b01a542     : 00000000`00000000 ffffc18b`58424e10 ffffc18b`8424c710 ffffc18b`58424e10 : nt!IoCaptureLiveDump+0x289
ffff8b0d`ae8b1310 fffff801`5b01ac60     : ffffffff`8000286c 00000000`00000000 00000000`00000000 00000000`0000017d : nt!DbgkpWerCaptureLiveFullDump+0x13a
ffff8b0d`ae8b1370 fffff801`5b01a391     : 00000000`00000002 00000000`00000000 fffff80a`05947038 ffff2c1d`d598c09a : nt!DbgkpWerProcessPolicyResult+0x30
ffff8b0d`ae8b13a0 fffff80a`05958821     : ffffe60d`357e4b20 ffff8b0d`ae8b1530 ffffe60d`353579f0 ffffe60d`35357900 : nt!DbgkWerCaptureLiveKernelDump+0x1a1
ffff8b0d`ae8b13f0 fffff80a`05958724     : fffff801`5ad63200 ffffe60d`00000000 00000000`00000000 ffffe60d`3e096191 : pdc!PdcpRevocationLiveDump+0xc1
ffff8b0d`ae8b14a0 fffff801`5a8b94ca     : ffffe60d`2fc60000 00000000`00000000 fffff80a`056a8400 ffffe60d`429c5780 : pdc!PdcpRevocationWorker+0x154
ffff8b0d`ae8b1530 fffff801`5a93b1e5     : ffffe60d`429c5780 ffffe60d`2fc78080 ffffe60d`429c5780 00000000`00000000 : nt!ExpWorkerThread+0x16a
ffff8b0d`ae8b15d0 fffff801`5a9c9d6c     : ffff9201`403b9180 ffffe60d`429c5780 fffff801`5a93b190 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff8b0d`ae8b1620 00000000`00000000     : ffff8b0d`ae8b2000 ffff8b0d`ae8ab000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c


SYMBOL_NAME:  pdc!PdcpRevocationLiveDump+c1

MODULE_NAME: pdc

IMAGE_NAME:  pdc.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  c1

FAILURE_BUCKET_ID:  LKD_0x17D_0x65_pdc!PdcpRevocationLiveDump

OS_VERSION:  10.0.17763.1

BUILDLAB_STR:  rs5_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {69e68e14-f0ca-1a9b-94e0-96617704d912}

Followup:     MachineOwner


Thank you,

Malloy993
 
Last edited by a moderator:
I've not downloaded that kernel dump yet (it's quite large), but I suspect this live kernel event (which is a problem from which Windows managed to recover) is related to a conflict between Modern Standby and VMWare on which you're running this guest.

Activators are registered Windows components that are allowed to keep the system partially active when it's in standby. This is all part of the complex low power states that Modern Standby provides. I don't pretend to know much more than that about how activators work, but since this a VM guest OS I think that a conflict between the VM host and Modern Standby in the guest Windows system is the most likely cause.
 
It's not an area in which I have any experience. Is this causing you problems? Is it important for the Windows guest to go into sleep?
 
Last edited:
I would suggest checking your event logs for any issues with your BITS service since that appears to be the activator which was revoked for some reason. Unfortunately, you aren't going to find much information about this bugcheck because most of it is undocumented, I suspect that Microsoft only share the details with hardware manufacturers.
 
Hello,

What makes you say it has something to do with the BITS Service?

Thank you,

Malloy993
 
Since it's a VM, I'd try to disable each and every power setting which allows anything between a full shutdown and a fully running system. No fast startup, no hibernation, no sleep mode.

I'm no expert in analysing dump files, but I have quite some experience with Virtual machines (Hyper-V and VMWare). Like ubuysa mentioned, VMs often don't play nicely with all the modern standby stuff and usually they don't need it either.

​

 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top