I keep getting this message using winxp pro. usually c:\windows\system32\config\software or c:\windows\system32\hall.dll and various other messages like this. The only way to get it to stop is to use the ghost disk I have made of my hd.. that does the trick but it does it again. When it does do it windows won't boot, not even in safe mode. I have seen lots others people with this problem, so it isn't just me. Has anyone got any idea as to what the problem is ? Why it is happening and if there is a permament fix for it ? I'm using windows XP pro... XP, the best OS yet ? not ! interested in your thoughts about this one.. thanks

Are you using a legit version of the OS? and Xp is the best OS MS has every produced. Laters, KTTD

yes legit version. Have seen many posts about this. any ideas?

I am going to test out WinXP home edition. I wonder if this is only happening with the pro edition ? any comments ?

My system was working fine for about 1 month. Then I got cable installed. A few days later, it done this. Anyone else had probs ? I have heard someone else have the same prob, and they also had a network card installed. Also heard it can be probs due to memory, but I tested my memeroy and it is working fine. My specs: p-3 550 256mb ram Geforce 256ddr pro 32mb SBlive 1024 sound card. Intel SE440 bx2 motherboard. Ricoh 8*4*32 cd re-write drive 8*DVD drive Network card Any ideas? People having same problem, post your problem description and comp specs. There must be a common reason for this happening.

I had a similar problem to this a while ago. It turned XP and 2000 don't like funny partitions created by bootmagic and programs like that... I was forced to completly wipe all partitions and re install and never had a problem since.. except for my bloody cpu usage sitting at around %30 - still working on that one.

Well the first time it happened I had no partitions at all. So don't really think that is the cause. This prob is on Microsoft website, so they know about it. They give you a workaround to fix it. But I've heard it happens again. They say it's someproblem with something at startup. I'll try to find the article again. Does anyone know if this happens in WinXP Home edition ?