Votre question

Crash de Pc trop souvent.. écran bleu

Tags :
  • Windows 7
  • Système d'exploitation
  • Écrans
Dernière réponse : dans Systèmes d'exploitation
2 Juin 2011 14:14:22

Bonjour,

Voilà, j'ai un problème avec mon ordinateur, il crash relativement souvent, écran bleu a répétition, enfin bref c'est le bonheur..
Je me suis penché sur la question et j'ai parcouru des tas de forum en espérant trouver LA solution mais j'avoue que j'ai essayé déjà beaucoup sans résultat significatif.

Ma config : Intel Core i5 CPU 650 @ 3.20GHz, 6.00 GB RAM, Radeon HD 3850, Carte mère : PEGATRON CORPORATION IPMIP-GS Rev 1.02, Windows 7 Edition Familiale Premium (x64) (build 7601) Service Pack 1..

Les manip que j'ai déjà essayé: memtest 86 = tout est ok, téléchargement de l'iso de windows 7 sur le site de microsoft, formatage et réinstallation de l'os dimanche dernier, windows update, j'ai mis tout les pilotes à jour, avec le site www.touslesdrivers.com et DriverMax..

Après je ne sais plus trop quoi faire..
j'ai penser à un problème de t° ou d'alimentation ?

Une maj du BIOS ?

Autres pages sur : crash ecran bleu

2 Juin 2011 14:15:32

--------------------------------------------------------------------------------
Welcome to WhoCrashed HOME EDITION v 3.01
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: KITARO
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6366023680 total
VM: 2147352576, free: 1945407488



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 02.06.2011 11:26:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060211-16036-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80002FB8B05)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
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 02.06.2011 11:26:26 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x1374B)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80002FB8B05)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\usbport.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: USB 1.1 & 2.0-Porttreiber
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 01.06.2011 22:16:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060211-12979-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0x1000000000, 0x2, 0x0, 0xFFFFF80002E994A2)
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 Wed 01.06.2011 05:49:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060111-15210-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF80000000010, 0x0, 0xFFFFF880051E8105, 0x0)
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 Mon 30.05.2011 11:59:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053011-19843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FCD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 Sun 29.05.2011 18:52:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-30217-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FDC5A1, 0xFFFFF88008A18160, 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 Sun 29.05.2011 18:06:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-33743-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002CA9E74)
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 29.05.2011 18:02:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-34101-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00A416250, 0xFFFFF8A00A416250, 0x5000001)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 Sun 29.05.2011 10:45:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-19843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028FFC5F, 0xFFFFF88004056150, 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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

9 crash dumps have been found and analyzed.
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.
m
0
l
2 Juin 2011 14:22:50

Ha ben justement un nouveau tout frais :

On Thu 02.06.2011 12:15:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060211-13182-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFF8, 0x2, 0x0, 0xFFFFF80002EE7B7C)
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 Thu 02.06.2011 12:15:41 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: 0xA (0xFFFFFFFFFFFFFFF8, 0x2, 0x0, 0xFFFFF80002EE7B7C)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
m
0
l
a b C Ecran
a b $ Windows 7
2 Juin 2011 22:08:57

Ce sont peut-être tes barettes de mémoires qui flanchent. Essaie de récupérer de télécharger et graver System Rescue CD. Tu boot dessus et tu lance un diagnostic mémoire (memtest86+).
m
0
l
Tom's guide dans le monde
  • Allemagne
  • Italie
  • Irlande
  • Royaume Uni
  • Etats Unis
Suivre Tom's Guide
Inscrivez-vous à la Newsletter
  • ajouter à twitter
  • ajouter à facebook
  • ajouter un flux RSS