Bluescreen pendant gaming

Fermé
ymk - 20 déc. 2020 à 14:50
ymk_04 Messages postés 3 Date d'inscription dimanche 20 décembre 2020 Statut Membre Dernière intervention 21 décembre 2020 - 21 déc. 2020 à 10:15
Bonjour,

Cela fait plusieurs jours qu'après que je lance un jeu (presque n'importe quel jeu un peu gourmand me le fait), au bout de 15 voire 30min de jeu je me retrouve avec un bluescreen, mais avec différents types d'erreurs, voici le rapport WHocrashed ci-dessous :

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 20/12/2020 00:06:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122020-7562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800628F1BBA, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 20/12/2020 12:01:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122020-8906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xC1 (0xFFFFD289C120EFD0, 0xFFFFD289C120EBBE, 0x654030, 0x23)
Error: SPECIAL_POOL_DETECTED_MEMORY_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 driver wrote to an invalid section of the special pool.
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 Sun 20/12/2020 12:01:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: atc.sys (atc+0x1812A2)
Bugcheck code: 0xC1 (0xFFFFD289C120EFD0, 0xFFFFD289C120EBBE, 0x654030, 0x23)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\drivers\atc.sys
product: Bitdefender® ATC
company: Bitdefender S.R.L. Bucharest, ROMANIA
description: Bitdefender Active Threat Control Filesystem Minifilter
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atc.sys (Bitdefender Active Threat Control Filesystem Minifilter, Bitdefender S.R.L. Bucharest, ROMANIA).
Google query: atc.sys Bitdefender S.R.L. Bucharest, ROMANIA SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION



On Sun 20/12/2020 11:17:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122020-7406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8041E0C802E, 0xFFFF948592545E20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 18/12/2020 00:12:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121820-6656-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFFE019C25ABBCC)
Bugcheck code: 0x50 (0xFFFFAF904A920B4C, 0x2, 0xFFFFE019C25ABBCC, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
Bug check description: This indicates that invalid system memory has been referenced.
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 Fri 18/12/2020 10:18:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121820-6640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x1A (0x61941, 0x2562E103D8C, 0xD, 0xFFFFB3023DA2FB00)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (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.


Mon setup PC date du 10 octobre 2020 et composé chez LDLC, voici la config :
Hardware: B450 AORUS ELITE, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor 8664, level: 23
16 logical processors, active mask: 65535
RAM: 34301718528 bytes (31,9GB)

J'ai bien mis tous les pilotes à jour, windows aussi, j'ai lancé le diagnostic de mémoire mais aucune erreur n'est sortie, ... Bref j'ai tout essayé en vain.
J'aimerais donc savoir d'où pourrait provenir cette instabilité.

En vous remerciant par avance !

3 réponses

seb77150 Messages postés 5823 Date d'inscription lundi 17 février 2020 Statut Membre Dernière intervention 28 septembre 2022 468
Modifié le 20 déc. 2020 à 14:51
salut, dans powershell en mode admin tape ceci:
sfc /scannow
puis donne moi le résultat

0
Salut,
merci pour ton aide

Voici le résultat : Le programme de protection des ressources Windows n’a trouvé aucune violation d’intégrité.
0
seb77150 Messages postés 5823 Date d'inscription lundi 17 février 2020 Statut Membre Dernière intervention 28 septembre 2022 468
20 déc. 2020 à 19:05
ok, télécharge OCCT (ne pas mettre a jour) puis fait un test occt en small data set pendant 5 min et envoie moi le rapport de test (attention tu n'a le droit qu'à un seul test)
0
ymk_04 Messages postés 3 Date d'inscription dimanche 20 décembre 2020 Statut Membre Dernière intervention 21 décembre 2020 > seb77150 Messages postés 5823 Date d'inscription lundi 17 février 2020 Statut Membre Dernière intervention 28 septembre 2022
20 déc. 2020 à 21:13
Rapport de test OCCT :
0
seb77150 Messages postés 5823 Date d'inscription lundi 17 février 2020 Statut Membre Dernière intervention 28 septembre 2022 468 > ymk_04 Messages postés 3 Date d'inscription dimanche 20 décembre 2020 Statut Membre Dernière intervention 21 décembre 2020
20 déc. 2020 à 23:01
ok, aucune anomalie dans le rapport. Telecharge CECI puis donne moi l'état de ton DD
0
ymk_04 Messages postés 3 Date d'inscription dimanche 20 décembre 2020 Statut Membre Dernière intervention 21 décembre 2020 > seb77150 Messages postés 5823 Date d'inscription lundi 17 février 2020 Statut Membre Dernière intervention 28 septembre 2022
20 déc. 2020 à 23:44
L'état du DD :
0
seb77150 Messages postés 5823 Date d'inscription lundi 17 février 2020 Statut Membre Dernière intervention 28 septembre 2022 468 > ymk_04 Messages postés 3 Date d'inscription dimanche 20 décembre 2020 Statut Membre Dernière intervention 21 décembre 2020
21 déc. 2020 à 09:29
ok, dans powershell tape cette commande: chkdsk C: /f
0
salut , faut vérifié que aucune attache du ventirad sur le processeur et soi casser ou pas verrouiller correctement si c'est le cas faut bien sur réparer la cause mais aussi changer la pâte thermique
0