- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a tablet with CPU: Atom z3735D. Its builtin gpu causes bsod when open webcam software, then open webcam properties. The webcam is built-in.
Dump attached.
windbg:
---------------------------------------------------------------------------------------------------------------------------------------
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\032915-13218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is: srv*
Windows 8 Kernel Version 9600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17328.x86fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0x8161c000 PsLoadedModuleList = 0x8181a498
Debug session time: Sun Mar 29 15:38:48.858 2015 (UTC + 3:00)
System Uptime: 0 days 0:06:40.330
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, 93cf6c40, 82acfb44, 9493dde0}
*** 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
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: 93cf6c40, Physical Device Object of the stack
Arg3: 82acfb44, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: 9493dde0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: igdkmd32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 548e641f
MODULE_NAME: igdkmd32
FAULTING_MODULE: 8d410000 igdkmd32
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
DPC_STACK_BASE: FFFFFFFF82AD4000
STACK_TEXT:
82acfb1c 817b82f5 0000009f 00000003 93cf6c40 nt!KeBugCheckEx
82acfb54 817b8241 00000000 81812810 00000a02 nt!PopIrpWatchdogBugcheck+0xae
82acfb68 8169ee56 8c7e3510 8c7e34c8 4dfa3ca5 nt!PopIrpWatchdog+0x28
82acfc20 8169ea66 82acfc68 00000000 88b14bc0 nt!KiExecuteAllDpcs+0x216
82acfd44 81730290 00000000 00000000 00000000 nt!KiRetireDpcList+0xf6
82acfd48 00000000 00000000 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_camera_IMAGE_igdkmd32.sys
BUCKET_ID: 0x9F_3_camera_IMAGE_igdkmd32.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_camera_image_igdkmd32.sys
FAILURE_ID_HASH: {d113fca4-7c99-b6fd-69d4-fcff2905392c}
Followup: MachineOwner
---------
0: kd> lmvm igdkmd32
start end module name
8d410000 8d704000 igdkmd32 T (no symbols)
Loaded symbol image file: igdkmd32.sys
Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
Image name: igdkmd32.sys
Timestamp: Mon Dec 15 07:31:27 2014 (548E641F)
CheckSum: 002E6921
ImageSize: 002F4000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !irp 9493dde0
Irp is active with 6 stacks 5 is current (= 0x9493dee0)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000...
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please try updating to the latest graphics drivers.
See the links below and download the driver for your operating system version.
https://downloadcenter.intel.com/download/24593/Intel-HD-Graphics-Driver-for-Windows-7-8-8-1-64-bit Intel® HD Graphics Driver for Windows* 7/8/8.1-64-bit
https://downloadcenter.intel.com/download/24592/Intel-HD-Graphics-Driver-for-Windows-7-8-8-1-32-bit Intel® HD Graphics Driver for Windows* 7/8/8.1 32-bit
Allan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
!Hi Alan,
I have installed the latest driver by following your link.
The issue still remains the same. New dump is attached.
The issue is the irp 'power change request' to intel camera.sys keeps pending for 1 min, then windows bsod due timeout. The irp:
0 e1 945ebdc0 00000000 8195f368-9390ef70 Success Error Cancel pending
\Driver\camera nt!PopRequestCompletion
Os: 32 bit win 8.1
Camera: gc2235.
Hardware ids: ACPI\VEN_INT&DEV_2235&SUBSYS_INTL0000
Intel camera driver info:
0: kd> lmvm camera
start end module name
a6c37000 a6cc3000 camera T (no symbols)
Loaded symbol image file: camera.sys
Image path: \SystemRoot\system32\DRIVERS\camera.sys
Image name: camera.sys
Timestamp: Wed Dec 10 11:23:18 2014 (548802F6)
CheckSum: 000773AA
ImageSize: 0008C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
The log:
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\033115-15812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is: srv*
Windows 8 Kernel Version 9600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17328.x86fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0x81874000 PsLoadedModuleList = 0x81a72498
Debug session time: Tue Mar 31 11:52:53.519 2015 (UTC + 3:00)
System Uptime: 0 days 0:03:09.991
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, 938f3c40, 82ccfb44, 9455bde0}
*** 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
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: 938f3c40, Physical Device Object of the stack
Arg3: 82ccfb44, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: 9455bde0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: igdkmd32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 548e641f
MODULE_NAME: igdkmd32
FAULTING_MODULE: 8d401000 igdkmd32
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
DPC_STACK_BASE: FFFFFFFF82CD4000
STACK_TEXT:
82ccfb1c 81a102f5 0000009f 00000003 938f3c40 nt!KeBugCheckEx
82ccfb54 81a10241 00000000 81a6a810 00000002 nt!PopIrpWatchdogBugcheck+0xae
82ccfb68 818f6e56 9390efb8 9390ef70 13313727 nt!PopIrpWatchdog+0x28
82ccfc20 818f6a66 82ccfc68 00000000 93939bc0 nt!KiExecuteAllDpcs+0x216
82ccfd44 81988290 00000000 fa5fedcb f417b15a nt!KiRetireDpcList+0xf6
82ccfd48 00000000 fa5fedcb f417b15a 27f256b0 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_camera_IMAGE_igdkmd32.sys
BUCKET_ID: 0x9F_3_camera_IMAGE_igdkmd32.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_camera_image_igdkmd32.sys
FAILURE_ID_HASH: {d113fca4-7c99-b6fd-69d4-fcff2905392c}
Followup: MachineOwner
---------
0: kd> lmvm igdkmd32
start end module name
8d401000 8d6f5000 igdkmd32 T (no symbols)
Loaded symbol image file: igdkmd32.sys
Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
Image name: igdkmd32.sys
Timestamp: Mon Dec 15 07:31:27 2014 (548E641F)
CheckSum: 002E6921
ImageSize: 002F4000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !irp 9455bde0
Irp is active with 6 stacks 5 is...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I recommend contacting the Tablet manufacturer, please bear in mind, the graphics engine driver provided on the link I gave you is different for tablets as it was developed for Desktop and Mobile computers.
Allan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Allan,
I did this, but have no reply from the Tablet manufacturer.
All those 3 related drivers was developed by Intel:
1. igdkmd32.sys
2. camera.sys
3. gc2235.sys
Everything was signed by Intel. Build Timestamps and checksums provided. Dump attached.
Could you please email this conversation to responsible developer to investigate?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The driver engine for desktop and mobile computers is different for Tablets. You need to either escalate this matter to different level of support with your Tablet manufacturer or get customized drivers from your tablet maker.
Allan.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page