Encore cet écran bleu !

[serge152]

Bonsoir,

Depuis quelques temps j'ai et de façon très très aléatoire un écran bleu

 

 

au redémarrage de l'ordi j'obtiens le message suivant :

 

 

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

 

Informations supplémentaires sur le problème :

BCCode: 100000b8

BCP1: FFFFFA80046C3A20

BCP2: FFFFF880009EEF80

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\042111-58874-01.dmp

C:\Users\Serge\AppData\Local\Temp\WER-103491-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

 

et après analyse avec whocraseh :

 

System Information (local)

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

 

computer name: PC-DE-SERGE

windows version: Windows 7 Service Pack 1, 6.1, build: 7601

windows dir: C:\Windows

CPU: AuthenticAMD AMD Phenom 8250e Triple-Core Processor AMD586, level: 16

3 logical processors, active mask: 7

RAM: 4293451776 total

VM: 2147352576, free: 1892098048

 

 

 

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

Crash Dump Analysis

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

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Thu 21/04/2011 18:43:30 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042111-58874-01.dmp

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

Bugcheck code: 0x100000B8 (0xFFFFFA80046C3A20, 0xFFFFF880009EEF80, 0x0, 0x0)

Error: CUSTOM_ERROR

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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/04/2011 18:43:30 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: 0xB8 (0xFFFFFA80046C3A20, 0xFFFFF880009EEF80, 0x0, 0x0)

Error: ATTEMPTED_SWITCH_FROM_DPC

Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.

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/04/2011 06:45:01 GMT your computer crashed

crash dump file: C:\Windows\Minidump\042111-32198-01.dmp

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

Bugcheck code: 0x100000B8 (0xFFFFFA80046AB040, 0xFFFFF8800336DF80, 0x0, 0x0)

Error: CUSTOM_ERROR

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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 18/04/2011 19:05:52 GMT your computer crashed

crash dump file: C:\Windows\Minidump\041811-35833-01.dmp

This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1EA08)

Bugcheck code: 0x100000B8 (0xFFFFFA80046BC040, 0xFFFFF8800336DF80, 0x0, 0x0)

Error: CUSTOM_ERROR

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics Kernel

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 Fri 25/03/2011 02:01:14 GMT your computer crashed

crash dump file: C:\Windows\Minidump\032511-33072-01.dmp

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

Bugcheck code: 0x100000B8 (0xFFFFFA80046F1690, 0xFFFFF8800336DF80, 0x0, 0x0)

Error: CUSTOM_ERROR

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

 

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

Conclusion

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

 

5 crash dumps have been found and analyzed.

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.

 

 

j'ai mis tous mes pilotes à jour

ce problème est aléatoire ! et l'ordi est très souvent allumé et utilisé il peut se passer plusieurs semaines sans crash !

par contre si je veux installer le controle parental de windows live le crash arrive à 45% de l'installation !!!

 

Pourriez-vous m'aider ??? svp !!!

[serge83]

bonsoir serge152,

 

Possibly this problem is caused by another driver which cannot be identified at this time

 

peut etre faire le point sur tout les drivers installés/mis a jour ces dernieres semaines...

 

point de restauration plus ancien?

 

pour windows live désinstaller complètement cette application redémarrer et réessayer...

 

sinon memtest pour les mémoires... http://www.sospc-en-ligne.com/tutoriaux-memtest.html

 

bon essais