Multiples bsods

Fermé
Isk - 11 déc. 2020 à 17:21
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 13 déc. 2020 à 17:20
Bonjour,

Depuis quelques jours, mon ordinateur fixe commence à avoir de nombreux BSODs qui m'arrivent toutes les 5 minutes (dès fois c'est toutes les minutes) et je ne sais pas pourquoi.
Voici les (quelques) différents messages d'erreurs :
irql_not_less_or_equal
kmode_exception_not_handled
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
page_fault_in_nonpaged_area
KERNEL_SECURITY_CHECK_FAILURE

Par contre quand je joue à quelconques jeux, je n'ai jamais eu aucun BSOD

J'ai réinitialisé(1fois) et formaté(1 fois) mon PC mais j'en ai encore
J'ai testé la RAM : aucun problème
J'ai testé le disque dur avec CrystalDiskInfo qui ne m'indique que tout est normal
J'ai fais tout ce qui est chkdsk sfc /scannow DISM etc, et tout est normal aussi
J'ai regardé les maj des drivers et de Windows Update tout est à jour.
Si vous pourriez m'aider ce serait grandement utile.

Je vous met ci-dessous le rapport de WhoCrashed :

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

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

On Fri 11/12/2020 17:18:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121120-6703-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF8002598C02D)
Bugcheck code: 0xD1 (0x3405EC10, 0xFF, 0x0, 0xFFFFF8002598C02D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 11/12/2020 17:18:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: amdppm.sys (0xFFFFF8002598C02D)
Bugcheck code: 0xD1 (0x3405EC10, 0xFF, 0x0, 0xFFFFF8002598C02D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 11/12/2020 17:15:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121120-7453-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8011FAEFA8D)
Bugcheck code: 0xBE (0xFFFFF8011FAEFA8D, 0x9000000056EF121, 0xFFFF8489BE62F7E0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 11/12/2020 17:13:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121120-6875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80451650C78, 0xFFFFF88EA2875C40, 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 11/12/2020 17:06:26 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121120-6546-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF80574EB68A0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80574EB68A0, 0xFFFFB908B851B908, 0xFFFFB908B851B140)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 11/12/2020 17:03:47 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121120-7328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x192 (0xFFFF918871803080, 0xFFFFB8836F649DC0, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
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 lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\LiveKernelReports\PoW32kWatchdog-20201122-2330.dmp

1 réponse

Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 24 631
12 déc. 2020 à 18:44
Salut,

Suivre ce lien : Résoudre BSOD sur Windows


0
Re
J’ai déjà tout fait ma température est constamment surveillée grâce aux logiciels CPUZ et GPUZ, j’ai déjà vu si le bios est a jour, j’ai déjà fait tout ce que vous m’aviez demandé
Si vous n’avez pas d’autres astuces, alors je pense que c’est un problème d’un composant, si oui pourriez-vous m’éclairer sur celui qui pose problème
0
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 24 631 > Isk
13 déc. 2020 à 17:20
C'est compliqué pour trouver le composant.
Commence déjà par tout débrancher en USB sauf clavier et souris.
Teste avec une seule barrette à la fois.

Sinon faudra tester avec une autre carte graphique.

Tente aussi de faire un clear CMOS :
https://www.malekal.com/clear-cmos-reinitialiser-le-bios/
https://www.commentcamarche.net/informatique/composants/1659-reinitialiser-le-bios-d-un-pc/
0