Upgrade a Windows 10: Kmode exception not handled

Pubblicità
ma hai provato ad installare i driver a mano dal sito del produttore della scheda madre?
Ma non ci sono tutti i driver di sistema sul sito del fornitore della scheda madre.
vedo solo questi:


Inoltre con Snappy Driver credo non trovi nulla di non installato:

1687771876485.webp
 
Ultima modifica:
Ho aperto Event Viewer di Windows, dove ho trovato questo a seguito di un riavvio causa quell'errore:

1687773220437.png

Così ho scaricato WinDbg e scovato alcuni dettagli:

Codice:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   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.047 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff805`17e00000 PsLoadedModuleList = 0xfffff805`18a2a2d0
Debug session time: Mon Jun 26 11:53:47.727 2023 (UTC + 2:00)
System Uptime: 0 days 0:21:41.409
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`181fc030 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff805`1e089160=000000000000001e
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff805180efd86, The address that the exception occurred at
Arg3: ffff970b55530050, Parameter 0 of the exception
Arg4: 000000000000005a, Parameter 1 of the exception

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: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7093

    Key  : Analysis.Elapsed.mSec
    Value: 7512

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

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x1e

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Failure.Bucket
    Value: 0x1E_C0000094_nt!PpmPerfSelectProcessorState

    Key  : Failure.Hash
    Value: {bde8e2c9-df0d-be8a-6751-181f4d2268d0}

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

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

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0

    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:  1e

BUGCHECK_P1: ffffffffc0000094

BUGCHECK_P2: fffff805180efd86

BUGCHECK_P3: ffff970b55530050

BUGCHECK_P4: 5a

FILE_IN_CAB:  MEMORY.DMP

EXCEPTION_PARAMETER1:  ffff970b55530050

EXCEPTION_PARAMETER2:  000000000000005a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT: 
fffff805`1e089158 fffff805`182f910e     : 00000000`0000001e ffffffff`c0000094 fffff805`180efd86 ffff970b`55530050 : nt!KeBugCheckEx
fffff805`1e089160 fffff805`18206722     : fffff805`182f90ec 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff805`1e0891a0 fffff805`180e5b37     : fffff805`1e089710 00000000`00000000 fffff805`1e074c60 fffff805`1820092e : nt!RtlpExecuteHandlerForException+0x12
fffff805`1e0891d0 fffff805`180e7b06     : fffff805`1e074378 fffff805`1e089e20 fffff805`1e074378 00000000`0000005d : nt!RtlDispatchException+0x297
fffff805`1e0898f0 fffff805`181fd142     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff805`1e089fb0 fffff805`181fd110     : fffff805`18210165 ffff970b`5544c620 fffff805`1e2444e9 ffff970b`5544c620 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff805`1e074238 fffff805`18210165     : ffff970b`5544c620 fffff805`1e2444e9 ffff970b`5544c620 fffff805`1801936a : nt!KiExceptionDispatchOnExceptionStackContinue
fffff805`1e074240 fffff805`18208504     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiExceptionDispatch+0x125
fffff805`1e074420 fffff805`180efd86     : fffff805`15b4a2e8 fffff805`1e074669 fffff805`18a1ed28 00000000`00000000 : nt!KiDivideErrorFault+0x304
fffff805`1e0745b0 fffff805`180efbae     : 000003f0`24bdb700 00000000`00000001 fffff805`18afc4e8 ffff970b`5600f920 : nt!PpmPerfSelectProcessorState+0x1a6
fffff805`1e0746d0 fffff805`18088810     : 00000000`00000000 fffff805`1e074b20 fffff805`1e074960 fffff805`1e074b20 : nt!PpmPerfSelectProcessorStates+0x5e
fffff805`1e074700 fffff805`180889c6     : 00000000`00000006 00000000`00000000 fffff805`1e074960 fffff805`1e074b20 : nt!PpmCheckRun+0x40
fffff805`1e074770 fffff805`1810c1ee     : 00000000`00000000 fffff805`1e074b20 00000000`00000000 00000000`00000000 : nt!PpmCheckStart+0x106
fffff805`1e074810 fffff805`1808b57e     : 00000000`00000000 fffff805`1e074b10 fffff805`15b42180 ffff970b`56ea7080 : nt!PpmCheckPeriodicStart+0x3e
fffff805`1e074860 fffff805`1808a864     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`0000c204 : nt!KiExecuteAllDpcs+0x30e
fffff805`1e0749d0 fffff805`1820092e     : 00000000`00000000 fffff805`15b42180 fffff805`18b27a00 ffff970b`5a05f080 : nt!KiRetireDpcList+0x1f4
fffff805`1e074c60 00000000`00000000     : fffff805`1e075000 fffff805`1e06f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!PpmPerfSelectProcessorState+1a6

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1a6

FAILURE_BUCKET_ID:  0x1E_C0000094_nt!PpmPerfSelectProcessorState

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {bde8e2c9-df0d-be8a-6751-181f4d2268d0}

Followup:     MachineOwner
---------

Non sono molto parlati per me. Voi vedete qualcosa di informativo?
 
da gestione dispositivi hai qualche periferica/componente non correttamente riconosciuta(col triangolo giallo) ? perchè quello sembra un problema di driver o bios non aggiornati
 
da li sembra tutto ok..

senza gpu intendevo: togli la 560 e colleghi il monitor alla scheda madre, per sfruttare la gpu del processore
oppure mi sono perso qualcosa e non stai già più usando la nvidia?

p.s. già che lo provi scollega tutte le periferiche non necessarie.. magari una di quelle ti manda il resto in bestia;
se poi ancora non va aggiornerei bios e scheda madre
 
da li sembra tutto ok..

senza gpu intendevo: togli la 560 e colleghi il monitor alla scheda madre, per sfruttare la gpu del processore
oppure mi sono perso qualcosa e non stai già più usando la nvidia?

p.s. già che lo provi scollega tutte le periferiche non necessarie.. magari una di quelle ti manda il resto in bestia;
se poi ancora non va aggiornerei bios e scheda madre
Questa le versione del BIOS che ho:
1.10.

Dove trovo i driver da installare per BIOS e scheda madre?
 

Allegati

  • IMG_20230626_131411.webp
    IMG_20230626_131411.webp
    1.6 MB · Visualizzazioni: 10
direi qui, sezioni bios e download
 
AIA!
Mentre aggiorna il bios con l'utility, è comparsa la maledetta schermata.
Ora non si avvia più :( Fatto danni?
 
Pubblicità
Pubblicità
Indietro
Top