Msg erreur et blue screen sur acer nitro
Fermé
rialta
-
18 mars 2022 à 17:53
fabul Messages postés 39204 Date d'inscription dimanche 18 janvier 2009 Statut Modérateur Dernière intervention 18 novembre 2024 - 20 mars 2022 à 15:28
fabul Messages postés 39204 Date d'inscription dimanche 18 janvier 2009 Statut Modérateur Dernière intervention 18 novembre 2024 - 20 mars 2022 à 15:28
3 réponses
fabul
Messages postés
39204
Date d'inscription
dimanche 18 janvier 2009
Statut
Modérateur
Dernière intervention
18 novembre 2024
5 420
18 mars 2022 à 17:56
18 mars 2022 à 17:56
Salut,
Analyses le crashdump avec WhoCrashed Home Free Edition
Nous dire c'est à cause de quel driver ?
Analyses le crashdump avec WhoCrashed Home Free Edition
Nous dire c'est à cause de quel driver ?
rialta1
Messages postés
8
Date d'inscription
mercredi 13 mars 2013
Statut
Membre
Dernière intervention
20 mars 2022
20 mars 2022 à 15:18
20 mars 2022 à 15:18
Voici le rapport
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 18/03/2022 17:11:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-10046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4164C0)
Bugcheck code: 0x4A (0x7FF872863834, 0x1, 0x0, 0xFFFFCD05D1AE7B20)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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.
On Fri 18/03/2022 17:11:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x85A9)
Bugcheck code: 0x4A (0x7FF872863834, 0x1, 0x0, 0xFFFFCD05D1AE7B20)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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.
On Fri 18/03/2022 15:59:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-7250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4164C0)
Bugcheck code: 0x4A (0x7FFA58803834, 0x1, 0x0, 0xFFFFE189D7117B20)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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.
On Thu 17/03/2022 16:02:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031722-7406-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x3a22)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80512305330, 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\LiveKernelReports\NDIS-20220317-1600.dmp
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 18/03/2022 17:11:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-10046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4164C0)
Bugcheck code: 0x4A (0x7FF872863834, 0x1, 0x0, 0xFFFFCD05D1AE7B20)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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.
On Fri 18/03/2022 17:11:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x85A9)
Bugcheck code: 0x4A (0x7FF872863834, 0x1, 0x0, 0xFFFFCD05D1AE7B20)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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.
On Fri 18/03/2022 15:59:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-7250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4164C0)
Bugcheck code: 0x4A (0x7FFA58803834, 0x1, 0x0, 0xFFFFE189D7117B20)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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.
On Thu 17/03/2022 16:02:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031722-7406-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x3a22)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80512305330, 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\LiveKernelReports\NDIS-20220317-1600.dmp
fabul
Messages postés
39204
Date d'inscription
dimanche 18 janvier 2009
Statut
Modérateur
Dernière intervention
18 novembre 2024
5 420
Modifié le 20 mars 2022 à 15:29
Modifié le 20 mars 2022 à 15:29
Le seul qui resort qui n'est pas de Microsoft c'est amdppm.sys
AMDPPM = AMD Primary Processor Module
Donc c'est un driver AMD, mais je ne connais pas bien AMD
Tu peux chercher des drivers AMD pour processeur
AMDPPM = AMD Primary Processor Module
Donc c'est un driver AMD, mais je ne connais pas bien AMD
Tu peux chercher des drivers AMD pour processeur
