Hallo,
ich habe immer mal wieder, in völlig unerklärlichen Abständen mit Bluescreens zu kämpfen.
Habe schon 1-2 Hardware Dinge (Board, Netzteil) ausgetauscht, bisher erfolglos.
Ein RAM-Test hat angeblich gezeigt, dass alles ok ist.
Bin jetzt über den WinDbg gestolpert, der hat mir zum letzten Crash folgnendes ausgeworfen - leider kann ich damit nicht wirklich was anfangen... Kann mir da jemand helfen?
---------
ich habe immer mal wieder, in völlig unerklärlichen Abständen mit Bluescreens zu kämpfen.
Habe schon 1-2 Hardware Dinge (Board, Netzteil) ausgetauscht, bisher erfolglos.
Ein RAM-Test hat angeblich gezeigt, dass alles ok ist.
Bin jetzt über den WinDbg gestolpert, der hat mir zum letzten Crash folgnendes ausgeworfen - leider kann ich damit nicht wirklich was anfangen... Kann mir da jemand helfen?
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff802`2fa00000 PsLoadedModuleList = 0xfffff802`3062a790
Debug session time: Fri Apr 26 12:33:52.096 2024 (UTC + 2:00)
System Uptime: 10 days 21:48:33.835
Loading Kernel Symbols
...............................................................
......Page 700c9b not present in the dump file. Type ".hh dbgerr004" for details
...............Page 368dd1 not present in the dump file. Type ".hh dbgerr004" for details
...........................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`2fdfda40 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffed89`5d9717e0=000000000000007e
7: kd> !analyze -v
*******************************************************************************
*******************************************************************************
- *
- Bugcheck Analysis *
- *
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8022fcb6cf3, The address that the exception occurred at
Arg3: ffffed895d9727d8, Exception Record Address
Arg4: ffffed895d972010, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 3483
Key : Analysis.Elapsed.mSec
Value: 13914
Key : Analysis.IO.Other.Mb
Value: 13
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 35
Key : Analysis.Init.CPU.mSec
Value: 1124
Key : Analysis.Init.Elapsed.mSec
Value: 42019
Key : Analysis.Memory.CommitPeak.Mb
Value: 110
Key : Bugcheck.Code.KiBugCheckData
Value: 0x7e
Key : Bugcheck.Code.LegacyAPI
Value: 0x7e
Key : Bugcheck.Code.TargetModel
Value: 0x7e
Key : Failure.Bucket
Value: AV_pdc!PdcPowerRequestBlockingCallback
Key : Failure.Hash
Value: {8a7020cf-d8d0-07c5-2974-2fe6456934b2}
Key : Hypervisor.Enlightenments.Value
Value: 0
Key : Hypervisor.Enlightenments.ValueHex
Value: 0
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
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: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0
Key : Hypervisor.Flags.Phase0InitDone
Value: 0
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: 16908288
Key : Hypervisor.Flags.ValueHex
Value: 1020000
Key : Hypervisor.Flags.VpAssistPage
Value: 0
Key : Hypervisor.Flags.VsmAvailable
Value: 0
Key : Hypervisor.RootFlags.AccessStats
Value: 0
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 0
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0
Key : Hypervisor.RootFlags.MceEnlightened
Value: 0
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0
Key : Hypervisor.RootFlags.Value
Value: 0
Key : Hypervisor.RootFlags.ValueHex
Value: 0
Key : SecureKernel.HalpHvciEnabled
Value: 0
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8022fcb6cf3
BUGCHECK_P3: ffffed895d9727d8
BUGCHECK_P4: ffffed895d972010
FILE_IN_CAB: MEMORY.DMP
EXCEPTION_RECORD: ffffed895d9727d8 -- (.exr 0xffffed895d9727d8)
ExceptionAddress: fffff8022fcb6cf3 (nt!PopInternalUpdateStopWatchState+0x0000000000000037)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffed895d972010 -- (.cxr 0xffffed895d972010)
rax=004000013ee804f1 rbx=fffff80232f6d401 rcx=ffffba8a8e7a6168
rdx=0000000000000000 rsi=ffffa68f670eea60 rdi=fffff80232f6d500
rip=fffff8022fcb6cf3 rsp=ffffed895d972a18 rbp=fffff80232f86340
r8=00000060eda72d00 r9=ffffba8a8e7a6168 r10=fffff8023061ec20
r11=ffffba8a8e7a6170 r12=0000000000000500 r13=0000000000000000
r14=fffff80232f6d508 r15=fffff80230725440
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!PopInternalUpdateStopWatchState+0x37:
fffff802`2fcb6cf3 4883781000 cmp qword ptr [rax+10h],0 ds:002b:00400001`3ee80501=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
READ_ADDRESS: unable to get nt!PspSessionIdBitmap
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffffed89`5d972a18 fffff802`2fcb6e8d : ffffed89`5d9729c4 00000000`00000004 ffff6991`233c1bd0 ffffa68f`670eea60 : nt!PopInternalUpdateStopWatchState+0x37
ffffed89`5d972a20 fffff802`30071725 : ffffed89`5d972ab8 00000000`00000004 ffffed89`5d972ac0 00000000`00000004 : nt!PoUnarmStopWatchCollection+0x4d
ffffed89`5d972a50 fffff802`32f61bd0 : fffff802`32f88294 fffff802`32f84856 000003e2`850b249d fffff802`32f8646f : nt!PdcPoPowerRequestBlockingCallback+0x75
ffffed89`5d972a80 fffff802`32f85c2c : 00000000`00000001 00000000`00000002 fffff802`00000000 fffff802`32f6d510 : pdc!PdcPowerRequestBlockingCallback+0x10
ffffed89`5d972ab0 fffff802`32f85cc1 : fffff802`32f6d468 fffff802`32f86340 ffffa68f`670eea60 000003e2`850b249d : pdc!PdcpGroupBlockingConditionsChanged+0x54
ffffed89`5d972ae0 fffff802`32f85cee : 00000000`00000000 fffff802`306248a0 00000000`30725440 00000000`00000500 : pdc!PdcpSetGroupReferenceCountDelta+0x3d
ffffed89`5d972b10 fffff802`32f8635d : fffff802`30725440 fffff802`306248f0 00000000`00000000 00000000`00000500 : pdc!PdcpSetGroupReferenceCountDeltaWorker+0x1e
ffffed89`5d972b40 fffff802`2fcc3ea5 : ffffa68f`a3bad040 fffff802`3007bbc0 ffffa68f`670eea60 00000000`00000000 : pdc!PdcpSimpleWorkItemCallback+0x1d
ffffed89`5d972b70 fffff802`2fd4ef55 : ffffa68f`a3bad040 00000000`00000080 ffffa68f`67087040 ffffa659`494a3700 : nt!ExpWorkerThread+0x105
ffffed89`5d972c10 fffff802`2fe06a48 : ffff9181`dcd80180 ffffa68f`a3bad040 fffff802`2fd4ef00 ffffed89`5d972ec0 : nt!PspSystemThreadStartup+0x55
ffffed89`5d972c60 00000000`00000000 : ffffed89`5d973000 ffffed89`5d96d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: pdc!PdcPowerRequestBlockingCallback+10
MODULE_NAME: pdc
IMAGE_NAME: pdc.sys
STACK_COMMAND: .cxr 0xffffed895d972010 ; kb
BUCKET_ID_FUNC_OFFSET: 10
FAILURE_BUCKET_ID: AV_pdc!PdcPowerRequestBlockingCallback
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8a7020cf-d8d0-07c5-2974-2fe6456934b2}
Followup: MachineOwner
---------