Ecran bleu
jane1261
Messages postés
317
Statut
Membre
-
jivef Messages postés 1024 Statut Membre -
jivef Messages postés 1024 Statut Membre -
Bonjour,
<config>Windows 7 / Chrome 22.0.1229.92</config>
J'ai de temps un temps un écran bleu, puis windows qui redémarre automatiquement. J'ai vu qu'il fallait installer whocrashed pour essayer de résoudre ce problème.
Voici le rapport généré, merci si quelqu'un peut m'aider car pour moi c'est du chinois :
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: CUPERS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6441549824 total
VM: 2147352576, free: 1914187776
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 9/10/2012 15:36:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100912-25365-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 Tue 9/10/2012 15:36:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 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.
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 7/10/2012 18:49:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100712-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF70, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 Sat 29/09/2012 09:20:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092912-16988-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8A01EE6A0C0, 0x0, 0xFFFFF80003496A10, 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 which cannot be identified at this time.
On Fri 28/09/2012 04:25:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092812-18954-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 27/09/2012 13:40:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-16083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA80183688C0, 0x2, 0x0, 0xFFFFF800035132F4)
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 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 Sun 23/09/2012 06:31:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092312-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000384EB23, 0xFFFFF880094E8150, 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 which cannot be identified at this time.
On Fri 21/09/2012 03:25:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092112-15990-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFE8A00FB5CD20, 0x0, 0xFFFFF800035AD9BC, 0x7)
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
<config>Windows 7 / Chrome 22.0.1229.92</config>
J'ai de temps un temps un écran bleu, puis windows qui redémarre automatiquement. J'ai vu qu'il fallait installer whocrashed pour essayer de résoudre ce problème.
Voici le rapport généré, merci si quelqu'un peut m'aider car pour moi c'est du chinois :
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: CUPERS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6441549824 total
VM: 2147352576, free: 1914187776
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 9/10/2012 15:36:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100912-25365-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 Tue 9/10/2012 15:36:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 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.
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 7/10/2012 18:49:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100712-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF70, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 Sat 29/09/2012 09:20:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092912-16988-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8A01EE6A0C0, 0x0, 0xFFFFF80003496A10, 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 which cannot be identified at this time.
On Fri 28/09/2012 04:25:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092812-18954-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 27/09/2012 13:40:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-16083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA80183688C0, 0x2, 0x0, 0xFFFFF800035132F4)
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 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 Sun 23/09/2012 06:31:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092312-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000384EB23, 0xFFFFF880094E8150, 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 which cannot be identified at this time.
On Fri 21/09/2012 03:25:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092112-15990-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFE8A00FB5CD20, 0x0, 0xFFFFF800035AD9BC, 0x7)
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
A voir également:
- 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
3 réponses
Salut !
Le processus ayant provoqué ce BSOD est : ntoskrnl.exe
Tu te rappel avoir installé quelque chose avant ces BSOD ?
Tu as tenté une réparation avec le CD de Seven ? Une restauration Système ?
Tu as quoi comme config' ?
Alex59380
Le processus ayant provoqué ce BSOD est : ntoskrnl.exe
Tu te rappel avoir installé quelque chose avant ces BSOD ?
Tu as tenté une réparation avec le CD de Seven ? Une restauration Système ?
Tu as quoi comme config' ?
Alex59380
Bonjour,
Je n'y connais pas grand chose... C'est quoi le BSOD ?
Si je comprends bien le rapport, le problème daterait du 21/09 ? J'ai regardé les programmes installés depuis : skype et les MAJ habituelles des programmes malwarebytes, avast, ...
J'ai effectivement tenté une restauration système il y a 2 ou 3 jours, mais sans succès. Je n'ai pas le cd de windows 7 car il était préinstallé sur le pc.
Ma config, c'est windows 7.
Merci pour ton aide, et bonne journée.
Jeannine
Je n'y connais pas grand chose... C'est quoi le BSOD ?
Si je comprends bien le rapport, le problème daterait du 21/09 ? J'ai regardé les programmes installés depuis : skype et les MAJ habituelles des programmes malwarebytes, avast, ...
J'ai effectivement tenté une restauration système il y a 2 ou 3 jours, mais sans succès. Je n'ai pas le cd de windows 7 car il était préinstallé sur le pc.
Ma config, c'est windows 7.
Merci pour ton aide, et bonne journée.
Jeannine
Quand j'ai tenté la restauration, j'avais posté un sujet sur le forum. Le voici : (suite à cela, quelqu'un m'a fait désinstaller puis réinstaller avast, et j'ai fait pareil avec chrome)
Bonjour,
Depuis quelques temps, j'ai de temps à autre un "écran bleu" écrit en anglais, qui disparait pour redémarrer le pc. Jusqu'à présent, je n'avais pas de problèmes après. Mais aujourd'hui, mon antivirus (avast) est désactivé sans que je puisse le réactiver (message : impossible de démarrer agent ... . Agent introuvable).
J'ai voulu restaurer le système, et cela est impossible ".... restauration du système n'a pu accéder à un fichier...."
En plus, je navigue en général avec google chrome, et l'icône a disparu. J'ai le message suivant : la version de ce fichier est incompatble avec la version de windows que vous utilisez...
Bonjour,
Depuis quelques temps, j'ai de temps à autre un "écran bleu" écrit en anglais, qui disparait pour redémarrer le pc. Jusqu'à présent, je n'avais pas de problèmes après. Mais aujourd'hui, mon antivirus (avast) est désactivé sans que je puisse le réactiver (message : impossible de démarrer agent ... . Agent introuvable).
J'ai voulu restaurer le système, et cela est impossible ".... restauration du système n'a pu accéder à un fichier...."
En plus, je navigue en général avec google chrome, et l'icône a disparu. J'ai le message suivant : la version de ce fichier est incompatble avec la version de windows que vous utilisez...
Bonjour,
Le BSOD est le Blue Screen Of Death, petit sobriquet donné à ce fameux écran bleu qui affuble si facilement tous les systèmes M$ Windows.
En gros, ça t'a couté cher et c'est une daube.
ntoskernel est le noyau de l'OS qui comme son nom de l'indique pas est dans la version 6.1 et pas 7...
Si tu as un problème avec ntoskernel c'est assez sérieux.
Ce peut être lié à un matériel qui ne serait pas bien reconnu par le noyau ou qui le ferait planter...
Débranche tous tes périphériques, à l'exception du clavier et de l'écran et redémarre ta machine.
Ensuite rebranche les un par un jusqu'à ce que tu reproduise le problème.
Bon courage.
Sinon, une autre option : Change de système d'exploitation et libère-toi !
A bientôt.
Jonas.
Le BSOD est le Blue Screen Of Death, petit sobriquet donné à ce fameux écran bleu qui affuble si facilement tous les systèmes M$ Windows.
En gros, ça t'a couté cher et c'est une daube.
ntoskernel est le noyau de l'OS qui comme son nom de l'indique pas est dans la version 6.1 et pas 7...
Si tu as un problème avec ntoskernel c'est assez sérieux.
Ce peut être lié à un matériel qui ne serait pas bien reconnu par le noyau ou qui le ferait planter...
Débranche tous tes périphériques, à l'exception du clavier et de l'écran et redémarre ta machine.
Ensuite rebranche les un par un jusqu'à ce que tu reproduise le problème.
Bon courage.
Sinon, une autre option : Change de système d'exploitation et libère-toi !
A bientôt.
Jonas.
