Startup causes explorer to fail

[mcnulty_nathan]

Whenever i start up my PC i get an error of "windows explorer has
encountered a problem and needs to close", this is only a recent
problem, another annoying thing with it is, if i press the close buton
(i.e to allow windows explorer to restart, none of my startup programs
begin (including my Zone Alarm which then is manually started))
explorer then removes al the icons and what not and then restarts and
is fine, but i have no programs running.. i have all the latest winows
updates and am running XP (i am running ZONE ALARM security suite
'latest version') so i cannot believe it to be a virus, i have a
registry cleaner (registry mechanic).

PLEASE HELP

Nathan

p.s i can give you pretty much any usefull information you might need,
i kinda know my computers quite well but this one has got me stumped

 

[=?iso-8859-1?Q?_db_=B4=AF`=B7.._=3E=3C=29=29=29=BA]

ok,

go ahead and reboot into
safemode with networking.

then fiddle around in this
mode for a while and provide
us with feedback if the problem
is found or not found in safemode.

--

<)))º>·´¯`·.¸. , . .·´¯`·.. ><)))º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><)))º>

..

 

[Ken Blake]

ok,

go ahead and reboot into
safemode with networking.

then fiddle around in this
mode for a while

There is probably no more dangerous advice that can be given someone with a
problem than "fiddle around."

 

[glee]

Are you sure the programs are not running? Just because you do not see their icons
in the Notification Area does not mean they are not running....if explorer crashes
and restarts, the icons will disappear but the programs may still be running. Press
Ctrl+Alt+Del to open the Task Manager, and see if the Zone Alarm processes are
running, as well as whatever else is normally in your startup axis. Some things may
be listed on the Applications tab, but most will probably be on the Processes tab.

Lose Registry Mechanic. There is no reason or use for a Registry cleaner in XP,
except perhaps to help you break things. What have you 'fixed" with it, and have
you kept the backups it should be making for all its fixes?

As Ben mentioned, you can try starting in safe Mode to see if the Explorer error
occurs there...but heed Ken's warning and don't "fiddle around" there, just see if
the error occurs or not.

When you get the error (in normal or Safe Mode), click the Click Here link at the
bottom of the message box to see the data that the error report contains, and post
back with that info.

 

[mcnulty_nathan]

thanks for the idea, i had not thought of safe mode. no problem in
safe mode.. it also appears that some programs load, but only the
programs that managed to load before explorer crashed..

i have not used registry mechanic it was just something that i thought
might be useful so i added it to the bottom of the thread..

as afore mentioned the details on the mesage box are such:
The instruction at "0x7c883f9c" referenced memory at "0x7c883f9c". The
memory could not be "written".

this is then followed by two buttons close or cancel. close restarts
explorer and cancel debugs giving me the error:
dr whatson postmortem debugger has encountered a problem, this does
have a "click here" link, which says:
Event Type: BEX P1:drwtsn32.exe
P2:5.1.2600.0 P3:3b7d84a2 P4:dbghelp.dll
etc...


(sorry for the delay ben on holiday; appreciate the help)

 

[mcnulty_nathan]

thanks for the idea, i had not thought of safe mode. no problem in
safe mode.. it also appears that some programs load, but only the
programs that managed to load before explorer crashed..

i have not used registry mechanic it was just something that i thought
might be useful so i added it to the bottom of the thread..

as afore mentioned the details on the mesage box are such:
The instruction at "0x7c883f9c" referenced memory at "0x7c883f9c". The
memory could not be "written".

this is then followed by two buttons close or cancel. close restarts
explorer and cancel debugs giving me the error:
dr whatson postmortem debugger has encountered a problem, this does
have a "click here" link, which says:
Event Type: BEX P1:drwtsn32.exe
P2:5.1.2600.0 P3:3b7d84a2 P4:dbghelp.dll
etc...


(sorry for the delay ben on holiday; appreciate the help)

 

[glee]

In searching for some instances of your error, I found a few references to it
occurring due to an incompatibility between Kaspersky AntiVirus and Logitech
QuickCam software, and also references to incompatibility between Zone Alarm
Security Suite and Logitech QuickCam software.

http://forums.logitech.com/logitech/board/message?board.id=quickcam_software&message.id=25436

http://forums.zonealarm.com/zonelabs/board/message?board.id=Antivirus&message.id=20822

Do you have QuickCam software installed?

Can you list for us what you have starting with Windows, IOW, what is in your
startup axis?

 

[mcnulty_nathan]

thanks for the idea to use safe mode.. it does not occur whilst in
safe mode...

by the way i had not yet used registry mechanic, i had got it as i
tought it might be useful...

so booting normally i get the error:
The instruction at "0x7c883f9c" referenced memory at "0x7c883f9c". The
memory could not be "written".
and no option of finding out more. cancel will debug and close will
restart. so upon cancel i get the error:
dr watson postmortem debugger has failed blah blah, when i clicked to
get further informayion i got this:

Error type: BEX P1:drwtsn32.exe
P2:5.1.2600.0 P3:3b7d84a2 P4:dbghelp.dll

and some more numbers P5 etc...

thanks for the help realy appreciate it
sorry for the delay i have been away

 

[mcnulty_nathan]

thanks for the idea to use safe mode.. it does not occur whilst in
safe mode...

by the way i had not yet used registry mechanic, i had got it as i
tought it might be useful...

so booting normally i get the error:
The instruction at "0x7c883f9c" referenced memory at "0x7c883f9c". The
memory could not be "written".
and no option of finding out more. cancel will debug and close will
restart. so upon cancel i get the error:
dr watson postmortem debugger has failed blah blah, when i clicked to
get further informayion i got this:

Error type: BEX P1:drwtsn32.exe
P2:5.1.2600.0 P3:3b7d84a2 P4:dbghelp.dll

and some more numbers P5 etc...

thanks for the help realy appreciate it
sorry for the delay i have been away

 

[=?iso-8859-1?Q?_db_=B4=AF`=B7.._=3E=3C=29=29=29=BA]

well, the reason
that you do not encounter
the error in safe mode is clear,
because there are distinct differences
between it and normal mode.

basically, one of the benefits
of safemode is related to drivers.

in safe mode, only microsoft drivers that
are exclusive to windows are loaded
and all non microsoft drivers are excluded.

we refer to these different drivers as
first party and third party drivers.

unfortunately, we have absolutely
no idea as to what you have installed
on your pc that is designed to function
in normal mode, but it is likely something
from a third party that is corrupting your
operating system.

it would be safe to say that if you
removed or uninstalled all your third
party programs and their incompatible
or corrupted drivers, your windows would
function well in normal mode and similar under safemode.

of course, the above is only an
example to give you a clearer
understanding of your issue.

basically you need to hunt around
for the specific program running
in normal mode and is causing your
o.s. to dysfunctional or research
the error codes windows is providing
to you as they are clues to what the
problem may be.

however, i would suggest for you
to further research the question,
"what is safemode" for additional
information; as i only provided one
example for the purpose of safemode.

--

<)))º>·´¯`·.¸. , . .·´¯`·.. ><)))º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><)))º>

..

 

[mcnulty_nathan]

cannot reply: this is a test

 

[mcnulty.nathan]

thanks for the idea to use safe mode.. it does not occur whilst in
safe mode...

by the way i had not yet used registry mechanic, i had got it as i
tought it might be useful...

so booting normally i get the error:
The instruction at "0x7c883f9c" referenced memory at "0x7c883f9c". The
memory could not be "written".
and no option of finding out more. cancel will debug and close will
restart. so upon cancel i get the error:
dr watson postmortem debugger has failed blah blah, when i clicked to
get further informayion i got this:

Error type: BEX P1:drwtsn32.exe
P2:5.1.2600.0 P3:3b7d84a2 P4:dbghelp.dll

and some more numbers P5 etc...

thanks for the help realy appreciate it
sorry for the delay i have been away

 

[mcnulty.nathan]

thankyou i do have logitech quick cam software installed.. i did not
realise this..
and upon stopping the software from starting up the issue has been
resolved.
thankyou

 

[glee]

YW. Good to know!