Plantage écran bleu

[Ask to Old Man]

Bonsoir, je suis nouveau parmis vous.

J'espère ne pas me tromper d'endroit ...

J'explique mon petit soucis :

J'ai overclocker avec le programme d'Asus mon CPU.

Je suis passer de 3.50 a 4.20GHZ soudains après 2 voir 5 minutes le pc plante écrand bleu et redémarre et affiche un rapport ... J'ai éventuellement ajouter des ventilateur et il ne chauffe pas.

Voiçis la configuration :

Carte Mère : Asus m4a89gtd Pro/usb3

Processeur: Amd phenom II x4 970 black édition

Rame : Corsair vengeance 16000 2x 2GB

Alimentation : corsair Gs 700W

Carte Graphique : Saphire 6870 1GB

Ventirad : macho hr-02

HDD : caviar black 500gb + un caviar 500gb

lecteur cd : LG
Voila je pense avoir tout mis.


Je vais poster le rapport avec le programme whocrash


Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: LIO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 970 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4293058560 total
VM: 2147352576, free: 1942474752



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 3/09/2011 22:36:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090411-17144-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF82000024628, 0x0, 0xFFFFF80003156101, 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.


On Sat 3/09/2011 22:32:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090411-22027-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1E73B0)
Bugcheck code: 0xD3 (0xFFFFF960002273B0, 0x2, 0x8, 0xFFFFF80002EE93BD)
Error: DRIVER_PORTION_MUST_BE_NONPAGED
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that the system 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.
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 3/09/2011 22:23:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090411-15381-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF800031DCCE5, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 which cannot be identified at this time.


On Sat 3/09/2011 22:11:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090411-16333-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF8800BFA96F8, 0x1, 0xFFFFF8000315A9B4, 0x0)
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.


On Sat 3/09/2011 22:09:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090411-15007-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7A48)
Bugcheck code: 0x116 (0xFFFFFA80062A7010, 0xFFFFF88004407A48, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


On Sat 3/09/2011 22:09:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090411-14367-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004F198F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 3/09/2011 10:21:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-18657-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF880095B8430, 0x0, 0xFFFFF8000323D731, 0x0)
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.

On Sat 3/09/2011 03:12:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-18579-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF8800C97F856, 0x0, 0xFFFFF800031C8DB9, 0x2)
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.


On Sat 3/09/2011 02:24:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-20607-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7A48)
Bugcheck code: 0x116 (0xFFFFFA800738D010, 0xFFFFF8800437EA48, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


On Sat 3/09/2011 02:21:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-20919-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7A48)
Bugcheck code: 0x116 (0xFFFFFA8007070010, 0xFFFFF8800437AA48, 0x0, 0xD)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


On Sat 3/09/2011 02:19:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-21528-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7A48)
Bugcheck code: 0x116 (0xFFFFFA8006F414E0, 0xFFFFF88004568A48, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




On Sat 3/09/2011 02:17:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-19453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF82000024628, 0x0, 0xFFFFF80003195101, 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.


On Fri 2/09/2011 22:51:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-23259-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFFFF800000003, 0x1, 0xFFFFF80002E8C348, 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.


On Wed 31/08/2011 06:15:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083111-13884-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004F39038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 31/08/2011 06:11:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083111-15615-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7A48)
Bugcheck code: 0x116 (0xFFFFFA8006BE4010, 0xFFFFF88004207A48, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR



26 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:


Si quelqu'un pouvais m'aider svp ... 26 erreur : Minidump ...

merci. Lio.

[pierreyves258]

Wha c'est joli ça ... Tout ça un un jour
Vu que c'est le processeur et le kernel qui crashent, je pense que c'est ton overclock qui n'est pas stable ! descent le et augmente un peut la tension aux bornes du processeur (0,10V), de 3.5 a 4.2 ça fais beaucoup je trouve

[EinsteinZero]

Bonjour
bienvenu sur le forum

Joli carton en effet, vu comme les drivers s'affolent, un +1 avec Pierre Yve...plus doux avec l'OC

[Ask to Old Man]

Bonsoir,

20% d'un coup Il fût une époque ou avec ce pourcentage, tu repartais
avec les cendres de ton processeur dans ta poche...

[airlive223]

Bonsoir, merci de vôs réponse. J'ai overcloker avec le programme fournis avec la carte mère. Asus. Turbo evo


Comment faire pour augmenter a +- de 3.5 a 4 ? merci

[pierreyves258]

essaye deja d'overclocker a 3.8

[airlive223]

Re bonsoir, j'ai déjà overcloker a 3.79 toujours avec turbo evo.

De temps en temps il est stable, et de temps en temps il plante..

[EinsteinZero]

Bonsoir
essaye de mettre un poil moins si tu peux

[airlive223]

re bonsoir, merci de vos réponses.

Avec turbo evo, je peux diminuer le cpu fréquency, le cpu voltage, le cpu/nb voltage et la dram voltage.

Disons que je suis a 3.79 et que j'aimerai 3.75 " exemple " je dois diminuer qu'elle fréquence?

[psychocat]

salut ta overclocke ta carte graphique avec ?

[pierreyves258]

Avec turbo evo, je peux diminuer le cpu fréquency, le cpu voltage, le cpu/nb voltage et la dram voltage.

Disons que je suis a 3.79 et que j'aimerai 3.75 " exemple " je dois diminuer qu'elle fréquence?

Tu a as deja toucher a cpu voltage quand tu a mais cpu frequency a 4.2 ??? si non c'est normal que ce soit instable !

Je dirais qu'il faudrais essayer d’augmenter cpu frequency de 0.2 (donc a 3.7) et cpu voltage de 0.10V

[airlive223]

salut ta overclocke ta carte graphique avec ?

Non jamais

[airlive223]

Avec turbo evo, je peux diminuer le cpu fréquency, le cpu voltage, le cpu/nb voltage et la dram voltage.

Disons que je suis a 3.79 et que j'aimerai 3.75 " exemple " je dois diminuer qu'elle fréquence?

Tu a as deja toucher a cpu voltage quand tu a mais cpu frequency a 4.2 ??? si non c'est normal que ce soit instable !

Je dirais qu'il faudrais essayer d’augmenter cpu frequency de 0.2 (donc a 3.7) et cpu voltage de 0.10V

Re bonsoir, j'ai remis le bios a Zéro.

J'ai encore des bluescreen ... alors que tout est remis a Zéro :(


toutes mes pièces sont nouvelles et n'ont même pas 1 mois ... d'oû pourrait venir le soucis? ..

[psychocat]

c'est ta carte graphique qui plante depuis le début ( alim , MOBO , CG va savoir la cause ) , l'OC n'a fait qu'induire tout le monde en erreur !

[airlive223]

c'est ta carte graphique qui plante depuis le début ( alim , MOBO , CG va savoir la cause ) , l'OC n'a fait qu'induire tout le monde en erreur !

Re bonsoir, donc pour toi cela serait ma carte graphique? ..