Login screen followed by BSOD with multiple_irp_requests_complete error 0x00000044?????

Hello all of you!!

First I'd like to thank every single one of you for your rapid replies!! Really, some posts elsewhere did not provoke a single reply from anyone so....Then second of all > I haven't been able to get into windows until now (after my post I shut down the whole sh*t and went to work to find out I was no longerable to get into windows again when I got home afterwards, until now that is;) I will start with the first one that replied but please keep in mind that it could take me some time to get back at ya all since I'm not very convinced I can easily reboot without losing access to windows.  Furthermore I have to say that although I did not get into windows I already tried the console (insert the xp disk and then after some time choose the R option which brought me into windows Dos mode but once there I looked around and had to be honest to myself by asking: ' What the H*ll am I doing here'.....;) So I rebooted and tried to repair the installation which seemed a normal clean install to me (but I can be wrong there ofcoursee) and voila I got into windows but the first screen to pop up was an error message saying a recovered from a severe error and after some investigating I concluded that the wmi had been damaged or dissapeared. Then I decided to reboot and that was the end of the story regarding getting into windows. Mind me I have some more questions which could really be plain and dumb to you guys but obviously not to me since I wouldn't ask about it ofcourse;)
1. Only one fan is active and its speed varies enormously, my hdd's are nearly too hot to handle and  temp of the cpu is 36 degrees. For this reason I shut down the sh*t a few hours ago and decided to try again only 10 minutes ago for I assumed the temp would perhaps be involved with this whole tragedy. SInce I now managed to get into windows I feel a 'lil encouraged to start believing the temp IS involved......anyone any idea on how to fit this puzzle??
2. Could a driver from another pc (the client) be 'fighting' for that packet  since I did install some hardware on the client pc? (that is....if I get you guys right then this is about two drivers fighting for one packet or some memory problem which perhaps could be the consequence of the driver problem right?)

So far so good.......I will now try to gain that control of my XP installed pc back again and like to state once more than I really appreciate you guys sharing your knowledge and I WILL get back to reward all of this generously!!

Regards from Paul van Bommel

Your temp of 36 degrees C seems like a good temp for any processor.  Depending on the processor, it should be able to handle at LEAST 50 degrees before you have to worry  (my athlon 2500+ for example averages 50 degrees idle).  It may be a temperature problem though, we cant rule that out.  Possibly your video card??  Sometimes RAM goes bad, this may cause blue screens.  Maybe when you shut down, that did a hard reset on all of your devices, so instead of rebooting as usual, you cut the power to reset everything and this might have solved it.  My real hunch is that the winxp repair feature you performed actually fixed this whole thing.

Hi there davemarm thanks again for your rapid reply!!

Have but 'lil time now to respond (45 minute break from work) so I'll keep it short here. The repair feature seemed to have solved the problem only after a reboot I bumped into the BSOD with the same message again so I repaired it once again with the option -recent settings that worked- and voila I'm back up and running although I must say that it takes a while before I get into windows, much longer than normally is the case.  Would it be wise to shut the sh*t down and unplug everything once you think? I kinda reinstalledwindows already but that did not solve my problem. Oh and I forgot to mention this perhaps vital piece of info > this pc happens to be my brothers so I'm not 100% familiar with the configuration etc. > therefore I did not pay attention to the fact that he normally has to F6 during windows setup to provide drivers for a raid controller > something I overlooked.......But it would be a damn coincedence if my attempt to restore the system (during which I forgot the raid controller) would cause exactly the same error as I already got when I did not restore it right?

Well I'm off to work now thank you thank you thank you for your reply........you WILL be rewarded generously and so will anybody who takes the effort to assist me in this 'lil war'.;)

Regards Paul van Bommel