New
#1
Newly build HTPC getting "Kernel Security Check Failure" on Win10...
Hey guys!
I just build a new HTPC with Windows 10 Pro (free update from Windows 7 Ultimate), but I keep getting the Kernel Security Check Failure on it.
No pattern what so ever on when it occurs.
Attachment 43146
WhoCrashed gives me following information (I know it shows the wrong date, system time was set a day ahead. Getting same error after fixing time as well):
System Information (local)
Computer name: HTPC2-PC
Windows version: Windows 10 , 10.0, build: 10240
Windows dir: C:\WINDOWS
Hardware: ASRock, FM2A78M-ITX+
CPU: AuthenticAMD AMD A10-7870K Radeon R7, 12 Compute Cores 4C+8G AMD586, level: 21
4 logical processors, active mask: 15
RAM: 16024104960 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 2015-10-18 09:14:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101815-9109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x139 (0x3, 0xFFFFF800BAEA3880, 0xFFFFF800BAEA37D8, 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 Sun 2015-10-18 08:18:57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101815-7437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00190ADD5C0, 0xFFFFD00190ADD518, 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 2015-10-17 20:54:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101715-7234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x139 (0x3, 0xFFFFD002045A17E0, 0xFFFFD002045A1738, 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 2015-10-17 18:06:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101715-7812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x139 (0x21, 0xFFFFD000843EB730, 0xFFFFD000843EB688, 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 2015-10-17 14:48:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101715-7546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x139 (0x3, 0xFFFFD0002C3C6710, 0xFFFFD0002C3C6668, 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 2015-10-17 14:16:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101715-16687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x139 (0x3, 0xFFFFF802BC210770, 0xFFFFF802BC2106C8, 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 2015-10-17 10:06:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101715-7468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x139 (0x3, 0xFFFFD0002B60C720, 0xFFFFD0002B60C678, 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 2015-10-17 10:06:16 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!NtUserPostMessage+0x5A4)
Bugcheck code: 0x139 (0x3, 0xFFFFD0002B60C720, 0xFFFFD0002B60C678, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel 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.