Écran bleu

[jedi81]

Hello à tous...

 

J'ai fréquemment des blue screens. Je voulais savoir comment trouver la cause du problème, en ayant réinstaller plusieurs fois les drivers...

 

Merci pour votre aide.

[papyreunion]

Bonjour,

 

si tu veux de l'aide il faut donner plus de précisions : message du blue screen

 

mettez la configuration de votre PC (Système d'exploitation, antivirus, firewall, processeur, ram...) voir ►Solution rapide à vos problèmes - Forums Zebulon.fr

[ticlou]

Salut

En complément a la réponse de papyreunion

 

Il faut nous donner l'erreur stop 0x000000 qui apparait sur l'écran bleu

 

Amicalement

ticlou

[jedi81]

-Carte mère : Asus P8z68 Deluxe

-Processeur : Intel i7 2700K

-Ram : Corsair DDR3 1600Mhz 16GB (4x4)

-Carte Graphique : EVGA GTX 570 HD 2560 MB

-1er disque dur : Crossair Force Series 3

90 Gb, Sata3,

-2ème disque dur : Samsung Spinpoint F3

1000 GB

-Allim : FSP aurum gold 700W

-Refroidissement : Corsair Hydro Series H80

-Clavier : Logitech G19

-Souris : Saitek Cyborg rat9

-imprimante : Hp photosmart Premium

-Anitivirus : Norton internet security 2012

- Microsoft Office Famille

-clé wifi : Netgear wna3100

-windows 7 édition familiale

 

 

 

Pour les rapports :

 

Signature du problème :

Nom d’événement de problème: BlueScreen

Version du système: 6.1.7601.2.1.0.768.3

Identificateur de paramètres régionaux: 4108

 

Informations supplémentaires sur le problème :

BCCode: d1

BCP1: 0000000000000000

BCP2: 0000000000000006

BCP3: 0000000000000008

BCP4: 0000000000000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

 

Fichiers aidant à décrire le problème :

C:\Windows\Minidump\051412-8673-01.dmp

C:\Users\jedi\AppData\Local\Temp\WER-24117-1.sysdata.xml

 

Lire notre déclaration de confidentialité en ligne :

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

 

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :

C:\Windows\system32\fr-FR\erofflps.txt

 

 

 

 

 

 

 

 

 

 

 

Signature du problème :

Nom d’événement de problème: BlueScreen

Version du système: 6.1.7601.2.1.0.768.3

Identificateur de paramètres régionaux: 4108

 

Informations supplémentaires sur le problème :

BCCode: 1000007e

BCP1: FFFFFFFFC0000005

BCP2: FFFFF88002CEE44C

BCP3: FFFFF8800CE997A8

BCP4: FFFFF8800CE99000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

 

Fichiers aidant à décrire le problème :

C:\Windows\Minidump\051412-8814-01.dmp

C:\Users\jedi\AppData\Local\Temp\WER-23072-0.sysdata.xml

 

Lire notre déclaration de confidentialité en ligne :

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

 

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :

C:\Windows\system32\fr-FR\erofflps.txt

 

 

 

 

Signature du problème :

Nom d’événement de problème: BlueScreen

Version du système: 6.1.7601.2.1.0.768.3

Identificateur de paramètres régionaux: 4108

 

Informations supplémentaires sur le problème :

BCCode: 1e

BCP1: FFFFFFFFC0000005

BCP2: FFFFF8800373C370

BCP3: 0000000000000000

BCP4: 0000000000000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

 

Fichiers aidant à décrire le problème :

C:\Windows\Minidump\051512-8502-01.dmp

C:\Users\jedi\AppData\Local\Temp\WER-24008-0.sysdata.xml

 

Lire notre déclaration de confidentialité en ligne :

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

 

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :

C:\Windows\system32\fr-FR\erofflps.txt

 

 

 

 

Signature du problème :

Nom d’événement de problème: BlueScreen

Version du système: 6.1.7601.2.1.0.768.3

Identificateur de paramètres régionaux: 4108

 

Informations supplémentaires sur le problème :

BCCode: 1000007e

BCP1: FFFFFFFFC0000005

BCP2: FFFFF8800617AFF3

BCP3: FFFFF88002593558

BCP4: FFFFF88002592DB0

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

 

Fichiers aidant à décrire le problème :

C:\Windows\Minidump\051512-8470-01.dmp

C:\Users\jedi\AppData\Local\Temp\WER-24117-1.sysdata.xml

 

Lire notre déclaration de confidentialité en ligne :

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

 

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :

C:\Windows\system32\fr-FR\erofflps.txt

 

Voilà si il manque qqch faites moi signe merci en tout cas pour votre aide

[ticlou]

Salut

Il faudrait télécharger Whocrashed pour identifier la cause du problème.

 

Voir ici la procédure WhoCrashed

 

Amicalement

ticlou

[jedi81]

Salut

Il faudrait télécharger Whocrashed pour identifier la cause du problème.

 

Voir ici la procédure WhoCrashed

 

Amicalement

ticlou

 

j'ai cliqué sur ton lien et cela ne fonctionne pas...

[ticlou]

Salut

Il faut aller plus bas dans la page puis cliquer sur le lien puis dans la page qui ouvre tu descends jusqu'à Crash Analysis Tools et tu choisis

 

la version free de Wocrashed

Amicalement

ticlou

[jedi81]

j'ai installé whocrashed voilà le rapport:

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Thu 17.05.2012 17:38:32 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051712-8408-01.dmp

This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xB303)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880063AC303, 0xFFFFF88002593878, 0xFFFFF880025930D0)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics MMS

Bug check description: This indicates that a system thread 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 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 17.05.2012 10:25:17 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051712-8751-01.dmp

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

Bugcheck code: 0x3B (0xC0000096, 0xFFFFF800034D651B, 0xFFFFF8800B40D4A0, 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 Thu 17.05.2012 10:01:21 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051712-8704-01.dmp

This was probably caused by the following module: symevent64x86.sys (SYMEVENT64x86+0x1004A)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800126304A, 0xFFFFF88004B9FF40, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

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

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

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.

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: symevent64x86.sys (Symantec Event Library, Symantec Corporation).

Google query: symevent64x86.sys Symantec Corporation SYSTEM_SERVICE_EXCEPTION

 

 

 

 

On Thu 17.05.2012 09:58:50 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051712-8798-02.dmp

This was probably caused by the following module: bcmwlhigh664.sys (bcmwlhigh664+0x77A53)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800BD09A53, 0xFFFFF8800374D478, 0xFFFFF8800374CCD0)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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

product: Broadcom 802.11 Network Adapter wireless driver

company: Broadcom Corporation

description: Broadcom 802.11 Network Adapter wireless driver

Bug check description: This indicates that a system thread 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.

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: bcmwlhigh664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).

Google query: bcmwlhigh664.sys Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

 

 

 

 

On Thu 17.05.2012 09:55:37 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051712-8892-01.dmp

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

Bugcheck code: 0x3D (0xFFFFF80000B9C050, 0x0, 0x0, 0xFFFFF880064042EE)

Error: INTERRUPT_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 bug check appears very infrequently.

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 17.05.2012 09:52:11 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051712-8798-01.dmp

This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xCF44D)

Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8800F51644D, 0xFFFFF8800BFC5D60, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

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

product: NVIDIA Windows Kernel Mode Driver, Version 296.10

company: NVIDIA Corporation

description: NVIDIA Windows Kernel Mode Driver, Version 296.10

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.

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 (NVIDIA Windows Kernel Mode Driver, Version 296.10 , NVIDIA Corporation).

Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION

 

 

 

 

On Thu 17.05.2012 09:40:13 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051712-9937-01.dmp

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

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001B71B2E, 0xFFFFF8800CD7BBF0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

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 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 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 Tue 15.05.2012 17:12:55 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051512-8502-02.dmp

This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x51A477)

Bugcheck code: 0xD1 (0x4, 0x2, 0x1, 0xFFFFF8800F979477)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

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

product: NVIDIA Windows Kernel Mode Driver, Version 296.10

company: NVIDIA Corporation

description: NVIDIA Windows Kernel Mode Driver, Version 296.10

Bug check description: This indicates that a kernel-mode driver 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 296.10 , NVIDIA Corporation).

Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

 

 

 

On Tue 15.05.2012 17:04:46 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051512-8611-01.dmp

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

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003606617, 0xFFFFF880037380E8, 0xFFFFF88003737940)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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 system thread 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 Tue 15.05.2012 16:41:05 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051512-8470-01.dmp

This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20FF3)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800617AFF3, 0xFFFFF88002593558, 0xFFFFF88002592DB0)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics MMS

Bug check description: This indicates that a system thread 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 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 Tue 15.05.2012 16:35:33 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051512-8502-01.dmp

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

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800373C370, 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 Mon 14.05.2012 20:58:20 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051412-8814-01.dmp

This was probably caused by the following module: bcmwlhigh664.sys (bcmwlhigh664+0x9544C)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002CEE44C, 0xFFFFF8800CE997A8, 0xFFFFF8800CE99000)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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

product: Broadcom 802.11 Network Adapter wireless driver

company: Broadcom Corporation

description: Broadcom 802.11 Network Adapter wireless driver

Bug check description: This indicates that a system thread 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.

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: bcmwlhigh664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).

Google query: bcmwlhigh664.sys Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

 

 

 

 

On Mon 14.05.2012 18:21:30 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051412-8673-01.dmp

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

Bugcheck code: 0xD1 (0x0, 0x6, 0x8, 0x0)

Error: DRIVER_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 a kernel-mode driver 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 Wed 25.04.2012 20:01:54 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042512-8564-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)

Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880037545A8, 0xFFFFF88003753E00, 0xFFFFF88001637AE7)

Error: NTFS_FILE_SYSTEM

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

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

company: Microsoft Corporation

description: Pilote du système de fichiers NT

Bug check description: This indicates a problem occurred in the NTFS file system.

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 25.04.2012 19:42:36 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042512-8361-01.dmp

This was probably caused by the following module: idsvia64.sys (IDSvia64+0x30749)

Bugcheck code: 0xA (0xFFFFFFFF, 0x2, 0x1, 0xFFFFF800037B3539)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_19.1.0.28\Definitions\IPSDefs\20120516.001\IDSvia64.sys

product: Symantec Intrusion Detection

company: Symantec Corporation

description: IDS Core Driver

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.

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: idsvia64.sys (IDS Core Driver, Symantec Corporation).

Google query: idsvia64.sys Symantec Corporation IRQL_NOT_LESS_OR_EQUAL

[ticlou]

Salut

Quand tu parles de réinstallation de drivers, as-tu essayé différentes versions?

 

Tu as plusieurs erreurs stop, je vérifie ma banque de données et je te tiens au courant

Amicalement

ticlou

[jedi81]

Alors non pas pensé à utiliser d'autres versions

 

merci pour ton aide en tout cas.