Bonjour, depuis hier mon pc fait que de bluescreen sans cesse sans raison. J'ai ré installer windows pensant que cela résoudrais le problème. J'aurais besoin d'aide voici le code d'erreur :
 
System Information (local)
--------------------------------------------------------------------------------
 
Computer name: DESKTOP-S8FDIFV
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\Windows
Hardware: MS-7B51, Micro-Star International Co., Ltd., MPG Z390 GAMING PLUS (MS-7B51)
CPU: GenuineIntel Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz Intel8664, level: 6
16 logical processors, active mask: 65535
RAM: 34290769920 bytes (31,9GB)
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dumps are enabled on your computer.  
 
Crash dump directories:  
C:\Windows
C:\Windows\Minidump
 
On Wed 25/12/2019 16:14:10 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122519-7671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.  
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.  
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 25/12/2019 16:14:10 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!memset+0x5B9BF)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.  
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.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 

Hello,
 
Fréquences stock sur le CPU? tu as tenté un memtest? teste aussi la stabilité avec une ram puis deux...

Alim, RAM, carte-mère, ventirad, config complète merciiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii

 
 
Oui fréquence stock, j'ai lancer un memtest rien de anormal, je vais tester ça merci

 
Salut voila tout :  
ALIM : Cooler master 750W 80plus gold
RAM : Ballistix Sport 32 Go (2 x 16 Go) DDR4 2666 MHz
CM : Msi MPG Z390 Gaming Plus
Cooling : Corsair H100x
CPU : Intel Core i9 9900K @ 3.60GHz
GPU : NVIDIA GeForce Msi RTX 2080 Gaming x trio
Stockage : 256Go SSD M.2 Samsung 860 Evo
               2To HDD Western Digital
 
Ecran : Acer Predator XF240H (144hz)
Clavier : Corsair K70 Mk.2 Rapide Fire Low Profile
Souris : Razer Deathadder
Casque : Beats Studio 3

Bonjour, nouveau message d'erreur que j'ai eu 3 fois :  
 
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dumps are enabled on your computer.  
 
Crash dump directories:  
C:\Windows
C:\Windows\Minidump
 
On Thu 26/12/2019 01:13:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122619-6937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)  
Bugcheck code: 0xD1 (0x0, 0xFF, 0xC2, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.  
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 26/12/2019 01:13:01 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: 0xD1 (0x0, 0xFF, 0xC2, 0x0)
Error: 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.  
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.  
 

Juste pour voir télécharge OCCT et fais un test CPU sur 10 min avoir une idee, nous donner la fréquence max en charge (3.6 Ghz si respect du TDP de 95w sinon classiquement 4. 7 ghz), et le vcore max en charge.

Quand tu dis memtest fait on parle bien de memtest86 sur clé usb, pas le memtest windows ?

Juste pour voir télécharge OCCT et fais un test CPU sur 10 min avoir une idee, nous donner la fréquence max en charge (3.6 Ghz si respect du TDP de 95w sinon classiquement 4. 7 ghz), et le vcore max en charge.
 
Quand tu dis memtest fait on parle bien de memtest86 sur clé usb, pas le memtest windows ?[/quotemsg]
 
J'ai fait le test, il est bien à 4.7ghz a 95w et je ne trouve pas le vcore max en charge.
Oui je parle bien du memtest sur clé usb.
(je fais le test avec une ram pas de problème pour le moment)
https://image.noelshack.com/fichier [...] puocct.png

Nouveau crash :  
crash dump file: C:\Windows\Minidump\122619-6984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)  
Bugcheck code: 0x3B (0x80000003, 0xFFFFF8005D516568, 0xFFFFE0012EA5D120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.  
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.  
 

up

Svp