j'ai utiliser whocrashed pour analyser le fichier dump et ca ma donner ceci j'espere que ca pourra aider.
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-6359K2H
Windows version: Windows 11, 10.0, version 2009, build: 22621 (x64)
Windows dir: C:\WINDOWS
Hardware: Z390 UD, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz 8664, level: 6
Processor count: 6 logical processors, active mask: 63
RAM: 24512,1MB
--------------------------------------------------------------------------------
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 08/01/2023 08:22:17 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\010823-19234-01.dmp (Minidump)
Bugcheck code: 0xD1(0x8, 0x2, 0x0, 0xFFFFF8055F7F51B5)
Bugcheck name: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.
On Tue 03/01/2023 05:19:57 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\010323-16734-01.dmp (Minidump)
Bugcheck code: 0xD1(0x8, 0x2, 0x0, 0xFFFFF800536E51B5)
Bugcheck name: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.
The following dump file was found but appeared to be corrupt: C:\WINDOWS\LiveKernelReports\WATCHDOG-20221203-1229.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. Only 2 are included in this report. If one or more dump files were found that could not be analyzed, it means they are corrupted. It's an emergency measure for the system to write out a crash dump file and because of this, it's not uncommon for this process to fail. Often, but not always, it points to a problem in the storage stack. For instance, if the disk that should write out the crash dump file has failed, there will be no crash dump file written out. 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. 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:07 (h:mm:ss).