Der Fehler besteht weiterhin
obwohl nun eine weitere (3.) Festplatte als Bootmedium verwendet wurde.
Hab nun einige Programme durchlaufen lassen die den Fehler gefunden haben.
Ich google mich gerade so durch, bin dennoch nicht schlauer.
Wer sich die .dmp Datein anschauen will, diese sind auf mein Server hochgeladen.
Fobografie.net:5000
Name: Bluescreen
PW: 2015Problem
Auszug:
==================================================
Dump File : 012315-17097-01.dmp
Crash Time : 23.01.2015 10:50:34
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050033
Parameter 3 : 00000000`000406f8
Parameter 4 : fffff800`02c83798
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012315-17097-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7600
Dump File Size : 292.696
Dump File Time : 23.01.2015 10:54:54
==================================================
System Information (local)
--------------------------------------------------------------------------------
computer name: HOME
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: ASRock, X99X Killer
CPU: GenuineIntel Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 68605059072 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 23.01.2015 09:50:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012315-17097-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002C83798)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 23.01.2015 09:50:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: vsdatant.sys (vsdatant+0x1637F)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002C83798)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\vsdatant.sys
product: ZoneAlarm Firewalling Driver
company: Check Point Software Technologies LTD
description: ZoneAlarm Firewalling Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vsdatant.sys (ZoneAlarm Firewalling Driver, Check Point Software Technologies LTD).
Google query: Check Point Software Technologies LTD UNEXPECTED_KERNEL_MODE_TRAP
On Fri 23.01.2015 03:17:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012315-24897-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002C7F5A2)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 23.01.2015 03:07:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012315-22105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002C8A3F0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
vsdatant.sys (ZoneAlarm Firewalling Driver, Check Point Software Technologies LTD)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
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.