Microsoft-Windows-Kernel-Power (Erreur Critique n 41) Plantage intempestif

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

bjr , j' ai appeller le sav et ils echangent la tablette . En esperant que cette fois ci ca sera bon. a mon avis il y a un default materiel sur les tablettes et les mises a jour ne se font pas forcement .J'ai regardé  sur l'historique de mise a jour et il y en beaucoup qui ont échoué . Merci quand meme pour toutes ces reponses.

j avais lu quelque part qu'en "overclockant" ta tablette si c'est possible peut être existe t il un prog ou astuce, je suis limite en tablette ;)

Mais dis nous ou tu en es

Ciao

Alors peut être une mise à jour du firmware, un changement de mémoire si c'est possible.

Et si cela peut t'aider...

Thank you for posting the question in Microsoft Community. As I understand, you are facing issues with the Mail app. I understand that it must be frustrating, but rest assured, we are here to help fix the issue and guide you in the right direction.

The kernel power event ID 41 error occurs when the computer is shut down, or it restarts unexpectedly. When a computer that is running Windows starts, a check is performed to determine whether the computer was shut down cleanly. If the computer was not shut down cleanly, a Kernel Power Event 41 message is generated.

Method 1:

First, I would suggest you to follow these steps and run the System maintenance troubleshooter:

a. Press Windows key + W to search Settings.

b. Type “Troubleshoot” without quotes and click on Troubleshootingin the****results displayed on the left side of the screen.

c. In the new window, click View all which is towards the left side of the screen.

d. In the list of options, click on System maintenance.

e. Click Next and follow the on-screen instructions.

Method 2:

Step A: Boot the computer in Safe modeand check if the issue persists. Follow these steps to start the computer in safe mode.

a)    Press the ‘Windows + C’ key on the keyboard.

b)    Click on Settings, More PC settings and then General.

c)    Scroll down to Advanced startup, click Restart now.

d)    Click on Troubleshoot, Advanced options, Startup Settings.

e)    Click Restart, select Enable Safe modeand then press Enter.

Note: Restart the computer to start in normal mode.

---

Step B:

If the issue does not persists in Safe Mode then perform a clean boot to check if any third party application is causing the issue, as clean boot helps in eliminating software conflicts. Follow these steps to start the computer in clean boot.

Step 1:

a) Press the ‘Windows + R’ key on the keyboard.

b) In the ‘Run’ windows type ’MSCONFIG’ and click ‘Ok’.

c) Click the ‘Boot’ tab and uncheck ‘Safe Boot’ option.

d) On the ‘General’ tab, click to select the option ‘Selective startup’, and then click to clear the optionLoad startup items check box.

e) On the ‘Services’ tab, click to select the ‘Hide all Microsoft services’ check box, and then click ‘Disable all’.

f) On the ‘Startup’ tab, click ‘Open Task Manager’.In theTask Manager windowunder**startup tab,**right click on each startup item which are enabled and select ‘Disable’.

g) Click ‘OK’, and then click Restart.

---

**Step 2: Enable half of the servicesa.**Follow steps 1a and 1b to start the System Configuration utility.

b. Click the Services tab, and then click to select the Hide all Microsoft services check box.

c. Click to select half of the check boxes in the Service list.

d. Click OK, and then click Restart.

---

Step 3: Determine whether the problem returnsIf the problem still occurs, repeat step 1 and step 2. In step 2, click to clear half of the check boxes that you originally selected in the Service list.

If the problem does not occur, repeat step 1 and step 2. In step 2, select only half of the remaining check boxes that are cleared in the Service list. Repeat these steps until you have selected all the check boxes.

If only one service is selected in the Service list, and you still experience the problem, the selected service causes the problem. Go to step 6. If no service causes this problem, go to step 4.

---

Step 4: Enable half of the Startup itemsIf no startup item causes this problem, a Microsoft service most likely causes the problem. To determine which Microsoft service may be causing the problem, repeat step 1 and step 2 without selecting the Hide all Microsoft services check box in either step.

---

Step 5: Determine whether the problem returnsIf the problem still occurs, repeat step 1 and step 4. In step 4, click to clear half of the check boxes that you originally selected in the Startup Item list.

If the problem does not occur, repeat step 1 and step 4. In step 4, select only half of the remaining check boxes that are cleared in the Startup Item list. Repeat these steps until you have selected all the check boxes.

If only one startup item is selected in the Startup Item list, and you still experience the problem, the startup item that is selected in the list is the service that is causing the problem. Go to step 6.

If no startup item causes this problem, a Microsoft service most likely causes the problem. To determine which Microsoft service may be causing the problem, repeat step 1 and step 2 without selecting the Hide all Microsoft services check box in either step.

---

Step 6: Resolve the problemAfter you determine the startup item or the service that causes the problem, contact the program manufacturer to determine whether the problem can be resolved. Or, run the System Configuration utility, and then click to clear the check box for the problem item.

---

Step 7:

Note: After you have finished troubleshooting, follow these steps to boot to normal startup:

a) Press the ‘Windows + R’ key on the keyboard.

b) In the ‘Run’ windows type ’MSCONFIG’ and click ‘Ok’.

c) On the ‘General’ tab, click the ‘Normal Startup’ option, and then click ‘OK’.

d) When you are prompted to restart the computer, click ‘Restart’.

Method 3:

If the issue is not resolved, I would suggest you to refer to the link and try to Refresh the computer:

How to restore, refresh, or reset your PC

If you are still facing the issue, please reply with more information and we will be glad to help you.

Thanks.

http://answers.microsoft.com/en-us/windows/forum/windows\_8-windows\_install/window-8-pro-crashing-due-to-kernel-power-event-41/2fe1c29a-13d5-4e1f-8ecb-0559ef95eb7e