Mon ordi crash ou reboot souvent
Fermé
CallOfDeath
Messages postés
13
Date d'inscription
samedi 5 février 2011
Statut
Membre
Dernière intervention
14 mars 2012
-
Modifié par CallOfDeath le 7/09/2011 à 18:53
antipolis a Messages postés 15609 Date d'inscription mercredi 5 novembre 2008 Statut Membre Dernière intervention 12 novembre 2014 - 8 sept. 2011 à 09:03
antipolis a Messages postés 15609 Date d'inscription mercredi 5 novembre 2008 Statut Membre Dernière intervention 12 novembre 2014 - 8 sept. 2011 à 09:03
A voir également:
- Mon ordi crash ou reboot souvent
- Mon ordi rame que faire - Guide
- Reboot pc - Guide
- Reboot system now - Guide
- Ordi scrabble - Télécharger - Jeux vidéo
- Ordi ecran noir - Guide
6 réponses
soulsy
Messages postés
2739
Date d'inscription
dimanche 1 mai 2011
Statut
Membre
Dernière intervention
21 juillet 2017
366
28 août 2011 à 17:41
28 août 2011 à 17:41
Bonjour,
Tu peux avoir plus de détail sur les écrans en utilisant ce logiciel :
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
Tu as installé un nouveau matériel ou logiciel depuis que tu as ces problèmes ?
Tu peux avoir plus de détail sur les écrans en utilisant ce logiciel :
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
Tu as installé un nouveau matériel ou logiciel depuis que tu as ces problèmes ?
CallOfDeath
Messages postés
13
Date d'inscription
samedi 5 février 2011
Statut
Membre
Dernière intervention
14 mars 2012
7 sept. 2011 à 18:53
7 sept. 2011 à 18:53
Post mise a jour plus de photo pour plus de détail
Edawards
Messages postés
17125
Date d'inscription
dimanche 25 juillet 2010
Statut
Membre
Dernière intervention
21 juillet 2020
1 935
8 sept. 2011 à 07:23
8 sept. 2011 à 07:23
CallOfDeath
Messages postés
13
Date d'inscription
samedi 5 février 2011
Statut
Membre
Dernière intervention
14 mars 2012
28 août 2011 à 18:22
28 août 2011 à 18:22
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 26/08/2011 12:12:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x1A (0x41287, 0x30004C, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: Unknown .
Google query: Unknown MEMORY_MANAGEMENT
On Thu 25/08/2011 00:56:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082511-29406-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x80679)
Bugcheck code: 0x4E (0x7, 0x6ADBC, 0x6ADA9, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 24/08/2011 07:43:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082411-28033-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE34)
Bugcheck code: 0x1A (0x41284, 0xFFFFFFFF87D80001, 0x242, 0xFFFFFFFF88A00000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 31/07/2011 15:36:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073111-27549-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45F9C)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801DB000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 29/07/2011 08:03:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-29608-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA7580)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC002FDE0, 0x5E7D3867, 0x40004CE0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Après son analyse Voila ce qu'il me donne et comme je comprends moyen l'anglais je la poste ici
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 26/08/2011 12:12:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x1A (0x41287, 0x30004C, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: Unknown .
Google query: Unknown MEMORY_MANAGEMENT
On Thu 25/08/2011 00:56:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082511-29406-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x80679)
Bugcheck code: 0x4E (0x7, 0x6ADBC, 0x6ADA9, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 24/08/2011 07:43:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082411-28033-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE34)
Bugcheck code: 0x1A (0x41284, 0xFFFFFFFF87D80001, 0x242, 0xFFFFFFFF88A00000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 31/07/2011 15:36:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073111-27549-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45F9C)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801DB000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 29/07/2011 08:03:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-29608-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA7580)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC002FDE0, 0x5E7D3867, 0x40004CE0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Après son analyse Voila ce qu'il me donne et comme je comprends moyen l'anglais je la poste ici
soulsy
Messages postés
2739
Date d'inscription
dimanche 1 mai 2011
Statut
Membre
Dernière intervention
21 juillet 2017
366
28 août 2011 à 18:26
28 août 2011 à 18:26
Ok, tu n'as pas répondu à mon autre question :
Tu as installé un nouveau matériel ou logiciel depuis que tu as ces problèmes ?
Fais un test de ta mémoire vive :
https://www.commentcamarche.net/informatique/composants/1437-tester-la-memoire-vive-ram-d-un-ordinateur-avec-memtest86/
Tu as installé un nouveau matériel ou logiciel depuis que tu as ces problèmes ?
Fais un test de ta mémoire vive :
https://www.commentcamarche.net/informatique/composants/1437-tester-la-memoire-vive-ram-d-un-ordinateur-avec-memtest86/
Edawards
Messages postés
17125
Date d'inscription
dimanche 25 juillet 2010
Statut
Membre
Dernière intervention
21 juillet 2020
1 935
28 août 2011 à 18:27
28 août 2011 à 18:27
Bonjour,
L'écran bleu que vous mentionnez dans votre première image est généralement l'indication d'un problème de cablage SCSI ou de nappes IDE.
En général, ce type d'erreur survient quand un logiciel comme PC-Magic ou Deamon Tools est installé.
Redémarrer en mode sans échec puis désinstaller le programme en cause.
Une ré-installation du pilote RAID à partir du DVD et une vérification du disque en utilisant la commande chkdsk peut suffire à résoudre le problème :
1) Accéder à la Console de récupération.
2) Lancer cette commande : chkdsk c: /p /r
L'écran bleu que vous mentionnez dans votre première image est généralement l'indication d'un problème de cablage SCSI ou de nappes IDE.
En général, ce type d'erreur survient quand un logiciel comme PC-Magic ou Deamon Tools est installé.
Redémarrer en mode sans échec puis désinstaller le programme en cause.
Une ré-installation du pilote RAID à partir du DVD et une vérification du disque en utilisant la commande chkdsk peut suffire à résoudre le problème :
1) Accéder à la Console de récupération.
2) Lancer cette commande : chkdsk c: /p /r
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
antipolis a
Messages postés
15609
Date d'inscription
mercredi 5 novembre 2008
Statut
Membre
Dernière intervention
12 novembre 2014
2 859
8 sept. 2011 à 09:03
8 sept. 2011 à 09:03
Deux pistes à suivre :
https://www.commentcamarche.net/faq/2490-supprimer-les-adwares-publicites-intempestives-pop-up-etc
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
De quoi vous occuper un bon moment.
https://www.commentcamarche.net/faq/2490-supprimer-les-adwares-publicites-intempestives-pop-up-etc
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
De quoi vous occuper un bon moment.
tititeufteuf
Messages postés
265
Date d'inscription
mardi 12 octobre 2010
Statut
Membre
Dernière intervention
25 août 2012
5
28 août 2011 à 18:24
28 août 2011 à 18:24
T'as du faire quelque chose pour que ça donne ça, c'est obligé.
