Crash PC
FiniarelVrangr
Messages postés
10
Date d'inscription
Statut
Membre
Dernière intervention
-
FiniarelVrangr Messages postés 10 Date d'inscription Statut Membre Dernière intervention -
FiniarelVrangr Messages postés 10 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
Mon PC n'arrête pas de crash que ce soit en jeu ou sur mon navigateur. Il arrive même qu'il redémarre tout seul. Voici le rapport de who crashed, en espérant que quelqu'un puisse m'aider.
Merci d'avance.
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-LBU6EAC
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., TUF B450-PLUS GAMING
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17104949248 bytes (15,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 25/05/2020 20:26:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-7390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80778F2943F, 0xFFFFDF8D97C1A2C0, 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 Mon 25/05/2020 20:26:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0xBFCFB)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80778F2943F, 0xFFFFDF8D97C1A2C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 Mon 25/05/2020 20:15:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-11218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80176B2943F, 0xFFFFA580C9E4B2C0, 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 Mon 25/05/2020 20:04:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-9437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8042132943F, 0xFFFFAB8549B942C0, 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 Mon 25/05/2020 19:17:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-7312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0xFFFFAA81CD5DDE88, 0x2, 0x0, 0xFFFFF8075BF21290)
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 25/05/2020 17:55:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-7562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x50 (0xFFFFB08B23D69AA4, 0x2, 0xFFFFF80075D0C3BA, 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. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Mon PC n'arrête pas de crash que ce soit en jeu ou sur mon navigateur. Il arrive même qu'il redémarre tout seul. Voici le rapport de who crashed, en espérant que quelqu'un puisse m'aider.
Merci d'avance.
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-LBU6EAC
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., TUF B450-PLUS GAMING
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17104949248 bytes (15,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 25/05/2020 20:26:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-7390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80778F2943F, 0xFFFFDF8D97C1A2C0, 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 Mon 25/05/2020 20:26:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0xBFCFB)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80778F2943F, 0xFFFFDF8D97C1A2C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 Mon 25/05/2020 20:15:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-11218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80176B2943F, 0xFFFFA580C9E4B2C0, 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 Mon 25/05/2020 20:04:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-9437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8042132943F, 0xFFFFAB8549B942C0, 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 Mon 25/05/2020 19:17:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-7312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0xFFFFAA81CD5DDE88, 0x2, 0x0, 0xFFFFF8075BF21290)
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 25/05/2020 17:55:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-7562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x50 (0xFFFFB08B23D69AA4, 0x2, 0xFFFFF80075D0C3BA, 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. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
A voir également:
- Crash PC
- Reinitialiser pc - Guide
- Test performance pc - Guide
- Pc lent - Guide
- Downloader for pc - Télécharger - Téléchargement & Transfert
- Forcer demarrage pc - Guide
17 réponses
Bonjour
traduction :
Cela semble être un bogue de pilote de logiciel typique et n’est pas susceptible d’être causé par un problème matériel.
Le crash a eu lieu dans le noyau Windows. Peut-être ce problème est causé par un autre pilote qui ne peut pas être identifié à ce stade.
traduction :
Cela semble être un bogue de pilote de logiciel typique et n’est pas susceptible d’être causé par un problème matériel.
Le crash a eu lieu dans le noyau Windows. Peut-être ce problème est causé par un autre pilote qui ne peut pas être identifié à ce stade.
autre commentaire de whocrashed :
Cela semble être un bogue de pilote de logiciel typique et n’est pas susceptible d’être causé par un problème matériel.
Le crash a eu lieu dans un pilote de système de fichiers. Comme il n’y a pas d’autre pilote responsable détecté, cela pourrait pointer vers un lecteur défectueux ou un disque corrompu. Il est suggéré que vous exécutez CHKDSK.
trop d'overclock?
Cela semble être un bogue de pilote de logiciel typique et n’est pas susceptible d’être causé par un problème matériel.
Le crash a eu lieu dans un pilote de système de fichiers. Comme il n’y a pas d’autre pilote responsable détecté, cela pourrait pointer vers un lecteur défectueux ou un disque corrompu. Il est suggéré que vous exécutez CHKDSK.
trop d'overclock?
Je n'ai pas fait d'overclock donc normalement non mais par contre je viens d'essayer 6 fois de suite d’exécuter CHKDSK mais il crash avant la fin à chaque fois.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
ça se fait en mode admin
chkdsk C: /f /r
ça peut être très long, s'il y a beaucoup à corrigé, son interruption forcé aggrave les problèmes
il semble qu'un DD a un problème
analyse la santé des DD avec
https://crystalmark.info/en/software/crystaldiskinfo/
chkdsk C: /f /r
ça peut être très long, s'il y a beaucoup à corrigé, son interruption forcé aggrave les problèmes
il semble qu'un DD a un problème
analyse la santé des DD avec
https://crystalmark.info/en/software/crystaldiskinfo/
Pour chkdsk, je l'ai fait en mode admin mais il se fermait après environ 10 secondes d'analyse.
J'ai analysé la santé de mon ssd et de mon hdd et ils sont tous les deux marqué comme corrects.
Merci encore pour vos réponses
J'ai analysé la santé de mon ssd et de mon hdd et ils sont tous les deux marqué comme corrects.
Merci encore pour vos réponses
Si le problème est aussi profond, peut être vaut-il mieux que je remettes tout à 0.
Peut-être un formatage de PC pourrait régler le problème ? Qu'en pensez vous ?
Peut-être un formatage de PC pourrait régler le problème ? Qu'en pensez vous ?
essaye de le faire en deux fois, d'abord /r puis le l'option /f
autre vérification : l'intégrité des fichiers système (invite et admin)
sfc /scannow
autre vérification : l'intégrité des fichiers système (invite et admin)
sfc /scannow
Désolé mais je n'ai pas vraiment compris comment appliquer les options /f et /r et quand je tapes sfc /scannow et que j'exécutes, rien ne s'ouvre.
Une autre chose que j'avais oubliée mais peut être que ça a un lien, est que mon ssd émets une petite lumière rouge clignotante. Je me suis toujours dit que c'était normal mais peut être que non.
Une autre chose que j'avais oubliée mais peut être que ça a un lien, est que mon ssd émets une petite lumière rouge clignotante. Je me suis toujours dit que c'était normal mais peut être que non.
mon ssd émets une petite lumière rouge clignotante
un ssd interne? contenant l'O.S.
concernant chkdsk
je propose de le faire en 2X
chkdsk c: /r
puis
chkdsk c: /f
un ssd interne? contenant l'O.S.
concernant chkdsk
je propose de le faire en 2X
chkdsk c: /r
puis
chkdsk c: /f
Merci, j'ai pu faire marcher sfc et ça m'a dit que des fichiers corrompus avaient été trouvé et réparés mais j'ai toujours des crahs donc j'imagine que ça doit venir du ssd.
va falloir sauvegarder rapidement l’essentiel et changer pour du neuf
pour les ssd Crystaldiskinfo indique un % de vie?
pour les ssd Crystaldiskinfo indique un % de vie?
demande à dany311 d'expliquer pourquoi il considère que ce DD est hs, pour moi c'est un peut tôt pour l'envoyer à la déchetterie
ssd émets une petite lumière rouge clignotante que dit le constructeur sur la signification?
ssd émets une petite lumière rouge clignotante que dit le constructeur sur la signification?