tpenninckx

Hello,

I've got a problem on a user's workstation.
At each boot, she gets an 'Explorer.exe has generated errors and will be close'.
If she logs off an log on, his session opens normally.

Here is the WINDBG result, can anyone help me to solve this ?

(I checked the shlwapi.dll file, it's exactly the same as on the others workstations)

Thanks
Thierry

!analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
*************************************************************************

FAULTING_IP:
+35f750ec
35f750ec ?? ???

EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
ExceptionAddress: 35f750ec
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 35f750ec
Attempt to read from address 35f750ec

FAULTING_THREAD: 00000630

DEFAULT_BUCKET_ID: CODE_RUNNING_ON_HEAP

PROCESS_NAME: Explorer.EXE

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

READ_ADDRESS: 35f750ec

BUGCHECK_STR: ACCESS_VIOLATION

IP_ON_HEAP:
+35f750ec
35f750ec ?? ???

LAST_CONTROL_TRANSFER: from 77e3a3d0 to 35f750ec

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
0108fe44 77e3a3d0 000100a4 0000c0d4 00200044 0x35f750ec
0108fe64 77e14750 35f750ec 000100a4 0000c0d4 USER32!UserCallWinProc+0x18
0108fe80 77e155b0 0044bce0 0000c0d4 00200044 USER32!DispatchClientMessage+0x4b
0108fea8 77f9ff57 0108feb8 00000018 0044bce0 USER32!__fnDWORD+0x22
0108ff20 70ac50ff 0108ff48 00000000 00000000 ntdll!KiUserCallbackDispatcher+0x13
0108ff74 70ac543d 0108ffa0 0108ffa4 0108ffa8 SHLWAPI!CThreadPool::RemoveWorkItem+0xc1
0108ffac 70ac551b 0006e76c 7c57b388 00000000 SHLWAPI!CThreadPool::Worker+0x2c
0108ffb4 7c57b388 00000000 00000001 0006e76c SHLWAPI!CThreadPool::WorkerThread+0x30
0108ffec 00000000 70ac54eb 00000000 00000000 KERNEL32!BaseThreadStart+0x52


FAILED_INSTRUCTION_ADDRESS:
+35f750ec
35f750ec ?? ???

FOLLOWUP_IP:
SHLWAPI!CThreadPool::RemoveWorkItem+c1
70ac50ff 85c0 test eax,eax

SYMBOL_STACK_INDEX: 5

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SHLWAPI!CThreadPool::RemoveWorkItem+c1

MODULE_NAME: SHLWAPI

IMAGE_NAME: SHLWAPI.DLL

DEBUG_FLR_IMAGE_TIMESTAMP: 43165e29

STACK_COMMAND: ~4s ; kb

FAILURE_BUCKET_ID: ACCESS_VIOLATION_BAD_IP_SHLWAPI!CThreadPool::RemoveWorkItem+c1

BUCKET_ID: ACCESS_VIOLATION_BAD_IP_SHLWAPI!CThreadPool::RemoveWorkItem+c1

Followup: MachineOwner
---------