Ach so! Ok werde ich dann demnächst in Angriff nehmen. Der Lüfter muss dann die Luft Richtung CPU pusten richtig? Oder raus ins Gehäuse innere?

Der CPU-Lüfter sollte die Luft nach hinten, also zum Hecklüfter blasen.![]()

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 06.06.2014 14:23:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFF800E746EB70, 0xFFFFF800E746EAC8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
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 Mon 02.06.2014 16:19:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-5312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF803020CF92A)
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 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.
fffff801`c589b000 fffff801`c6844000 atikmdag atikmdag.sys Fri May 23 03:46:07 2014 (537EA85F)
fffff801`c5694000 fffff801`c5722000 atikmpag atikmpag.sys Fri May 23 03:11:53 2014 (537EA059)
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, fffff800e746eb70, fffff800e746eac8, 0}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+859a8 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (139)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000003
Arg2: fffff800e746eb70
Arg3: fffff800e746eac8
Arg4: 0000000000000000
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x139
PROCESS_NAME: MsMpEng.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800e5be2ae9 to fffff800e5bd6fa0
SYMBOL_ON_RAW_STACK: 1
STACK_ADDR_RAW_STACK_SYMBOL: fffff800e746e950
STACK_COMMAND: dds E746E950-0x20 ; kb
STACK_TEXT:
ffffffff`e746e930 ????????
ffffffff`e746e934 ????????
ffffffff`e746e938 ????????
ffffffff`e746e93c ????????
ffffffff`e746e940 ????????
ffffffff`e746e944 ????????
ffffffff`e746e948 ????????
ffffffff`e746e94c ????????
ffffffff`e746e950 ????????
ffffffff`e746e954 ????????
ffffffff`e746e958 ????????
ffffffff`e746e95c ????????
ffffffff`e746e960 ????????
ffffffff`e746e964 ????????
ffffffff`e746e968 ????????
ffffffff`e746e96c ????????
ffffffff`e746e970 ????????
ffffffff`e746e974 ????????
ffffffff`e746e978 ????????
ffffffff`e746e97c ????????
ffffffff`e746e980 ????????
ffffffff`e746e984 ????????
ffffffff`e746e988 ????????
ffffffff`e746e98c ????????
ffffffff`e746e990 ????????
ffffffff`e746e994 ????????
ffffffff`e746e998 ????????
ffffffff`e746e99c ????????
ffffffff`e746e9a0 ????????
ffffffff`e746e9a4 ????????
ffffffff`e746e9a8 ????????
ffffffff`e746e9ac ????????
FOLLOWUP_IP:
atikmdag+859a8
fffff801`c59209a8 ?? ???
SYMBOL_NAME: atikmdag+859a8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 537ea85f
FAILURE_BUCKET_ID: X64_0x139_atikmdag+859a8
BUCKET_ID: X64_0x139_atikmdag+859a8
Followup: MachineOwner
---------
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=3048]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = F7
BiosReleaseDate = 08/02/2013
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z87X-D3H
SystemFamily = To be filled by O.E.M.
SystemVersion = To be filled by O.E.M.
SystemSKU = To be filled by O.E.M.
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = Z87X-D3H-CF
BaseBoardVersion = x.x
On Mon 16.06.2014 07:21:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061614-8984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8025905F0A6)
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 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 Mon 16.06.2014 07:21:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8025905F0A6)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.