Forum-seven : Communauté francaise de Windows 7

Bonjour,

J'ai, il y a quelques jours, restaurer mon pc à son "état d'usine" car trop de bugs et de blue screen.
Mais dés les premières heures, j'ai de nouveau un blue screen. Pourtant, seuls les programmes de base sont installés et j'ai fait une analyse du système avec Malwarebytes.

Un nouveau bluescreen est apparu cet après-midi. Voilà le rapport WhoCrashed :
System Information (local)
--------------------------------------------------------------------------------

computer name: SOPHIE-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 5359386624 total
VM: 2147352576, free: 1981566976



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 11/01/2011 17:57:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011111-34133-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFD6B05C0E84B, 0x0, 0xFFFFF8000313E609, 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.


On Tue 11/01/2011 17:57:23 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: 0x50 (0xFFFFFD6B05C0E84B, 0x0, 0xFFFFF8000313E609, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 Tue 11/01/2011 12:02:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011111-18813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002E81EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



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

3 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.


Que puis-je faire pour empêcher ces bugs d'être aussi fréquents? Merci d'avance pour votre aide!

Bonjour
Vérifie la température de ton proc et fais un test de la mémoire.
@+

Bonjour,

Essaye d'utiliser ceci: http://www.nirsoft.net/utils/blue_screen_view.html

slevin a écrit :Bonjour,

Essaye d'utiliser ceci: http://www.nirsoft.net/utils/blue_screen_view.html

Salut

Peut être un peu compliqué comme outil pour un utilisateur non averti. De plus, on a déjà les infos sur les crash. Donc la solution à appliquer est bien de tester la mémoire avec l'outil windows : Panneau de configuration, système et sécurité, outils d'administration, diagnostic de mémoire windows. Choisis de tester le mémoire au redémarrage de ton ordinateur, redémarre et laisse faire.

pour la température, télécharges et exécute SIW : ftp://ce37d74f2e5cca2c870edd92195df439: ... _14288.exe

double clique sur le programme, il s’exécute sans installation. Dans la colonne de gauche sélectionne "sensors" dans la rubrique "hardwar"e et indique nous les températures relevées (CPU et GPU si dispo) sur la partie droite de la fenêtre.

@ slevin
pour les blue screen, tu as aussi "whocrashed" qui renvoies plein d'infos, mais plus facile à décrypter que BlueScreenView qui est vraiment un outil pointu.

@+

Merci pour vos conseils!

J'ai effectué le test de mémoire et rien à signaler apparemment.

Pour les températures : CPU : 33° et GPU : 50° (la plus haute est pour "Mainbord" : 59°).

Salut

C'est chaud 59° pour un chipset

quelle est ta carte mère (ou ton modèle de PC si c'est une marque

Vérifies aussi ton disque dur et tes fichiers systèmes

Pour le disque dur : ordinateur, clic droit sur ton disque c: Propriétés, onglet outils, vérifier maintenant
coches les deux options. Attention, la procédure peut être un peu longue

Pour le système : Démarrer, tous les programmes, accessoires, clic droit sur invite de commandes, choisis exécuter en tant qu'administrateur
dans la fenêtre qui s'ouvre, tapes : sfc /scannow et laisse la vérification se poursuivre

@+

bonjour, j'ai aussi le meme probleme sauf que moi je n'ai meme pas reussit à formater à son etat d'usine... quand je fais F11, ca demarre normalement et j'ai l'ecran bleu directemment !

mon probleme de base, j'arrive pas du tout à acceder à mon bureau sans que mon pc ne se reteigne avecj cette ecran bleu ...

je suis sur un pc portable hp pavilon ,
j'ai tenter de restaurer le systeme en vain, defragmenter pareil..

je voudrais donc formater le pc, mais quand je l'ai acheter à la FNAC je n'ai pas eu le CD ROM, j'y est été tout à l'heure et ils m'ont dit qu'il n'y avait pas besoin de cd il fallait faire F11 au démarrage... j'ai donc fait ça mais pareil, j'ai l'ecran bleu des que j'arrive au moment de rentrer mon mot de passe, il n'y à que en en mode sans echec que j'arrive à acceder au bureau


voilà si quelqu'un aurait une astuce car depuis 5 jours j'essaye de reparer mais en vain


voici le rapport:


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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 30/10/2010 05:04:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x6E6A0534)
Bugcheck code: 0x19 (0x22, 0xFFFFFFFF8615E000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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.
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 BAD_POOL_HEADER



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

1 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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.

BertrandB : "quelle est ta carte mère (ou ton modèle de PC si c'est une marque)" : J'ai un packard bell iextreme M5800 (je ne suis pas sure que ça réponde à ta question par contre)
J'ai vérifié le disque dur et les fichiers ainsi que la mémoire mais toujours rien

Je voudrais le rapporter en magasin vu qu'il est sous-garantie, qu'il est neuf et que je ne trouve pas la source de l'erreur mais vont-ils le reprendre à votre avis?

De plus, un bluscreen MEMORY_MANAGEMENT est apparu depuis

-> nouveau rapport Whocrashed:
System Information (local)
--------------------------------------------------------------------------------

computer name: SOPHIE-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 5359386624 total
VM: 2147352576, free: 1963118592



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 16/01/2011 16:19:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011611-17612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41287, 0x408F9, 0x0, 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 Sun 16/01/2011 16:19:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0x86161)
Bugcheck code: 0x1A (0x41287, 0x408F9, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 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 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 Tue 11/01/2011 17:57:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011111-34133-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFD6B05C0E84B, 0x0, 0xFFFFF8000313E609, 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.


On Tue 11/01/2011 12:02:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011111-18813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002E81EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



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

4 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.