Jump to content

Explorer.exe crash in Vista, Almost Solved, PLEASE HELP!


extremepilot

Recommended Posts

I used the INCREDIBLE sticky on how to generate a dmp, and it generated two, unfortunately each one is about 200mb so I wont upload, but here are the bits that I THINK SHOULD help solve the problem:

FIRST .DMP:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Boris\Desktop\PID-2168__EXPLORER.EXE__1st_chance_Process_Shut_Down__full_0ec4_2009-06-04_20-02-31-198_0878.dmp]

User Mini Dump File with Full Memory: Only application data is available

Comment: '1st_chance_Process_Shut_Down_exception_in_EXPLORER.EXE_running_on_IRENE-PC'

Symbol search path is: *** Invalid ***

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

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

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

Executable search path is:

Windows Vista Version 6000 MP (2 procs) Free x86 compatible

Product: WinNt, suite: SingleUserTS Personal

Machine Name:

Debug session time: Thu Jun 4 20:02:31.000 2009 (GMT-4)

System Uptime: 0 days 0:41:12.684

Process Uptime: 0 days 0:22:40.000

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

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

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

Loading unloaded module list

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

eax=000000c0 ebx=00000002 ecx=049ffd88 edx=00000000 esi=00000000 edi=00000000

eip=77860f34 esp=049ffca4 ebp=049ffd40 iopl=0 nv up ei pl zr na pe nc

cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -

ntdll!KiFastSystemCallRet:

77860f34 c3 ret

SECOND .DMP:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Boris\Desktop\PID-2168__EXPLORER.EXE__2nd_chance_UnknownException__full_0ec4_2009-06-04_20-01-58-134_0878.dmp]

User Mini Dump File with Full Memory: Only application data is available

Comment: '2nd_chance_UnknownException_exception_in_EXPLORER.EXE_running_on_IRENE-PC'

Symbol search path is: *** Invalid ***

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

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

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

Executable search path is:

Windows Vista Version 6000 MP (2 procs) Free x86 compatible

Product: WinNt, suite: SingleUserTS Personal

Machine Name:

Debug session time: Thu Jun 4 20:01:59.000 2009 (GMT-4)

System Uptime: 0 days 0:41:04.066

Process Uptime: 0 days 0:22:08.000

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

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

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

Loading unloaded module list

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

This dump file has an exception of interest stored in it.

The stored exception information can be accessed via .ecxr.

(878.2fc): Unknown exception - code c06d007e (first/second chance not available)

eax=0947e6b8 ebx=00000000 ecx=00000001 edx=00000000 esi=098292bc edi=00000000

eip=7640b09e esp=0947e6b8 ebp=0947e708 iopl=0 nv up ei pl nz ac pe nc

cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000216

*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -

kernel32!RaiseException+0x58:

7640b09e c9 leave

PLEASE HELP !! Thanks in advance!

Link to comment
Share on other sites


I FOUND THE CAUSE OF THE PROBLEM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

A BUGGY DRIVER FOR THE INTEL 4965AGN BUILT IN WIRELESS ADAPTER IN THE DELL M1330 LAPTOP!!!

Uninstalled Driver through Device Manager, Uninstalled driver software from Programs and Features, restarted computer, downloaded new driver DIRECTLY FROM THE DELL WEBSITE!!!

Hopefully this will help someone else in the future!!

Link to comment
Share on other sites

A BUGGY DRIVER FOR THE INTEL 4965AGN BUILT IN WIRELESS ADAPTER IN THE DELL M1330 LAPTOP!!!

Right from the absolute most basic info from the crash dump:

MODULE_NAME: WLIHVUI
IMAGE_NAME: WLIHVUI.dll
BUCKET_ID: c06d007e_WLIHVUI!DllUnregisterServer+bdcc
FAILURE_BUCKET_ID: APPLICATION_FAULT_c06d007e_WLIHVUI.dll!DllUnregisterServer

WLIHVUI.dll is part of the drivers for the intel proset/wireless driver.

Kind of a late reply on my part. Not really useful anymore, I know...

Hopefully this will help someone else in the future!!

It most likely won't. The chances of a specific explorer.exe crash being due to that specific driver problem is well below 1%. It could have been basically anything else (including any driver for any hardware pretty much). One has to have the crash dump to be able to know.

Link to comment
Share on other sites

Yup - looks like it was loading the device profile from an XML file when it crashed:

// The crashing thread:
0:044> kn
# ChildEBP RetAddr
00 0947e708 097ad05c kernel32!RaiseException+0x58
WARNING: Stack unwind information not available. Following frames may be wrong.
01 0947e770 097acd56 WLIHVUI!DllUnregisterServer+0xbdcc
02 0947e7ec 0977a8fa WLIHVUI!DllUnregisterServer+0xbac6
03 0947e8f0 097a59ab WLIHVUI+0x1a8fa
04 0947e9d0 097a4516 WLIHVUI!DllUnregisterServer+0x471b
05 0947eb0c 097a33e3 WLIHVUI!DllUnregisterServer+0x3286
06 0947ebf0 097a3d3e WLIHVUI!DllUnregisterServer+0x2153
07 0947ecdc 76511f4d WLIHVUI!DllUnregisterServer+0x2aae
08 0947ed64 76527021 ole32!CServerContextActivator::CreateInstance+0x172
09 0947eda4 76512071 ole32!ActivationPropertiesIn::DelegateCreateInstance+0x108
0a 0947edf8 76511fe6 ole32!CApartmentActivator::CreateInstance+0x112
0b 0947ee18 76511b5d ole32!CProcessActivator::CCICallback+0x6d
0c 0947ee38 76511b0e ole32!CProcessActivator::AttemptActivation+0x2c
0d 0947ee74 765120d4 ole32!CProcessActivator::ActivateByContext+0x4f
0e 0947ee9c 76527021 ole32!CProcessActivator::CreateInstance+0x49
0f 0947eedc 765270e7 ole32!ActivationPropertiesIn::DelegateCreateInstance+0x108
10 0947f13c 76527021 ole32!CClientContextActivator::CreateInstance+0xb0
11 0947f17c 76526f49 ole32!ActivationPropertiesIn::DelegateCreateInstance+0x108
12 0947f954 7653dbc7 ole32!ICoCreateInstanceEx+0x403
13 0947f9b4 7653de0a ole32!CComActivator::DoCreateInstance+0xd9
14 0947f9d8 7653ddc3 ole32!CoCreateInstanceEx+0x38
15 0947fa08 6d48d327 ole32!CoCreateInstance+0x37
16 0947fa34 6d48caee wlanui!IHVHelper::IHVHlpInitialize+0x2c
17 0947fa78 6d48ccdc wlanui!CAdvancedUI::ShowAdvancedUI+0x127
18 0947faa4 6d48cd48 wlanui!WLInvokeProfileUI+0x28
19 0947fadc 6d48ce30 wlanui!WLInvokeProfileUIFromXMLFile+0x47
1a 0947fb3c 650c1c3f wlanui!WlanUIEditProfile+0xa4
1b 0947fb98 650c250c wlanpref!ShowWlanProfileDialog+0x43
1c 0947fbcc 769c8b13 wlanpref!CPreflistContextMenu::InvokeCommand+0x129
1d 0947fc34 769c8a60 shell32!CShellExecute::_InvokeInProcExec+0xaf
1e 0947fc4c 769c8a1b shell32!CShellExecute::_InvokeCtxMenu+0x2e
1f 0947fc60 768ce1d2 shell32!CShellExecute::_DoExecute+0x4f
20 0947fc70 7745b132 shell32!CShellExecute::s_ExecuteThreadProc+0x25
21 0947fcec 76433823 shlwapi!WrapperThreadProc+0x10f
22 0947fcf8 7783a9bd kernel32!BaseThreadInitThunk+0xe
23 0947fd38 00000000 ntdll!_RtlUserThreadStart+0x23

// Looks like something wanted to bring up the wireless properties of the driver or the network places:
0:044> .frame 1b
1b 0947fb98 650c250c wlanpref!ShowWlanProfileDialog+0x43

0:044> dt ifaceguid
Local var @ 0x947fb78 Type _GUID
{704df1d0-0b07-4b19-84e8-9afac41e8306} // <- The GUID for a network interface, likely your wireless
0:044> dt strName
Local var @ 0x947fb74 Type WTL::CString
+0x000 m_pchData : 0x015d90fc "06B409947164"

// Loading the xml file:
0:044> .frame 19
19 0947fadc 6d48ce30 wlanui!WLInvokeProfileUIFromXMLFile+0x47
0:044> dt wstrProfileXmlInput
Local var @ 0x947fae4 Type wchar_t*
0x08089028 "<?xml version="1.0"?>..<WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1">...<name>06B409947164</name>...<SSIDConfig>....<SSID>....."

// Loading the UI extensibility CLSID, so the driver has hooks to extend the display properties:
0:044> .frame 08
08 0947ed64 76527021 ole32!CServerContextActivator::CreateInstance+0x172
0:044> dt pClsid
Local var @ 0x947ed18 Type _GUID*
0x05c07324
{1bf6cb2d-2ae0-4879-a7aa-a75834fbd0e3} // <- UI extensibility CLSID

0:044> lmvm wlihvui
start end module name
09760000 0984e000 WLIHVUI (export symbols) WLIHVUI.dll
Loaded symbol image file: WLIHVUI.dll
Image path: C:\Windows\System32\WLIHVUI.dll
Image name: WLIHVUI.dll
Timestamp: Mon Oct 08 17:21:43 2007 (470A9F67)
CheckSum: 000F7982
ImageSize: 000EE000
File version: 11.5.0.0
Product version: 11.5.0.0
File flags: 0 (Mask 3F)
File OS: 4 Unknown Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
ProductName: WLIHVUI Module
InternalName: WLIHVUI
OriginalFilename: WLIHVUI.DLL
ProductVersion: 11. 5. 0. 0
FileVersion: 11. 5. 0. 0
FileDescription: WLIHVUI Module
LegalCopyright: Copyright (c) Intel Corporation 1999-2007

... and then we go into the Intel driver, doing whatever it is it does with this data, and crashes. So, it seems the driver was using the UI extensibility APIs to load data from an xml file, and crashed doing whatever it was it was doing with the file. If the newer driver works, it would seem Intel has fixed the problem. I just posted so you could see what was happening - you already know the fix, but now you know why it was broken.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...