[Résolu] Problème récurrent blue screen

[sharel]

Bonjour,

voila depuis un petit moment a froid, mon pc me fait un blue screen avec un code erreur, tout se fige et il redémarre.

hier pas de blue screen mais le pc c'est figé pendant 1 min et après quand il est redevenu normal un message, en bas a droite avec écrit que le pilote d'afichage AMD ne répondais plus et a été récupéré.

Et se matin le pc est rester bloquer au démarrage sur "inizialing usb controller" puis après un redémarrage tout va bien pour l'instant.

 

J'avoue ne pas savoir si c'est problèmes sont liée alors dans le doute je viens vous demander votre aide

 

pour le blue screen, je suis aller dans l'observateur d'évènement est le problème qui apparait 12 fois, viens du Kernel-power(j'avoue ne pas savoir a quoi sa correspond), niveau Critique et l'id de l'évènement: 41

voici une copie du message:

générale

Le système a redémarré sans s’arrêter correctement au préalable. Cette erreur peut survenir si le système ne répond plus, s’est bloqué ou n’est plus alimenté de façon inattendue.

 

Détail

EventData

 

BugcheckCode 26

BugcheckParameter1 0x5003

BugcheckParameter2 0xc0802000

BugcheckParameter3 0x238b

BugcheckParameter4 0x37ef009

SleepInProgress false

PowerButtonTimestamp 0

 

j'ai pris l'initiative de faire un memtest, après 13 pass aucune erreur détecté

et un benchmark avec sandra lite 2011:

juste une erreur

<<< Rendu Vidéo (GFX) >>>

--------------------------------------------------------------------------------

 

Erreur (335): Périphériques Direct3D 11 : ATI Radeon HD

4800 Series (800 SM4.1 750MHz, 1Go

DDR5 4x900MHz, PCIe 2.00 x16) : Format

d'Affichage nécessaire non disponible.

Essayez d'actualiser les pilotes vidéo.

 

Voila si vous avez besoin de plus d'info

pour la config: processeur phenom II x4 955 black édition, carte mère asus m4a79 xtd evo, 4go de ddr3 g.skill ripjaws pc10600, carte graphique radeon HD 4870, alim be quiet straight power 500w

 

 

merci d'avance pour votre aide

[planta100]

Bonjour

essai de réinstaller les pilotes de la carte graphique ATI,

 

mais dans ta signature tu as une nvidia?

[sharel]

Merci pour ta réponse,

non j'ai bien une ati, j'ai changer entre temps et j'ai oublier de le modifier, je vais le faire de se pas

et pour les pilotes oui j'ai oublier de le précisé j'ai réinstallé tout les drivers déjà

[galimatias]

bonjour

peux tu nous mettre la copie de l'écran de Hwmonitor

 

peux tu vérifier que tous les connecteurs sont bien enfichés.

tu as quoi comme alimentation ?

 

As tu fait un chkdisk avec réparation ? Si non, peux tu en exécuté un ?

 

Cordialement

Modifié le 8 décembre 2010 par galimatias

[ticlou]

Salut sharel

Tu peux employer le logiciel Whocrashed pour avoir les données de ton écran bleu

 

site officiel

 

Resplendence Software - WhoCrashed, automatic crash dump analyzer

 

tuto et téléchargement

WhoCrashed

Amicalement

Ticlou

[sharel]

merci pour vos réponses

 

@galimatias

peux tu nous mettre la copie de l'écran de Hwmonitor

 

peux tu vérifier que tous les connecteurs sont bien enfichés.

connecteur ok

 

As tu fait un chkdisk avec réparation ? Si non, peux tu en exécuté un ?

chkdsk ok aussi

 

tu as quoi comme alimentation ?

alim be quiet straight power 500w

 

@ ticlou

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Sat 04/12/2010 16:35:00 GMT your computer crashed

crash dump file: C:\Windows\Minidump\120410-21606-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)

Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x238B, 0x37EF009)

Error: MEMORY_MANAGEMENT

file path: C:\Windows\system32\ntkrnlpa.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 04/12/2010 16:35:00 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)

Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x238B, 0x37EF009)

Error: MEMORY_MANAGEMENT

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.

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: ntkrpamp.exe .

Google query: ntkrpamp.exe MEMORY_MANAGEMENT

 

 

 

 

On Thu 02/12/2010 17:44:21 GMT your computer crashed

crash dump file: C:\Windows\Minidump\120210-19968-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x322493)

Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86797594, 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 Mon 29/11/2010 18:49:12 GMT your computer crashed

crash dump file: C:\Windows\Minidump\112910-21340-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x322493)

Bugcheck code: 0x124 (0x0, 0xFFFFFFFF867AF22C, 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 Mon 29/11/2010 17:45:18 GMT your computer crashed

crash dump file: C:\Windows\Minidump\112910-22604-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x85903)

Bugcheck code: 0x50 (0xFFFFFFFF8C00A8DC, 0x0, 0xFFFFFFFF82C1847E, 0x2)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\ntkrnlpa.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 Sun 28/11/2010 11:37:45 GMT your computer crashed

crash dump file: C:\Windows\Minidump\112810-26707-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0xBD7A3)

Bugcheck code: 0x1A (0x41284, 0xFFFFFFFFFD75E001, 0x196D, 0xFFFFFFFF97230000)

Error: MEMORY_MANAGEMENT

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 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 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 Thu 25/11/2010 07:44:17 GMT your computer crashed

crash dump file: C:\Windows\Minidump\112510-22776-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)

Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82AB7DAF)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntkrnlpa.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 Thu 18/11/2010 19:30:39 GMT your computer crashed

crash dump file: C:\Windows\Minidump\111810-19531-01.dmp

This was probably caused by the following module: tcpip.sys (tcpip+0x85E9F)

Bugcheck code: 0xA (0xFFFFFFFF8D3532A4, 0x2, 0x0, 0xFFFFFFFF82ABB93C)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\tcpip.sys

product: Système d’exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote TCP/IP

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 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 Wed 17/11/2010 17:59:48 GMT your computer crashed

crash dump file: C:\Windows\Minidump\111710-24304-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x85903)

Bugcheck code: 0x50 (0xFFFFFFFF8C00A86C, 0x0, 0xFFFFFFFF82C2E47E, 0x2)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\ntkrnlpa.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 Tue 16/11/2010 19:23:39 GMT your computer crashed

crash dump file: C:\Windows\Minidump\111610-18891-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)

Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82AA7DAF)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntkrnlpa.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 Thu 21/10/2010 16:58:04 GMT your computer crashed

crash dump file: C:\Windows\Minidump\102110-17971-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)

Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82AA7DAF)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntkrnlpa.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.

 

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

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

 

ntkrpamp.exe

 

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.

[ticlou]

Salut sharel

Tu as plusieurs erreurs, on commence par vérifier la ram

 

Tu peux vérifier la ram avec memtest

En téléchargement ici http://telechargement.zebulon.fr/memtest86.html

 

Si l'ordinateur ne fait pas le test sans planter, tu procèdes avec un cd ou sur disquette, voir le tuto ici

tuto pour booster sur disquette ou cd

Tutoriel Memtest86

 

As-tu des lecteurs virtuels ou émulation genre (Alcohol, Deamon Tool, etc.)?

Amicalement

Ticlou

Modifié le 8 décembre 2010 par ticlou

[sharel]

bonsoir

@ ticlou :

Tu peux vérifier la ram avec memtest

J'ai déjà tester la ram, je suis monté a 13 pass sans aucune erreurs

As-tu des lecteurs virtuels ou émulation genre (Alcohol, Deamon Tool, etc.)?

aucun lecteur virtuel

 

voici le nouveau blue screen de se soir, je vais finir par les collectionné si sa continue

On Thu 09/12/2010 17:57:44 GMT your computer crashed

crash dump file: C:\Windows\Minidump\120910-25256-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)

Bugcheck code: 0xD3 (0xFFFFFFFF8BBFA448, 0x2, 0x0, 0xFFFFFFFF82A8093C)

Error: DRIVER_PORTION_MUST_BE_NONPAGED

file path: C:\Windows\system32\ntkrnlpa.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Thu 09/12/2010 17:57:44 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x29D3)

Bugcheck code: 0xD3 (0xFFFFFFFF8BBFA448, 0x2, 0x0, 0xFFFFFFFF82A8093C)

Error: DRIVER_PORTION_MUST_BE_NONPAGED

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.

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: ntkrpamp.exe .

Google query: ntkrpamp.exe DRIVER_PORTION_MUST_BE_NONPAGED

 

 

[sharel]

Bonjour,

encore 2 reboot pendant que j'etait en train de jouer alors que le pc etait chaud, j'ai l'impression que sa empire et je ne sais plus ou chercher, es que en remplaçant les fichiers en cause comme ntoskrnl.exe ou même ntkrnlpa.exe et les autres, sa peut arranger le probème? je ne pense pas mais sait on jamais.

je vais faire une analyse antivirus et antimalware par précaution, j'aurai peut être du commencer par la

[Tonton]

Bonjour sharel,

 

Peux-tu stp poster un log HJT ?

Lien :

 

Ca va ns permettre d'y voir un peu plus clair !