3 Replies Latest reply on Apr 26, 2010 3:26 PM by awbacker

    igdkmd64/i3 540 crashing widows 7 x64, no bsod but occastionally a .dmp file


      I am getting a crash when playing video, particularly full screen video, on my i3 540 HTPC.  Usually there is no .dmp file, but I have gotten 3 of them from the daily crashes in LiveKernelReports.   The problem is semi-intermittent, but nearly exclusively happens when playing video.  Out of the 50 or so crashes, 1 of them happened at desktop. 


      When playing the video, the system will freeze.  The display will present with ~14 columns, alternating between clean display and garbled.  The garbled columns appear like stacked = signs, about 20px high each, with alternating garbage and clean display (iirc.).   Anyway, it always presents the same way, leading me to believe it is a video issue.  Also, on reboot the machine needs to get through post with video off, then rebooted again to get video out to work.  This issue is the same using dvi=>hdmi or hdmi, but hdmi is even touchier.


      Memtest x86 runs overnight, far more than 10 passes.  Win7 mem check is fine.  Running distributed.net 4 threads for a day causes no issues, even when running furmark at the same time.   sfc /scannow returns clean.  All power saving options have been disabled.


      i3 540 stock

      asus p7h55m-pro

      toshiba 46" lcd - 1080p

      4gb ddr3 mushkin, 600W ocz psu,1 wd hdd, 1 dvd


      The 3 minidumps all point to igdkmd64.sys.  I have them to attach,  but can not in this forum software.  They look sorta like this, but this is from the previous (2086 build) if I am not mistaken.  I have not had a crash produce a .dmp file since then, it usually goes down too fast.


      Probably  caused by : igdkmd64.sys ( igdkmd64+1cc60 )

      !analyze -v

      Arg1: fffffa8006a184e0, Optional  pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
      Arg2: fffff88004833c60, The pointer into responsible device driver  module (e.g owner tag).
      Arg3: 0000000000000000, The secondary driver specific bucketing key.
      Arg4: 0000000000000000, Optional internal context dependent data.

      FAULTING_MODULE:  fffff80002c64000 nt

      FAULTING_IP: igdkmd64+1cc60

      TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

      fffff880`053b8630 fffffa80`0618a210 : fffff880`040b88a0  fffff8a0`02e21d19 fffffa80`03f48c10 fffff880`04833c60 : watchdog+0xa577
      fffff880`053b8638 fffff880`040b88a0 : fffff8a0`02e21d19  fffffa80`03f48c10 fffff880`04833c60 00000000`00000000 :  0xfffffa80`0618a210
      fffff880`053b8640 fffff8a0`02e21d19 : fffffa80`03f48c10  fffff880`04833c60 00000000`00000000 00000000`00000000 : dxgkrnl+0x1f8a0
      fffff880`053b8648 fffffa80`03f48c10 : fffff880`04833c60  00000000`00000000 00000000`00000000 fffffa80`000009d0 :  0xfffff8a0`02e21d19
      fffff880`053b8650 fffff880`04833c60 : 00000000`00000000  00000000`00000000 fffffa80`000009d0 00000000`00000000 :  0xfffffa80`03f48c10
      fffff880`053b8658 00000000`00000000 : 00000000`00000000  fffffa80`000009d0 00000000`00000000 00000000`00000000 : igdkmd64+0x1cc60

      0:  kd> lmvm igdkmd64
      start             end                 module name
      fffff880`04817000 fffff880`051ef3a0   igdkmd64 T (no symbols)          
           Loaded symbol image file: igdkmd64.sys
           Image path: igdkmd64.sys
           Image name: igdkmd64.sys
           Timestamp:        Wed Mar 31 15:47:01 2010 (4BB3D0E5)
           CheckSum:         009DC368
           ImageSize:        009D83A0
           Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4