Sdílet prostřednictvím

System windows 11 problem Kernel-41 porucha napajeni Notebook asus nitro5

Anonymní
2024-12-13T18:47:07+00:00

nahodne zamrznuti cca 60s a restart zadna modra smrt nic jen černa obrazovka

mindup

************* 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.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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

Loading Dump File [C:\Windows\Minidump\121324-10500-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 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff806`8f400000 PsLoadedModuleList = 0xfffff806`902f4850
Debug session time: Fri Dec 13 18:44:18.243 2024 (UTC + 1:00)
System Uptime: 0 days 4:56:11.047
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols

Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`8f8b85d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffbe80`3d55ace0=0000000000000133
11: 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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff806903c33a0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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.CPU.mSec
    Value: 1453

    Key  : Analysis.Elapsed.mSec
    Value: 1465

    Key  : Analysis.IO.Other.Mb
    Value: 19

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 22

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    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_ISR_dxgmms2!VidSchIsMonitoredFenceSignaled

    Key  : Failure.Hash
    Value: {b3499a4e-49c8-a174-0cf7-eb15cd4502c8}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 24a10ef

    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

    Key  : Stack.Pointer
    Value: ISR

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff806903c33a0

BUGCHECK_P4: 0

FILE_IN_CAB:  121324-10500-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff9983822ea300

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffbe80`3d55acd8 fffff806`8f775129     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`903c33a0 : nt!KeBugCheckEx
ffffbe80`3d55ace0 fffff806`8f767b61     : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00115ac2 : nt!KeAccumulateTicks+0x589
ffffbe80`3d55ad50 fffff806`8f66ebfb     : 00000029`605ea9be 00000000`00000000 fffff806`0000000b ffff9983`7253d500 : nt!KiUpdateRunTime+0xc9
ffffbe80`3d55add0 fffff806`8f6702ad     : ffff9983`7253d500 00000000`00000000 ffff9983`7253d5b0 fffff806`9038dd80 : nt!KeClockInterruptNotify+0x96b
ffffbe80`3d55af50 fffff806`8fa7be9e     : 00000000`d3499302 ffff9983`7253d500 fffffc02`811b7210 00000029`60d960e8 : nt!KiCallInterruptServiceRoutine+0x2ed
ffffbe80`3d55afb0 fffff806`8fa7c6ac     : 00000029`60d94d52 fffffc02`811b7290 00000029`60d94d62 000033a0`3beb25ab : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffffc02`811b7210 fffff806`8f7d023a     : fffffc02`811b7440 fffffc02`811b7838 ffff9983`8177c000 ffff9983`72ad48a0 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffffc02`811b73a0 fffff806`8f7d1a63     : fffffc02`811b7400 00000000`00000000 ffffbe80`3d53e180 00000000`000007b0 : nt!KxWaitForLockOwnerShipWithIrql+0x76
fffffc02`811b7410 fffff806`8f66864d     : fffffc02`811b74a0 fffffc02`811b7591 00000000`00000000 ffff9983`8177c7c0 : nt!KiAcquireQueuedSpinLockInstrumented+0x93
fffffc02`811b7450 fffff806`3803866b     : ffff9983`7fffff10 00000000`00000000 fffffc02`811b75a0 fffff806`38008bc2 : nt!KeAcquireInStackQueuedSpinLock+0x8d
fffffc02`811b7480 fffff806`380af606     : ffff9983`824c0000 01008a11`006070f6 00000000`00000048 00000000`00000004 : dxgmms2!VidSchIsMonitoredFenceSignaled+0x3b
fffffc02`811b74d0 fffff806`380b08ee     : ffff9983`00000000 00000000`00000000 ffff9983`8e6e5a50 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::FlushPagingBufferInternal+0x226
fffffc02`811b75e0 fffff806`380b0076     : 00000000`00000001 ffff9983`8e6e5a50 00000000`00000000 fffff806`8fa81b01 : dxgmms2!VIDMM_PHYSICAL_ADAPTER::PageInAllocation+0x18e
fffffc02`811b7680 fffff806`380b63b6     : fffffc02`811b7a80 ffff9983`8ea8ac10 fffff806`1d3fe280 ffff9983`822ea300 : dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x106
fffffc02`811b7810 fffff806`380b503e     : ffff9983`824c0000 ffffac8e`436225e0 ffff9983`824c0000 ffffac8e`436225e0 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x1e6
fffffc02`811b7a00 fffff806`8f85585a     : ffffac8e`2740a000 fffff806`380b4901 ffffbe80`3d53e100 024fe07f`b8bbbd02 : dxgmms2!VidMmWorkerThreadProc+0x6de
fffffc02`811b7bb0 fffff806`8fa7ae54     : ffffbe80`3d53e180 ffff9983`822ea300 fffff806`8f855800 0f000000`0434bd80 : nt!PspSystemThreadStartup+0x5a
fffffc02`811b7c00 00000000`00000000     : fffffc02`811b8000 fffffc02`811b1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  dxgmms2!VidSchIsMonitoredFenceSignaled+3b

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.26100.2454

STACK_COMMAND:  .process /r /p 0xffff9983724ae040; .thread 0xffff9983822ea300 ; kb

BUCKET_ID_FUNC_OFFSET:  3b

FAILURE_BUCKET_ID:  0x133_ISR_dxgmms2!VidSchIsMonitoredFenceSignaled

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b3499a4e-49c8-a174-0cf7-eb15cd4502c8}

Followup:     MachineOwner
---------
Windows pro domácnosti | Windows 11 | Selhání výkonu a systému

Otázka je uzamčená. Tato otázka se migrovala z komunity podpory Microsoftu. Můžete hlasovat, jestli je užitečná, ale nemůžete k ní přidávat komentáře či odpovědi ani ji nemůžete sledovat.

Počet komentářů: 0 Žádné komentáře

Odpovědi: 11

Seřadit podle: Nejužitečnější
  1. Anonymní
    2025-01-04T07:21:19+00:00

    drivery jsou nini aktualni akorat kdyz dam dignostiku ram zakladni tak je vporadku akdyz dam dignostiku tu hlobkovu atk to zaprne na 20 procentech a za 8 hod se to nepohlo tk nevim

    Byla tato odpověď užitečná?

    Počet osob, které tuto odpověď považovaly za užitečnou: 1.
    Počet komentářů: 0 Žádné komentáře
  2. Anonymní
    2024-12-14T10:23:07+00:00

    ano bios je aktualni co ma podpora pod my m ID počitace coz je 11.7.2023

    Byla tato odpověď užitečná?

    Počet komentářů: 0 Žádné komentáře
  3. Miroslav Pragl 78,271 Reputační body Dobrovolný moderátor
    2024-12-14T08:55:53+00:00

    Odinstaluj ovace uplne (pomoci DDU) a nainstaluj znova nacisto aktualni

    Dalsi ovladace a BIOS mas aktualizovane?

    MP

    Byla tato odpověď užitečná?

    Počet komentářů: 0 Žádné komentáře
  4. Anonymní
    2024-12-14T07:12:32+00:00

    grafika nvidia rtx 3070 toplota bez použivaní je okolo 35°C a ovladače jsou aktuální ještě jedine udělat kompletni výmeny teplovodive pasty

    Byla tato odpověď užitečná?

    Počet komentářů: 0 Žádné komentáře
  5. Miroslav Pragl 78,271 Reputační body Dobrovolný moderátor
    2024-12-13T23:12:50+00:00

    Dle chyby v DirectX to vypada na problem grafickeho adapteru. Zkontrolu jeho teplotu a aktualnost ovladacu.

    MP

    Byla tato odpověď užitečná?

    Počet komentářů: 0 Žádné komentáře