Not loading default values every startup ends with a blackscreen

creativus

Honorable
Aug 15, 2014
84
0
10,630
My pc has an Asus P5Q SE mobo and a LGA775 modded Xeon E5450 cpu. I had been working it with cpu overclocked 30%, some day it didn't work so I cancelled the overclock but it still was shutting down with a blue screen. I solved that problem by uninstalling ESET antivirus and using windows defender instead as suggested here:
https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/windows-recovered-from-this-unexpected-shutdown-i/70947d97-20d3-424c-9570-39f72a69f6a4?auth=1

Yesterday, the computer's date and time was wrong, I corrected on Windows, then it was normal.

Today I thought maybe the problem wasn't the overclock and maybe I could overclock it again, so I tried it but it didn't work. Instead now when I start the computer it asks me to load default bios values or to enter bios and unless I load default values by pressing F2 I end up with a blackscreen. Also a future date comes up every startup. If I get a blackscreen the only thing I can do is clearing the RTC RAM so it can ask me to press F1 or F2 again.

I have tried loading default values for everything in the bios myself but it didn't work. I have no idea what's going on, please help.
 

creativus

Honorable
Aug 15, 2014
84
0
10,630
I knew date and time was related to the CMOS battery but I didn't think it asking me the bios settings every startup was due to the CMOS battery, but it apparently is. So the solution is simple, replace the CMOS battery ? I'll do it for the first time.

Can my overclock work again also ?
 

creativus

Honorable
Aug 15, 2014
84
0
10,630
It didn't restart as I thought it would. It just gave a blackscreen. I cut down its power and started it again and it did start. I also entered bios, saw that it keeped the CMOS profile I created to keep my overclock settings, I exited without saving settings and got Windows working with a wrong date and time again.
 

That would be expected behavior. However, it seems that there may be additional problem with overclocking. Try running comp for a few days with CPU set to default values and see how it behaves.