8 Replies Latest reply on Jun 29, 2016 11:13 AM by Intel Corporation

    igdkmd32.sys causes BSOD on RCA W101 V2

    Dr_Spaceman

      Windows 10 RCA W101 V2 2in1 tablet/laptop, running an Intel Atom Z3735F board. This crash occurs at least once a day, often more. The info from the crash dumps is always the same:

       

       

       

      Microsoft (R) Windows Debugger Version 10.0.10586.567 X86

      Copyright (c) Microsoft Corporation. All rights reserved.

       

       

       

       

      Loading Dump File [C:\Users\Jim\Desktop\042116-17109-01.dmp]

      Mini Kernel Dump File: Only registers and stack trace are available

       

       

      Symbol search path is: srv*

      Executable search path is:

      Windows 10 Kernel Version 10240 MP (4 procs) Free x86 compatible

      Product: WinNt, suite: TerminalServer SingleUserTS Personal

      Built by: 10240.16644.x86fre.th1.160104-1507

      Machine Name:

      Kernel base = 0x8161d000 PsLoadedModuleList = 0x8185ea38

      Debug session time: Thu Apr 21 09:08:16.502 2016 (UTC - 4:00)

      System Uptime: 0 days 21:03:08.928

      Loading Kernel Symbols

      ...............................................................

      ................................................................

      ................................................................

      .........................

      Loading User Symbols

      *******************************************************************************

      *                                                                            *

      *                        Bugcheck Analysis                                    *

      *                                                                            *

      *******************************************************************************

       

       

      Use !analyze -v to get detailed debugging information.

       

       

      BugCheck 9F, {3, 90a3ca20, 82c97b30, 95c2a388}

       

       

      Implicit thread is now 899f6400

      *** WARNING: Unable to verify timestamp for igdkmd32.sys

      *** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys

      Probably caused by : igdkmd32.sys ( igdkmd32+31bd0 )

       

       

      Followup:    MachineOwner

      ---------

       

       

      0: kd> !analyze -v

      *******************************************************************************

      *                                                                            *

      *                        Bugcheck Analysis                                    *

      *                                                                            *

      *******************************************************************************

       

       

      DRIVER_POWER_STATE_FAILURE (9f)

      A driver has failed to complete a power IRP within a specific time.

      Arguments:

      Arg1: 00000003, A device object has been blocking an Irp for too long a time

      Arg2: 90a3ca20, Physical Device Object of the stack

      Arg3: 82c97b30, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

      Arg4: 95c2a388, The blocked IRP

       

       

      Debugging Details:

      ------------------

       

       

      Implicit thread is now 899f6400

       

       

      DUMP_CLASS: 1

       

       

      DUMP_QUALIFIER: 400

       

       

      BUILD_VERSION_STRING:  10240.16644.x86fre.th1.160104-1507

       

       

      SYSTEM_MANUFACTURER:  RCA

       

       

      SYSTEM_PRODUCT_NAME:  W101 V2

       

       

      SYSTEM_SKU:  Default string

       

       

      SYSTEM_VERSION:  Default string

       

       

      BIOS_VENDOR:  American Megatrends Inc.

       

       

      BIOS_VERSION:  5.6.5

       

       

      BIOS_DATE:  11/09/2015

       

       

      BASEBOARD_MANUFACTURER:  AMI Corporation

       

       

      BASEBOARD_PRODUCT:  Aptio CRB

       

       

      BASEBOARD_VERSION:  Default string

       

       

      DUMP_TYPE:  2

       

       

      BUGCHECK_P1: 3

       

       

      BUGCHECK_P2: ffffffff90a3ca20

       

       

      BUGCHECK_P3: ffffffff82c97b30

       

       

      BUGCHECK_P4: ffffffff95c2a388

       

       

      DRVPOWERSTATE_SUBCODE:  3

       

       

      FAULTING_THREAD:  899f6400

       

       

      CPU_COUNT: 4

       

       

      CPU_MHZ: 535

       

       

      CPU_VENDOR:  GenuineIntel

       

       

      CPU_FAMILY: 6

       

       

      CPU_MODEL: 37

       

       

      CPU_STEPPING: 8

       

       

      CPU_MICROCODE: 6,37,8,0 (F,M,S,R)  SIG: 830'00000000 (cache) 830'00000000 (init)

       

       

      CUSTOMER_CRASH_COUNT:  1

       

       

      DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

       

       

      BUGCHECK_STR:  0x9F

       

       

      PROCESS_NAME:  System

       

       

      CURRENT_IRQL:  2

       

       

      ANALYSIS_SESSION_HOST:  DESKTOP-JC9OSTJ

       

       

      ANALYSIS_SESSION_TIME:  04-24-2016 14:38:34.0906

       

       

      ANALYSIS_VERSION: 10.0.10586.567 x86fre

       

       

      LAST_CONTROL_TRANSFER:  from 8164865a to 81757c79

       

       

      STACK_TEXT:

      88db925c 8164865a 00000000 00000000 899f6400 nt!KiSwapContext+0x19

      88db92c8 81648069 88db9400 899f6400 00000000 nt!KiSwapThread+0x19a

      88db930c 81649ac9 00000000 8ecafb28 88db93f4 nt!KiCommitThreadWait+0x159

      88db93c4 8170170d 88db9400 0000001c 00000000 nt!KeWaitForSingleObject+0x299

      88db943c 818b2067 8185c2a0 00000005 88db99a4 nt!ExfAcquirePushLockSharedEx+0x13d

      88db9450 818b102a f94411b3 88db97fc 88db9888 nt!PopCurrentPowerState+0x191

      88db97e0 817539eb 00000005 00000000 00000000 nt!NtPowerInformation+0x43e

      88db97e0 81743a5d 00000005 00000000 00000000 nt!KiSystemServicePostCall

      88db986c 96171bd0 00000005 00000000 00000000 nt!ZwPowerInformation+0x11

      WARNING: Stack unwind information not available. Following frames may be wrong.

      88db99c8 96172af4 94858000 c000000d 00000000 igdkmd32+0x31bd0

      88db9b10 96171829 00000001 00000001 00000000 igdkmd32+0x32af4

      88db9b58 8b7af810 94858000 ffffffff 00000001 igdkmd32+0x31829

      88db9b84 8b7af35c ffffffff 00000001 00000000 dxgkrnl!DpiDxgkDdiSetPowerState+0x32

      88db9be4 8b7afad7 9482b020 00000001 00000000 dxgkrnl!DpiFdoSetAdapterPowerState+0x1ec

      88db9c30 8b7af516 9482b020 95c2a388 88db9d08 dxgkrnl!DpiFdoHandleDevicePower+0x285

      88db9c40 8b7af4b9 9482b020 95c2a388 9482b020 dxgkrnl!DpiFdoDispatchPower+0x28

      88db9d08 8172e696 9482b020 95c2a388 00000000 dxgkrnl!DpiDispatchPower+0x6f

      88db9d70 816d3c91 00000000 f9441be3 00000000 nt!PopIrpWorker+0x2b4

      88db9db0 81758491 8172e3e2 00000000 00000000 nt!PspSystemThreadStartup+0x5b

      88db9dbc 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x15

       

       

       

       

      STACK_COMMAND:  .thread 0xffffffff899f6400 ; kb

       

       

      THREAD_SHA1_HASH_MOD_FUNC:  b5c4d2ea9d99080517f419586c35e489af74a39e

       

       

      THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  7a605754a1603bf9a22be034aaebd9799cc6ac4a

       

       

      THREAD_SHA1_HASH_MOD:  0fcaa5a2935b892939b68e0ea0838ff2b6ad0a21

       

       

      FOLLOWUP_IP:

      igdkmd32+31bd0

      96171bd0 ??              ???

       

       

      SYMBOL_STACK_INDEX:  9

       

       

      SYMBOL_NAME:  igdkmd32+31bd0

       

       

      FOLLOWUP_NAME:  MachineOwner

       

       

      MODULE_NAME: igdkmd32

       

       

      IMAGE_NAME:  igdkmd32.sys

       

       

      DEBUG_FLR_IMAGE_TIMESTAMP:  55d1fef7

       

       

      BUCKET_ID_FUNC_OFFSET:  31bd0

       

       

      FAILURE_BUCKET_ID:  0x9F_3_igdkmd32!Unknown_Function

       

       

      BUCKET_ID:  0x9F_3_igdkmd32!Unknown_Function

       

       

      PRIMARY_PROBLEM_CLASS:  0x9F_3_igdkmd32!Unknown_Function

       

       

      TARGET_TIME:  2016-04-21T13:08:16.000Z

       

       

      OSBUILD:  10240

       

       

      OSSERVICEPACK:  0

       

       

      SERVICEPACK_NUMBER: 0

       

       

      OS_REVISION: 0

       

       

      SUITE_MASK:  784

       

       

      PRODUCT_TYPE:  1

       

       

      OSPLATFORM_TYPE:  x86

       

       

      OSNAME:  Windows 10

       

       

      OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

       

       

      OS_LOCALE:

       

       

      USER_LCID:  0

       

       

      OSBUILD_TIMESTAMP:  2016-01-04 20:38:42

       

       

      BUILDDATESTAMP_STR:  160104-1507

       

       

      BUILDLAB_STR:  th1

       

       

      BUILDOSVER_STR:  10.0.10240.16644.x86fre.th1.160104-1507

       

       

      ANALYSIS_SESSION_ELAPSED_TIME: 3374

       

       

      ANALYSIS_SOURCE:  KM

       

       

      FAILURE_ID_HASH_STRING:  km:0x9f_3_igdkmd32!unknown_function

       

       

      FAILURE_ID_HASH:  {c8b600bb-a3a9-f931-913f-0aa6a83c47e7}

       

       

      Followup:    MachineOwner

      ---------

       

       

       

      Additionally, a warning sign of an impending crash is the cessation of any fluctuations shown in CPUID HWMonitor for temperature, voltages, or anything else. I'm not sure how to interpret this, but I assume the fluctuations continue but just aren't being shown due to a graphics problem. If I stop and restart the program, it either fails to load, or shows a blank screen.

       

       

      I have also noticed on this system, in that same program, that the max value given for the temperature of "GT" (not sure what that is but I assume it is graphics-related) will be a nonsensically high 216C...always that same value...as opposed to the 40-50C normally shown for the max core temperatures.

       

       

      That does not signify an impending crash, the system continues to work fine in that instance, I'm also not sure how to interpret this or even if it's related to the BSODs, but I'm throwing it in anyway.