Everytime I have had ANY trouble with XP Pro, it seems THIS is the problem I get!Hive (file) problem in XP Pro

[Brutuskend]

Everytime I have had ANY trouble with XP Pro, it seems THIS is the problem I get!

On booting I get the following error message:

Registry File Fature
The Refistry can not load HIVE (File)
systemroot\system32\config\software
or it's log or alternative
is corrupt absent or not writable

Last time this happend I just reinstalled. But what a pain in the ass!

Does anyone know a easier way to fix this problem?

Does ANYONE know WHY this keeps happening?

(System in profile)

(Tri Booting with 98SE/ XP Pro on one raid 0 set-up partitioned in half, 2000 Pro on it's own Raid 0 set-up.

T.I.A.

I have this in the OS forum as well, but it takes for ever (If at all) to get anyone to help in there it seems!

 

[MCS]

I used to get this from time to time, and while I can't tell you EXACTLY what causes it (could be a variety of reasons), I can tell you what has happened. The fie called SOFTWARE in ROOT\Windows\system32\config has become corrupted. This can happen at shutdown when the file is being updated and it is too large a size. As you are dual booting you can simply make a backup of this file and when it happens boot into one of the other OSs and copy it over - that will fix things.

On my particular setup it was some beta Highpoint drivers which were occasionally causing this corruption. Once I had updated these drivers the problem went away.

Hope this helps!

 

[Amused]

I had this problem once. I fixed it by making XP purge the page file on shut down. This takes about 30 seconds and gives it enough time to shut down. I never had the problem again.

Go to Run > Regedit > HKEY_Local_Machine > System > CurrentControlSet > Control > Session Manager > Memory Managment and change the value in "ClearPageFileAtShutdown" to "1"

This problem is a problem identified with 2K and XP. There are KB articles on it if you search. Although MS does not give this as a fix, it was discussed on many newsgroups, so I tried it. Like I said, I never had the problem again.

BTW, do you overclock?

 

[Brutuskend]

On my particular setup it was some beta Highpoint drivers which were occasionally causing this corruption. Once I had updated these drivers the problem went away

AHH that could be it I suppose. I do have Highpoint controlers, though I'm not sure I'm using Beta drivers.

BTW, do you overclock?

Yeah, I have dual 750 PIII's @ 863.


Strange that I'm also running 2000 Pro and yet I never have this trouble in THAT OS.

Go to Run > Regedit > HKEY_Local_Machine > System > CurrentControlSet > Control > Session Manager > Memory Managment and change the value in "ClearPageFileAtShutdown" to "1"

Anyway to fix it if I can't boot into XP? Other than re installing that is.

BTW: Thanks for the replys!!

 

[Amused]

Originally posted by: Brutuskend

On my particular setup it was some beta Highpoint drivers which were occasionally causing this corruption. Once I had updated these drivers the problem went away

AHH that could be it I suppose. I do have Highpoint controlers, though I'm not sure I'm using Beta drivers.

Oh wow, I'm running an Iwill SideRAID 100. I had other problems with Highpoint drivers and Xp's default drivers (which were Highpoint drivers), but when I used the latest from Iwill, those cleared up.

BTW, do you overclock?

Yeah, I have dual 750 PIII's @ 863.

Just curious. The time this happened to me, I was aggressivly OCing. But I have OCed since then just as much, and never had the problem again.

Strange that I'm also running 2000 Pro and yet I never have this trouble in THAT OS.

Like I pointed out, the MS KB article on this says it's a problem with both 2K and XP. So did the newsgroups I read.

Go to Run > Regedit > HKEY_Local_Machine > System > CurrentControlSet > Control > Session Manager > Memory Managment and change the value in "ClearPageFileAtShutdown" to "1"

Anyway to fix it if I can't boot into XP? Other than re installing that is.

BTW: Thanks for the replys!!

Not that I've seen to be effective. The only way is to repair or restore the registry. This can be tricky, because the registry has to be a recent copy, or things you've done recently like loaded programs and new hardware wont work right.

You're welcome