Espace membre :
flechePublicité

13 messages
Filtrer ok

Config récente qui crash

Salut à tous. Je m'oriente vers vous après pas mal de tests et recherches, car je ne trouve pas de solution.

Je me suis monté une config y'a environ 1 an, qui tournait très bien mais depuis 2 semaines le pc bug régulièrement et aléatoirement. Ça peut être une fatal error (BSOD), un freeze (souvent avec un son qui se met en boucle), ou de gros ralentissements. Ça arrive souvent quand je fais une activité "graphique", genre un jeu un peu gourmand (Starcraft2) ou des vidéos flash (streaming live) en plein écran. Ça n'arrive presque jamais au début d'une session, plutôt après quelques heures d'utilisation, donc au début j'ai pensé à un composant qui chauffe, par exemple la CG. Si le pc commence à planter, parfois il ne démarre même plus (il reboot avant le bios) et je dois attendre un moment pc éteint pour qu'il veuille bien se rallumer et atteindre le bios.

Seulement j'ai fait des tests et je n'ai rien trouvé :

- WhoCrashed indiquait plutôt un problème logiciel, lié à la CG, donc j'ai réinstallé proprement plusieurs pilotes différents mais ça ne change rien

- J'ai regardé la température des composants avec plusieurs logiciels (OCCT, Aida64, HWmonitor..) qui disent tous des températures inférieures à 45° sur toutes les sondes, même après des heures, quand le pc est dans une phase ou il plante toutes les 5 minutes.

- J'ai fait des stress-tests OCCT et des tests Aida64, qui fonctionnent, ça fait bizarre de voir le pc tourner à fond sans planter alors que sur un jeu ça tient 5 min.

- J'ai fait 2 MemTest différents sur cd, car le premier cd buggait au bout d'une minute en indiquant des milliers d'erreurs sur la ram, tandis que le deuxième enchaine les passes mais ne trouve rien... Contradictoire.

- Pensant à un problème d'alim j'ai vérifié le voltage, HWmonitor et OCCT donnaient ce genre de valeur :
+12V: 8,3
+5V: 5,1
+3V: 3,1
ce qui a l'air très problématique pour +12V, même impossible si j'ai bien compris, tandis que Aida64 et le bios disent des valeurs plus cohérentes :
+12V: 12,1
+5V: 5,1
+3V: 3,1
ce qui a l'air normal.

Bref, je patauge et m'égare dans toutes les directions mais je n'avance pas... N'auriez vous pas des idées pour approfondir la recherche du problème ou du composant défectueux ? J'ai l'impression d'être arrivé aux limites des logiciels comme Aida64, y'a de très belles courbes de voltage/température/utilisation etc.. pendant les stress-tests. Elles sont très stables, tout à l'air de tourner parfaitement mais pourtant le problème est la. Que faire ?

La config :

proc : i5 2500K (avec un ventirad CoolerMaster Hyper 212)
ram : 2 x 4Go DDR3 Kingston HyperX
cg : Sapphire HD 7850
alim : LDLC 500W Quality Select
cm : MSI Z77A-G45
écran LG 21.5"
dd : WD 250Go
Windows 7 64bits


Merci d'avance pour votre aide !
 
 


Mets nous un screen des températures.

Pour la ram, tu as tester chaque barrette séparément?
 
 


moi je ferai un formatage et une ré-installation complète pour commencer
Edité le 22/03/2013 à 17:18
 
 
Y'à t'il de l'overclocking dans le PC ???
 
 
Merci pour vos réponses.

- Pour la ram, non j'ai testé les deux barrettes en même temps, mais comme je l'ai dit dans mon premier message, les deux tests MemTest que j'ai fait étaient tellement contradictoires que je trouve pas ça concluant... Il faudrait peut-être que j'essaye avec un troisième CD pour être sur (ca passe sur clé usb MemTest ?).

- Le screen des températures arrive, mais tout a l'air vraiment normal : tout tourne autour de 30 ou 40° (CM, proc, GPU etc..)

- J'ai pensé à formater et réinstaller mais si le problème n'a rien à voir (par exemple problème matériel), j'ai pas trop envie de tout formater pour rien. Ça m'est déjà arrivé, c'est assez frustrant ^^

- Le PC n'est pas du tout overclocké, comme il est relativement récent et qu'il fait largement tourner ce que je veux je n'en ai pas besoin.
 
 
Quand tu test la ram, test chaque barrette séparément. En testant plusieurs barrettes ensembles, certaines erreurs peuvent être masquées.
 
 
 
voila également le rapport WhoCrashed, je sais pas si ça vaut quelque chose :




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

Crash dump directory: C:WindowsMinidump

Crash dumps are enabled on your computer.

On Thu 21/03/2013 00:42:01 GMT your computer crashed
crash dump file: C:WindowsMinidump32113-25272-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002F9F3E7)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:Windowssystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 21/03/2013 00:42:01 GMT your computer crashed
crash dump file: C:Windowsmemory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002F9F3E7)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 20/03/2013 00:51:21 GMT your computer crashed
crash dump file: C:WindowsMinidump32013-26208-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xDA (0x504, 0xFFFFF6FC40000010, 0x3D, 0x2)
Error: SYSTEM_PTE_MISUSE
file path: C:Windowssystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 20/03/2013 00:48:23 GMT your computer crashed
crash dump file: C:WindowsMinidump32013-19562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF80802F15C38, 0xC, 0x0, 0xFFFFF80002D023D9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:Windowssystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 17/03/2013 19:49:01 GMT your computer crashed
crash dump file: C:WindowsMinidump31713-14227-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x284ED
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000314ED8, 0xFFFFF8800865C6E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:Windowssystem32win32k.sys
product: Système d?exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 17/03/2013 19:42:39 GMT your computer crashed
crash dump file: C:WindowsMinidump31713-14882-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x110B79)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880049D3B79, 0xFFFFF880076C8EC8, 0xFFFFF880076C8720)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:Windowssystem32driversatikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sun 17/03/2013 14:54:54 GMT your computer crashed
crash dump file: C:WindowsMinidump31713-12230-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x7CD0B)
Bugcheck code: 0xD1 (0xD50F4EF1, 0x2, 0x1, 0xFFFFF88003E1160B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:Windowssystem32driversatikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 16/03/2013 02:45:57 GMT your computer crashed
crash dump file: C:WindowsMinidump31613-12682-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x58011369, 0x8, 0x58011369)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:Windowssystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 15/03/2013 05:18:04 GMT your computer crashed
crash dump file: C:WindowsMinidump31513-13884-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF8800D534E80, 0x1, 0xFFFFF80002FCA2CA, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:Windowssystem32ntoskrnl.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 that cannot be identified at this time.



On Fri 15/03/2013 05:17:55 GMT your computer crashed
crash dump file: C:WindowsMinidump31513-16239-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Fri 15/03/2013 04:46:45 GMT your computer crashed
crash dump file: C:WindowsMinidump31513-13244-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF880113C1958, 0x1, 0xFFFFF80002F98669, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:Windowssystem32ntoskrnl.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 that cannot be identified at this time.



On Mon 11/03/2013 01:11:00 GMT your computer crashed
crash dump file: C:WindowsMinidump31113-14898-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x30, 0x2, 0x1, 0xFFFFF80002CF1E77)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:Windowssystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 11/03/2013 01:07:18 GMT your computer crashed
crash dump file: C:WindowsMinidump31113-15475-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x100115)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004BD1115, 0xFFFFF88003EBEDC8, 0xFFFFF88003EBE620)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:Windowssystem32driversatikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sat 09/03/2013 23:52:35 GMT your computer crashed
crash dump file: C:WindowsMinidump31013-13275-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD1026)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF960000D1026)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:Windowssystem32win32k.sys
product: Système d?exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 02/03/2013 02:15:19 GMT your computer crashed
crash dump file: C:WindowsMinidump30213-15553-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR




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

18 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

atikmdag.sys (ATI Radeon Kernel Mode 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.
 
 
Bon alors ça le dit clairement:

"18 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)"


Voici mes conseils:

1 - Télécharge les derniers pilotes de ta carte graphique
2 - Télécharge Driver Sweeper
3 - Désinstalle le pilote graphique
4 - Redémarre en mode sans échec (F8 au démarrage) et passe un coup de Driver Sweeper
5 - Redémarre normalement et installe le pilote graphique à jour
6 - Redémarre et test !!


Edité le 23/03/2013 à 18:09
 
 
Merci du conseil mais j'ai déjà fait ça, avec Driver Sweeper, ça n'a rien changé. J'ai même testé plusieurs drivers différents.

Le truc c'est que des fois le pc bug sévèrement : il reboot en continu et n'arrive même pas jusqu'a l'étape du bios (ça dure 2s). Il me semble peu probable qu'un problème de driver puisse faire ça, puisque Windows ne rentre pas en compte dans cette étape, donc je cherche plutôt du côté d'un composant défectueux.

[edit] Je précise que j'ai refait plusieurs passes de MemTest86+, sur les deux barrettes séparément, et je n'ai eu aucune erreur. Une fois le processus de test a planté sur une des barrette, mais je l'ai relancé et plus rien depuis.
Edité le 23/03/2013 à 20:04
 
 
esayes un Clear CMOS et si tu arrives a la booter normalement je te recommande vivement de mettre le bios de ta carte mere a jour, j'ai la meme carte mere avec le bios 2.0 il a fallu la mettre a jour pour qu'elle puisse reconnaitre la GTX66O et le CPU également bref tente cette mise a jour vers le bios 2.9 ensuite si ça marche pas on explore d'autres pistes
 
 
moumah a écrit:
esayes un Clear CMOS et si tu arrives a la booter normalement je te recommande vivement de mettre le bios de ta carte mere a jour, j'ai la meme carte mere avec le bios 2.0 il a fallu la mettre a jour pour qu'elle puisse reconnaitre la GTX66O et le CPU également bref tente cette mise a jour vers le bios 2.9 ensuite si ça marche pas on explore d'autres pistes
Effectivement il faudrait isoler le BIOS, donc moi je dirais en "reset optimised default" du BIOS, et si ça continue tu le met à jour... Si ça continue encore, il faudra essayé la carte graphique dans un autre PC... C'est ce que je ferais si ça serait mon PC!
 
 
merci beaucoup pour les pistes, je vais tester tout ça !
 
 
     
13 messages
Filtrer ok
Vous devez être connecté pour écrire un message !

BE GEEK ! Avec Clubic Logo

flechePublicité