Ecran bleu

Fermé
Utilisateur anonyme - 22 févr. 2014 à 12:20
 Utilisateur anonyme - 9 mars 2014 à 21:58
Bonjour, j'ai toujours un écran bleu et j'aimerais savoir d'où il vient avec WhoCrashed j'ai ça.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 22/02/2014 10:20:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-17269-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9ED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002FC9ED, 0xFFFFF88008B5C110, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.

Merci.

A voir également:

1 réponse

Utilisateur anonyme
23 févr. 2014 à 19:35
d'autre pfff

On Sun 23/02/2014 18:32:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022314-7347-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x27C124)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600035C124, 0xFFFFF8800ABDFA10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.



On Sun 23/02/2014 11:42:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022314-6552-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4283)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000E4283, 0xFFFFF88008A0C000, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.
0
Utilisateur anonyme
25 févr. 2014 à 10:04
encore un c'est vraiment chiant.

On Tue 25/02/2014 08:59:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022514-8845-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9ED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600023C9ED, 0xFFFFF8800916E110, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.
0
Utilisateur anonyme
9 mars 2014 à 21:58
pas de réponse :s j'en es toujours pff.
0