PC qui redémarre après branchement chargeur

Tous les problèmes de Windows : message d'erreur, BSOD et écran bleu, erreur Windows Update ou d'installation, etc

Modérateur : Mods Windows

Howard64
Messages : 28
Inscription : 27 févr. 2023 13:22

PC qui redémarre après branchement chargeur

par Howard64 »

Bonjour,
Je vous écris car je sèche complètement sur ce problème.
J'ai un Lenovo MT 82LM-BU-idea FM Ideapad5 14ALC05 avec un processeur AMD RYZEN 7 5700U.
À chaque fois que je le branche au secteur pour le recharger, celui-ci après quelques minutes m'affiche un écran bleu et redémarre.
J'ai lancé un rapport WhoCrashed mais après avoir regardé sur détecteur d'empreinte et lancer un checkdisk je ne parviens pas à avancer.
Ci-dessous le rapport WhoCrashed :

Code : Tout sélectionner

Crash dumps are enabled on your computer. 

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

On Mon 27/02/2023 13:04:15 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022723-11875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x428C50) 
Bugcheck code: 0xA (0x42, 0x2, 0x1, 0xFFFFF8051DA80925)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Mon 27/02/2023 13:04:15 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: storport.sys (storport+0x5972) 
Bugcheck code: 0xA (0x42, 0x2, 0x1, 0xFFFFF8051DA80925)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 27/02/2023 12:27:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022723-17843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x428C50) 
Bugcheck code: 0xA (0xC0, 0x2, 0x0, 0xFFFFF8061A81E0BF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Mon 27/02/2023 12:22:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022723-14437-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8010BDD6C2E) 
Bugcheck code: 0x50 (0xFFFFFD03CDFBAFFF, 0x2, 0xFFFFF8010BDD6C2E, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that invalid system memory has been referenced. 
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 27/02/2023 11:54:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022723-13328-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFFFF46CEC46034) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFF46CEC46034, 0x1, 0x870)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 
The crash took place in a 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 Tue 21/02/2023 18:23:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022123-11375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x428C50) 
Bugcheck code: 0xEF (0xFFFF988B9D32E140, 0x0, 0xFFFF988B9D32E140, 0x0)
Error: CRITICAL_PROCESS_DIED
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 a critical system process died. 
There is a possibility this problem was caused by a virus or other malware. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

Quelqu'un aurait-il une piste à m'indiquer ?

D'avance je vous remercie pour le temps accordé à mon cas.

Howard
Malekal_morte
Messages : 117010
Inscription : 10 sept. 2005 13:57

Re: PC qui redémarre après branchement chargeur

par Malekal_morte »

Salut,

Comment télécharger et créer un Live USB Ubuntu
Teste dessus pour voir s'il s'agit d'un problème matériel.

~~

Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).

Télécharge et lance le scan FRST, 3 rapports FRST seront générés :
* FRST.txt
* Shortcut.txt
* Additionnal.txt

Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ et en retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus
Windows 11 : Compatibilité, Configuration minimale requise, télécharger ISO et installer Windows 11

Comment demander de l'aide sur le forum
Evaluer le site malekal.com
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
  • Sujets similaires
    Réponses
    Vues
    Dernier message

Revenir à « Windows : Résoudre les problèmes »