Pour bien commencer mon post... Bonne Année !
Voilà, il y a 3 sem je me suis monté un pc... 1 sem plus tard j'ai commencé a avoir des écrans bleus mais je pouvais quand même me servir de mon pc. J'ai tout refait mes branchements au cas où et mis mes drivers a jour.
Mais il y a 3 jours c'était BSOD par dessus BSOD.
system_service_exception
system_thread_exception_not_handled
kernel_security_check_failure
mémory_management
unexpected_kernel_nonpaged_area
page_fault_in_nonpaged_area
critical processus died
J'ai installer Wocrashed et le fichier qui cause problème est ntoskrnl.exe ...
Code : Tout sélectionner
Crash dumps are enabled on your computer.
On Sat 2018-01-06 18:21:18 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010618-60312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x139 (0x3, 0xFFFF8581E27BF7E0, 0xFFFF8581E27BF738, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 2018-01-06 18:21:18 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xCA0C)
Bugcheck code: 0x139 (0x3, 0xFFFF8581E27BF7E0, 0xFFFF8581E27BF738, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a standard 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 2018-01-06 18:21:09 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010618-33468-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Sat 2018-01-06 18:14:51 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010618-33500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801E9924929, 0xFFFF9680599C5720, 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.
On Sat 2018-01-06 17:32:23 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010618-28718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803191378E0, 0xFFFF828055BC5E60, 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. Voici les composants de mon pc:
Asus Prime x370-a
Ryzen 7 1700
16 go de ram
DD de 2 t Firecuda
Geforce 1060 6 go
un lecteur/graveur de dvd
watercooling h60 corsair
carte réseau sans-fil Tp-Link (tl-wdn4800)
J'ai mis mes drivers a jour... je n'ai pas de virus... le pc a été sur le net que pour les mises a jour (win 10 nouvellement installé hier soir) et ce matin j'ai eu d'autres BSOD ce matin dont 2 nouveau messages:
BAD SYSTEM CONFIG INFO
system_service_exception
éléments ayant échoués: win32kfull.sys
Est-ce possible que ce soit un périphérique qui (ram, DD, bloc d'alimentation, lecteur dvd, carte graphique, carte-mère) qui cause ce problème ?
Aidez moi svp avant que je m'arrache les cheveux...
Merci...
---------------------------------------------------------
EDIT: je suis en train de faire un test de ram avec Memtest86 et j'ai 10 erreurs... ce pourrait-il que ce soit ma ram défectueuse ou corrompue qui occasionne ce plantage de ntoskrnl.exe ????
