PROBLEME PC , ECRAN BLEU , ECRAN QUI FREEZE , REDEMARAGE

salut

regarde si ceci peut t'aider ==> clique ici

@+

Ok merci , mais si j'ai fais tout les trucs demandés mais cela ne marche pas . Comment je fais ?

Ok merci beaucoup

Bonjour , mon système windows est le 11

J'ai acheté ce PC le 22 novembre 2022

oui je l'ai lancé

https://file///C:/Users/UTILISATEUR-PC/Documents/WhoCrashedOutput.htm

Ok excuse-moi j'ai mal lu ...

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: DESKTOP-RAHGUVH
Windows version: Windows 10, 10.0, version 2009, build: 22631
Windows dir: C:\Windows
Hardware: B550 GAMING X V2, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 5600X 6-Core Processor 8664, level: 25
12 logical processors, active mask: 4095
RAM: 34258083840 bytes (31,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 Tue 02/01/2024 09:02:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010224-8953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B00)
Bugcheck code: 0x13A (0x11, 0xFFFF820977200140, 0xFFFF82098246C7A0, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 02/01/2024 09:00:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010224-10859-01.dmp
This was probably caused by the following module: tpm.sys (0xFFFFF80748405158)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80748405158, 0xFFFF9181455B8638, 0xFFFF9181455B7E50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tpm.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de périphérique TPM
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.



On Mon 01/01/2024 22:38:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010124-5437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B00)
Bugcheck code: 0x13A (0x11, 0xFFFFE48354400140, 0xFFFFE4835EE3F2C0, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 01/01/2024 22:35:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010124-9406-01.dmp
This was probably caused by the following module: tpm.sys (0xFFFFF8054A7B5158)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8054A7B5158, 0xFFFFA68FBF9B0638, 0xFFFFA68FBF9AFE50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tpm.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de périphérique TPM
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.



On Sun 31/12/2023 20:52:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123123-10593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B00)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8073BF1D340)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



 

Conclusion

5 crash dumps have 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.
 

oui merci beaucoup de ton aide , mais maintenant quand j'allume mon pc j'ai mon écran devient noir pendant 1 secondes puis s'enlève et quelques secondes ça refait la même choses et après ça s'arrête je ne comprends pas .

je voulais réinstaller windows , mais cela me fait une erreur quand installer un support d'installation de windows ;

Erreur : 

je l'ai déjà mais je n'avais aucune erreur bizarre

oui je l'ai déjà installé

j'ai envoyé la vidéo en drive , on voit l'écran qui devient noir

pourquoi un artefact , j'ai changé ma carte graphique en août 2023

Rebonsoir , excusez-moi pour la réponse tardive oui je pense que c'est matériel , mais j'ai eu à l'instant un blue screen toujours la même erreur : ntoskrnl.exe

Le rapport :

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 Sat 06/01/2024 21:44:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010624-11234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B00)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80335F26340)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.