Se connecter / S'enregistrer

Résolu [Résolu] Des Blue Screen of Death ( ecran bleu ) ~aléatoires~

Solutions (15)
Tags :
  • Écran bleu
  • Matériel
|
Bonjour,
Présentation de la config :
CM : Asus P5QE
Proc : Intel E8500
Ram : G skill DDRAM2 4 x 1Go
CG : Asus HD5750 1Go
OS :7 x64 Home premium à jour via win update

Pour info la CG est branchée sur un ampli et l'ampli sur ma télé (52 pouces) le probleme est identique en HDMI ou VGA en direct sur la télé.

Les ecrans bleus de la mort sont systématique quand je joue à Medal of honnor et moins régulier quand je suis en mode bureautique.

ce que j'ai fait:
- vérification des HDD via le logiciel constructeur (seagate)
- démontage du ventirad et changement de pate thermique
- Maj des drivers de la carte graphique catalyst 11.1a en ayant pris le soin de désinstaller les précédents et d'utiliser drive sweeper
- réglage du mode éco de la carte graphique :

Citation :
Allez dans le centre de contrôle Catalyst et activez l'ATi Overdrive. Inutile de toucher aux fréquences. Validez et quittez le centre de contrôle.

Ensuite, allez dans C:\Users\<votre username>\AppData\Local\ATi\ACE et ouvrez le fichier Profiles.xml avec votre éditeur préféré.

Cherchez la chaine "CoreClockTarget", vous devriez tomber sur des lignes avec "Want_0", "Want_1" etc en dessous. Elles correspondent aux différentes fréquences que le driver va utiliser selon la charge de travail, la "Want_0" étant celle utilisée au repos. C'est elle qui nous intéresse. Un peu plus loin, vous avez la même chose pour la mémoire ("MemoryClockTarget") , le voltage GPU ("CoreVoltageTarget") et le voltage mémoire ("MemoryVoltageTarget").

Vous êtes libre de faire ce que vous voulez, mais histoire de minimiser la prise de risque, de régler ça vite fait et de la jouer safe, pour chaque section "blablaTarget", copiez tout simplement les valeurs de "Want_1" dans "Want_0". Elles sont normalement plus élevées et devrait permettre au GPU de travailler correctement. C'est bête et méchant mais ça marche et y'a pas à se prendre la tête. Vous pouvez taper un voltage / une fréquence sorti du chapeau si vous le souhaitez et si vous savez ce que vous faites, mais les valeurs indiquées sont celles préconisées par ATi, il n'y a donc pas de risque (si ce n'est de consommer un peu plus de courant).

ATTENTION !! Pour les 5970, du fait qu'il y a 2 GPU, il y a DEUX fois les mêmes sections (CoreClockTarget_0 pour le GPU 1 et CoreClockTarget_1 pour le GPU 2). N'oubliez pas de les modifier. Par extension, je pense que cela peut s'appliquer aussi pour les personnes ayant des cartes en CrossFire mais je ne peux pas l'affirmer, je n'ai pas le cas à la maison.

Sauvegardez vos modifications et vérifiez bien que le fichier n'ait pas été écrasé par le centre de contrôle Catalyst (si vous l'avez fermé, ça ne devrait pas arriver)

Redémarrez.


- sfc /verifyonly = pas d'erreur

Les BSOD du plus vieux au plus recents :

Citation :
A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: dxgmms1.sys

SYSTEM_SERVICE_EXCEPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff88003d1ac97, 0xfffff88008fd4fc0,
0x0000000000000000)

*** dxgmms1.sys - Address 0xfffff88003d1ac97 base at 0xfffff88003cf7000 DateStamp
0x4d3fa174

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: yk62x64.sys

KMODE_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000001e (0xffffffffc0000005, 0xfffff88002f20530, 0x0000000000000000,
0x0000000000000000)

*** yk62x64.sys - Address 0xfffff880045820f0 base at 0xfffff8800456c000 DateStamp
0x4ac07193

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

SYSTEM_SERVICE_EXCEPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff80002ad680c, 0xfffff88007784a60,
0x0000000000000000)

*** ntoskrnl.exe - Address 0xfffff80002ad1740 base at 0xfffff80002a61000 DateStamp
0x4cc791bd


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: aswTdi.SYS

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x000000d1 (0xfffffa20060e7848, 0x0000000000000002, 0x0000000000000000,
0xfffff88003b50b90)

*** aswTdi.SYS - Address 0xfffff88003b50b90 base at 0xfffff88003b4b000 DateStamp
0x4d2eba73


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: aswTdi.SYS

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x000000d1 (0xfffffaa005b9c318, 0x0000000000000002, 0x0000000000000000,
0xfffff88003d62b90)

*** aswTdi.SYS - Address 0xfffff88003d62b90 base at 0xfffff88003d5d000 DateStamp
0x4d2eba73


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: atikmdag.sys

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000050 (0xfffff8000462ad00, 0x0000000000000000, 0xfffff88004402695,
0x0000000000000002)

*** atikmdag.sys - Address 0xfffff88004132c9f base at 0xfffff8800404c000 DateStamp
0x4d372890


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: aswTdi.SYS

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x1000007e (0xffffffffc0000005, 0xfffff80001aca203, 0xfffff88001fdb3c8,
0xfffff88001fdac30)

*** aswTdi.SYS - Address 0xfffff88003bd699e base at 0xfffff88003bd0000 DateStamp
0x4d2eba73


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: atikmdag.sys

SYSTEM_SERVICE_EXCEPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff880046af695, 0xfffff8800a8e88c0,
0x0000000000000000)

*** atikmdag.sys - Address 0xfffff880046af695 base at 0xfffff880042f9000 DateStamp
0x4d372890


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: atikmdag.sys

SYSTEM_SERVICE_EXCEPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff8800445c695, 0xfffff88009e248c0,
0x0000000000000000)

*** atikmdag.sys - Address 0xfffff8800445c695 base at 0xfffff880040a6000 DateStamp
0x4d372890

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: dxgmms1.sys

SYSTEM_SERVICE_EXCEPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff88003fd3599, 0xfffff8800924efd0,
0x0000000000000000)

*** dxgmms1.sys - Address 0xfffff88003fd3599 base at 0xfffff88003fb7000 DateStamp
0x4d3fa174


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: Wdf01000.sys

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x000000d1 (0xffffffffffffffd3, 0x0000000000000002, 0x0000000000000000,
0xfffff88000f851a2)

*** Wdf01000.sys - Address 0xfffff88000f851a2 base at 0xfffff88000f4e000 DateStamp
0x4a5bc19f


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

SYSTEM_SERVICE_EXCEPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000003b (0x00000000c000001d, 0xfffff80001a9f502, 0xfffff8800a103bd0,
0x0000000000000000)

*** ntoskrnl.exe - Address 0xfffff80001a76740 base at 0xfffff80001a06000 DateStamp
0x4cc791bd


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000000a (0xfffffa8042229e04, 0x0000000000000002, 0x0000000000000000,
0xfffff80002a95d14)

*** ntoskrnl.exe - Address 0xfffff80002a85740 base at 0xfffff80002a15000 DateStamp
0x4cc791bd


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

SYSTEM_SERVICE_EXCEPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff80002d69104, 0xfffff88008876c50,
0x0000000000000000)

*** ntoskrnl.exe - Address 0xfffff80002ac5740 base at 0xfffff80002a55000 DateStamp
0x4cc791bd


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000050 (0xfffff80007a7c930, 0x0000000000000008, 0xfffff80007a7c930,
0x0000000000000002)

*** ntoskrnl.exe - Address 0xfffff80002a7d740 base at 0xfffff80002a0d000 DateStamp
0x4cc791bd


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000050 (0xfffff800033715c4, 0x0000000000000000, 0xfffff88004020cf7,
0x0000000000000000)

*** ntoskrnl.exe - Address 0xfffff80001a71740 base at 0xfffff80001a01000 DateStamp
0x4cc791bd


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: dxgmms1.sys

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x1000007e (0xffffffffc0000005, 0xfffff8800417ccf7, 0xfffff8800216d6a8,
0xfffff8800216cf10)

*** dxgmms1.sys - Address 0xfffff88004179ed3 base at 0xfffff8800415c000 DateStamp
0x4d3fa174


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: atikmdag.sys

SYSTEM_SERVICE_EXCEPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff88004c1869e, 0xfffff88006a588c0,
0x0000000000000000)

*** atikmdag.sys - Address 0xfffff88004c1869e base at 0xfffff88004862000 DateStamp
0x4d372890


Depuis (ce matin) réinstallation de l'OS avec connection internet coupée et installation du minimum et vous devinez la suite : crash en jouant à Medal of honnor.
Donc les BSOD précédents ne servent pas à grand chose :-(

rapport de whocrashed :
Citation :
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 15/02/2011 13:54:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021511-36785-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFFA0003917C40, 0x2, 0x1, 0xFFFFF80002AD36FF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 which cannot be identified at this time.


On Tue 15/02/2011 13:54:37 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: 0xA (0xFFFFFA0003917C40, 0x2, 0x1, 0xFFFFF80002AD36FF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 which cannot be identified at this time.


On Tue 15/02/2011 13:51:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021511-24772-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x4E (0x99, 0x39759, 0x2, 0x1A418)
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 Tue 15/02/2011 13:22:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021511-38251-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFAA00207FB60, 0x0, 0xFFFFF88004162395, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 which cannot be identified at this time.


Citation :
A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000050 (0xfffffaa00207fb60, 0x0000000000000000, 0xfffff88004162395,
0x0000000000000005)

*** ntoskrnl.exe - Address 0xfffff80002a74f00 base at 0xfffff80002a03000 DateStamp
0x4a5bc600


Citation :
A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

PFN_LIST_CORRUPT

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000004e (0x0000000000000099, 0x0000000000039759, 0x0000000000000002,
0x000000000001a418)

*** ntoskrnl.exe - Address 0xfffff80002ad6f00 base at 0xfffff80002a65000 DateStamp
0x4a5bc600


Citation :
A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000000a (0xfffffa0003917c40, 0x0000000000000002, 0x0000000000000001,
0xfffff80002ad36ff)

*** ntoskrnl.exe - Address 0xfffff80002acbf00 base at 0xfffff80002a5a000 DateStamp
0x4a5bc600





Prochaine étape test de la CG avec Furmark puis au démarrage de la ram avec memtest86+

Si vous avez d'autres idées, je suis preneur. Je n'ai pas trop de plantage avec Worms armaggedon en m^me temps les ressources du PC sont moins utilisés (quoique avec une banana bomb pour les connaisseurs ;)  )

Merci d'avance pour votre aide
Contenus similaires
Meilleure solution
partage
|
J ai trouvé !!

Si ça intéresse c'était les réglages de la Ram qui n était pas bon. Après avoir fait un CMOS (sans le vouloir, je n'avais pas enlevé la pile mais tout c'était mis à zéro, date,...) tout était en auto dans le bios (normal vous me direz). Et du coup
pas le bon FSB et tension incorrecte... Tout ça pour ça...

Donc les Mac c'est pas pour tout de suite ;) 

PS : Merci à CameleonBond pour ne pas m'avoir laissé alone in the dark !!!
  • Commenter cette solution |
Score
0
òh
òi
|
J ai encore une question pourquoi les tests de la Ram etaient bons ?
  • Commenter cette réponse |
Score
0
òh
òi
, IDNaute |
Meilleure réponse sélectionnée par Dafen@IDN.
  • Commenter cette réponse |
Score
0
òh
òi
, Hardware (collector) |
mac t'aurai pu avoir pareil mais c'est pas grave et les écran sont pas bleu mais noir enfin se si qu'on m'a dit :D  et enfin mac c'est pour les couil**** :D  cher c'est moche et ta mieux si tu te le monte toi même au pire acheté juste l'os
  • Commenter cette réponse |
Score
0
òh
òi
|
Moi aussi je pense a une CG defectueuse mais une question sur la windowserie qui serait sans licence ou impropre me laisse franchement sans voix... vu le tarif exhorbitant, le mini c'est que ça ne vienne pas de là... mais dans le doute il va y avoir du super grub et une nouvelle install avec du ubuntu ça faisait longtemps qu'il n'y avait pas eu une distrib de linux sur ma Put*** de Connerie (pourquoi j'ai pas acheté un mac ;)  ) En fait j'ai les nerfs d'avoir claqué autant de tunes dans un truc foireux. Il n'y a évidemment aucune envie de troller ni de bouler qui que ce soit! Mon pere à la même CG (marque et modele) et n 'a aucun probleme (nous jouons au même jeux!!!). Ce qui de fait me laisse tres perplexe d'ou ma venu sur le fofo.
  • Commenter cette réponse |
Score
0
òh
òi
, Hardware + (collector) |
a ton stades je pense plutot a une CG défectueuse :/ 
  • Commenter cette réponse |
Score
0
òh
òi
|
200 euros pieces et vu les emmerdes j aurai du choisir mandriva ou autres! au moins j aurai eu des emmerdes gratuits... le prochain matos sera un mac pro au moins pas autant de prolemes
  • Commenter cette réponse |
Score
0
òh
òi
, IDNaute |
To OS, il est legal?
Prpre?
  • Commenter cette réponse |
Score
0
òh
òi
|
Après install des derniers driver toujours le même probleme.
  • Commenter cette réponse |
Score
0
òh
òi
|
J'ai trois sorties sur la carte graphique une dvi une hdmi et une vga. Quand j'ai testé via la sortie vga meme topo que la prise hdmi. [Apparté on]En cours de download pour les drivers mais seulement à 25Ko/s, j'ai l'impression d'etre chez aol illimité avec un vieux modem...
  • Commenter cette réponse |
Score
0
òh
òi
, Hardware + (collector) |
bon alim OK, mais test avec des prise de CG différente si tu en a plusieurs

les pilote 11.2 sont arriver tu peut tester ;) 
  • Commenter cette réponse |
Score
0
òh
òi
|
voila le dernier rapport de whocrashed (audessus). pas de rapport bsd. Furmark en route depuis environ 30 minutes temperature 69°c et plantage... Est ce bien la CG ??
  • Commenter cette réponse |
Score
0
òh
òi
|
On Tue 15/02/2011 16:17:41 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x3BA5C2)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88004BE95C2, 0xFFFFF88008759798, 0xFFFFF88008758FF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

L heure du rapport ne correspond pas à la vraie heure...
  • Commenter cette réponse |
Score
0
òh
òi
|
Corsair modulaire 620W
  • Commenter cette réponse |
Score
0
òh
òi
, Hardware + (collector) |
salut

quel est ton alimentation ? puissance et marque ?

  • Commenter cette réponse |

Ce n'est pas ce que vous cherchiez ?

Tom's guide dans le monde
  • Allemagne
  • Italie
  • Irlande
  • Royaume Uni
  • Etats Unis
Suivre Tom's Guide
Inscrivez-vous à la Newsletter
  • ajouter à twitter
  • ajouter à facebook
  • ajouter un flux RSS