Multiple ecran bleu
gustaflex_8
-
Utilisateur anonyme -
Utilisateur anonyme -
Bonjour,
depuis quelques temps j ai plusieurs ecran bleu qui me font relancer mon ordi. apres quelques recherches sur internet j ai telecharger le logiciel who crashed pour savoir d ou cela venait mais je ne comprend pas trop les resultats et surtout je ne sais pas comment faire pour que cela s arrette.
voila donc le rapport who crashed
System Information (local)
--------------------------------------------------------------------------------
computer name: CARO
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\windows
CPU: GenuineIntel Intel(R) Celeron(R) CPU 2.93GHz Intel586, level: 15
1 logical processors, active mask: 1
RAM: 1072283648 total
VM: 2147352576, free: 2037522432
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\windows\Minidump
Crash dumps are enabled on your computer.
On Thu 16/06/2011 18:15:16 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5C846)
Bugcheck code: 0x1A (0x41284, 0xFFFFFFFFC852D001, 0x1027, 0xFFFFFFFFC0C00000)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Thu 16/06/2011 18:05:53 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF62F)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 16/06/2011 16:59:46 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118A2B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805EFA2B, 0xFFFFFFFFB7FB4BB0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
Bug check description: This indicates that a kernel-mode program 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 which cannot be identified at this time.
On Thu 16/06/2011 16:52:09 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5C846)
Bugcheck code: 0x4E (0x99, 0xF650, 0x3, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 16/06/2011 14:08:04 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-03.dmp
This was probably caused by the following module: win32k.sys (win32k+0x9658)
Bugcheck code: 0x4E (0x99, 0x1152B, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Thu 16/06/2011 12:45:05 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1249E)
Bugcheck code: 0x1000000A (0xFFFFFFFFC0C00018, 0x1, 0x0, 0xFFFFFFFF804E949E)
Error: CUSTOM_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 16/06/2011 12:43:34 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF62F)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time
voila pour le rapport
si quelqu un pouvait m aider ca serait sympa
depuis quelques temps j ai plusieurs ecran bleu qui me font relancer mon ordi. apres quelques recherches sur internet j ai telecharger le logiciel who crashed pour savoir d ou cela venait mais je ne comprend pas trop les resultats et surtout je ne sais pas comment faire pour que cela s arrette.
voila donc le rapport who crashed
System Information (local)
--------------------------------------------------------------------------------
computer name: CARO
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\windows
CPU: GenuineIntel Intel(R) Celeron(R) CPU 2.93GHz Intel586, level: 15
1 logical processors, active mask: 1
RAM: 1072283648 total
VM: 2147352576, free: 2037522432
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\windows\Minidump
Crash dumps are enabled on your computer.
On Thu 16/06/2011 18:15:16 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5C846)
Bugcheck code: 0x1A (0x41284, 0xFFFFFFFFC852D001, 0x1027, 0xFFFFFFFFC0C00000)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Thu 16/06/2011 18:05:53 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF62F)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 16/06/2011 16:59:46 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118A2B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805EFA2B, 0xFFFFFFFFB7FB4BB0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
Bug check description: This indicates that a kernel-mode program 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 which cannot be identified at this time.
On Thu 16/06/2011 16:52:09 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5C846)
Bugcheck code: 0x4E (0x99, 0xF650, 0x3, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 16/06/2011 14:08:04 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-03.dmp
This was probably caused by the following module: win32k.sys (win32k+0x9658)
Bugcheck code: 0x4E (0x99, 0x1152B, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Thu 16/06/2011 12:45:05 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1249E)
Bugcheck code: 0x1000000A (0xFFFFFFFFC0C00018, 0x1, 0x0, 0xFFFFFFFF804E949E)
Error: CUSTOM_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 16/06/2011 12:43:34 GMT your computer crashed
crash dump file: C:\windows\Minidump\Mini061611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF62F)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time
voila pour le rapport
si quelqu un pouvait m aider ca serait sympa
A voir également:
- Multiple ecran bleu
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
8 réponses
essaye lors du démarrage de ton PC, d'appuyer sur "F8" et il te proposera plusieurs choix (Mode sans échec, démarrer Windows normalement, dernière configuration fonctionnelle, ...) choisis le choix dernière configuration fonctionnelle. ça pourrait permettre a ton PC de ne plus avoir ces écrans bleu
Signature hors charte - Supprimée par la modération
Signature hors charte - Supprimée par la modération
Salut, ntoskrnl.exe est cité un peu partout dans ton rapport or il s'agit d'un processus important dans le démarrage de Windows, voici la manip que du vas sans doute devoir effectuer mais il faut pour cela que tu ais ton CD d'installation Windows, lis bien le tuto suivant :
https://www.commentcamarche.net/faq/5583-ntoskrnl-manquant-ou-endommage
https://www.commentcamarche.net/faq/5583-ntoskrnl-manquant-ou-endommage
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
le probleme c est que c un ordinateur que l on m a donné acheter dans le commerce mais la fille n a plus les cd d installation par contre j ai encore l autocollant sur le boitier avec les numeros de licences
es ce que je peux me servir d un autre cd de windows xp que j ai sur un autre ordinateur avec ces numeros la
deuxiemement j ai tester avec une autre barrette de memoire et cela continue quand meme
es ce que je peux me servir d un autre cd de windows xp que j ai sur un autre ordinateur avec ces numeros la
deuxiemement j ai tester avec une autre barrette de memoire et cela continue quand meme
j ai retrouve un cd d installation de mon autre ordinateur qui est lui aussi un fujitsu es ce que ca peut quand meme fonctionner ??????
j ai reussi a aller au moment il faut entre la commande et ca me met impossible de creer le fichier ntkrnlp.exe
Salut, je ne peut te dire pourquoi il n'a pas voulu créer le fichier, essayons une autre méthode plutôt manuelle mais avant, effectue un sauvegarde de ton système :
- Tout d'abord, vas dans le CD d'installation Windows que tu as et tu récupère le fichier ntkrnlp.exe dans le dossier \i386 et copies le dans ton PC.
- Il va falloir que tu ailles dans le dossier C:\WINDOWS\system32 et que tu recherches ntkrnlp.exe dedans.
- En laissant la fenêtre ouverte, clique sur la barre des taches en bas sur le bureau, clique droit "Gestionnaire des taches" puis tu vas dans l'onglet "processus" tu recherches ntkrnlp.exe, tu clique dessus et tu fais terminer processus.
- Juste après cette action, échange les 2 fichiers ntkrnlp.exe et redémarre ton PC.
Au cas ou si cela ne marcherais pas, je voudrais que tu effectues une analyse antivirus sur ton PC et une analyse HijackThis, poste le rapport HijackThis sur le forum pour pouvoir l'analyser.
- Tout d'abord, vas dans le CD d'installation Windows que tu as et tu récupère le fichier ntkrnlp.exe dans le dossier \i386 et copies le dans ton PC.
- Il va falloir que tu ailles dans le dossier C:\WINDOWS\system32 et que tu recherches ntkrnlp.exe dedans.
- En laissant la fenêtre ouverte, clique sur la barre des taches en bas sur le bureau, clique droit "Gestionnaire des taches" puis tu vas dans l'onglet "processus" tu recherches ntkrnlp.exe, tu clique dessus et tu fais terminer processus.
- Juste après cette action, échange les 2 fichiers ntkrnlp.exe et redémarre ton PC.
Au cas ou si cela ne marcherais pas, je voudrais que tu effectues une analyse antivirus sur ton PC et une analyse HijackThis, poste le rapport HijackThis sur le forum pour pouvoir l'analyser.
