Ecran bleu: STOP : 0x0000000a
Fermé
Romarik74
Messages postés
4
Date d'inscription
mercredi 1 janvier 2014
Statut
Membre
Dernière intervention
17 janvier 2014
-
1 janv. 2014 à 10:50
Romarik74 Messages postés 4 Date d'inscription mercredi 1 janvier 2014 Statut Membre Dernière intervention 17 janvier 2014 - 17 janv. 2014 à 10:22
Romarik74 Messages postés 4 Date d'inscription mercredi 1 janvier 2014 Statut Membre Dernière intervention 17 janvier 2014 - 17 janv. 2014 à 10:22
A voir également:
- 0x0000000a
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran samsung - Guide
- Ecran noir pc - Guide
- Retourner ecran windows - Guide
5 réponses
Cesel45
Messages postés
13152
Date d'inscription
mardi 24 avril 2007
Statut
Contributeur
Dernière intervention
29 novembre 2023
2 813
1 janv. 2014 à 12:18
1 janv. 2014 à 12:18
Bonjour
Tu as des informations dans cette page..
https://support.microsoft.com/fr-fr/help/314063
Tu as des informations dans cette page..
https://support.microsoft.com/fr-fr/help/314063
Romarik74
Messages postés
4
Date d'inscription
mercredi 1 janvier 2014
Statut
Membre
Dernière intervention
17 janvier 2014
11 janv. 2014 à 19:20
11 janv. 2014 à 19:20
up? Personne n'a la moindre idée on dirait...
Cesel45
Messages postés
13152
Date d'inscription
mardi 24 avril 2007
Statut
Contributeur
Dernière intervention
29 novembre 2023
2 813
11 janv. 2014 à 19:37
11 janv. 2014 à 19:37
Tu n'auras pas mieux que le lien mis plus haut.
Romarik74
Messages postés
4
Date d'inscription
mercredi 1 janvier 2014
Statut
Membre
Dernière intervention
17 janvier 2014
11 janv. 2014 à 23:47
11 janv. 2014 à 23:47
Justement.
Jusqu'à ce matin...ça a recommencé. Si seulement on pouvait connaître la nature du problème.
Jusqu'à ce matin...ça a recommencé. Si seulement on pouvait connaître la nature du problème.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Romarik74
Messages postés
4
Date d'inscription
mercredi 1 janvier 2014
Statut
Membre
Dernière intervention
17 janvier 2014
17 janv. 2014 à 10:22
17 janv. 2014 à 10:22
De nouveau info avec Whocrashed:
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 17/01/2014 09:01:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011714-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x3F51)
Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFFE62EB4BA)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL
On Fri 17/01/2014 09:01:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x3F51)
Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFFE62EB4BA)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL
On Tue 14/01/2014 14:01:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011414-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x3F51)
Bugcheck code: 0xA (0x100000, 0x1B, 0x0, 0xFFFFFFFFE62E64B5)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL
Conclusion
3 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:
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.
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 17/01/2014 09:01:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011714-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x3F51)
Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFFE62EB4BA)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL
On Fri 17/01/2014 09:01:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x3F51)
Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFFE62EB4BA)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL
On Tue 14/01/2014 14:01:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011414-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x3F51)
Bugcheck code: 0xA (0x100000, 0x1B, 0x0, 0xFFFFFFFFE62E64B5)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL
Conclusion
3 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:
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.
