Depuis dimanche, mon ordi(portable, Dell latitude 3580,windows 10) me fait des misères.
J'ai voulu,mal m'en a pris,voir si le logiciel DellSupportAssit servait à quelque chose avant de le désinstaller. Je l'ai donc lancer, il m'a conseillé de mettre à jour des pilotes et logiciels, j'ai dit OK.il met les pilotes à jour (dont BIOS et ventilation, de mémoire) puis commence pour les logiciels, et là, l'ordi redémarre.
Et une mise à joiur windows attendait son tour et en profite
Redémarrage, je me loggue sur mon compte windows, et là BSOD "system thread exception not handeld" et redémarrage.
J'essaie donc de suivre tout ce qui est dit dans l'un des articles de malekal :
Suppression de la dernière mise à jour qualité (BSOD), puis de la mise à jour de fonction (BSOD), restauration (problème : as de point de restauration...), démarrage en mode sans échec (là, j'ai raté et pas compris une étape, donc cru que ça marchait pas). Je me suis donc résigné à une réinitialisation de Windows mais... BSOD.
Je refais un démarrage en mode sans échec avec réseau, et ça marche, plus de BSOD (mais pas d'accès au wifi, je n'ai pas de cable réseau).
Je fais un WhoCrashed :
Code : Tout sélectionner
--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
PLEASE NOTE THAT THIS VERSION OF WHOCRASHED IS NOT LICENSED FOR USE BY PROFESSIONAL SUPPORT ENGINEERS.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-2K5V2TE
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\WINDOWS
Hardware: Latitude 3580, Dell Inc., 0NVHKG
CPU: GenuineIntel Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz 8664, level: 6
4 logical processors, active mask: 15
RAM: 8281690112 bytes (7,7GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Mon 11/07/2022 08:54:33 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\071122-68968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F78A0)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80606540773, 0xFFFFED04501A8E88, 0xFFFFED04501A86C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Mon 11/07/2022 08:54:33 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!memset+0x7E3E)
Bugcheck code: 0x7E (0xFFFFFFFF80000003, 0xFFFFF80606540773, 0xFFFFED04501A8E88, 0xFFFFED04501A86C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 10/07/2022 23:40:00 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\071022-60968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F78A0)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80540D40773, 0xFFFFAA88AC24BE88, 0xFFFFAA88AC24B6C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\071022-56750-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. Only 3 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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. Je vérifie les températures (seul speccy fonctionne/s'installe en mode sans échec, et il me donne que la température du disque dur : 33°C
Je mets à jour les pilotes qualcom (réseaux wifi) et Realteck, pusique le mode sans échec avec réseau n'a pas de wifi ni de son.
Je tente une mise à jour du bios (version dell 1.15.1 du 27/01/2021), je vérifie sur le site de DELL et installe la dernière version : 1.20.0 du 12/05/2022.
Je rédémarre en mode normal, le wifi fonctionne, mais... BSOD.
Je tente un Clear CMOS avec d'abord une remise à zéro électrique. Toujours BSOD.
Là, avant d'aller plus loin , je décide de créer une clef de boot sous debian pour avoir une solution de secours, et je modifie l'ordre de priorité du bios pour permettre de botter sur la clef, toujours e suivant un article de malekal.
Et là, nouveau problème !
Non seulement en redémarant pour tester la clef, celle-ci ne fonctionne pas (je pense que je me suis planté entre GPT et MBR...), mais pire, l'ordi ne boot plus :(
L'écran m'affiche une erreur : "PXE-E61 media test faillure, check cable"
PXE -M0F : exiting PXE Rom
No boot device found. press any key to reboot the machine.
Et rien ne se passe quand j'appuie sur des touches.
Je redémarre donc à la bourrin, appuie sur F2 pour entrer dans le bios, et j'arrive sur Support Assist dell, il me propose de tester le matériel, puis me dit qu'il n'y a aucun problème hardware.
Du coup, je vais dans le BIOS pour annuler les modifications que j'y avais faites, d'abord en retournant aux paramètres d'usines du BIOS (toujours même problème), puis au retour aux caractéristiques par défaut du bios, toujours même problème.
Là, je suis au bout de mes limites, je crains avoir empiré les choses et je ne sais plus quoi (et j'ai ressorti un vieux notebook asus de 2013 qui rame à mort pour vous écrire).
Je viens donc vous demander de l'aide :'(
En vous remerciant par avance,
Grégoire
