PC plante depuis que j'ai installé ma hd 6870

PC plante depuis que j'ai installé ma hd 6870 - Carte graphique - Hardware

Marsh Posté le 23-04-2011 à 20:54:58    

J'ai remplacé ma 8800GTS par un 6870. Parfaitement fluide dans crysis2 à 70 imps en moyenne (1920*1200)mais au bout de 10 minutes de jeux le PC fait un bluescreen. J'ai monitoré les températures et tout est plus que correct le gpu ne dépasse pas les 70°C le cpu idem. j'entend un peu l'alim mais il est largement en dessous de ses 500W (enermax) De temps en temps le pc même laissé en idle fait un bluescreen sachant qu'avant de changer la cg je pouvais passer des semaines allumé 24/7 sans faire de reboots.  :cry:  
J'espère que c'est un problème logicielle: Mon Windows n'est pas a jour (je ne veux pas vraiment le mettre à jour...) pour l'installation j'ai désinstallé tout les drivers nvidea avant de mettre la radeon, puis j'ai mis les derniers drivers ati. :sweat:
Peut être la Vram qui n'est pas au contact de dissipateur peut poser problème...


Message édité par docdino le 23-04-2011 à 22:55:39
Reply

Marsh Posté le 23-04-2011 à 20:54:58   

Reply

Marsh Posté le 24-04-2011 à 09:02:48    

Bonjour,
télécharger 'who crashed", installez-le, lancez-le, faites "Analyse" bouton en haut à gauche.
Vous aurez les résultats sur la page courantes en déroulant vers le bas.
S'il vous dit qu'il n'y a pas de fichiers à analyser, attendez le prochain bsod et refaites l’analyse.
 
Who crashed analyse les fichiers DUMP créés par windows après un BSOD. Vous saurez quels sont les fichiers responsables.


Message édité par chermositto le 24-04-2011 à 09:03:52
Reply

Marsh Posté le 24-04-2011 à 09:05:00    

pleure pas si tu prend le temps de lire le forum , rien que dans la 1 ere page tu a 7 personne avec ton problème.
 
mais pour vérifier c'est quoi ta config complete ?


---------------
L'urbex : faire découvrir le patrimoine oublié / Mes albums urbex : https://www.flickr.com/photos/14695 [...] 5272741566 et https://www.flickr.com/photos/20070 [...] 0316987281
Reply

Marsh Posté le 24-04-2011 à 11:58:37    

ma config:
boitier p180
gigabyte sli ds4
QX6800 @2,93Ghz stable à 3,8 mais pas OC en ce moment à cause des crash
noctua NH-U12F
8 Go Kingston hyperX 6400 cl4
Samsung 500Go sata, Western digital 500 Go(memup en interne sur IDE)
enermax liberty 500w
Dell 24 WFP
SAPHIRE HD 6870 1go
 
J'ai passé mon anti-vir commodo sur paranoia et ça fait 12 heures que je n'ai plus de crash. ce mode bloque les applications en arrière plan de W7 qui pourrai bugger ainsi que d'éventuelles malwares. à voire si ça règle définitivement le problème.  
J'avais essayé de lire le fichier dump directement et j'avais abandonné cette idée. Merci pour le "who crashed" qui devrai me le décripter  :)


Message édité par docdino le 24-04-2011 à 21:09:58
Reply

Marsh Posté le 24-04-2011 à 21:09:33    

windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Extreme CPU Q6800 @ 2.93GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8589467648 total
VM: 2147352576, free: 1987391488
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Sat 23/04/2011 18:27:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042311-16442-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xA2C3, 0xA2C5000145A6)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Sat 23/04/2011 14:33:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042311-17253-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB9570, 0xFFFFF8800CC4EE00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Sat 23/04/2011 10:07:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042311-19156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x1AC3, 0x1AC5000035A6)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Fri 22/04/2011 19:32:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042211-17784-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x1B0F, 0x1B090000363E)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Thu 21/04/2011 20:07:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042111-25474-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x1B03, 0x1B0500003626)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
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 17/04/2011 01:41:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041711-65988-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xA5AA, 0xA5AD00014B74)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Sat 16/04/2011 09:23:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041611-30466-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x156354)  
Bugcheck code: 0x116 (0xFFFFFA800897C4E0, 0xFFFFF8801002F354, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.  
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: nvlddmkm.sys .  
Google query: nvlddmkm.sys VIDEO_TDR_ERROR
 
 
 
 
On Sat 16/04/2011 09:05:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041611-31793-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA800765A028, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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 which cannot be identified at this time.  
 
 
On Sat 16/04/2011 09:00:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041611-32307-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA800780E028, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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 which cannot be identified at this time.  
 
 
On Sat 16/04/2011 08:56:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041611-30061-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007BA4028, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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 which cannot be identified at this time.  
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
10 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:  
 
nvlddmkm.sys  

Reply

Marsh Posté le 24-04-2011 à 21:12:03    

peut etre un conflit avec le driver Nvidia qui n'est apparemment pas complètement désinstallé. Mais je ne trouve rien en cherchant dans le disque dur.
 
ntoskrnl.exe plante=> un processus critique dans le cycle de botte-vers le haut de votre ordinateur (?)  
nvlddmkm.sys plante => driver nvidea video
hal.dll => sert dans le boot?


Message édité par docdino le 24-04-2011 à 21:30:37
Reply

Marsh Posté le 24-04-2011 à 22:08:40    

Faut absolument que tu désinstalles le reste des drivers nvidia avec ceci:
http://downloads.guru3d.com/Guru3D [...] d1655.html
Procédure:
- Désinstalle les drivers nVidia (NVIDIA driver + NVIDIA PhysX + NVIDIA Stereoscopic 3D driver).
- télécharge Driver Sweeper
- redémarre windows en mode sans échec
- installe Driver Sweeper
- Lance Driver Sweeper
- sélectione les applications à nettoyer (nVidia display + nVidia Physx) clique sur "Analyse" puis "clean"
- A l'invitation, redémarre Windows
- Par la suite la console s'ouvre au redémarrage et propose d'effacer les fichier qui se trouve sur C:
- Elimine le reste des composants sur C:\NVIDIA


Message édité par Profil supprimé le 24-04-2011 à 22:11:11
Reply

Sujets relatifs:

Leave a Replay

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