Ecran bleu

[tribo36]

Bonjour à tous.
Alors voilà j'ai des gros problèmes avec mon ordinateur portable(packard bell,easynote lj65). Quand je lance un jeux, mon ordi plante et j'ai un écran bleu avec des erreur différente à chaque fois:
-stop 0x0000007f(le pus fréquent)
-stop 0x0000008
-stop 0x00000024

Merci d'avance.

[tribo36]

Pour être plus précis voici mon dernier plantage:stop 0x0000007f(0x000000D 0x0000000 0x0000000 0x0000000)

[EinsteinZero]

Bonsoir

il y a peut-être un problème avec un pilotes....mettre à jour les pilotes (première erreur)

ton deuxième code Erreur est incomplet...non exploitable

ton dernier code erreur est lié a un problème disque dur...celui-ci est peut-être fatigué

ceci-dit, télécharge Whochrashed >>ici<<, lance le logiciel et poste (copier/coller) son rapport, on en saura un peu plus

[Pac428]

Bonsoir Tribo.

Je commencerais par tester la mémoire en enlevant si possible la première barrette

pour la remplacer par la seconde. Je dis ça un peu au pif, n'ayant pas la doc détaillée de ta machine.

Mais bon ce qui est sûr c'est que tu as 4 Go de mémoire, donc probablement deux barrettes.

Ce qui est sûr aussi c'est que l'erreur stop 0x0000007f correspond presque toujours à

une barrette mémoire qui est en train de rendre son billet de sortie.

Par contre charger WhoCrashed comme l'indique EZ est une très bonne idée de toutes façons.

++

[tribo36]

Ok merci je télécharge le logiciel et je poste le rapport

[tribo36]

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

computer name: THIBAUD-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4200 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3147792384 total
VM: 2147352576, free: 1957093376



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 11/06/2012 20:58:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061112-16660-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x46F6B)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntkrnlpa.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.


On Mon 11/06/2012 20:58:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KiCoprocessorError+0xAB)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe UNEXPECTED_KERNEL_MODE_TRAP




On Mon 11/06/2012 19:53:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061112-20748-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x14251)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFB66E68B8, 0xFFFFFFFFB66E6490, 0xFFFFFFFF8B0167BD)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Mon 11/06/2012 19:40:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061112-24102-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x23E5F0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C925F0, 0xFFFFFFFFB110E9F8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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 Mon 11/06/2012 19:27:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061112-28002-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9365F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82AA965F, 0xFFFFFFFFB0CD5B64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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 10/06/2012 14:55:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061012-16239-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xBA984)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF807C8750, 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 Sun 10/06/2012 13:52:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061012-16598-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0xFFFFFFFFBB1C58B1, 0xFF, 0x1, 0xFFFFFFFF828A786A)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 10/06/2012 12:16:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061012-16754-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3DBB)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF92B60DBB, 0xFFFFFFFF8C59CB30, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 Fri 08/06/2012 21:06:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060812-19484-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD9E4B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82973310, 0xFFFFFFFF9633E4AC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 Fri 08/06/2012 20:50:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060812-22573-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9D1F7)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF807C8750, 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 08/06/2012 19:52:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060812-29936-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFFFFF82686C57)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.



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

11 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:

ntkrpamp.exe

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.

[EinsteinZero]

Bonsoir

vu comme les Erreurs se baladent, je serait plutôt d'accord avec pac, cela ressemble à un composant mémoire qui lâche....

si le PC à 2 barrettes de Ram, tu devrais essayer de démarrer une seul (en alternance) afin de voir si le PC plante uniquement sur une des 2 barettes

[tribo36]

D'accords je vais essayer et je vous tient au courant.

[tribo36]

J'ai tester chacune de mes barettes et les deux font planter mon ordi.Vous croyez que les deux peuvent etre morte?

[HexCrunch]

bonne soirée
dans ce cas on va faire un petit test de tes barrettes
suis le tuto ici comment ca marche
ou ceci [url=http://www.sospc-en-ligne.com/tutoriaux-memtest.html]c'est mieux que le premier[/url]
amicalement

[tribo36]

J'ai essayé memtest86+(version usb key) et à environ 50% du test mon ordi s'éteint. J''essais encore une fois mais je pense pas que ça va marcher.

[tribo36]

J'ai réussi à utiliser memtest et aucune erreur sur mes deux barrettes(j'ai fais qu'une pass à chaque fois). Avez-vous d'autres solutions à mon problème?

[EinsteinZero]

Bonsoir

1 passe ça ne suffit pas pour que le Test soit fiable...le fait que ça plante pendant le Test c'est plutôt inquiétant et confirme le Pb matériel

[tribo36]

En fait, le test plante soit quand je test les deux barrettes en meme temps, soit quand je test une barrette sur un slot en particulier.Le problème peut-il venir de l'emplacement ou l'on met la barrette?

[EinsteinZero]

Oui, mais dans ce cas, ça voudrait dire que le connecteur à un soucis...donc un pb de carte mère ce qui est plus ennuyeux