Problème Blue Screen après réparation
Résolu
flog73
Messages postés
212
Date d'inscription
Statut
Membre
Dernière intervention
-
flog73 Messages postés 212 Date d'inscription Statut Membre Dernière intervention -
flog73 Messages postés 212 Date d'inscription Statut Membre Dernière intervention -
Salut à tous,
J'ai amené mon pc à réparer suite à de gros problèmes, formatage + réinstallation de Windows7, seulement je l'ai laisser allumer cette aprem pendant que j'était chez un ami et il m'as fait un Blue Screen Of Death... Quelqu'un pourrais m'aider ? J'en ai besoin pour finir ma préparation de mes oraux de cette semaine et si il me fait ça tout le temps ça risque d'être ennuyeux!!
voici les codes d'erreurs
STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8006E18060, 0xFFFFFA8006E18340, 0xFFFFF80003193510)
Merci d'avance,
Flo.
J'ai amené mon pc à réparer suite à de gros problèmes, formatage + réinstallation de Windows7, seulement je l'ai laisser allumer cette aprem pendant que j'était chez un ami et il m'as fait un Blue Screen Of Death... Quelqu'un pourrais m'aider ? J'en ai besoin pour finir ma préparation de mes oraux de cette semaine et si il me fait ça tout le temps ça risque d'être ennuyeux!!
voici les codes d'erreurs
STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8006E18060, 0xFFFFFA8006E18340, 0xFFFFF80003193510)
Merci d'avance,
Flo.
A voir également:
- Problème Blue Screen après réparation
- Blue screen windows 10 - Guide
- Screen whatsapp - Accueil - Messagerie instantanée
- Prime reparation - Accueil - Sauvegarde
- Blue griffon - Télécharger - HTML
- Apowersoft screen recorder - Télécharger - Capture d'écran
3 réponses
Le message d'erreur me fait penser à un problème de DD et la personne qui me l'as réparé m'as prévenu qu'il avait ramassé pourtant c'est du Western Digital, je craint de devoir changer de dd avant les exam sa m'ennuyrerait pour parler poliment :(
Essayez ce logiciiel: http://www.resplendence.com/download/whocrashedSetup.exe
Il permet d'identifier la cause des crashes.
Il permet d'identifier la cause des crashes.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 20/05/2012 12:50:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-28860-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF80000007B0E, 0x8, 0xFFFFF80000007B0E, 0x0)
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 Sun 20/05/2012 12:50:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athurx.sys (athurx+0x9BF7B)
Bugcheck code: 0x50 (0xFFFFF80000007B0E, 0x8, 0xFFFFF80000007B0E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\athurx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
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.
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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athurx.sys Atheros Communications, Inc. PAGE_FAULT_IN_NONPAGED_AREA
On Sun 20/05/2012 12:36:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-24523-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF80000007BCE, 0x8, 0xFFFFF80000007BCE, 0x0)
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.
--------------------------------------------------------------------------------
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:
athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, 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 directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 20/05/2012 12:50:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-28860-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF80000007B0E, 0x8, 0xFFFFF80000007B0E, 0x0)
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 Sun 20/05/2012 12:50:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athurx.sys (athurx+0x9BF7B)
Bugcheck code: 0x50 (0xFFFFF80000007B0E, 0x8, 0xFFFFF80000007B0E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\athurx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
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.
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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athurx.sys Atheros Communications, Inc. PAGE_FAULT_IN_NONPAGED_AREA
On Sun 20/05/2012 12:36:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-24523-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF80000007BCE, 0x8, 0xFFFFF80000007BCE, 0x0)
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.
--------------------------------------------------------------------------------
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:
athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, 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.