I have Windows XP SP2 and its been working fine for a couple months (its a fairly new pc) until this happened. Now when ever i right click on anything on the desktop it shows it loading......and then it stops loading and shows the regular mouse. Then it shows it loading again. Then its done. But nothings right clicked!. Then explorer crashes and show the "send errror report, dont send error report, or debug" I hit debug and then the debugger crashs too. I did find a crash file...(I moved it to the desktop for easier access. It was in C:/WINDOWS/Internet Logs/)

Microsoft ® Windows Debugger Version 6.5.0003.7

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Documents and Settings\xxxxx\Desktop\explorer_2nd_2005_10_03_22_ 16_25_small.dmp]User Mini Dump File: Only registers, stack and portions of memory are available

Comment: 'Zone Labs self-generated second chance exception dump. Use .ecxr to see the correct fault stack.

Thread times

tid User Kernel (hh:mm:ss)

-----------------------------------

0xb50 00:00:00 / 00:00:00

0x350 00:00:00 / 00:00:00

0xc84 00:00:00 / 00:00:00

0x94c 00:00:00 / 00:00:00

0xf24 00:00:00 / 00:00:01

0xd68 00:00:00 / 00:00:00

0xee8 00:00:00 / 00:00:04

0xf10 00:00:00 / 00:00:00

0xb88 00:00:00 / 00:00:00

0xbe4 00:00:00 / 00:00:00

0xc80 00:00:00 / 00:00:00

0xd60 00:00:00 / 00:00:00

0xd28 00:00:00 / 00:00:00

0xd2c 00:00:00 / 00:00:00

0xd0c 00:00:00 / 00:00:00

0xd5c 00:00:00 / 00:00:00

0xd18 00:00:00 / 00:00:00

0xfb0 00:00:00 / 00:00:00

0x5f0 00:00:00 / 00:00:00

0xfa0 00:00:02 / 00:00:02

0x71c 00:00:00 / 00:00:00

0xc94 00:00:00 / 00:00:00

0x4d4 00:00:00 / 00:00:00

'

Windows XP Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: SingleUserTS Personal

Debug session time: Mon Oct 3 22:16:27.000 2005 (GMT-4)

System Uptime: not available

Process Uptime: 0 days 0:02:05.000

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:

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

(b4c.fa0): Access violation - code c0000005 (!!! second chance !!!)

eax=03ed0000 ebx=00000000 ecx=00000007 edx=7c90eb94 esi=0142d9bc edi=0142d9c4

eip=7c90eb94 esp=0142cf3c ebp=0142cf4c iopl=0 nv up ei pl zr na po 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:

7c90eb94 c3 ret

Once i see

Comment: 'Zone Labs self-generated second chance exception dump. Use .ecxr to see the correct fault stack.

I am thinking thats it a problem with my Zone Alarm Security Suite, but it never did this before. So i shut it down and explorer still crashed. I dont want to uninstall my security suite but...

Maybe a smarter person than me can find out whats happening because right now I'm out of options, besides DELL Support..

HELP!!!!

I doubt it's a problem with ZoneAlarm. The program aparently just generates its own log when something crashes.

From the look of the error, a symbol in ntdll.dll is missing. Maybe that file got messed up?

then could someone share me there ntdll.dll?

It's on the recovory CD, but I don't know how to restore specific files manually.

I got an idea! Open up the command prompt and enter

sfc /scannow

If the file is corrupt it will tell you.

i got a Windows File Message about DLL Cache

Guys, a second-chance exception means the app crashed. If Zone Alarm self-generated a second-chance exception, it's most likely because internally it created a first-chance exception (internal error) that it couldn't deal with, so it crashed itself (aka a second-chance exception). So yes, ZoneAlarm is indeed at fault here.