Plötzlicher Bluescreen

Question

Windows ist nicht mehr funktionsfähig:

Beschreibung

Der Computer wurde nach einem schwerwiegenden Fehler neu gestartet. Der Fehlercode war: 0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff8026e91c340). Ein volles Abbild wurde gespeichert in: C:\Windows\Minidump\090324-11546-01.dmp. Berichts-ID: 44a1d6b6-5a8d-4f1e-9b69-4100da5e60d0.

Warum tritt dieser Fehler plötzlich auf?

Dmp file: "************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- 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.015 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 42 Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\090324-11546-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 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff8026dc00000 PsLoadedModuleList = 0xfffff8026e813510 Debug session time: Tue Sep 3 23:59:31.077 2024 (UTC + 2:00) System Uptime: 0 days 4:06:56.812 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............ Loading User Symbols Loading unloaded module list ................................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8026e015fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff8026c22f9f0=0000000000000133 0: 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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: fffff8026e91c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeout 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.Elapsed.mSec Value: 5264 Key : Analysis.IO.Other.Mb Value: 6 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 16 Key : Analysis.Init.CPU.mSec Value: 15 Key : Analysis.Init.Elapsed.mSec Value: 135259 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : Bugcheck.Code.LegacyAPI Value: 0x133 Key : Bugcheck.Code.TargetModel Value: 0x133 Key : Dump.Attributes.AsUlong Value: 1808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: 0x133_DPC_afd!AfdCompletePollIrp Key : Failure.Hash Value: {ef73738c-d5c3-cdde-e832-877bfe61e63d} Key : Hypervisor.Enlightenments.ValueHex Value: 1417df84 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 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: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 1 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: 21631230 Key : Hypervisor.Flags.ValueHex Value: 14a10fe 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 BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8026e91c340 FILE_IN_CAB: 090324-11546-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump FAULTING_THREAD: fffff8026e94c700 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff8026c22f9e8 fffff8026de2f6e5 : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx fffff8026c22f9f0 fffff8026de2edb1 : 00003323d89e5b08 00000000000e7834 00000000000e7833 0000000000000000 : nt!KeAccumulateTicks+0x3d5 fffff8026c22fa50 fffff8026de2c3bf : 0000000000000010 0000000000001388 00000000000e7800 0000000000089fe0 : nt!KiUpdateRunTime+0xd1 fffff8026c22fc00 fffff8026de2cfa8 : 0000000000000000 ffff9280ebfb0a00 fffff8026a8df180 0000000000000000 : nt!KiUpdateTime+0x63f fffff8026c22fea0 fffff8026de2c86a : fffff8026e85fe38 ffff9280ebfb0ab0 ffff9280ebfb0ab0 0000000000000002 : nt!KeClockInterruptNotify+0x228 fffff8026c22ff40 fffff8026deb76bc : 000000227f854171 fffff8026e90d470 fffff8026e90d520 fffff8026e017f4b : nt!HalpTimerClockInterrupt+0x10a fffff8026c22ff70 fffff8026e0181aa : fffff8026c220490 fffff8026e90d470 ffffcf8752672658 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x9c fffff8026c22ffb0 fffff8026e018a77 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff8026c220410 fffff8026de4f7ec : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff8026c2205a0 fffff8026de7be3e : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxWaitForSpinLockAndAcquire+0x1c fffff8026c2205d0 fffff8026de7b2a7 : ffffcf875a2bb5e0 0000000000000002 ffffcf875341b9b0 0000000000000000 : nt!IopfCompleteRequest+0xb7e fffff8026c2206b0 fffff80287e16299 : 0000000000000000 ffffcf875a2bb5e0 ffffcf87459ff0a0 0000000000000000 : nt!IofCompleteRequest+0x17 fffff8026c2206e0 fffff80287e157be : 0000000000000004 fffff8026a8df180 ffffcf875a615470 fffff8026c220829 : afd!AfdCompletePollIrp+0x95 fffff8026c220730 fffff8026de5194b : ffffcf8700000004 ffffcf8700000001 fffff80200000000 0000000000000002 : afd!AfdTimeoutPoll+0x2e fffff8026c220760 fffff8026de52cd9 : 0000000000000000 0000000000000000 0000000000000000 fffff8026a8e6ec8 : nt!KiProcessExpiredTimerList+0x1eb fffff8026c220890 fffff8026e01afae : 0000000000000000 fffff8026a8df180 fffff8026e94c700 ffffcf8750111080 : nt!KiRetireDpcList+0xaf9 fffff8026c220b40 0000000000000000 : fffff8026c221000 fffff8026c21a000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e SYMBOL_NAME: afd!AfdCompletePollIrp+95 MODULE_NAME: afd IMAGE_NAME: afd.sys IMAGE_VERSION: 10.0.22621.4034 STACK_COMMAND: .process /r /p 0xfffff8026e948f40; .thread 0xfffff8026e94c700 ; kb BUCKET_ID_FUNC_OFFSET: 95 FAILURE_BUCKET_ID: 0x133_DPC_afd!AfdCompletePollIrp OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ef73738c-d5c3-cdde-e832-877bfe61e63d} Followup: MachineOwner ---------"

Answer 1

komisch... gab es weitere abstürze oder war es ein einmaliges problem?

Answer 2

Der RAM-Check lief ohne Probleme, aber die Ergebnisse sind nirgendwo zu finden. Der Windows-Defender ist der einzige Virenschutz, den ich verwende. Es sind keine Treiber-Updater, -Cleaner oder -Optimierer installiert. Die üblichen Windows-Reparaturen wie SFC /scannow und DISM liefen reibungslos, aber es wurden keine Fehler gefunden.

Answer 3

ntoskrnl.wrong.symbols.exe kann auf ein problem mit ram hindeuten.

bitte führe den ram-check mit dem windows-tool windows-speicherdiagnose durch (einfach das fettgeschriebene in das suchfenster von windows copy-pasten oder schreiben und dann die eingabe drücken).

verwendest du irgendwelche virenschutzprogramme außer defender?

irgendwelche treiber-updater/cleaner/optimierer?

hast du schon die üblichen windows-reparaturen (sfc /scannow, dism) gemacht?

Answer 4

https://www.dropbox.com/scl/fi/eu6gh03uuybr61y59cyhs/090324-11546-01.dmp?rlkey=ik3z45mle3bcspocrl6cvosa3&st=8r6dedrt&dl=0

Answer 5

bitte die datei C:\Windows\Minidump\090324-11546-01.dmp auf onedrive/dropbox etc. hochladen und hier einen öffentlichen link posten.