Crash PC - Ecran bleu + reboot incessants
Résolu/Fermé
Horo
-
23 mai 2022 à 23:00
fabul Messages postés 37775 Date d'inscription dimanche 18 janvier 2009 Statut Modérateur Dernière intervention 6 mai 2024 - 24 mai 2022 à 17:05
fabul Messages postés 37775 Date d'inscription dimanche 18 janvier 2009 Statut Modérateur Dernière intervention 6 mai 2024 - 24 mai 2022 à 17:05
A voir également:
- Crash PC - Ecran bleu + reboot incessants
- Double ecran pc - Guide
- Reboot pc - Guide
- Ecran noir pc - Guide
- Écran bleu - Guide
- Test performance pc - Guide
5 réponses
fabul
Messages postés
37775
Date d'inscription
dimanche 18 janvier 2009
Statut
Modérateur
Dernière intervention
6 mai 2024
5 180
Modifié le 23 mai 2022 à 23:09
Modifié le 23 mai 2022 à 23:09
Salut,
Vérifies l'état de ton disque avec CristalDiskInfo
https://crystalmark.info/en/software/crystaldiskinfo/
Copies nous un log WhoCrashed Free Home Edition
https://www.resplendence.com/whocrashed
Vérifies l'état de ton disque avec CristalDiskInfo
https://crystalmark.info/en/software/crystaldiskinfo/
Copies nous un log WhoCrashed Free Home Edition
https://www.resplendence.com/whocrashed
Salut fabul,
Merci pour ta réponse.
Crystaldisk m'indique que l'état de santé de mes deux disques durs est bon, y a-t-il un log à t'envoyer ?
Pour ce qui est du log WhoCrashed, le voici :
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Mon 23/05/2022 21:30:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052322-12078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80248C231E8, 0xFFFFF48AD9206AC8, 0xFFFFF48AD92062E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 23/05/2022 21:30:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: avgsp.sys (avgSP+0x42A64)
Bugcheck code: 0x7E (0xFFFFFFFF80000003, 0xFFFFF80248C231E8, 0xFFFFF48AD9206AC8, 0xFFFFF48AD92062E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\avgsp.sys
product: AVG Internet Security System
company: AVG Technologies CZ, s.r.o.
description: AVG Self Protection
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: avgsp.sys (AVG Self Protection, AVG Technologies CZ, s.r.o.).
Google query: avgsp.sys AVG Technologies CZ, s.r.o. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Thu 19/05/2022 19:27:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051922-11968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0x124 (0x0, 0xFFFF8E8D3DC02028, 0xB2000000, 0x30005)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 Wed 18/05/2022 22:35:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051822-11984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006952B520, 0xFFFFF68439E3FF00, 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 Tue 17/05/2022 20:24:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051722-11234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0xA (0x7FFFFFFF0000, 0x2, 0x0, 0xFFFFF806508BFF90)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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 Mon 16/05/2022 19:20:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051622-10875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF85, 0x0, 0xFFFFF8003D12B520, 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.
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
avgsp.sys (AVG Self Protection, AVG Technologies CZ, s.r.o.)
Merci pour ta réponse.
Crystaldisk m'indique que l'état de santé de mes deux disques durs est bon, y a-t-il un log à t'envoyer ?
Pour ce qui est du log WhoCrashed, le voici :
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Mon 23/05/2022 21:30:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052322-12078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80248C231E8, 0xFFFFF48AD9206AC8, 0xFFFFF48AD92062E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 23/05/2022 21:30:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: avgsp.sys (avgSP+0x42A64)
Bugcheck code: 0x7E (0xFFFFFFFF80000003, 0xFFFFF80248C231E8, 0xFFFFF48AD9206AC8, 0xFFFFF48AD92062E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\avgsp.sys
product: AVG Internet Security System
company: AVG Technologies CZ, s.r.o.
description: AVG Self Protection
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: avgsp.sys (AVG Self Protection, AVG Technologies CZ, s.r.o.).
Google query: avgsp.sys AVG Technologies CZ, s.r.o. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Thu 19/05/2022 19:27:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051922-11968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0x124 (0x0, 0xFFFF8E8D3DC02028, 0xB2000000, 0x30005)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 Wed 18/05/2022 22:35:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051822-11984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006952B520, 0xFFFFF68439E3FF00, 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 Tue 17/05/2022 20:24:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051722-11234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0xA (0x7FFFFFFF0000, 0x2, 0x0, 0xFFFFF806508BFF90)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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 Mon 16/05/2022 19:20:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051622-10875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B40)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF85, 0x0, 0xFFFFF8003D12B520, 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.
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
avgsp.sys (AVG Self Protection, AVG Technologies CZ, s.r.o.)
fabul
Messages postés
37775
Date d'inscription
dimanche 18 janvier 2009
Statut
Modérateur
Dernière intervention
6 mai 2024
5 180
24 mai 2022 à 00:13
24 mai 2022 à 00:13
Désinstalles AVG Internet Security pour commencer voir si déjà ça règle le problème.
Salut,
Je viens de le désinstaller, je croise les doigts pour que ça fasse le taff. Je reviendrai dans le coin sous ce post si ça recommence, je devrais le savoir assez vite..
En tout cas, merci fabul ! Passe une excellente journée !
Je viens de le désinstaller, je croise les doigts pour que ça fasse le taff. Je reviendrai dans le coin sous ce post si ça recommence, je devrais le savoir assez vite..
En tout cas, merci fabul ! Passe une excellente journée !
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
fabul
Messages postés
37775
Date d'inscription
dimanche 18 janvier 2009
Statut
Modérateur
Dernière intervention
6 mai 2024
5 180
24 mai 2022 à 17:05
24 mai 2022 à 17:05
Bon, alors si tu ne reviens pas, je marque ton problème comme résolu.
On pourra refaire le contraire si le problème continue.
De rien,
@+
On pourra refaire le contraire si le problème continue.
De rien,
@+
