First BSOD this year ;)

[ionbasa]

well after about a year I got a bsod.
Its the computer in my specs.
Here is a quick snippet:
View attachment 100716
Here is the dump ziped:
View attachment 100717
Windows said this sysdata.xml file might be usefull:
View attachment 100719
Also I think this might be related.
View attachment 100718
it just started happening after my bsod. a right click context menue remains on the screen. it stays on topof every windows?
EDIT: look closely you can see a right click context menue on the screen as if it were a watermark.

 

[ionbasa]

any help would be greatly apreciated.

 

[zigzag3143]

well after about a year I got a bsod.
Its the computer in my specs.
Here is a quick snippet:
View attachment 100716
Here is the dump ziped:
View attachment 100717
Windows said this sysdata.xml file might be usefull:
View attachment 100719
Also I think this might be related.
View attachment 100718
it just started happening after my bsod. a right click context menue remains on the screen. it stays on topof every windows?
EDIT: look closely you can see a right click context menue on the screen as if it were a watermark.

YThis crash was caused was caused by your intel driver igdkmd64.sys. It needs to be updated. There are some really old drivers that need to be upgraded as well

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

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


Loading Dump File [C:\Users\K\Desktop\092710-33243-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e55e50
Debug session time: Mon Sep 27 20:28:09.778 2010 (GMT-4)
System Uptime: 0 days 10:17:44.287
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff880041848c6}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+1768c6 )

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: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff880041848c6

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  b

LAST_CONTROL_TRANSFER:  from fffff80002c87ca9 to fffff80002c88740

STACK_TEXT:  
fffff800`00ba4d28 fffff800`02c87ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02c86172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`041848c6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`01f9bff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : igdkmd64+0x1768c6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igdkmd64+1768c6
fffff880`041848c6 e865caffff      call    igdkmd64+0x173330 (fffff880`04181330)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  igdkmd64+1768c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aba7591

FAILURE_BUCKET_ID:  X64_0x7f_8_igdkmd64+1768c6

BUCKET_ID:  X64_0x7f_8_igdkmd64+1768c6

Followup: MachineOwner
---------

Old drivers

[SIZE=2][B][COLOR=Red]
mdmxsdk.sys        fffff880`035b7000    fffff880`035bb280    0x00004280    0x449716be    6/19/2006 17:27:26                        
xaudio64.sys        fffff880`061b4000    fffff880`061bc000    0x00008000    0x44d3e987    8/4/2006 20:42:47                        
CAX_CNXT.sys        fffff880`04eb2000    fffff880`04f7a000    0x000c8000    0x453672b0    10/18/2006 14:30:08                        
CAXHWAZL.sys        fffff880`04e5f000    fffff880`04eb2000    0x00053000    0x453672ed    10/18/2006 14:31:09                        
CAX_DPV.sys        fffff880`04a5e000    fffff880`04bd8000    0x0017a000    0x4536737a    10/18/2006 14:33:30                        
tifm21.sys        fffff880`03e48000    fffff880`03e9a000    0x00052000    0x4638512d    5/2/2007 04:51:57                        
nscirda.sys        fffff880`02cde000    fffff880`02ce6e00    0x00008e00    0x47919a5c    1/19/2008 02:36:12                        
vncmirror.sys        fffff880`03ec6000    fffff880`03ecd000    0x00007000    0x47dab929    3/14/2008 13:43:05      [/COLOR][/B][/SIZE]

 

[ionbasa]

thanks for the quick reply, now just to find out what those drivers belong to?

 

[CarlTR6]

Here is how to find drivers:

- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver

- compare the Google results with what's installed on your system to figure out which device/program it belongs to

- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
-
if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

- - To remove any left over driver remnants, especially from graphics cards, use driver sweeper Guru3D - Driver Sweeper

I hope this helps you.

 

[CarlTR6]

Here is additional help:

mdmxsdk.sys 6/19/2006 - Diagnostic Interface DRIVER or Diagnostic Interface x86 Driver or mdmxsdk belongs to the software Diagnostic Interface or Diagnostic Legacy Interface or mdmxsdk or Diagnostic Interface x86 Driver by Conexant (www.conexant.com).

xaudio64.sys 8/4/2006 - Conexant modem audio driver Conexant: Support

CAX_CNXT.sys 10/18/2006 - Conexant Modem Conexant: Support

CAXHWAZL.sys 10/18/2006 - Conexant Modem Conexant: Support

CAX_DPV.sys 10/18/2006 - Conexant Modem Conexant: Support

tifm21.sys 5/2/2007 - belongs to the software Texas Instruments PCIxx21/PCIxx12 Integrated FlashMedia Controller or Texas Instruments PCIxx21 PCIxx12 FlashMedia or Texas Instruments PCIxx21 PCIxx12 Integrated FlashMedia Controller or Texas Instruments PCIxx21 UltraMedia or tifm by Texas Instruments.

nscirda.sys 1/19/2008 - NSC Fast Infrared Driver: Windows Update

vncmirror.sys 3/14/2008 - VNC Mirror Miniport is a driver file from RealVNC Ltd. belonging to VNC Server for Windows.

 

[ionbasa]

Thank you for your help will update asap.

--maked as solved.