J'avais quelques problème d'écran bleu depuis quelques temps lié à mon avis à ma carte graphique qui ne doit pas être bien enclenché je pense.
J'ai aussi noté un soucis de déplacements du curseur de la souris.
J'ai télécharger la version 7C52v2E sur le site de msi
https://www.msi.com/Motherboard/A320M-A-PRO-MAX/support
J'ai mis le dossier sur une clé usb formaté en ntfs parce que le flash dans le bios en fat32 ne voyait rien.
L'update a fonctionné mais a rendu l'ordinateur très instable d'où ma volonté de revenir en arrière mais impossible, j'explique.
J'avais une version de 2020 avant mais impossible de revenir en arrière pour le remettre.
Depuis l'ordinateur crash en permanence, j'ai eu toutes les peines du monde à arriver sur le bureau après la maj, je suis revenu sur l'écran d'accueil 10s avant d'avoir l'impossibilité de revenir sur le bureau, l'ordinateur crasher de suite, impossible d'utiliser le recovery ça voulait pas, j'ai été obligé de faire un f6 (load optImized defaut) f10 (sauvegarder) dans le bios pour m'en sortir et enfin parvenir à revenir sur le bureau mais l'ordinateur est plus stable du tout.
Des solutions pour revenir en arrière?
Voici un WhoCrashed :
Code : Tout sélectionner
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 7.06
--------------------------------------------------------------------------------
WhoCrashed is a comprehensible crash dump analyzer. It analyzes the system crashes of your computer or a remote computer on the network.
If your computer has displayed a blue (or black) screen of death or rebooted suddenly then your system may have crashed because of a malfunctioning device driver or because of a hardware failure. WhoCrashed will go to great lengths to help you find the root cause of the problem and a solution if available. It will analyze the crash dump files on your system or a system on the network with the single click of a button. In case the problem is caused by a malfunctioning driver, it will tell you what drivers are likely to be responsible for crashing your computer. In case of a hardware failure, it will tell you the most likely root cause and how to fix the problem.
When the analysis process is complete, WhoCrashed will write a report that offers suggestions on how to proceed in any situation, including internet links which will help you further troubleshoot any detected problems.
WhoCrashed will do great efforts to find out why your system crashed and what can be done to remedy the problem.
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-8Q44N6A
Windows version: Windows 10, 10.0, version 2009, build: 19045 (x64)
Windows dir: C:\Windows
Hardware: MS-7C52, Micro-Star International Co., Ltd., A320M-A PRO MAX (MS-7C52)
CPU: AuthenticAMD AMD Ryzen 5 3400G with Radeon Vega Graphics 8664, level: 23
Processor count: 8 logical processors, active mask: 255
RAM: 14261,3MB
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 25/08/2023 18:27:49 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\082523-7406-01.dmp (Minidump)
Bugcheck code: 0xA(0x200000000, 0x2, 0x1, 0xFFFFF80218C5703E)
Bugcheck name: IRQL_NOT_LESS_OR_EQUAL
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.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.
On Fri 25/08/2023 18:27:49 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code: 0xA(0x200000000, 0x2, 0x1, 0xFFFFF80218C5703E)
Bugcheck name: IRQL_NOT_LESS_OR_EQUAL
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.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.
On Fri 25/08/2023 18:16:13 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\082523-7500-01.dmp (Minidump)
Bugcheck code: 0xA(0x4878DF04, 0xD, 0x0, 0xFFFFF80206E4362B)
Bugcheck name: IRQL_NOT_LESS_OR_EQUAL
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.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.
On Fri 25/08/2023 17:44:04 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\082523-7484-01.dmp (Minidump)
Bugcheck code: 0x139(0x3, 0xFFFF9A051A4DE860, 0xFFFF9A051A4DE7B8, 0x0)
Bugcheck name: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
Analysis: This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
On Fri 25/08/2023 17:37:53 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\082523-7437-02.dmp (Minidump)
Bugcheck code: 0x1E(0xFFFFFFFFC0000005, 0xFFFFF8001BCB1ED0, 0x0, 0x3A)
Bugcheck name: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
Analysis: This could be caused by either a software or hardware problem.
Hardware failure is often caused by overheating. Read this article on thermal issues
On Fri 25/08/2023 15:24:27 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\082523-7437-01.dmp (Minidump)
Bugcheck code: 0xEF(0xFFFF878BB1A1F080, 0x0, 0x0, 0x0)
Bugcheck name: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
Analysis: This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider 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 suggestions displayed in the bugcheck analysis above.
The analysis process took 0:00:09 (h:mm:ss).