Bonjour,
Depuis 1 mois, apparaissent des écrans bleus aléatoirement sur mon pc +- 1fois par jour (souvent au démarrage d'une applications mais parfois sans raisons particulières).
J'ai été dans le journal Windows et il détecte une "Kernel" erreur et Kernel PP.
Je dispose mon pc depuis novembre 2011 et je n'ai eu aucun problème jusqu'à ce jour.
J'ai mis à jour ma CG, windows, quelques pilotes, j'ai fais un test de la RAM et aucuns problèmes semblent apparaitrent.
Voici ma config :
DD : Hitachi Deskstar 7k1000C 500Go
Alim : Corsair Gaming Series GS700 80 PLUS
CM : ASUS P8P67 LE
Proc : Intel Core i5-2500 (3.3Ghz)
Mém : Corsair Vengeance Series 8Go (2x4Go) DDR3 1866MHz
CG: Gainward Ge-Force GTX 570 "Golden Sample" 1280 MB
J'ai lu tout les postes de ce forum mais aucuns ne m'éclairent afin de résoudre mon problème.
Je n'ai pas les moyens pour racheter chaque pièce de cette ordinateur afin de voir ce qui est déficient.
J'ai téléchargé un programme "WhoCrashed" qui explique d'ou viennent ses écrans bleus. voici sont rapport ( je suis un novice dans le domaine informatique et ces informations me sont incompréhensible) :
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 22/01/2014 21:33:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012214-19796-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9ED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600031C9ED, 0xFFFFF880046D5100, 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 Wed 22/01/2014 21:33:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!BRUSHOBJ_hGetColorTransform+0x3AC21)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600031C9ED, 0xFFFFF880046D5100, 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 Wed 22/01/2014 17:09:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012214-21559-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9ED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002FC9ED, 0xFFFFF88003A95100, 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 Mon 20/01/2014 17:28:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012014-19297-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C46E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600022C46E, 0xFFFFF88003BF4720, 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 Fri 19/10/2012 17:18:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102012-12682-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8008A82060, 0xFFFFF80000B9C4D8, 0xFFFFFA800695E2D0)
Error: DRIVER_POWER_STATE_FAILURE
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 the driver is in an inconsistent or invalid power state.
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 that cannot be identified at this time.
On Fri 29/06/2012 14:36:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062912-13603-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8008B97060, 0xFFFFF80000B9C4D8, 0xFFFFFA8009F497D0)
Error: DRIVER_POWER_STATE_FAILURE
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 the driver is in an inconsistent or invalid power state.
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 that cannot be identified at this time.
Conclusion
7 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution.
Also configuring your system to produce a full memory dump may help you.
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 vraiment besoin d'aide,merci d'avance
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
