Windows 10 PRO X64 BSOD ntoskrnl.exe+3f6c90

Di primo acchito, senza approfondire, abbiamo un sistema non aggiornato (ora siamo alla 21H1 build 19043.1052) e un crash del driver della scheda video nVidia.

Ecco.

Anche qui si tratta del driver video Nvidia.

Non avevi messo quella scheda fra le periferiche del tuo sistema.

Di quale scheda si tratta esattamente?

Ho appena condiviso il file dump, è possibile sapere a cosa è imputabile, in modo da non andare alla neuro?

Grazie in anticipo

io stò effettuando qualche ricerca per curiosità e ho scaricato windbg preview, il risultato è il seguente;

Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\modad\Desktop\Minidump\060921-11546-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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff80651800000 PsLoadedModuleList = 0xfffff8065242a2b0 Debug session time: Wed Jun 9 16:17:07.928 2021 (UTC + 2:00) System Uptime: 1 days 14:51:34.641 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ....... Loading User Symbols Loading unloaded module list ........................................ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff80651bf6c90 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff8065547de20=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: fffff806524fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeout

Debugging Details:

*** WARNING: Unable to verify timestamp for nvlddmkm.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 6421

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 55083

Key  : Analysis.Init.CPU.mSec
Value: 296

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

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

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

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff806524fb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff8065546dad0 -- (.trap 0xfffff8065546dad0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffb68615aadcd0 rbx=0000000000000000 rcx=0000000000000000 rdx=ffffb68615058000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8066b45f060 rsp=fffff8065546dc60 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=ffffb686181eeae0 r11=fffff8065546dcb0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy nvlddmkm+0x9f060: fffff806`6b45f060 4883c428 add rsp,28h Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff8065547de18 fffff80651c1ee32 : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx fffff8065547de20 fffff80651a16ac3 : 00008d5d8751c329 fffff8064cd68180 0000000000000000 fffff8064cd68180 : nt!KeAccumulateTicks+0x205b12 fffff8065547de80 fffff80651a165aa : fffff806524f3900 fffff8065546db50 fffff80653fddf00 0000000000006001 : nt!KeClockInterruptNotify+0x453 fffff8065547df30 fffff80651a7e795 : fffff806524f3900 0000000000000000 0000000000000000 fffff53c02fd07d4 : nt!HalpTimerClockIpiRoutine+0x1a fffff8065547df60 fffff80651bf873a : fffff8065546db50 fffff806524f3900 0000000000000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5 fffff8065547dfb0 fffff80651bf8ca7 : ffffb6861586d630 fffff80600000000 0000003000000030 fffff80600000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff8065546dad0 fffff8066b45f060 : 0000000000000140 fffff8066b4d45a3 0000000000000020 ffffb68613f3ecc0 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff8065546dc60 0000000000000140 : fffff8066b4d45a3 0000000000000020 ffffb68613f3ecc0 ffffb68613f3ecc0 : nvlddmkm+0x9f060 fffff8065546dc68 fffff8066b4d45a3 : 0000000000000020 ffffb68613f3ecc0 ffffb68613f3ecc0 fffff8066b45eb51 : 0x140 fffff8065546dc70 0000000000000020 : ffffb68613f3ecc0 ffffb68613f3ecc0 fffff8066b45eb51 0000000000000000 : nvlddmkm+0x1145a3 fffff8065546dc78 ffffb68613f3ecc0 : ffffb68613f3ecc0 fffff8066b45eb51 0000000000000000 ffffb68600000020 : 0x20 fffff8065546dc80 ffffb68613f3ecc0 : fffff8066b45eb51 0000000000000000 ffffb68600000020 fffff8065546dce0 : 0xffffb68613f3ecc0 fffff8065546dc88 fffff8066b45eb51 : 0000000000000000 ffffb68600000020 fffff8065546dce0 0000000000000000 : 0xffffb68613f3ecc0 fffff8065546dc90 0000000000000000 : ffffb68600000020 fffff8065546dce0 0000000000000000 ffffb686181ec000 : nvlddmkm+0x9eb51

SYMBOL_NAME: nvlddmkm+9f060

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 9f060

FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}

Followup: MachineOwner

Beh, ce ne sono di molto peggio...

C'è dentro di tutto, di più.

Un disastro da paura.

E, sicuramente, Windows 10 e suoi aggiornamenti non c'entrano per nulla.

Segui i suggerimenti.

Buon lavoro.

Franco non è il mio dump, l'ho trovato in rete e ho voluto condividerlo.