Bonjour a tous, Cela fait depuis noel que j'ai que des blues screan sur mon pc. Ces blues screans arrive quand je télécharge un jeux ou un logiciel très lourd, ou bien quand je joues a un joue très charger style five m (gta 5), quand je record ou bien même quand je fais le rendu d'une vidéo... Les blues screans ont commencer suite a un crash d'une mise a jour windows.
J'ai déjà formater le pc, réinitialiser windows ect... rien à y faire. (peux etre que je le fais mal...)
Avant les blues screans souvent discord crash ou même google.
Voici ma config :
Intel i7-9700KF 8X 3.6Ghz
Geforce RTX 3070 8Go
32Go RAM DDR4
500Go SSD NVMe M.2 PCIe
2To HDD
Je vous mes ci contre les analyses WhoCrashed :
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 19/05/2021 13:51:07 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051921-8187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80137A1300F, 0xFFFFB60DE8516F68, 0xFFFFB60DE85167A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Wed 19/05/2021 13:51:07 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+0x1AD0C)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80137A1300F, 0xFFFFB60DE8516F68, 0xFFFFB60DE85167A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
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 bug check indicates that a system thread generated an exception that the error handler did not catch.
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 Wed 19/05/2021 13:37:10 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051921-8468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0xBE (0xFFFFA25100000030, 0x1A000003EC733025, 0xFFFF8C8EBC85DBF0, 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 Wed 19/05/2021 13:27:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051921-8828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0xA (0x900008, 0x2, 0x0, 0xFFFFF80118B9F70F)
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.
Lire la suite...