Explorer.exe

[donjuan17]

okay this is making me mad
i just clean installed a genuine copy of xp(actual disk not burned).
I havent installed no programs on it yet. and every 25 to 30 minutes or so
my computer will just freeze up solid.
but when i go to task manager and end expleror.exe and restart it
it works just fine.
i don't understand it.
help would be greatly appreciated

[Lerroy_Jenkins]

What are you doing in explorer when it crashes?

[RobDog888]

do you have any other programs installed or just the plain OS? Any service packs installed / windows updates?

[alex_read]

You can use both the Windows event viewer logs and performance monitor to try and track down the problem here.

[Hack]

Have you applied service packs?

[donjuan17]

Have you applied service packs?

thanks man just installed service pack 3 for Xp
and it did the trick
thank you so much

[RobDog888]

Installing a service pack shouldnt really be a fix as straight out of the box an unpatched XP instance shouldnt be doing that to begin with.

[donjuan17]

it is my oem disk (with SP2). i fresh installed it and booted up windows
30 minutes after i was just browsing through my secondary D drive and freeze.
after i ended experor.exe and restarted it i went to internet expleror and it froze again. its the strangest thing because i had just installed windows.

but after i installed service pack like HACK told me to do it seemed to work just fine.
sense then i'v installed IE7 and AVGfree 8.0 as well as comodo firewall pro.

do you think the sp3 fixed a glitch or something or what?

[RobDog888]

Well whenever you install an OS you ALWAYS need to do a Windows Update which will install hotfixes and service packs. But for a problem like that with Explorer it shouldnt be happening on an unpatched install. Its too major of an issue for Bill to let out of the production like that and many many others would have complained about it too.

[donjuan17]

i know. its never happened to me before. iv used the oem before and its never done it to me.
do you think it is a hardware issue lurking and waiting to strike again.

[RobDog888]

Its possible but it could be a hardware issue like a bad driver perhaps but could be fixed with the SP as they also have drivers in them too. Its really hard to say.

[Lerroy_Jenkins]

By the sounds of it I would say there was a line of code that went missing when you were installing your OS. It happens all the time, well some times during my working day and my small team are responsible for 300 PC's. So we get through PC's quite quickly.

A Service pack SHOULDN'T of solved the problem as RobDog888 has stated, firstly Bill Gates and his crew would not allow something like that to of happened. Secondly if that type of thing DID happen, people here wouldn't be so perplexed (Correct me if that is the wrong word) when it did happen.

[drag0n_45]

A Service pack SHOULDN'T of solved the problem as RobDog888 has stated,

I disagree. If XP clean were to come out, then some hardware were to come out afterwards and have incompatibilities with Windows XP (no SP), Microsoft would have realized this and released an update to address that new hardware. That's probably what happened in this case.

[RobDog888]

No, then that would be a driver issue which SP's do also contain but you could have installed the proper driver if you had "new" hardware.

[drag0n_45]

Rob, are you trying to say that you've never seen software or hardware that's made for Windows XP SP2 ONLY?

[drag0n_45]

I know. I wasn't referring to a driver. I was referring to a functionality. I have seen some programs and software that will only work on SP2. I understand the concept of a driver and installing it in Service Pack 2, but there were also plenty of programmatic and functional additions to the service pack.

I can find you a sample of such software if you'd like, as software would eliminate the driver discussion.

My point is that there may be some programmatic functionality that the system is trying to use that just isn't there in SP2.

[RobDog888]

Well alex posted something good on the topic but anyways... the addition on a service pack on an OS still should never be a solution in general but with newer systems/hardware coming out (XP is what like 7 years old) more issues could arise that are hardware related and fixed with drivers either provided by the hardware manufacturer's driver on a accompanied cd or if they have got MS to add their driver to a service pack then that will fix it but ultimately a servce pack is not the real solution here. Obtaining the correct driver from the manufacturer is the best solution.

[drag0n_45]

Oh I'm not arguing that point - that would be the first thing I'd try. I'm just saying I've seen those nonstandard programs and hardware out there. (For example, a crappy TV tuner card I bought a few years back.) So he may just have something of the like.

[RobDog888]

Oh yea in that regards then that is different. On a "standard" system either from a name brand manufacturer like Dell or HP you will never have an issue with XP and no service packs. They design their hardware to be most stable working with each other and best performing too. The problems arise when you get thsoe off the wall hardware pieces in your system. Even their drivers can cause issues as usually they are not of the best quality as they are going for quantity to make more $

[drag0n_45]

Exactly. So That's why SP2 worked. Aftermarket parts.

[RobDog888]

Well parts that were manufacturered after so they didnt get a chance to send their drivers to MS for inclusion in the base OS

Guess this thread can be Resolved now?

[drag0n_45]

Or that.