Problème installation pilote graphique

Salut,
Le pilote référé en #3 est-il bien le AMD Catalyst(TM) Display Driver version 12.3 ?
Si c'est bien le cas, quelle serait la version précédente ?
S'il faut remplacer la 12.3 par une plus ancienne, il y aurait-il lieu de d'abord désinstaller (et comment ?) et puis de tenter le coup en installant la 10.2 ?
Cdlt.

Au cas où...
Lien de la 10.2 : https://community.amd.com/

Oui, c'est bien la version 12.3.

S'il veut tester une version plus ancienne, il peut cliquer sur "Previous Drivers and Software" à droite de la page.

Merci Destrio !
:)

Si c'est à moi que la question est posée, je te répondrai que très franchement, je n'en sais rien : Destrio5 détient l'expertise, mais pas moi. Il faudrait donc que tu donnes un écho à ses suggestions.
Ce qui a retenu mon attention dans ton sujet, c'est qu'il présente de grandes similitudes avec un autre que j'avais trouvé sur le web. Mais comme comparaison n'est pas raison, je m'étais abstenu d'intervenir (jusqu'au #8) parce que c'est la règle et parce que je ne maîtrise absolument pas le sujet.
Pour ton information et celle de Destrio5, voici le lien du topic dont je parlais :
http://www.boards.ie/vbulletin/showthread.php?p=77956724
Laisse donc Destrio5 s'exprimer à ce sujet avant de prendre une quelconque initiative et ce d'autant qu'il semble y avoir d'autres éléments à prendre en compte dans ta situation.

À++

ca marche, je vais attendre avant de changer de driver alors

Il dit quoi exactement "whocrashed" ?

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 16/04/2012 20:22:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-30888-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x4E (0x2, 0x6ACD6, 0x15FFFF, 0x1)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Mon 16/04/2012 20:22:12 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x2, 0x6ACD6, 0x15FFFF, 0x1)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Mon 16/04/2012 18:04:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-26972-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x33099)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A011AB0E00, 0xFFFFF8A011AB1100, 0x530010C)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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 Mon 16/04/2012 09:15:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-17768-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000843FC0, 0xFFFF, 0x0)
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.

Tu avais ce problème avant de formater ?

Tu as quoi comme antivirus / pare-feu ?