bonjour,
Alors hier j'ai mis les pilotes de la carte graphique à jour et ça a été le drame...soit le pc ne démarré plus du tout ( il tournait mais ne bootait pas, rien, pas d'image et pas de bip , toujours cette diode du MemOK qui clignotait ) soit, lorsqu'il parvenait a booter ( après quelques reset ) l'image plantait dès que j'essayais de bouger la souris.
Donc je ne pouvais plus rien faire ; j'ai donc décidé de formater le pc, puisque apparement la cause des problèmes était en grande partie coté pilote, cela aurait surement pas fait de mal.
Puis là en pleine installation de windows, pouf, plantage, arret sur image plus rien ne bouge.
Faut-il que je comprenne que le problème ne provient donc pas du software? mais que c'est bien un problème matériel?
PS: j'ai oublier de préciser, on ne sait jamais j'ai essayé un clearCmos, qui n'a rien donné mais plus important, j'ai essayé de booter sur un 2ème disque dur que j'avais ou il y avait un dual boot seven/linux mais sans résultats les plantages étaient toujours bien là.
J'attends vos réactions avec impatiente. Merci @++
Edit : j'ai réussi a booter sur seven de mon 2eme disque dur, enfin ! je poste le rapport de whocrashed de ce disque dur au cas ou les causes ne seraient pas les même:
- Code: Tout sélectionner
On Tue 01/02/2011 15:25:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020111-14445-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA7FFFFF9FE0, 0x2, 0x1, 0xFFFFF80002B19349)
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 Tue 01/02/2011 15:25:44 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 (0xFFFFFA7FFFFF9FE0, 0x2, 0x1, 0xFFFFF80002B19349)
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.
On Mon 31/01/2011 20:41:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013111-13041-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0079754D0, 0xFFFFF8A0079754D0, 0x5000013)
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 30/01/2011 21:46:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013111-14118-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA7FFFFF9FE0, 0x2, 0x1, 0xFFFFF80002AC3349)
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 27/01/2011 11:43:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-16473-01.dmp
This was probably caused by the following module: atipmdag.sys (atipmdag+0x38D0D7)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004C820D7, 0xFFFFF88005FF69E8, 0xFFFFF88005FF6240)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atipmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a system thread 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.
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: atipmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atipmdag.sys ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 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:
atipmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
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.
SVP j'ai vraiment besoin d'être aidé là. j'attends vos réponses.
je vais essayé de faire une analyse avec memtest sur les conseil d'einsteinzero
@++
.
pour ta vanne.