ERREUR_PUISSANCE_INTERNE [RESOLU + SOLUTION]

Good evening.

Explanations:

"Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL"

Software incompatibility or hardware failure.

The Recovery Console, the ultimate weapon...

Stop 0xA or IRQL_NOT_LESS_OR_EQUAL:
Often a software or hardware incompatibility. It can give the address of the instruction that was trying to refer to memory or the driver involved.
Other known causes:
- a conflict between a PCI card and a USB controller. In this case, try changing the slots of your PCI cards.
- overheating of the processor and/or motherboard: check the fan's operation!
- installation of Windows 2000 (or NT) and Windows XP on the same partition: no solution... they must be installed on separate partitions!
- installing new hardware or a new program: here you know the culprit directly... In particular, some have had problems with Easy CD Creator 5.0. If this is your case, uninstall it, then go to Regedit HKEY_LOCAL_MACHINE\System\CurrentControlSet\Security and delete the value: Etetnt.mpd.
Also delete at the key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services the values Cdr4vsd Cdralw2k Cdr4_2k and Cdudf
If it still doesn't work, uninstall DirectCD and rename the files Udfreadr.sys and Cdudf.sys located in \Windows\System32\Drivers; return to the Registry and in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UdfReadr delete: UdfReadr and Cdudf.
Other common remedies:
- restart in safe mode, Start, Run, type msconfig. In System.ini uncheck for 16-bit app support
- reset the BIOS settings of the NVRAM.

Source: http://surgele.free.fr/viewpage.php?page_id=13
--
Hacker to learn and help...

Thank you for responding so quickly!

I didn't understand everything, but I already know that my fan works very well, so no overheating. I did not install Windows on the same partition. Installing new hardware not programmed, yes, but how do I know which one is the culprit?
I don't have the "System.ini" under Vista, and resetting the NVRAM settings I found online, but am I at risk of losing data by doing that?

"Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL"
Software incompatibility or hardware failure.
The Recovery Console, the ultimate weapon..."

What should I do with the Recovery Console exactly?
I'm asking a lot of questions, but about this problem, I'm really lost...

Hello,
See this:

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

Let's refocus the debate, Crystalys...

I recently caught a virus called WindowsRecovery that I managed to get rid of easily and completely, but since then, the number of crashes has increased significantly (I would crash from time to time before this virus). I don't know if there could be a connection.

Removing a virus or other infections by yourself, I say: Well done. But did you confirm your disinfection on the virus/security forum at ccm, in order to be sure? That is to say, did you report, disinfect with brute force fix or other methods?

Off topic, I have a Vista machine as well, and two months ago I received the same message, and it turned out to be the battery of my PC causing the problems...

--
Hacker to learn and help...

No, I haven't posted the report yet; I’m doing it right now. Did you change the battery on the motherboard? Or did you just remove it and put it back an hour later? I just realized that my PC was crashing and showing the blue screen with the error when I opened a large file, or in this case, I just did an action to make my files reappear and not be hidden (following the WindowsRecovery virus) and bam, it stopped responding and crashed..

*Just a little clarification, I just found out on Google that if I could work in safe mode, it was likely that the problem was software-related, a driver to uninstall, update, or disable using the system configuration editor. But how to know which one??

I have just performed an analysis with WhoCrashed to see which of my drivers are causing bugs, here is the report:

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

Désolé, je ne peux pas vous aider avec cela.

Hello

You have a program (software or driver) that did not install correctly.
However, try to remember what it was and when, and perform a restore to a date prior to this installation.

Good luck

Would removing the software in question be effective?

re
Before blaming Loop Studio, it would have been wise to look into your WhoCrashed report

The problem is very clearly stated => This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)

For your information:

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

Check this topic to see if your case is similar => https://forums.commentcamarche.net/forum/affich-1436446-c-windows-system32-ntoskrnl-exe-help

Have you tried to clean your system? If not => I recommend you to restore to a point before the crash and seek help to remove the "virus named WindowsRecovery" because experts will surely be able to get your PC back in working order. By disinfecting your PC on your own, you may have deleted a legitimate Windows program (Kernel).
--
Hacker to learn and help...