Ecran bleu puis re-plantage si redémarrage immédiat

Ecran bleu puis re-plantage si redémarrage immédiat - Matériels & problèmes divers - Hardware

Marsh Posté le 21-08-2016 à 17:51:11    

Bonjour à tous :hello:  
 
D'habitude je me débrouille avec mes PC, mais là je me décide à appeler à l'aide car je ne vois pas trop comment résoudre mon problème...
 
Souci :  
Mon PC plante (écran bleu) parfois en plein jeu, mais le plus souvent après la fin de session, quelques minutes après le retour au bureau Windows.  
Si je tente un redémarrage immédiat, soit il n'atteint pas l'écran de login (à nouveau écran bleu puis redémarrage en boucle), soit il fait semblant d'aboutir mais affiche une belle alternance de bandes verticales...  
En revanche, si je le laisse éteint 5 minutes, je peux ensuite redémarrer sans problème.
 
En usage hors jeu (web / bureautique / lecture vidéo essentiellement), pas de plantage à déplorer, le PC peut rester allumé plusieurs jours de suite sans souci.
 
J'ai pensé à un éventuel problème de température côté carte graphique ou CPU (surtout pour les crashs en plein jeu) donc j'ai installé Speedfan et enregistré les logs.
En jeu (Diablo III), le CPU est à 45°C, le GPU à 60°C, stables tous les deux.  
Rien de remarquable dans les dernières secondes d'enregistrement des logs.
 
 
En idle, CPU à 27°C et GPU à 34°C.
 
Mon PC est un montage maison, la base date de 2009, voici la config :  
- CM : Asus P5Q Pro
- CPU : Core 2 Duo E8400 @ 3.00 GHz,
- RAM : 4x1Go DDR2 PC2-6400 Gskill
- GPU : Sapphire Radeon HD 7850 1 Go (ajoutée en 2013)
- DD principal : SSD Crucial MX100 256 Go SATA III (ajouté en 2014)
- Boîtier Antec P182 et alim Corsair HX520W
 
Le tout tourne depuis juillet sous Windows 10 Famille (64 bits), mais mon problème existait déjà sous Windows 7 depuis quelques semaines avant la mise à jour.
Comme je faisais peu de jeu dernièrement, le problème n'était pas vraiment gênant.  
Là j'ai recommencé D3, et j'aimerais bien savoir quoi faire pour le résoudre : ça la fout mal de planter les potes en pleine faille supérieure :p
 
Une idée ?  
 
Petit complément de dernière minute :  
Antivirus : Windows Defender, à jour.  
J'ai passé un coup de AdwCleaner qui n'a rien trouvé de spécial.
Edit : drivers graphiques à jour (Radeon Crimson 15.11)


Message édité par Foerdom le 21-08-2016 à 18:00:01
Reply

Marsh Posté le 21-08-2016 à 17:51:11   

Reply

Marsh Posté le 24-08-2016 à 14:21:51    

Un petit up au cas où, j'ajoute une photo de mon écran après redémarrage.
Voici ce que j'obtiens à la place de l'écran de login de Windows 10 :
http://reho.st/thumb/self/729242c7f91d1c67738aec39df6520042f334ee8.jpg

Reply

Marsh Posté le 24-08-2016 à 14:24:24    

Salut,
 
Tu pourrais regarder quel est le processus responsable du crash avec un petit logiciel tel que "WhoCrashed" par exemple, et nous poster le rapport de crash ?


---------------
https://www.flickr.com/photos/182924845@N04/
Reply

Marsh Posté le 24-08-2016 à 14:42:27    

Yes sir !  
 
Voici les rapports pour les crashs du week-end.
 
 

Citation :

Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\WINDOWS\Minidump
 
Crash dumps are enabled on your computer.
 
On Mon 22/08/2016 21:10:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082316-11406-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VIDMM_GLOBAL::MakeOneVirtualAddressRangeNotResident+0x29)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80193993BF1, 0xFFFFD000205F5FA8, 0xFFFFD000205F57C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Mon 22/08/2016 21:10:35 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VIDMM_GLOBAL::MakeOneVirtualAddressRangeNotResident+0x29)  
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80193993BF1, 0xFFFFD000205F5FA8, 0xFFFFD000205F57C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Sun 21/08/2016 21:55:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082216-11406-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DXGALLOCATIONREFERENCE::DXGALLOCATIONREFERENCE+0x22)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801E76D0B83, 0xFFFFD000228D68E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.  
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Sun 21/08/2016 20:51:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082116-11156-01.dmp
This was probably caused by the following module: l1e62x64.sys (L1E62x64+0x6EB3)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8008FBE6EB3, 0xFFFFF80298C3BFC8, 0xFFFFF80298C3B7E0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\l1e62x64.sys
product: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
company: Atheros Communications, Inc.
description: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
Bug check description: This indicates that a kernel-mode program 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: l1e62x64.sys (Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20), Atheros Communications, Inc.).  
Google query: Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED
 
 
 
On Sun 21/08/2016 20:05:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082116-11296-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull+0xE0A85)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8024C754127, 0xFFFFD00054D76ED0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.  
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Sun 21/08/2016 14:28:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082116-11234-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidMmCompareForInsertAlignedRange+0x0)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800AEEEEF08, 0xFFFFD000215A6490, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.  
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Sun 21/08/2016 13:35:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082116-11312-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DXGALLOCATIONREFERENCE::DXGALLOCATIONREFERENCE+0x22)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006A6D4B83, 0xFFFFD00023A268E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.  
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Sat 20/08/2016 20:28:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082016-11156-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x5CF52)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96087BECF52, 0xFFFFD0009548DD50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.  
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  


 
 
Est-ce que c'est exploitable ?

Reply

Marsh Posté le 24-08-2016 à 14:49:04    

Salut, peut-être un pilote pas à jour, je commencerai par celui de la carte graphique, directement sur le site d'AMD.

Message cité 1 fois
Reply

Marsh Posté le 25-08-2016 à 10:05:26    

sebg@33 a écrit :

Salut, peut-être un pilote pas à jour, je commencerai par celui de la carte graphique, directement sur le site d'AMD.


 
J'avais déjà mis à jour, mais dans le doute j'ai tout viré avec DDU, et réinstallé le pilote minimal sur le site d'AMD.
Pas mieux, nouveau plantage après 30 minutes de jeu, mêmes symptômes.  
 
Une autre idée ?  

Reply

Sujets relatifs:

Leave a Replay

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