INTERNAL_POWER_ERROR [RESOLU + SOLUTION]

Bonsoir.

Explications :

"Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL"

Incompatibilité logiciel ou défaillance matériel.

La Console de Récupération, l'arme ultime...

Stop 0xA ou IRQL_NOT_LESS_OR_EQUAL :
Souvent une incompatibilité logicielle ou matérielle. Elle peut donner l'adresse de l'instruction qui tentait de se référer à la mémoire ou le driver mis en cause.
Autres causes connues :
- conflit entre une carte PCI et un contrôleur USB. Dans ce cas essayes de changer d'emplacement tes cartes PCI.
- surchauffe du processeur et/ou de la carte mère : vérifier le fonctionnement du ventilateur !
- installation de Windows 2000 (ou NT) et de Windows XP sur une même partition : pas de solution... faut les installer sur des partitions séparées !
- l'installation d'un nouveau matériel ou d'un nouveau programme : là tu connais directement le coupable... En particulier certains ont eu des problèmes avec Easy CD Creator 5.0. Si c'est ton cas, désinstalles-le, ensuite Regedit HKEY_LOCAL_MACHINE\System\CurrentControlSet\Security et supprimes la valeur : Etetnt.mpd.
Supprimes également à la clé HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services les valeurs Cdr4vsd Cdralw2k Cdr4_2k et Cdudf
Si ça ne fonctionne toujours pas désinstalles DirectCD et renommes les fichiers Udfreadr.sys et Cdudf.sys placés dans \Windows\System32\Drivers ; retournes dans la Base de Registres et dans HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UdfReadr supprimes : UdfReadr et Cdudf.
Autres remèdes fréquents :
- redémarres en mode sans échec, Démarrer, exécuter, tape msconfig. Dans System.ini décoche for 16-bit app support
- réinitialisation dans le BIOS des paramètres de la NVRAM.

Source : http://surgele.free.fr/viewpage.php?page_id=13

merci de m'avoir répondu aussi rapidement !

Je n'ai pas tout compris mais je sais déjà que mon ventilateur marche très bien donc pas de surchauffe, je n'ai pas installer de windows sur une même partition, inatallation d'un nouveau matérielle non programme oui mais comment savoir lequel est coupable ?
je n'ai pas le "System.ini" sous vista, et reinitialisé les paramètres de la NVRAM j'ai trouvé sur internet mais ai-je des risques de perdre des donnés en l'effectuant ?

"Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL"
Incompatibilité logiciel ou défaillance matériel.
La Console de Récupération, l'arme ultime..."

Que doi-je faire avec la console de recuperation exactement?
Je psoe beaucoup de questions mais sur ce problème je suis vraiment pomé..

Bonjour,
Voir ceci :

http://info.solution.online.fr/solutions.informatiques-faq.erreurs-stop-windows-xp.html

Recentrons le débat Crystalys...

J'ai recensement chopé un virus nommé WindowsRecovery que j'ai réussi à virer sans soucis & parfaitement, et depuis le nombre de plantage est très fréquent (je planté de temps en temps avant ce virus) je ne sais pas s'il peut y avoir un rapport.

Éliminer un virus ou autres infections, soit-même je dis : Bravo. Mais as-tu confirmé ta désinfection sur le forum virus/sécurité de ccm, afin d'en avoir le coeur net. C'est à dire rapport, désinfection avec fix de force brute ou autres ?

Hors sujet, j'ai un vista aussi, y'a deux mois j'avais eu ce même message, et il s'agissait de la pile de mon pc qui faisait des scènes...

Non je n'ai pas encore posté le rapport, je le fais de suite alors. Tu as changé la pile sur la carte mère ? ou tu l'a juste retiré puis remise 1h plus tard ? Je viens de réaliser que mon pc plantait et affichait la page bleu contenant l'erreur quand j'ouvrais un gros fichier ou par exemple dans le cas présent, je viens de faire une manip afin que mes fichiers réapparaissent et ne soient plus des fichiers cachés (suite au virus WindowsRecovery) et hop il ne repond plus et plante..

*Petit précision, je viens de découvrir sur Google que si je pouvais travailler en mode sans echec, c'était que le problème était à priori d'ordre logiciel, un pilote à desinstaller, à mettre à jours ou à desactiver grâce à l'éditeur de configuration système. Mais comment savoir lequel ??

Je viens d'effecuter une analyse avec WhoCrashed pour voir lequel de mes driver bug, voila le rapport :

System Information (local)
--------------------------------------------------------------------------------

computer name: PC-DE-KIREN
windows version: Windows Vista Service Pack 1, 6.0, build: 6001
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) 9500 Quad-Core Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 3756670976 total
VM: 2147352576, free: 1997455360

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are disabled for your computer.

On Thu 28/04/2011 21:54:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFCFCEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 28/04/2011 12:07:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xA0 (0x1, 0x6, 0xFFFFFFFF8A85B658, 0x0)
Error: INTERNAL_POWER_ERROR
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 power policy manager experienced a fatal error.
This problem might be caused by a thermal issue.
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 28/04/2011 12:03:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFC7CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 28/04/2011 11:55:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFCBCEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 28/04/2011 11:51:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFD3CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 27/04/2011 23:21:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xA0 (0x1, 0x6, 0xFFFFFFFF8A940658, 0x0)
Error: INTERNAL_POWER_ERROR
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 power policy manager experienced a fatal error.
This problem might be caused by a thermal issue.
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 27/04/2011 21:57:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFC3CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 27/04/2011 21:53:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFD3CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 27/04/2011 20:56:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFBFCEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 27/04/2011 11:50:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFD3CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 26/04/2011 23:50:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xA0 (0x1, 0x6, 0xFFFFFFFF8A6E71E8, 0x0)
Error: INTERNAL_POWER_ERROR
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 power policy manager experienced a fatal error.
This problem might be caused by a thermal issue.
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 26/04/2011 22:33:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFCBCEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 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.

helpp

bonjour

Tu as un programme (logiciel ou pilote)qui s'est mal installé.
Par contre essaie de te souvenir quoi et quand et Fait une restauration a une date antérieur a cette installation.

courage

Supprimer le logiciel en question serait efficace ?

re
Avant d'incriminer loop studio, il aurai été judicieux de se pencher sur ton rapport de WhoCrashed

On peut lire très clairement le problème => This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)

Pour informations :

https://www.commentcamarche.net/contents/915-ntoskrnl-ntoskrnl-exe

Vois sur ce topic si ton cas est similaire => https://forums.commentcamarche.net/forum/affich-1436446-c-windows-system32-ntoskrnl-exe-help

As-tu essayé de purger ton système ? si non => Je te recommande de revenir au point de restauration avant plantage et de demander de l'aide pour la suppression "virus nommé WindowsRecovery" car les experts pourront surement remettre ton pc en état de marche. Car en désinfectant ton pc par tes soins tu as du supprimer un programme légitime de Windows (Kernel).