Re: Blue screen of death : Kernel security
le 01 Jan 2016 17:34
j'ai lanché whocrashed, et j'ai eu le rapport suivant :
System Information (local)
--------------------------------------------------------------------------------
Computer name: HARMEN
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: X550JK, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i5-4200H CPU @ 2.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8467275776 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 01/01/2016 16:20:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010116-31203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00022D317F0, 0xFFFFD00022D31748, 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 Fri 01/01/2016 16:20:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x25BE8)
Bugcheck code: 0x139 (0x3, 0xFFFFD00022D317F0, 0xFFFFD00022D31748, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
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: 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 Fri 01/01/2016 16:03:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010116-36625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD000394E26F0, 0xFFFFD000394E2648, 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 Fri 01/01/2016 15:49:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010116-37453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00028770520, 0xFFFFD00028770478, 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.
--------------------------------------------------------------------------------
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.
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.