Bluescreen! Minidump = Bahnhof

[elan-eo-akin]

Hallo!

Ich habe heute einen erneute Bluescreen bei ETQW erhalten und bin ratlos was da der Verursacher ist, vielleicht ist einer von Euch schlauer. Bin für jede Hilfe sehr dankbar!

Hier ist der Inhalt des Minidumps:

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini100808-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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81a3f000 PsLoadedModuleList = 0x81b56c70
Debug session time: Wed Oct 8 17:40:24.581 2008 (GMT+2)
System Uptime: 0 days 0:38:01.520
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {0, 0, 0, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DMMVIDEOSIGNALMODE:ivideAndRound+a )

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: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_0

TRAP_FRAME: aff40b4c -- (.trap 0xffffffffaff40b4c)
ErrCode = 00000000
eax=00000000 ebx=9e553e08 ecx=00000000 edx=00000000 esi=aff40c3c edi=950ca008
eip=8b91a969 esp=aff40bc0 ebp=aff40bc0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!DMMVIDEOSIGNALMODE:ivideAndRound+0xa:
8b91a969 f7750c div eax,dword ptr [ebp+0Ch] ss:0010:aff40bcc=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: etqw.exe

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from 81cc0a44 to 81b0c135

STACK_TEXT:
aff40aec 81cc0a44 0000007f e0c72518 8b91a969 nt!KeBugCheck+0x14
aff40b40 81a97808 aff40b4c aff40bc0 8b91a969 nt!Ki386CheckDivideByZeroTrap+0x44
aff40b40 8b91a969 aff40b4c aff40bc0 8b91a969 nt!KiTrap00+0x88
aff40bc0 8b94a3a7 00000000 00000000 950ca008 dxgkrnl!DMMVIDEOSIGNALMODE:ivideAndRound+0xa
aff40c04 8b94e571 aff40c3c 00000001 00000000 dxgkrnl!DmmMapVSyncFromRationalToInteger+0x59
aff40cb4 8b94e0f0 9e553e08 00000001 00000001 dxgkrnl!DXGDEVICE::SetDisplayMode+0x152
aff40d48 90ee197b 0e0ef7c8 0e0ef7c0 aff40d64 dxgkrnl!DxgkSetDisplayMode+0x57b
aff40d58 81a96a7a 0e0ef7c8 0e0ef7dc 77d69a94 win32k!NtGdiDdDDISetDisplayMode+0x14
aff40d58 77d69a94 0e0ef7c8 0e0ef7dc 77d69a94 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0e0ef7dc 00000000 00000000 00000000 00000000 0x77d69a94


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl!DMMVIDEOSIGNALMODE:ivideAndRound+a
8b91a969 f7750c div eax,dword ptr [ebp+0Ch]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: dxgkrnl!DMMVIDEOSIGNALMODE:ivideAndRound+a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4893b1df

FAILURE_BUCKET_ID: 0x7f_0_dxgkrnl!DMMVIDEOSIGNALMODE:ivideAndRound+a

BUCKET_ID: 0x7f_0_dxgkrnl!DMMVIDEOSIGNALMODE:ivideAndRound+a

Followup: MachineOwner

 

[biervernichter]

dxgkrnl.sys

scheint ein DirectX problem zu geben..

versuch mal direct x neu zu installieren...


installier auch mal den Graka treiber neu

 

[werkam]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: etqw.exe

 

[cplpro]

Das ist der Fehler: UNEXPECTED_KERNEL_MODE_TRAP (7f)


http://support.microsoft.com/kb/137539

 

[elan-eo-akin]

Also ich bin ja gerade deswegen ratlos UNEXPECTED_KERNEL_MODE_TRAP (7f) sowie dxgkrnl.sys in einem Bluescreen versammelt!

Ist es jetzt mein Prozzi, der leicht übertaktet is un schon immer gut laeuft oder die Grafikkarte mit DirectX???

 

[cplpro]

Zuerst würde ich ein DirectX Update machen.

Tritt der Fehler auch bei anderen Programmen auf ?
Was sagen die Temps ?

 

[KL0k]

und da du meinst deine cpu is übertaktet -> mach mal n prime testlauf fürn paar stunden