Windows 7 resets date to 1/1/1601 on reboot

November 5, 2011 at 07:39:06
Specs: Windows 7, AMD DDR
Windows 7 all of a sudden started having problems with time keeping. Of course I went to step #1 and put in a new CMOS battery. That did not help, the CMOS time works perfectly. The issue seems to be a disconnect between Windows and the BIOS. If I reset the date/time in Windows everything works fine until next reboot when Windows loses the time/date settings again. (BIOS time is still correct)
I have reset all BIOS setting to default
I have changed Windows time sync to different servers
I have replaced the CMOS battery
I have stripped windows out and did a clean install
I also ran HIRENS which also showed the incorrect date when it loaded it's mini-WinXP OS.
Nothing has worked!

What could possible keep Windows from talking to the system BIOS clock?

See More: Windows 7 resets date to 1/1/1601 on reboot

Report •

November 5, 2011 at 09:04:25
Real time clock has nothing to do with cmos anymore.

It is easy enough to try and adjust time in bios. Problem is that time is not a time that should ever show or be able to show.

Turn it all off and remove power plug. Press power button a few times or let site overnight. Then boot to bios and see what it says.

1/3 of highway deaths are caused by drunks. The rest are by people who can't drive any better than a drunk.

Report •

November 5, 2011 at 13:00:35
I have done that already. Unplugged, discharged the caps, pulled the CMOS battery then put everything back and rebooted. When I rebooted I reset the CMOS clock and rebooted back to Windoze 7. Upon entering Win7 the taskbar clock said 1/1/2005. I reset it using various time servers (Yes, I have done this more than once) which corrected the time, then I let it run. It will run normally until I reboot which totally resets the clock to either 1/1/1601 or 1/1/2005.
It's my understanding that the CMOS time and Win7 time must be fairly close to each other in order for proper operation to happen.
During the boot process does Windows not hook the CMOS time for an initial setting?

Report •

November 5, 2011 at 13:31:45
Have you run a virus scan?

Report •

Related Solutions

November 5, 2011 at 14:23:35
This won't help fix the actual problem but the significance of the 1601 date is given in the top few lines here (which might help):

I once had an old registry cleaning program that gave 1-1-1601 entries.

I rather doubt it is a virus but nothing lost by running MalwareBytes freebie. It often finds and fixes what AV's miss.

Always pop back and let us know the outcome - thanks

Report •

November 5, 2011 at 19:14:50
Before I stripped the old OS I have ran MalwareBytes, Advance System Care, AVG, Norton On-Line scan and Super Anti Spyware but...As I have said before, I stripped out the old Win7 and did a clean re-install. Not a virus.

Report •

November 6, 2011 at 00:41:05
Windows does take the CMOS date/time initially, adjusts the time for your timezone and will only change once you've connected to the internet. The 1601 bit is something to do with the Julian calendar which was decided as the baseline for PCs many years ago, though not quite that long ago I hasten to add ;-)

I also think that it is worth considering malware, though if you have done a clean install this would seem to negate this possibility unless you have an external or 2nd drive that is infected?

"I've always been mad, I know I've been mad, like the most of us..." Pink Floyd

Report •

November 6, 2011 at 04:39:58
Look at this article:
That's scary!

You have to be a little bit crazy to keep you from going insane.

Report •

November 7, 2011 at 06:08:41
It's possible the CMOS may have become infected but that still does not explain why the CMOS date stays the same but the date on Win XP and Win 7 both are being changed upon booting. My best guess so far is that when Windoze is "supposed" to hook the date/time from the CMOS something is broken on the MB that is not allowing Win to pick up the date/time.

Report •

November 8, 2011 at 08:34:17
I "think" I have solved the mysterious date/time problem.

I believe that this was a MalWare issue and the MalWare had somehow gotten into a small system partition on the HD. Of course no virus scanner that I used scanned this partition because it had no drive letter nor any reasonable function that I know of. It may have served some video caching function because the NVidia files appeared to be the intiially corrupted files.

Upon my first drive wipe all I did was install the Win7 CD and hit format and install. I really paid no mind to the system partition I saw on the HD of about 400M because I have seen these many times before. When Windoze formatted C:\ the virus was unaffected because it was not living in the C drive/partition. So naturally when Windows installed the virus came back to life hopping across the partition like it was not even there.

The second time I stripped the OS from the HD I did not use the Windoze 7 disc but used a 3rd party app to completely wipe the drive including all partitions and MBR. What I had then was a completely clean HD with noplace for anything to hide because the entire drive is unformatted.

I reinstalled Win7 with no partitions and it has worked perfectly since yesterday and many reboots, both cold, warm and total unplugged capicitor discharged, cold iron boots! Everything as of this time appears to be functioning normally.

Moral of this story?
When scanning for malware, viruses, etc... MAKE SURE if there is a partition on your HD that it has a drive letter and your virus scanner can get to it. Learn from my lesson the easy way, I already did it the hard way and it sucked.

Report •

November 8, 2011 at 11:18:19
Glad to here news. Thx for popping back to let us know.

Report •

Ask Question