igdkmd32.sys causes BSOD on RCA W101 V2

[JK_]

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

...

[idata]

Hello, Dr_Spaceman:

Thank you for contacting the Intel Communities.In this case, the issue could be related to the driver itself, for the platform your are currently using (Intel® Atom™ Processor Z3735F) the driver support is available from the OEM side.My recommendation would be to create a BSOD dump file, please check link below, and then report the issue to the manufacturer of this device adding that file.Creating file: http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669dOEM support site: https://rcasupport.formstack.com/forms/support https://rcasupport.formstack.com/forms/supportIf any additional questions or inquiries are present, feel free to contact us back.Regards,Esteban C

[idata]

Hello, Dr_Spaceman:

Thought I would just check in and find out if you were able to resolve this problem.I look forward to hearing from you.Regards,Esteban C

[JK_]

Hello, I have had some distractions lately and so haven't been able to pursue this matter, but rest assured I will be getting back to it. Thank you for your interest.

[idata]

Great, thank you for letting me know that.

I look forward to hearing from you.Regards,Esteban C

[idata]

Hello, Dr_Spaceman:

I was checking this thread and I would like to know if there is any update regarding the information requested previously.I look forward to hearing from you.Regards,Esteban C

[idata]

Hello, Dr_Spaceman:

I was checking this thread and I would like to know if you were able to get this resolved or gather up the BSOD dump file requested in order to further assist you on this.Look forward to hearing from you.Regards,Esteban C

[JK_]

Hello again, I am sorry for not replying for so long, I've just been preoccupied with other things. I can tell you that RCA Support was distinctly unhelpful. I believe the first couple of responses were auto-generated, as they displayed no understanding of what I had written in my ticket.

Then I was told to try a hard reset, and if that doesn't work, send it to them for warranty service. The good news is, the problem seems to have cleared up by itself. I don't know why, but if it starts again I will be looking for help again.

[idata]

Oh well Dr_Spaceman, it is good to hear that the issue has been solved by itself hehe.

I will be setting your last comment as correct answer to finish up with this thread, hope you don't mind.But if additional or further inquiries are present, feel free to contact us back.Regards,Esteban C