Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
MULTIPLE_IRP_COMPLETE REQUEST Error BSOD after logging in on Welcome screen - I posted about this earlier but still cannot find anything on it (apart from the Microsoft KB articles which don't seem to apply to this situation)
I have found out something else however, that the system will work when selecting Last Known Good Configuration - but next time it is restarted from the working session, it will crash after I log in! (on any account)
I've tried disabling startup programs in MSCONFIG, i've tried disabling hardware - nothing works. I just cant understand why last known good works, and then it stops working after a restart?
Any ideas people because im lost.
Thanks
Alex
That is a odd problem. When you log in successfully using last known good, can you copy the profile and then select that profile to login?
I have had these problems but I always make a backup profile prior to making any serious changes to my machines, hence I have a easy fallback. Without one I'm not sure whether this suggestion of mine above will copy the bad profile or the last known good one. Can't hurt to try though.
0 
Well i thought about this - what is ran immediately after you login that could have this effect? It can't be the startup applications as I've used MSCONFIG and tried disabling them all at once - even then it still crashed on the next reboot.
is there some sort of script that is ran?
0
I've also taken some screenshots of the event viewer involving ZoneAlarms TrueVector component that may be connected to the problem:
these are at:
http://members.lycos.co.uk/alexsutton85/events.JPG
and
http://members.lycos.co.uk/alexsutton85/events2.JPG
Copy the links exactly :)
Thanks
Alex
0
Disable the LAN device?
Oh and would I be better off uninstalling Zone Alarm in safe mode?
Thanks
Alex
0 0
I've seen this a lot. Removing the LAN device and reinstalling it (if your not sure how to remove network devices, simply go to add remove hardware and delete the Network Interface card you connect to the net with).
Reboot, and reinstall this devices, see if it works, then reinstall zonealarm and see if it works.
0
I found the problem! I reinstalled XP and it went wrong again and i was trying to think this time where i went wrong and it WASNT zone alarm but it WAS Folder Shield all along. Now i need to find out WHY it does it, because I use Folder Shield a lot.
I do know that folder shield started as a service *and* as a process - maybe thats a problem?
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
