Bsod récurents

C'est vrai que je n'ai pas précisé les plus récurrents, le plus souvent c'est irql-not-less-or-equal et pendant la mise à jour de Bitdefender et la réparation de mon disque-dur c'était memory management.
Une panne semble bizarre car min PC est très récent. C'est moi qui l'ai monté grâce à la vidéo de JeanBaptisteShow.

De plus j'ai d'abord fais un test de mon disque dur en allant dans les propriétés de celui ci et il m'a confirmé qu'il y a un problème. Si j'y arrive je vous envoie le rapport WhoCrashed

Welcome to WhoCrashed (HOME EDITION) v 6.50

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-NO9A3IU
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: MS-7A38, Micro-Star International Co., Ltd., B350M BAZOOKA (MS-7A38)
CPU: AuthenticAMD AMD Ryzen 3 2200G with Radeon Vega Graphics AMD586, level: 23
4 logical processors, active mask: 15
RAM: 8536076288 bytes (7,9GB)



Crash Dump Analysis

Crash dumps are enabled on your computer.

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

On Sat 23/02/2019 00:34:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: rdyboost.sys (rdyboost+0xD081)
Bugcheck code: 0x1A (0x1236, 0xFFFFA70EC56BF390, 0xFFFFA70EC56BF4B0, 0x18C95C)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This indicates that a severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
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 Sat 23/02/2019 00:19:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022319-24531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0C0)
Bugcheck code: 0x1A (0x403, 0xFFFFD600F1E28D00, 0x8000000144F30867, 0xFFFFD600F1E22500)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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 Fri 22/02/2019 23:51:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022219-33484-01.dmp
This was probably caused by the following module: <gras>ntoskrnl.exe (nt+0x1AA0C0)
Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF80049702A20)
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.



The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\022219-30796-01.dmp
C:\WINDOWS\Minidump\022319-25593-01.dmp
C:\WINDOWS\Minidump\022319-25671-01.dmp



Conclusion

6 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.


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.

Bonjour, j'ai fais un test Tous Les Driver et il en manquait trois : un de la carte graphique mais c'était une bêta, un pour AMD SM bus mais je n'arrive pas à le télécharger et je suis allé sur un forum quelqu'un a dit qu'il n'était pas essentiel et enfin un " family controler " mais je ne vois pas le rapport.