Question Locked

Explorer is hanging at login and other odd times

0 helpful
22 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am Running Windows XP Pro, Sp3.

The Problem, Explorer seems to hang randomly, at first only when trying to login to the machine, now it has done it while in normal opperation.

So this all started when I started playing Mass Effect for PC. A fun game to be sure, but it has a nasty problem, it crashes, but it doesn't die peacfully, it would seamingly crash your video drivers with it. I run a duel monitor setup, and what would happen is the game would hang, and the primary monitor would black out, and the secondary would suddenly get the task bar, icons, etc. and be the primary, with a hidden secondary. If you look in display properties, it has now loaded the default VGA driver. There are several strange artifacts left over aswell, like the shutdown/restart computer window, will mysteriously just be floating buttons with a black line for a border where the Window usually is.
Restarting the computer would magically fix the problem, everything would go back to the way it was. The crash would not stop the computer from gracfully shutting down and restarting, no hard resets required.
After a few days, when I would restart the computer, and try to login, it would just sit there. I would click my icon at the welcome screen, it would scroll into position and just sit there. I can control alt delete and finally see my walpaper, but no icons, explorer refuses to load. I can end task it, then try and load it manually, still doesn't work. Interestingly, I can login as a different account and (so far) it seems to work 100% of the time.

Up till now, a second restart would fix the problem, so I never gave it much attention.

Then yesterday, it happened, I restarted, and it happened again, it took 4 restarts to get it too work. It finally magically worked, after I used spybot to kill some new DLL (was bold) and suddely logging in worked. It was an MS DLL for apperently notifying stuff for login and logouts and was recommeneded to not be shutdown. I turned the DLL back on and stuff kept working. I did malware scans with Spybot and virus scans with Avira, clean on both fronts. So I did a new files search on my system, except for Mass Effect game files and temp internet files, there is nothing new in the last 4 months.
Also yesterday, after it finally booted, and worked, I was using it. I plugged in my MP3 player and got the safte to remove hardware icon, so I procedded to go and hide it. I went into taskbar properties, told it to always hide, clicked OK, and it hung that propertise window, which of course hung explorer. Explorer crashed, and I could not restart it manually. It would just hang, just like it does when trying to login. At this time I had not played Mass Effect on that session, so now I find it hard to believe that could be the problem.

I have done chkdsk C: /f and I have defragged, done the usual. Explorer.exe seems fine. All my startups look good.

Anyone have any ideas what is causing this or how I can fix it?

~~~~~~~~~~~~~~~~~~~~~~~~~~
New Info from comments

Also, Temperatures look good (This is at the highest strain, mid game, at idle they are much lower), GPU at 49-50C, CPU at 40C, HDD's at 26C each, Main board at 25C.

Update:
I've since deleted nTune

22 replies

by ---tk---

a driver or heat issue... mainly b/c the issue seems to elevate when you are running your system pretty hard... What graphics card are you running?

by slayer_

But that doesnt explain why it died on me on a session where I had not played.

Also, Temperatures look good (This is at the highest strain, mid game, at idle they are much lower), GPU at 49-50C, CPU at 40C, HDD's at 26C each, Main board at 25C

by robo_dev

Go back to the pre-game state.

My guess would be that the game seriously whacked your DirectX drivers.

I would start with System Restore, followed by reloading video drivers, then digging into
the directX diags tool, system file checker, etc.

http://www.updatexp.com/directx-diagnostic-tool.html

If it's some weird virus/malware thing, then process explorer from Microsoft may help.

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

by robo_dev

if that pukes, then it's a hardware problem for sure.

to me it sounds like you've got a damaged DLL of some sort.

Look at your Event Logs to see if things are failing.....

by the scummy one

the damage is to the memory, can determine how severe the system acts. Hangs can be from the memory (usually virtual) not being read properly, however physical memory can have the same effect(s).
when the memory is damaged worse, the system will crash instead (taking out a monitor until reboot may be a mini crash).
If you cannot find another reason for it, test the memory/video card, as it may lay right there.

by slayer_

Several times since intitial install, so thats probably not likely, but DirectX could be, perhaps I shall try reinstalling that.

I have system restore enabled, but it was 3 months ago that I installed it, so if restore actually restores, it may break more than it fixes, I'd like to hear other possiblities first before trying system restore.

by slayer_

Such as, My user can be broken and not logging in, but I can open task manager, log myself out, and login as someone else and it works.
Which lead me to believe it was a startup, right up until it happened WHILE i was using it, and couldnt reload explorer after it died.

by slayer_

I ran the nTune stability tests for an hour, it showed fine, what else can I do to test it?

by the scummy one

I pulled an old system out of my closet a couple of months ago. It worked fine when I last used it, however when I moved I was too lazy to set it up.
Anyway, when I tried booting it it booted fine, and then hung hard (really hard) when loading my desktop. I thought it was a hard disk issue, so I put the drive in another system and backed up data without issue.

I decided to set the system up as a linux system, so I ran diags on it and booted to a live cd without the HDD installed (for diags). Memtest86 ran for a few hours and had no issues reported, motherboard came out fine, etc..
Everything seemed fine until I installed the HDD and tried booting again to XP, I powered it off and was sure that the drive was bad (or the install at least), so I rebooted to the live disk and went to partition the drive and install Linux. KDE hung trying to come up.
This would seem that somethign other than the HDD was a problem, however I was at a loss. The RAM was tested, the whole computer was tested. I was about to swap poer supplies thinking that was the most likely thing left. But I got lazy (again -- yes, I know it happens) and when the case was open I pulled a stick of RAM. When I booted XP came up without any issues/delays. So, I thought maybe it was just loose, as the memtest passed. I put it back in, and double checked the other, and it hung like -- well, I wont go there.
Anyway, I pulled the RAM back out and it worked fine again. So, to check the port, I put the good RAM in the second slot, and it still worked fine. I removed the good RAM and added the bad one, and couldnt even start to boot.
So I pulled the bad RAM and it has worked since.

This should show as far as tests go, a failing chip may show well when in fact it is not.
However, this is not too common, so you should likely look at TK's advice first, just another thing to throw in when you are ready to pull your hair out and go bald like me :0

by rob miners

Locate the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\shell
Make sure that its value is set to explorer.exe.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"Shell"="Explorer.exe"

by ---tk---

Apparently this is all over the net... Some say the PS is the issue, some say the conflicting drivers with the over clocking utility... but I have yet to see anyone say "that fixed my problem"

I would look into your PS, make sure its strong enough. And try getting rid of the overclocking utility...

If i was in your position I would probably think about a fresh install of XP... because of all the crashes/hard kills... It cant hurt, and you can add it to the list of trouble shooting steps....

I own the 9800GTX+'s which does hang really bad when I over clock it... Also when I max out the settings in L4D my system hangs... which I will bet its my PS... (not enough power)
Which come to think about it, I am going to remove the OCing utility tonight and see if that helps, my own issue :)

added: come to think about both of my issues could be power related.... hm...

by slayer_

Well, I installed the OCing utilitiy because of the game crashes, it would crash after a half hour if I didn't overclock, if I do overclock, it lasts about 2 hours.
My PS should be able to handle it, its a 550 Watt, $150. It is powering a lot of hardware but I havent had it run hot yet.

It's worth a try though, I can still overclock using Riva if I want too, don't really need nTune installed.

by slayer_

The other user seems to always work, but I log in so rarely to that other user, it could be a fluke. I was thinking the same however, making a new profile and using that instead.
But I would like to know the cause of this so it does not happen again.

by slayer_

So I used Riva to OC my VC back to the same levels, played about 1.5 hours of Mass Effect before it died, restarted the computer. And it logged back in fine. I'll do this a couple more times however before I consider this problem solved.

by macelius

Found it's nTuneCmd.exe, I think it's futily trying to set my geforece's oc settings at startup, which i told it to do, but it never works and goes back to stock anyway. It only happens every few times, if I let it sit a minute or two it will continue, if I kill nTuneCmd.exe or ntunes.exe it loads explorer.exe right away.
GL
~M

This discussion is closed to new replies.