Panne Ecran bleu "Internal power error" [résolu]

[pipistrelus]

Bonjour,

suite à un problème avec un de mes disques durs internes, j'ai modifié un peu la config de mon pc (monté de toute pièce) en rajoutant une carte PCIE-Sata pour connecter des disques durs, sauf que maintenant j'ai mon ordi qui plante (au bout de 20-30min généralement) avec un message de Windows 10 10: écran bleu "Internal power error".
J'aimerais une aide pour identifier d’où vient la panne et comment la résoudre.

Merci d'avance !

[Malekal_morte]

Salut,

Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc

Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.

plus d'informations sur ces écrans bleus, sur la page suivante : Les écrans bleus de plantages (BSOD)

On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.

[pipistrelus]

Merci pour la réponse.

Alors je tiens à préciser quelques points et je poste l'analyse WhoCrashed après :

• Je n'ai pas de périphérique connecté en ce moment, juste l'uSb de l'imprimante (non allumée)

• Ces plantages sont intempestifs, dès je démarre windows au bout de 10-15-20min

• Suite à un problème avec un disque (non reconnu non alloué) j'ai racheté et installé une carte d'extension PCIE/sata , j'en avais déjà une mais elle n'avait que deux ports, la nouvelle en a 4. Sauf que la nouvelle n'avait pas l'air de supporter 4 branchements (disque non détectés) donc j'ai branché 2 cartes PCIE/Sata

• Pour cela il m'a fallut débrancher et rebrancher ma carte graphique et j'en ai profiter pour rebrancher et "déméller les branchements à l'alim et en cable sata.

• Suite à ça j'ai (ré)installé des drivers (grâce à "touslesdrivers" et "driverscloud") pour AMD, les port usb etc...

• Comme j'ai changé de matériel et qu'il n'était pas détecté au début, j'ai fais un instant flash du BIOS et un clearCMOS de la carte graphique...

• Comme j'étais dans le bios, j'ai passé mes disques d u mode IDE au mode AHCI (je ne connaissait pas cette fonction avant et apparemment mes disques durs devraient le supporter...

Donc les cause potentielles peuvent être nombreuses... Et je suis bien embêté pour trouver laquelle est la bonne maintenant...[/list]


*********
J’arrête la mon petit roman et voici le rapport :

CAUSE identifiée : module: ntoskrnl.exe (nt+0x1C14E0)

Code : Tout sélectionner

System Information (local)
Computer name: DESKTOP-IIBH3GS
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\WINDOWS
Hardware: ASRock, 970 Extreme4
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD8664, level: 21
8 logical processors, active mask: 255
RAM: 8545394688 bytes (8,0GB)



Crash Dump Analysis
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sun 26/01/2020 00:51:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012620-69593-01.dmp
[b]This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)[/b]
Bugcheck code: 0xA0 (0x608, 0xFFFFCD09475603A8, 0x0, 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 is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25/01/2020 17:03:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012620-146781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA0 (0x608, 0xFFFF830E8B34F3A8, 0x0, 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 is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 26/01/2020 00:51:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!PoFxSetComponentWake+0x14C)
Bugcheck code: 0xA0 (0x608, 0xFFFFCD09475603A8, 0x0, 0x0)
Error: INTERNAL_POWER_ERROR
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25/01/2020 00:37:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012520-70390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA0 (0x608, 0xFFFFB9032DF6A3A8, 0x0, 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 is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25/01/2020 00:24:31 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012520-76281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA0 (0x608, 0xFFFFA3838656C3A8, 0x0, 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 is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25/01/2020 00:11:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012520-67671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA0 (0x608, 0xFFFFE30F9F9743A8, 0x0, 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 is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25/01/2020 16:51:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012520-29578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA0 (0x608, 0xFFFF86020BD563A8, 0x0, 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 is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25/01/2020 16:35:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012520-29921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA0 (0x608, 0xFFFFBB8DD0B6E3A8, 0x0, 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 is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25/01/2020 16:22:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012520-73718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA0 (0x608, 0xFFFFC08D819773A8, 0x0, 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 is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25/01/2020 16:09:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012520-42187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA0 (0x608, 0xFFFF880C6A5653A8, 0x0, 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 is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




Conclusion
On your computer a total of 43 crash dumps have been found. Only 10 have been analyzed. No offending third party drivers have been found. Connsider 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 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.

[Malekal_morte]

Je te propose de tourner quelques heures avec une live CD Ubuntu.
Si ça plante, c'est matériel.
=> Télécharger et créer un Live USB Ubuntu.

[pipistrelus]

Bonjour,

Merci pour cette idée !

Finalement, j'ai essayé de débrancher la nouvelle carte PCI/sata et j'ai refais une mise a jour des pilotes de ma carte graphique et le problème à sitôt disparu.
Donc je pense que c'est la carte sata qui n'est pas compatible avec mon pc ou qui est défectueuse.

[Malekal_morte]

ok ça semble logique =)
bonne fin de soirée !
Merci du retour.