1 Reply Latest reply on May 4, 2010 5:32 PM by digkstra

    driver stuck in an infinite loop



      The driver igxprd32 for the display device \Device\Video0 got stuck in an infinite loop.  The same problem with


      Driver_version: Ver:
      Game_application: torchlight
      Desktop_Screen_Resolution: 1280 x1024
      Desktop Color Depth: True Color (32 bit)
      Desktop_Refresh_Rate: 60 Hz
      Issue: driver infinite loop
      diagnostic_report:      Intel(R) Graphics Media Accelerator Driver Report

      Report Date:            11/08/2009
      Report Time[hr:mm:ss]:  18:38:30
      Driver Version:
      Operating System:               Windows XP* Professional, Service Pack 3 (5.1.2600)
      Default Language:               Russian
      DirectX* Version:               9.0
      Physical Memory:                3037 MB
      Minimum Graphics Memory:        32 MB
      Maximum Graphics Memory:        256 MB
      Graphics Memory in Use: 16 MB
      Processor:              x86 family 6 Model 23 Stepping 10
      Processor Speed:                2806 MHZ
      Vendor ID:              8086
      Device ID:              2E22
      Device Revision:                03

      *   Accelerator Information   *

      Accelerator in Use:             Intel(R) G45/G43 Express Chipset
      Video BIOS:             1702.0
      Current Graphics Mode:  1280 x 1024 True Color (60 Hz)


      The device driver is spinning in an infinite loop, most likely waiting for
      hardware to become idle. This usually indicates problem with the hardware
      itself or with the device driver programming the hardware incorrectly.
      If the kernel debugger is connected and running when watchdog detects a
      timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
      and detailed message including bugcheck arguments will be printed to the
      debugger. This way we can identify an offending thread, set breakpoints in it,
      and hit go to return to the spinning code to debug it further. Because
      KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
      information in this case. The arguments are already printed out to the kernel
      debugger. You can also retrieve them from a global variable via
      "dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
      On MP machines it is possible to hit a timeout when the spinning thread is
      interrupted by hardware interrupt and ISR or DPC routine is running at the time
      of the bugcheck (this is because the timeout's work item can be delivered and
      handled on the second CPU and the same time). If this is the case you will have
      to look deeper at the offending thread's stack (e.g. using dds) to determine
      spinning code which caused the timeout to occur.
      Arg1: 893ba4c8, Pointer to a stuck thread object.  Do .thread then kb on it to find
             the hung location.
      Arg2: 89699ab0, Pointer to a DEFERRED_WATCHDOG object.
      Arg3: 8936c5d0, Pointer to offending driver name.
      Arg4: 00000003, Number of times this error occurred.  If a debugger is attached,
             this error is not always fatal -- see DESCRIPTION below.  On the
             blue screen, this will always equal 1.

      Debugging Details:

      ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

      Could not read faulting driver name
      ERROR - could not read driver name for bugcheck parameter 3

      Mini Kernel Dump does not contain unloaded driver list

      FAULTING_THREAD:  893ba4c8



      LAST_CONTROL_TRANSFER:  from 00000000 to bf06c816

      8a41b1b0 00000000 00000000 00000000 00000000 igxpdv32+0xe816

      STACK_COMMAND:  .thread ffffffff893ba4c8 ; kb

      bf06c816 f6c410           test    ah,0x10

      FOLLOWUP_NAME:  MachineOwner

      SYMBOL_NAME:  igxpdv32+e816

      MODULE_NAME:  igxpdv32

      IMAGE_NAME:  igxpdv32.DLL