• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

What are the causes of Windows Registry errors with O/C?

nealh

Diamond Member
Title says it all ...update to my problem
My system:
1.2ghz tbird Jan week 3(Alpha PAL 6035)
Asus A7V133
256 ram Mosel rev pc143
V5 5500 pci...pci slot 3 to allow use of promis controller
3com..pci slot 2
SB live pci slot 1

Primary IDE: Cdrom..master
Secondary IDE: CDRW: master
Promise..IDE3: Maxtor 30gb Ata100

I get registry problems at 10xfsb 140, 10.5 x 133...of course if I push it over 1400 I get registry error....it will post all the way up to 1485 but not load W98
BTW..i can sometimes get into w98 and run fine at 10x140...but others on boot I get the registry errors??

Thanks

 
The way it did it on my computer and I'm sure it is the same for many out there, is the DMA channal being o/c. If you are using the FSB to o/c then the DMA channal is also being o/c. The way to correct this problem is to slow down the HD in the bios, i.e. make it UDMA1 and not UDMA2. The overall increase in speed of the HD is still better, even with you slowing it down, then when you had the FSB at 100MHz.
 
Any other suggestions...
BTW my bios recognizes my Maxtor 30gb ATA100 as UDMA5 on A7v133 with promise controller using ATA100
 


<< No way to get into Promise BIOS to change the dma setting >>


that's true &amp; the promise driver is programmed to use all devices attached to it in their most optimal configuration.
 
My Duron can do 950MHz and work fine in Win2K (benchmarking, but no games), but when I boot in Win98 I get Registry errors, even at 910MHz.
 
Now that is weird....

Right now I am at 10 x 139 fsb...seems very stable...but go to 140fsb and I get registry error...yesterday ...all day at 10x140...very strange
 
Thanks can not go any higher at 1.85v...

but i found my problem maybe....if you got to accessories and system tools...and click on system info...then go to tools...go to system configuration..then to start up tab...uncheck the first line which has to do with checking the system registry at boot....

I am running smooth at 1.2@1.4...will try out 3d games to test how stable I am.
 
Hmmm. I hadn't been OC'ing much just for that same reason... the registry errors. Anyone out there know if unchecking the first line so as not to check the system registry at boot will cause any problems? Don't want to muck up my data... but wouldn't mind another few mhz 🙂.
 
if it's crapping out on the registry check, then it will most likely crap out under any heavy CPU load. Try a game or a stressful benchmark and see if its still smooth, and let us know. I am very interested in this cause ive been having the registry check errors when i o/c to a certain point.
Thanks,
Matt
 
Yep registry errors here too at any thing over the Gig a hurts for my duron 800.

If i were you guys I would not uncheck the reg checker. It serves a important function. It makes backups every day. you can restore your registry like this

at the C: prompt type C:scanreg /restore and choose the last date your registry was good.

I dont think you want to uncheck thip option. I want to uncheck it myself to see if you can go higher but I dont think you can.
 
I yse registry clean and always have a backup of my registry...I have yet to see an advantage of the scan registry...last time it worked for me I was installing windows and for some reason on a boot it scanned the registry and found an error and reloaded an old registry( i only had w98, V5 drivers, sb live and nic) and low and behold it reloaded the registry before the V5 drivers and nic but had sblive drivers...so i had reload the V5 drivers, nic...I am still not sure w98 is ok after this seems ok except but I keep having the system crash if I use the turn off monitor function in power schemes.

BTW I ran Voodoolights screensaver intensive 3d app for over 45min last night system is stable...in the past when I ran it on my o/c piii700@945 if I pushed o/c of cpu(to 980) or videocard this will lock right away or within 25min(cpu at 971)

Neal
 
I had to reinstall W2K three times in 10 hours because of registry errors. I found out that my system was running too fast (imagine that ;-) ) and ACPI was killing the power to everything at shutdown before the hard drive could write the memory cache to disk. This annihilated my registry over and over, until I disabled Windows' Power Management. I have to manually turn off my machine (read: actually push the power button), but I don't have to reinstall every time I shut down my system. This is a possibility, unless you're positive you already pinpointed the problem. Good luck.

--jason
 
No I am not sure what the problem is sometimes I boot the 1.2GHZ Tbird after it has been off for while to 1400 with a 9.5x147 and runs fine ...I can even defrag the hdd then if I restart with it warmed up get the registry error I have reloaded w98 and left registry scan on...since if I turn off on and boot the ms registry checker comes on and reverts to such old registry like I just installed w98 without drivers for video even.

What are you suggesting turn off power managenment in Windows ...I have it disabled in bios....can you explain in abit more detail what you are doing...

Thanks
Neal
 
What happened to me is that when I overclocked my system, the shutdown process was sped up and the time it took to shut down was shortened to the point that it was TOO fast.

The hard drive doesn't immediately write all the information sent to it to the disk. It keeps it in a RAM cache. Depending on the size of this cache (mine is 2MB on my drive), the time it takes to write this data to the disk itself during shutdown (so it is not lost when the power goes off) may increase.

The automatic power management killed to power to the system before the hard drive could fully write the cache back to the disk, and I ended up with corrupted or missing data about 25% to 40% of the time I shut down (not restarted). Normally, it caused a registry error that could not be fixed, and I ended up reinstalling Windows 2000 about four times in a period of one day. Not to mention having several other non-fatal errors occur that I fixed without having to fully reinstall.

Is your system still killing the power by itself when you shut down? If you do, keep reading. Otherwise, this probably isn't the problem that you're having.

So what I did was disable ACPI by replacing the ACPI driver with a &quot;Standard PC&quot; driver. (Check under Computer in your Device Manager). I know Microsoft admitted it was a problem in W9X and put out a fix for it (sorry, don't have a link...try Windows Update for the fix), but never admitted it was a problem with W2K also. I found this out the hard way. So check it out...if you could describe your problem more thoroughly, I could possibly see if it was similar to the errors I was getting. Good luck!
 
Back
Top