Bug carte graphique qui arrete de m afficher
Panth33ra Messages postés 21907 Date d'inscription Statut Membre Dernière intervention -
sa marque sa sur Whocrashed
Welcome to WhoCrashed (Home Edition) v 6.70
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: PC
Windows version: Windows 10, 10.0, version 2009, build: 22621
Windows dir: C:\WINDOWS
Hardware: H410M S2H V2, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz 8664, level: 6
6 logical processors, active mask: 63
RAM: 17081479168 bytes (15,9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 14/01/2024 19:41:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\WATCHDOG-20240114-1941.dmp
This was probably caused by the following module: watchdog.sys (watchdog!WdReferenceObject+0x14C)
Bugcheck code: 0x193 (0x815, 0x2, 0xFFFF85096DCB2080, 0x0)
Error: VIDEO_DXGKRNL_LIVEDUMP
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: A livedump triggered by dxgkrnl occurred. You may have problems with your graphics driver or hardware.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
One crash dump has been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
3 réponses
puis quand je l'ouvre avec windbg sa met sa
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_DXGKRNL_LIVEDUMP (193)
Livedumps triggered by dxgkrnl when a problem is detected.
(This code can never be used for a real BugCheck; it is used to identify live dumps.)
Arguments:
Arg1: 0000000000000815, Reason Code.
100 Internal
Arg2: 0000000000000002, Reserved.
Arg3: ffff85096dcb2080, Reserved.
Arg4: 0000000000000000, Reserved.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1686
Key : Analysis.Elapsed.mSec
Value: 5286
Key : Analysis.IO.Other.Mb
Value: 6
Key : Analysis.IO.Read.Mb
Value: 14
Key : Analysis.IO.Write.Mb
Value: 40
Key : Analysis.Init.CPU.mSec
Value: 171
Key : Analysis.Init.Elapsed.mSec
Value: 36446
Key : Analysis.Memory.CommitPeak.Mb
Value: 98
Key : Bugcheck.Code.KiBugCheckData
Value: 0x0
Key : Bugcheck.Code.LegacyAPI
Value: 0x193
Key : Dump.Attributes.AsUlong
Value: 10
Key : Failure.Bucket
Value: LKD_0x193_watchdog!WdpDbgCaptureKernelDump
Key : Failure.Hash
Value: {27237f65-f3eb-f2f7-9c21-ee7274da0ced}
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: 0
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: 21500158
Key : Hypervisor.Flags.ValueHex
Value: 14810fe
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 : SecureKernel.HalpHvciEnabled
Value: 0
Key : WER.OS.Branch
Value: ni_release_svc_prod3
Key : WER.OS.Version
Value: 10.0.22621.2506
BUGCHECK_CODE: 193
BUGCHECK_P1: 815
BUGCHECK_P2: 2
BUGCHECK_P3: ffff85096dcb2080
BUGCHECK_P4: 0
FILE_IN_CAB: WATCHDOG-20240114-1941.dmp
DUMP_FILE_ATTRIBUTES: 0x10
Live Generated Dump
PROCESS_NAME: System
STACK_TEXT:
ffffa90d`b215bea0 fffff800`76c991a3 : 00000000`00000000 ffffa90d`b215bf70 00000000`00000000 00000000`00000000 : nt!IopLiveDumpCollectPages+0xd9
ffffa90d`b215bef0 fffff800`76caaadb : ffffffff`ffffffff ffffffff`ffffffff ffffa90d`b215bf70 00000000`00000000 : nt!IopLiveDumpEndMirroringCallback+0x33
ffffa90d`b215bf20 fffff800`76b4bf24 : 00000000`00000000 00000000`00000000 ffff8509`70f62010 ffffa90d`b215c110 : nt!MmDuplicateMemory+0x2ff
ffffa90d`b215bfb0 fffff800`76c98983 : 00000000`00000001 ffffa90d`b215c020 ffff8509`74f4cae0 00000000`00000000 : nt!IopLiveDumpCapture+0x78
ffffa90d`b215c010 fffff800`76b49e3e : ffff8509`70f62010 ffff8509`70f62010 ffffbf86`16878508 00000000`00000000 : nt!IopLiveDumpCaptureMemoryPages+0x4b
ffffa90d`b215c150 fffff800`767393ac : 00000000`00000000 ffffa90d`b215c4b0 00000000`00000000 00000000`00036cf4 : nt!IoCaptureLiveDump+0x406
ffffa90d`b215c390 fffff800`76b0312d : 00000000`00000022 ffffffff`80003490 00000000`00000000 ffff8509`773aa070 : nt!DbgkCaptureLiveKernelDump+0x354
ffffa90d`b215c420 fffff800`7662c458 : ffffffff`00000025 ffffa90d`b215c780 ffff8509`00000048 00000000`00000000 : nt!NtSystemDebugControl+0x12126d
ffffa90d`b215c540 fffff800`7661c4d0 : fffff800`8dfb950c ffff8509`6b9c0dd0 fffff800`8dfc99ea ffffffff`80004074 : nt!KiSystemServiceExitPico+0x454
ffffa90d`b215c748 fffff800`8dfb950c : ffff8509`6b9c0dd0 fffff800`8dfc99ea ffffffff`80004074 ffff8509`6b9c0b20 : nt!KiServiceLinkage
ffffa90d`b215c750 fffff800`8dfc8f37 : 00000000`00000193 00000000`00000000 00000000`00000815 00000000`00000000 : watchdog!WdpDbgCaptureKernelDump+0x9c
ffffa90d`b215c7e0 fffff800`8dfc8d8c : 00000000`00000007 00000000`00000193 00000000`00000815 fffff800`7643554f : watchdog!WdDbgReportRecreate+0xe7
ffffa90d`b215c840 fffff800`8dfb865f : ffffa90d`b69a27b0 ffffa90d`b215ca00 ffff8509`430a9500 fffff800`76f4aac0 : watchdog!WdDbgReportCreate+0x5c
ffffa90d`b215c8b0 fffff800`76434f85 : ffff8509`430a9500 ffff8509`654e8000 ffffa90d`00000000 ffff8509`00000000 : watchdog!WdpProcessWatchdogTimeoutReportThread+0x4f
ffffa90d`b215c900 fffff800`76507167 : ffff8509`654e8080 00000000`00000bb1 ffff8509`654e8080 fffff800`76434e30 : nt!ExpWorkerThread+0x155
ffffa90d`b215caf0 fffff800`7661bb94 : ffffd001`44591180 ffff8509`654e8080 fffff800`76507110 60013b04`02009fa0 : nt!PspSystemThreadStartup+0x57
ffffa90d`b215cb40 00000000`00000000 : ffffa90d`b215d000 ffffa90d`b2156000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: watchdog!WdpDbgCaptureKernelDump+9c
MODULE_NAME: watchdog
IMAGE_NAME: watchdog.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 9c
FAILURE_BUCKET_ID: LKD_0x193_watchdog!WdpDbgCaptureKernelDump
OS_VERSION: 10.0.22621.2506
BUILDLAB_STR: ni_release_svc_prod3
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {27237f65-f3eb-f2f7-9c21-ee7274da0ced}
Followup: MachineOwner
---------
Boonjour,
Précise pour quelle carte graphique si c'est bien elle qui fout la m... ?
Bonjour,
Je vous invite à vous rendre sur le site Nvidia, téléchargez le logiciel pour mettre les pilotes à jour. Ensuite redémarrez votre PC. Et si le problème persiste, il faudrait peut-être songé de changer de carte graphique. Bien à vous,
Si c'est bien une CG NVidia... https://www.nvidia.fr/Download/index.aspx?lang=fr par contre si c'est une CG AMD... https://www.amd.com/fr/support
