Bonjour a tous, j'ai acheté un PC d'occasion il y'a 2 semaines, tout marchais bien jusqu'a il y'a quelques jours. J'ai 1 a 2 fois par jour un BSOD Kernel Security Failure et je ne comprends pas pourquoi.
Je ne suis pas un expert en informatique alors je demande votre aide.
J'ai fait une analyse avec WhoCrashed, voici les resultats:
System Information (local)
Computer name: DESKTOP-0P384AQ
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\WINDOWS
Hardware: B450 AORUS ELITE, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor 8664, level: 23
12 logical processors, active mask: 4095
RAM: 17128566784 bytes (16,0GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 26/08/2021 01:54:58 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082621-6093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0x139 (0x3, 0xFFFFFD8AB08927E0, 0xFFFFFD8AB0892738, 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 Thu 26/08/2021 02:36:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082621-6125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF805374BF73F)
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 26/08/2021 02:36:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x12B2E)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF805374BF73F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 Wed 25/08/2021 14:08:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082521-6171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80331CBF73F)
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
4 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.
Je suis a votre disposition pour effectuer d'autres tests ou manipulation pour m'aider a résoudre ce problème.
PS: J'ai effectuer une nouvelle installation Windows, mis a jour mes drivers avec iobit driver booster mais j'ai toujours ce BSOD et je précise qu'il peut arriver a n'importe quel moment, même lorsque je ne me sers pas du PC et qu'il n'effectue aucune tache particuliere.
WhoCrashedOutput.htm