Unsolved
This post is more than 5 years old
22 Posts
0
122782
October 22nd, 2013 14:00
System crash on E7440 + Windows 7 x64
Anyone else come across a system crash on the E7440 laptop? I believe it is related to the audio driver.
Thanks!
Loading Dump File [Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0020d7f2? DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`018b1902? Symbol search path is: SRV*C:\My\Sym*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504 Machine Name: Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e49670 Debug session time: Wed Oct 16 05:49:31.303 2013 (UTC - 4:00) System Uptime: 0 days 2:25:26.100 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa800c74f040, fffff80000b9c3d0}
*** WARNING: Unable to verify timestamp for IntcDAud.sys *** ERROR: Module load completed but symbols could not be loaded for IntcDAud.sys Implicit thread is now fffffa80`0c74f040 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : portcls.sys ( portcls!DispatchPnp+3dd )
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 (usually 10 minutes). Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa800c74f040, The thread currently holding on to the Pnp lock. Arg4: fffff80000b9c3d0, nt!TRIAGE_9F_PNP on Win7
Debugging Details: ------------------
Implicit thread is now fffffa80`0c74f040
DRVPOWERSTATE_SUBCODE: 4
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002c79c12 to fffff80002c8708a
STACK_TEXT: fffff880`033c42a0 fffff800`02c79c12 : fffffa80`0c74f040 fffffa80`0c74f040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a fffff880`033c43e0 fffff800`02c8af9f : fffffa80`0f474e10 00000000`00000002 fffffa80`00000000 00000000`000007ff : nt!KiCommitThreadWait+0x1d2 fffff880`033c4470 fffff800`02d8bf55 : fffff880`06f4e100 fffffa80`00000000 fffff880`06f4e100 fffffa80`10d6f600 : nt!KeWaitForSingleObject+0x19f fffff880`033c4510 fffff880`06f52495 : fffffa80`0f47b1b0 fffffa80`10d6f690 fffff880`6864534b fffffa80`10d6f690 : nt!IoReleaseRemoveLockAndWaitEx+0x45 fffff880`033c4550 fffff880`06f5207c : 00000000`c000000d fffffa80`10d6f690 fffff880`06ed2100 fffff800`02f76f16 : portcls!DispatchPnp+0x3dd fffff880`033c45b0 fffff880`06edee8e : fffffa80`0f47b3b0 fffff880`06ed2100 fffffa80`0f47b060 00000000`00000000 : portcls!PcDispatchIrp+0x6c fffff880`033c45e0 fffffa80`0f47b3b0 : fffff880`06ed2100 fffffa80`0f47b060 00000000`00000000 fffff8a0`028104f0 : IntcDAud+0x1ce8e fffff880`033c45e8 fffff880`06ed2100 : fffffa80`0f47b060 00000000`00000000 fffff8a0`028104f0 fffff880`06f94889 : 0xfffffa80`0f47b3b0 fffff880`033c45f0 fffffa80`0f47b060 : 00000000`00000000 fffff8a0`028104f0 fffff880`06f94889 fffffa80`10d6f8c8 : IntcDAud+0x10100 fffff880`033c45f8 00000000`00000000 : fffff8a0`028104f0 fffff880`06f94889 fffffa80`10d6f8c8 fffffa80`10d6f910 : 0xfffffa80`0f47b060
STACK_COMMAND: kb
FOLLOWUP_IP: portcls!DispatchPnp+3dd fffff880`06f52495 498bcc mov rcx,r12
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: portcls!DispatchPnp+3dd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: portcls
IMAGE_NAME: portcls.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc03
FAILURE_BUCKET_ID: X64_0x9F_4_portcls!DispatchPnp+3dd
BUCKET_ID: X64_0x9F_4_portcls!DispatchPnp+3dd
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 (usually 10 minutes). Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa800c74f040, The thread currently holding on to the Pnp lock. Arg4: fffff80000b9c3d0, nt!TRIAGE_9F_PNP on Win7
Debugging Details: ------------------
Implicit thread is now fffffa80`0c74f040
DRVPOWERSTATE_SUBCODE: 4
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002c79c12 to fffff80002c8708a
STACK_TEXT: fffff880`033c42a0 fffff800`02c79c12 : fffffa80`0c74f040 fffffa80`0c74f040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a fffff880`033c43e0 fffff800`02c8af9f : fffffa80`0f474e10 00000000`00000002 fffffa80`00000000 00000000`000007ff : nt!KiCommitThreadWait+0x1d2 fffff880`033c4470 fffff800`02d8bf55 : fffff880`06f4e100 fffffa80`00000000 fffff880`06f4e100 fffffa80`10d6f600 : nt!KeWaitForSingleObject+0x19f fffff880`033c4510 fffff880`06f52495 : fffffa80`0f47b1b0 fffffa80`10d6f690 fffff880`6864534b fffffa80`10d6f690 : nt!IoReleaseRemoveLockAndWaitEx+0x45 fffff880`033c4550 fffff880`06f5207c : 00000000`c000000d fffffa80`10d6f690 fffff880`06ed2100 fffff800`02f76f16 : portcls!DispatchPnp+0x3dd fffff880`033c45b0 fffff880`06edee8e : fffffa80`0f47b3b0 fffff880`06ed2100 fffffa80`0f47b060 00000000`00000000 : portcls!PcDispatchIrp+0x6c fffff880`033c45e0 fffffa80`0f47b3b0 : fffff880`06ed2100 fffffa80`0f47b060 00000000`00000000 fffff8a0`028104f0 : IntcDAud+0x1ce8e fffff880`033c45e8 fffff880`06ed2100 : fffffa80`0f47b060 00000000`00000000 fffff8a0`028104f0 fffff880`06f94889 : 0xfffffa80`0f47b3b0 fffff880`033c45f0 fffffa80`0f47b060 : 00000000`00000000 fffff8a0`028104f0 fffff880`06f94889 fffffa80`10d6f8c8 : IntcDAud+0x10100 fffff880`033c45f8 00000000`00000000 : fffff8a0`028104f0 fffff880`06f94889 fffffa80`10d6f8c8 fffffa80`10d6f910 : 0xfffffa80`0f47b060
STACK_COMMAND: kb
FOLLOWUP_IP: portcls!DispatchPnp+3dd fffff880`06f52495 498bcc mov rcx,r12
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: portcls!DispatchPnp+3dd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: portcls
IMAGE_NAME: portcls.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc03
FAILURE_BUCKET_ID: X64_0x9F_4_portcls!DispatchPnp+3dd
BUCKET_ID: X64_0x9F_4_portcls!DispatchPnp+3dd
Followup: MachineOwner ---------
drmaddog
22 Posts
0
October 28th, 2013 14:00
Dkalmick
11 Posts
0
November 14th, 2013 17:00
We're also having this issue on Win7 64 E7440. Machine won't go to sleep anymore. On sleep it just hangs requiring a hard shutdown. Found the this post by google search for the same dump code. I'm seeing IntcDAud.sys, Portcls.sys as potential problems. So yah, I'm thinking it it's an audio driver. This doesn't seem to have any connection to the dock as the machine will put itself to sleep as per its timer and never makes it asleep. Ran Dell Client update, no driver update...thought it could've been a rootkit, but it sounds like this is a driver issue. I'll open a case with prosupport.
egardiner
1 Message
0
December 20th, 2013 06:00
Just wanted to add a "me too," as I am seeing what appears to be the same issue (BSOD on closing e7440 lid; appears related to docking/undocking). The memory dump I looked at also indicated portcls.sys as the likely cause. I'm also running Win7 64-bit.
Dkalmick
11 Posts
0
December 20th, 2013 09:00
I think we solved it. Corrupt audio or the usb 3.0 and chipset driver. Uninstall and reinstall all three. Sorry I was in a huge hurry and didn't have time to troubleshoot. I think there may have been a problem with dell's image. just go grab he new drivers then uninstall restart then reinstall. Haven't seen the problem since
drmaddog
22 Posts
0
December 23rd, 2013 07:00
Thanks for the information Dkalmick!
I hope to be able to try this out either today or tomorrow.