TouchBIOS messes with system clock

[FoLmEr]

I just installed the newest TouchBIOS (11.1201.1), and I'm still experiencing my system clock is turned back.

I opened TouchBIOS
Browsed a few pages
Changed my RAM timings (tRCD) from 8 to 9
Saved successfully
Rebooted from within the program, and noted the clock had just changed from 00:08 to 00:09 AM
Checked BIOS - the RAM change had been made successfully
Booted Windows - the time is 00:08 AM, 1 minute has been lost

All versions of the program I've tried has done this.

Do you have any idea what's causing this? Anything I can try to workaround the problem?


Thanks

[Dark Mantis]

Hi and welcome.

I would say it just sounds like some faulty BIOS writing there so probably the best thing is to contact GGTS and let them know about it as they mighjt not even be aware.

Just enter your email address and click on the language of choice.
GGTS   http://ggts.gigabyte.com/

Please expect several days for a reply.

[FoLmEr]

Thanks, I've done as you suggested.

Guess I'll just have to wait and see what happens.

[Dark Mantis]

Please post back and let us know what GGTS said to you in reply. I am sure there must be very many people affected by this. 

[FoLmEr]

I'll be sure to post back when/if Gigabyte gives me anything useful.

Just tried updating my BIOS to F9 - same problem.

I have a GA-Z68X-UD4-B3 board btw.

[Gloup_Gloup]

Hi FoLmEr, 

Just a suggestion, have you check a batterie on motherboard?

 Maybe is not powerfull and generate a problem like your situation.

Gloup_Gloup

[FoLmEr]

I haven't tried it, no.

But honestly, if the battery is bad, the problem should be there when NOT using TouchBIOS also; it isn't.

The problem is 100% reproducible, and the longer I have TouchBIOS open before saving+restarting, the longer the clock is set back, quite possibly meaning it reads BIOS settings on program start, including the clock, and upon saving, it puts the time of launch back in the BIOS.

Makes perfect sense. Although, if I may say so, it seems like a newbie mistake that shouldn't ever have slipped through testing. There are also still some random unhandled exceptions crashing the app, but I won't go into that here.

What I can't get my head around, though, is that I'm apparently the only one having this problem. I can't imagine it would be difficult to fix either, since I guess it would be relatively easy to skip the reading/writing of the clock to/from BIOS entirely - I mean, you can't even adjust it in the app in the first place.

[Dark Mantis]

I would agree that would make perfect sense as to why it happens but I can't see how you could be the only one though! Have you had a reply from Gigabyte yet ?

I take it then that if you removed the Touch BIOS the problem would disappear ?

[FoLmEr]

No reply from Gigabyte yet.

I have no issues with my system aside from TouchBIOS messing with the clock when used. I still have it installed but I change settings manually from within the BIOS setup if I want to make changes and there's no conflicts or other hiccups if that's what you mean.

[Dark Mantis]

In that case it would certainly seem to be down to purely the Touch BIOS then.

[FoLmEr]

That's my thought too. Or conflicting software/drivers that in some way hinders TB in its operation.

Although I havetried installing the latest TB on a fresh win7 installation on another HDD and it's shown exactly the same problem.

Hence, if you have other suggestions, I'm all ears

[Dark Mantis]

No I'm afraid not. I think we are just back to waiting for GGTS to come up with a useful answer. Sounds like it requires some rewriting.

[FoLmEr]

"We are checking this issue. When we have any update, I will keep you informed."

Was the response I got. Seen from an optimistic angle, I guess there's hope

[Dark Mantis]

Well at least they accept that there is any issue in the first place as that is often the stumbling block. Hopefully they will sort it out soon then and let you know. Please pass it on to us.