So! War gerade fröhlich am Videochatten, da kommt plötzlich wieder ein Bluescreen. Ich verzweifel noch mit diesem Rechner -.-
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091513-19874-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`0304c000 PsLoadedModuleList = 0xfffff800`0328f6d0
Debug session time: Sun Sep 15 16:14:34.333 2013 (UTC + 2:00)
System Uptime: 0 days 7:49:37.656
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050033, 406f8, fffff880057b2322}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiWaitForSchedulerEvents+e6 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff880057b2322
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800030c1129 to fffff800030c1b80
STACK_TEXT:
fffff800`00ba4d28 fffff800`030c1129 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`030bf5f2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`057b2322 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0xe6
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiWaitForSchedulerEvents+e6
fffff880`057b2322 4c89642420 mov qword ptr [rsp+20h],r12
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VidSchiWaitForSchedulerEvents+e6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13
FAILURE_BUCKET_ID: X64_0x7f_8_dxgmms1!VidSchiWaitForSchedulerEvents+e6
BUCKET_ID: X64_0x7f_8_dxgmms1!VidSchiWaitForSchedulerEvents+e6
Followup: MachineOwner
---------
Jetzt werde ich den Rechner mal ordentlich fordern... ich hoffe er übersteht das WE ohne Bluescreen. Falls doch einer auftaucht melde ich mich 
