Bluescreen sous window 7

Bluescreen sous window 7 - Win 7 - Windows & Software

Marsh Posté le 31-05-2016 à 01:13:00    

ça fait maintenant 6 mois que j'ai des problèmes de bluescreen qui avant arrivaient 1-2 fois par semaines (la plupart du temps cela arrivait quand j'était sur facebook) mais depuis 1 semaines j'ai des bluescreen 2-3 fois par jour et ça commence a me le faire pendant que je suis en jeux ou en train de bosser(sur word) Je sais pas trop par quoi commencer pour résoudre le problème ,(je compte appeler le service client LDLC demain)  
Voici ma config:
Intel Core i3-4160 - Quad Core (3.2 GHz, Turbo 3.6 GHz)  
MSI B85-G43
Sapphire Radeon R7 260X 2GO OC ICAFE GAMING  
Seagate 7200.14 - 1 To 7200 RPM 64 Mo Serial ATA III  
Graveur DVD Super Multi double couche Samsung  
Zalman R1 - Boitier moyen tour  
LDLC BG-400 Alimentation 400W Bronze  
 
Et cela  
Signature du problème :
  Nom d’événement de problème: BlueScreen
  Version du système: 6.1.7601.2.1.0.768.3
  Identificateur de paramètres régionaux: 1036
 
Informations supplémentaires sur le problème :
  BCCode: 1000007e
  BCP1: FFFFFFFFC0000005
  BCP2: FFFFF8800261E666
  BCP3: FFFFF8800318C808
  BCP4: FFFFF8800318C060
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1
 
Fichiers aidant à décrire le problème :
  C:\Windows\Minidump\053016-21528-01.dmp
  C:\Users\Baptiste\AppData\Local\Temp\WER-66082-0.sysdata.xml
 
Lire notre déclaration de confidentialité en ligne :
  http://go.microsoft.com/fwlink/?li [...] cid=0x040c
 
Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
  C:\Windows\system32\fr-FR\erofflps.txt
 
Si vous avez une idée je suis preneur =)

Reply

Marsh Posté le 31-05-2016 à 01:13:00   

Reply

Marsh Posté le 31-05-2016 à 11:35:26    

A priori il peut y avoir deux raisons à ce BSOD :
- un driver moisi
- un problème hardware
 
Pour avoir plus d'infos, peux tu nous poster le rapport de Whocrashed ?


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
Reply

Marsh Posté le 31-05-2016 à 14:17:47    

Du coup voila le rapport de who crashed
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Tue 31/05/2016 11:56:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053116-22089-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x8666)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88006440666, 0xFFFFF8800318C808, 0xFFFFF8800318C060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Tue 31/05/2016 11:56:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athurx.sys (athurx+0x8666)  
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88006440666, 0xFFFFF8800318C808, 0xFFFFF8800318C060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
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 bug check indicates that a system thread generated an exception that the error handler did not catch.
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: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
 
 
 
On Tue 31/05/2016 11:53:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053116-15849-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x8666)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88009A19666, 0xFFFFF88004FD8808, 0xFFFFF88004FD8060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Mon 30/05/2016 22:31:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053116-14523-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x8666)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002630666, 0xFFFFF880059AF808, 0xFFFFF880059AF060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Mon 30/05/2016 17:32:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053016-18283-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x8666)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002621666, 0xFFFFF88003C60808, 0xFFFFF88003C60060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Mon 30/05/2016 15:21:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053016-21528-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x8666)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800261E666, 0xFFFFF8800318C808, 0xFFFFF8800318C060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Mon 30/05/2016 15:19:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053016-17971-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x8666)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002810666, 0xFFFFF8800318C808, 0xFFFFF8800318C060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Sun 29/05/2016 18:06:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052916-23103-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x8666)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002612666, 0xFFFFF88003185808, 0xFFFFF88003185060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Sun 29/05/2016 18:03:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052916-15553-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x8666)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88009C0B666, 0xFFFFF88003185808, 0xFFFFF88003185060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Mon 23/05/2016 21:59:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-19702-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x277CE)  
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).  
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR
 
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
10 crash dumps have been found and analyzed. 2 third party drivers have 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:  
 
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
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 with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.  
 
 
Du coup je pense faut mettre a jour les drivers mais je sais pas trop lesquel ni comment faire :/

Reply

Marsh Posté le 31-05-2016 à 15:19:25    

Toutes ces erreurs sont dues à ton Wifi.
Essaye de regarder s'il existe des drivers plus récent. Sinon réinstalle les.
 
Concernant la seule erreur due à ton GPU, tu peux faire pareil.


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
Reply

Marsh Posté le 31-05-2016 à 15:26:17    

Ou la clé Wifi est morte. ;)

Reply

Marsh Posté le 31-05-2016 à 15:28:23    

Yep.
Comme j'ai dit : driver ou hardware.
Je suis parti en mode optimiste en suppostant que le matos est bon.


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
Reply

Marsh Posté le 31-05-2016 à 15:35:03    

Okay merci Beaucoup je pense c'est la clé wifi je l'ai remis il y a peu de temps(j'ai changer mon pc de place avant il était en ethernet) et c'est depuis que je l'ai remise que mon Pc crash.après  elle est quasi neuve mais ça doit etre un problème de pilote je vais tout réinstaller et je vous tien au courant(faut que je retrouve le CD) :bounce:

Reply

Marsh Posté le 31-05-2016 à 15:55:21    

Récupère plutôt ceux à jour sur le site du constructeur de la clé.
 
As tu moyen de tester avec une autre clé, ou en rebranchant en ethernet ?
Si tu n'as plus de soucis, alors c'était bien la clé.


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed