A Multitude of Misery (As Well)

Sigmatik · 17 Jan 2010

So I posted here a while back, talking about how explorer crashes upon login. Well, I reformatted and did a clean install of Win 7. However, explorer is still crashing upon login. And the only way to fix it is by logging out, or restarting and canceling the logout or restart. It seems like it's some sort of retarded Windows process that causes the crash, but how would I know which one to stop? Because I cannot end processes because task manager also locks up. Is task manager a part of explorer? Because if so, that's freaking idiotic. I've just dealt with it over the past few months by not fully restarting my computer and just keeping it running unless there are updates, but recently explorer has been crashing randomly as well.

Now, I have only a few processes running right now that are not a part of Windows, and those processes are all for my HP computer. I have updated ALL of the drivers. However, I did do an event log check and this error comes up consistently;

"Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x062100F25F60. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server."

Could this be the culprit?

Sorry if I sound angry. After using Windows for 15 years, and having so so many bad experiences, I've just about had enough.

Thanks to any that are able to help.

**Pauly** · 17 Jan 2010

First thing i would do is to establish if its windows crashing the system or a third party app trying to boot on logon

Run msconfig, under startup tab uncheck everything, under services tab tick hide all MS services then uncheck everything thats left, reboot see how you go

If it stops crashing then you know the prob was a third party app, which can then be re introduced one by one to find the culprit

If it doesnt help then the issue is prob in windows so i would try booting as diagnostic startup just to prove the problem isnt to deep rooted, if this works then could run a system file check which you can do by
Start>cmd.exe>right click run as admin>type sfc /scannow

Hope this helps, post back your results

Orpheous · 17 Jan 2010

Try booting up with only 1 stick of RAM, then shut down, swap and reboot. I'd also suggest running Memtest86, overnight if possible. Faulty/failing memory can do all sorts of wierd and wonderful things...

Sigmatik · 17 Jan 2010

Ahh thanks a lot guys. I'll give those a try.