Tout d'abord, bonjour à tous. JE viens vers vous en quête d'expertise, mes connaissances en infos ne suffisant clairement plus.
J''ai des BSOD récurents de type IRQL NOT LESS OR EQUAL.
Au début, par flemme et parce que dans le fond il n'y avait pas grand chose sur mon ssd en dehors de quelques logiciels/jeux qu'il suffirait de réinstaller (je sauvegarde tout mes doc sur un hdd), je me dit que je vais tout simplement réinstaller windows et les drivers.
Ce que je fais, les drivers via Drivercloud, maj windows etc.
Rebelotte. JE commence à tout vérifier. Je passe mes drivers sous drivers verifier, pas de crash. Mes deux disque sur HD Tunes, pas de problème de ce côté là. Memtest 86, ma RAM va bien. Je soupçonne le problème de venir de ma CG. Je désinstalle mes drivers via Driver uninstaller en mode sans echec, je réinstalle manuellement sans Geforce experience. (j'ai fais tout les scans sfc, dism etc)
Toujours des crash. en jeu, sur youtube/netflix ou en étant simplement en train de naviguer sur internet. Dernier crash, au redémarrage, windows ne démarre pas et j'ai un nouveau bsod : CRITICAL PROCESS DIED. Il n'apparait pas dans whocrashed.
De ce que j'ai pu lire sur IRQL NOT LESS OR EQUAL, c'est que ca vient soit de la ram soit des drivers D'après whocrashed, ca vient du de ntkrnlmp.exe et ntoskernel. exe
Je ne pense pas avoir de problème logiciel. Je soupçonne ma CG d'être défaillante au niveau matériel (elle commence à vieillir, au contraire de mon processeur, CM et RAM que j'ai acquis en septembre). Je ne souhaite pas particulièrement en acheter une tout de suite et cherche donc toute les options pour être absolument certain que si je devais le faire, cette dépense règlera le problème. Ya-t-il un moyen pour savoir si c'est bien ça la problème ?
Si une bonne âme à la moindre idée de comment je peux savoir ce qu'il se passe, je suis toute ouïe. Je suis en confinement et j'ai le temps, s'il manque des infos signalez le-moi
Mon système et les rapports crash dump :
MSI B450 TOMAHAWK MAX
AMD RYZEN 5 3600 6-core
16GB RAM
GEforce GTX 750ti
Rapports who crashed :
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 03/04/2020 21:22:45 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!setjmpex+0x8209)
Bugcheck code: 0xA (0x1A0, 0xFF, 0x16, 0xFFFFF80731CBB4BF)
Error: 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.
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 Thu 02/04/2020 22:09:52 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040220-9468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
Bugcheck code: 0xA (0x5D00, 0xFF, 0xAA, 0xFFFFF800288D6CC1)
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 Thu 02/04/2020 15:33:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040220-6203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80657F11298)
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 Thu 02/04/2020 14:17:33 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040220-6125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8025848B80
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\040320-6984-01.dmp
5 crash dumps have been found and analyzed. Only 4 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.