BSOD et soucis maj windows

loic18 -  
bazfile Messages postés 58603 Date d'inscription   Statut Modérateur, Contributeur sécurité Dernière intervention   -

Bonjour à tous, je viens vers vous aujourd'hui pour vous demander un peu d'aide. Mon pc fixe fait régulièrement des bluescreens en jeu ou lorsque je tente de faire des mises à jours windows et en lisant quelques topics j'ai donc installer whocrashed pour tenter d'identifier le soucis mais j'avoue ne pas savoir comment décrypter le rapport que je vous joint ci-dessous:

[i]System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-QHJGMO8
Windows version: Windows 10, 10.0, version 2009, build: 19044
Windows dir: C:\Windows
Hardware: MS-7C02, Micro-Star International Co., Ltd, B450 TOMAHAWK MAX (MS-7C02)
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor 8664, level: 23
12 logical processors, active mask: 4095
RAM: 17101770752 bytes (15,9GB)


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

Crash dumps are enabled on your computer. 

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

On Fri 12/01/2024 16:53:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011224-14375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F92D0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8047720DEDE, 0xFFFFBE8D6B6F3D20, 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 12/01/2024 16:53:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x1E3C) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8047720DEDE, 0xFFFFBE8D6B6F3D20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Wed 10/01/2024 19:55:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011024-21078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F92D0) 
Bugcheck code: 0x50 (0xFFFFC3051F71E458, 0x2, 0xFFFFF8037440E638, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

On Tue 05/12/2023 09:31:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120523-14250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F92D0) 
Bugcheck code: 0x50 (0xFFFF908F617B9266, 0x2, 0xFFFFF8046DC0E61B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

On Fri 01/12/2023 09:24:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120123-14734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F92D0) 
Bugcheck code: 0x139 (0xE, 0xFFFFFE82C56D1650, 0xFFFFFE82C56D15A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

On Sat 18/11/2023 20:53:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111823-18937-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x2fb7) 
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8066FCFB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 a Microsoft module. The description of the module may give a hint about a non responding device in the system. [/i]

Merci d'avance à tout ceux qui donneront un peu de leur temps pour m'aiguiller dans ce dépannage.

A voir également:

1 réponse

bazfile Messages postés 58603 Date d'inscription   Statut Modérateur, Contributeur sécurité Dernière intervention   19 799
 

Bonjour.

Le bug d'aujourd'hui provient du pilote fltmgr.sys voir cette page.

Vérifie aussi si les pilotes de ta carte mère sont bien à jour, notamment celui du chipset, d'après WhoCrashed ta carte mère est une MSI B450 TOMAHAWK MAX (MS-7C02), si c'est bien le cas voir cette page


0