CG problème avec le pilote ou virus

Bjr

Essayes ce pilote : 

https://www.nvidia.com/fr-fr/geforce/drivers/results/257586/

Si à un moment il t'es demandé de créer un compte nvidia c'est normal,  c'est pour l'appli associée,  il est devenu presque impossible de s'en passer. Ou tu choisis "installation personnalisée" et tu ne l'installer pas, je ne sais plus si c'est possible.  Sinon faudra la desinstaller elle uniquement après si tu vend le pc.

@brucine StatutMembre  @flo88 StatutContributeur grand merci à vous comme vous le voyez grace à vous ca marche <3

gros hic parfois au bout de 2mn parfois 10mn parfois 5mn il s'eteint et avec un message différent parfois écran bleu ci dessous

Cet écran bleu apparait d'emblé en marche ou lors du démarrage après un arrêt ?

aléatoirement, cad j'allume le pc, et je regarde juste wupdate ou un périphérique ou rien parfois et ca crashe :-(

tu penses à un virus ? sinon j'emmène chez un informaticien mais va t'il obligatoirement trouver la cause ?

Bonjour,

Analysez avec WhoCrashed Free Home Edition

https://forums.commentcamarche.net/forum/affich-38251615-cg-probleme-avec-le-pilote-ou-virus#

Qu'on voie de quel driver le problème viens si c'est un driver.

Idéalement je trouve une clé "Key" de IOBit Driver Booster Pro (En Giveaway)

https://www.google.com/search?q=IOBit+Driver+Booster+Giveaway

Et j'installe la version Free du site Officiel pour entrer la clé

/!\ Attention > En installant pas d’autre logiciel à l'installation Il faut décocher et ne pas cliquer 2 fois installer de suite (C'est pour proposer un autre logiciel) /!\

Ensuite il laisse des tâches planifiées à désactiver.
 

@fabul StatutModérateur oh merci trop bien, on va y arriver, merci merci merci

voilà t'en dis quoi du coup ?

System Information (local)

Computer name: DESKTOP-9B4PJ64
Windows version: Windows 10, 10.0, version 2009, build: 19045
Windows dir: C:\Windows
Hardware: MPG B460 Trident A (MS-B926), Micro-Star International Co., Ltd., MPG B460I GAMING EDGE WIFI (MS-7C86)
CPU: GenuineIntel Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 17102823424 bytes (15,9GB)


 

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Fri 28/11/2025 18:39:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-8421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF802457340E1)
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 Fri 28/11/2025 18:39:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x15D128)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF802457340E1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 28/11/2025 18:36:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-7171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xBE (0xFFFF97C00509FFE0, 0x8A00000000200121, 0xFFFFEB01AB944050, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Fri 28/11/2025 18:35:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-7296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xBE (0xFFFFF8C005003FE0, 0x8A00000000200121, 0xFFFFBA0FF1832050, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Fri 28/11/2025 18:34:26 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-6765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xBE (0xFFFFE04005063FE0, 0x8A00000000200121, 0xFFFFB987C465A050, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Fri 28/11/2025 09:44:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-6968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF8068045871A)
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.



 

Conclusion

6 crash dumps have been found and analyzed. 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.




On Fri 28/11/2025 18:39:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-8421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF802457340E1)
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 Fri 28/11/2025 18:39:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x15D128)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF802457340E1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 28/11/2025 18:36:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-7171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xBE (0xFFFF97C00509FFE0, 0x8A00000000200121, 0xFFFFEB01AB944050, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Fri 28/11/2025 18:35:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-7296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xBE (0xFFFFF8C005003FE0, 0x8A00000000200121, 0xFFFFBA0FF1832050, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Fri 28/11/2025 18:34:26 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-6765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xBE (0xFFFFE04005063FE0, 0x8A00000000200121, 0xFFFFB987C465A050, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Fri 28/11/2025 09:44:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112825-6968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FE580)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF8068045871A)
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.



 

Conclusion

6 crash dumps have been found and analyzed. 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.


 

No offending third party drivers have been found.

Ça veut dire que les drivers ne sont peut être pas en cause, aucun problème lié directement, mais essayez IOBit quand même.


Surchauffe-il ? Vous pouvez vérifier avec OCCT Per (Personnal Edition)

https://www.ocbase.com/download


Et/Ou vérifiez la RAM en bootant sur une clé USB Memtest86 Free avec le programme inclus.

https://www.memtest86.com/download.htm

Démarrez dessus par la touche Boot Menu du PC

On peut chercher sur Google "[Marque Modèle] Boot Menu Key"


Vérifier le disque / SSD avec CrystalDiskInfo (C'est peut être le bobo)

https://crystalmark.info/en/software/crystaldiskinfo/

Sinon pour tenter de réparer Windows si des fichiers sont défaillants, par clic droit sur le bouton démarrer, utilisez cette commande avec Windows PowerShell (Terminal Admin)

CHKDSK /F C:

Répondre O pour Oui pour ensuite redémarrer Windows.

Ensuite

Dism /Online /Cleanup-Image /RestoreHealth

Ensuite

sfc /scannow 

merci bcp de ton aide précieuse <3 @fabul StatutModérateur déjà un 1er rapport

Bonjour 

Le sujet de départ portant sur la carte graphique,  les écrans bleus c'est autre chose,  pour la cohérence de la discussion se serait mieux de mettre celle-ci en résolu et de faire un autre sujet sur les plantages uniquement. @fabul StatutModérateur qu'en dit-tu ?