Probleme crash de l'ordi et écran bleu [Résolu/Fermé]

Signaler
Messages postés
2
Date d'inscription
vendredi 6 juillet 2012
Statut
Membre
Dernière intervention
6 juillet 2012
-
Messages postés
2
Date d'inscription
vendredi 6 juillet 2012
Statut
Membre
Dernière intervention
6 juillet 2012
-
Bonjour,
Voila 3 semaines que mon ordinateur plante et redémarre après l'affichage d'un écran bleu.
J'ai donc cherché sur le forum si d'autres personnes avait le même problème, et à un moment donner à été dit d'utiliser WhoCrashed pour analyser les drivers, j'esperai que vous pourriez m'aider à comprendre se qu'il faut faire et comprendre par rapport a ce résultat, Merci d'avance !

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 06/07/2012 13:30:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070612-35459-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x7A (0xFFFFF6FC5000AC30, 0xFFFFFFFFC0000185, 0x5B3CF880, 0xFFFFF8A001586F9C)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.
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 06/07/2012 13:30:47 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt+0x7F1C0)
Bugcheck code: 0x7A (0xFFFFF6FC5000AC30, 0xFFFFFFFFC0000185, 0x5B3CF880, 0xFFFFF8A001586F9C)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 04/07/2012 20:02:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070412-33665-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x6FB8)
Bugcheck code: 0x116 (0xFFFFFA8001E4B170, 0xFFFFF88001006FB8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




On Tue 03/07/2012 15:05:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070312-21075-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x7A (0xFFFFF6FC5001B758, 0xFFFFFFFFC0000185, 0x611880, 0xFFFFF8A0036EB000)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.
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 03/07/2012 12:58:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070312-22276-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8003496B30, 0xFFFFFA8003496E10, 0xFFFFF80002D81510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 03/07/2012 11:31:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070312-26956-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF880C00000B5, 0x8, 0xFFFFF880C00000B5, 0x5)
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 02/07/2012 18:58:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070212-23368-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x7A (0xFFFFF6FC50001680, 0xFFFFFFFFC0000185, 0x34EF5880, 0xFFFFF8A0002D0000)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.
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 02/07/2012 18:15:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070212-23322-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x8D668)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002AE7668, 0xFFFFF88002FC05F8, 0xFFFFF88002FBFE50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
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 02/07/2012 17:12:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070212-27674-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x7A (0xFFFFF6FC00017178, 0xFFFFFFFFC0000185, 0x4F8CA860, 0xFFFFF80002E2FE50)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.
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 02/07/2012 11:13:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070212-19468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8003360B30, 0xFFFFFA8003360E10, 0xFFFFF80002D9C510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\070512-40622-01.dmp




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

On your computer a total of 11 crash dumps have been found. Only 10 could be 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:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, 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.

3 réponses


le probleme vient de ta carte graphique.

soit pilote soit logiciel soit connectique ou bien carte hs
Messages postés
2
Date d'inscription
vendredi 6 juillet 2012
Statut
Membre
Dernière intervention
6 juillet 2012

Pouvez vous m'indiquer comment être sur d'où sa vient ? et le réparer si possible ...