I just built a completely new system and it is fantastic or it should be.
It seems to be stable through all the stress tests I have tried but I recently ran the Firestrike test and that dam thing keeps saying my results are invalid because my rtc is skewing, indicating I am cheating or there is a hardware fault. Obviously I am not cheating. They say if I am not cheating and have an otherwise stable system, then send in various junk and their developers will analyse it for me. Sure, no doubt they mean well but how long will that take, in the meantime I have to decide if I am going to RMA the mobo.
The Firestrike test is a DX11 test that obviously only runs on Windoze and whilst I have no problem with the Futuremark company and developers, I never ever trust anything that WIndoze tells me. Ergo, their results are based on WIndoze so I do not trust them, especially when they validated one of my OC runs but reject the stock runs :\ There is also the possibility that there is something wrong inside Windoze 7 as Micro$oft have been rolling out easy upgrade steps to W7 to help idiots upgrade :sarcastic: to Windoze 8. Futuremark, the guys that create the Firestrike test have recently banned all WIndoze 8 computers from submitting test results to them due to a completely trashed rtc in Windoze 8 rotfl!
The Firestrike test uses some external software to gather timing information and that is where the problem actually lies. Either their code is wrong for this latest chipset on my ASUS mobo or there really is a hardware issue. ASUS have a hardware diagnostic program that specifically tests the rtc and that passes my hardware, including the rtc, as successful all the time.
However, I have noticed some dodgy handling of the systems sensors using hwmonitor. There appears to be a whole bunch of voltages and the cpu fan missing when I use hwmonitor but this is random as other times I use hwmonitor, the missing sensors are there.
So I would like to write some simplish code to test the RTC but although I know I can access the rtc, I am not sure what I can do to test it's accuracy. I am a competent C/C++ developer and have been working on linux in a commercial environment for years, including messing about with the kernel and modules.
I just need a hint on what to do to test the rtc accuracy?
It seems to be stable through all the stress tests I have tried but I recently ran the Firestrike test and that dam thing keeps saying my results are invalid because my rtc is skewing, indicating I am cheating or there is a hardware fault. Obviously I am not cheating. They say if I am not cheating and have an otherwise stable system, then send in various junk and their developers will analyse it for me. Sure, no doubt they mean well but how long will that take, in the meantime I have to decide if I am going to RMA the mobo.
The Firestrike test is a DX11 test that obviously only runs on Windoze and whilst I have no problem with the Futuremark company and developers, I never ever trust anything that WIndoze tells me. Ergo, their results are based on WIndoze so I do not trust them, especially when they validated one of my OC runs but reject the stock runs :\ There is also the possibility that there is something wrong inside Windoze 7 as Micro$oft have been rolling out easy upgrade steps to W7 to help idiots upgrade :sarcastic: to Windoze 8. Futuremark, the guys that create the Firestrike test have recently banned all WIndoze 8 computers from submitting test results to them due to a completely trashed rtc in Windoze 8 rotfl!
The Firestrike test uses some external software to gather timing information and that is where the problem actually lies. Either their code is wrong for this latest chipset on my ASUS mobo or there really is a hardware issue. ASUS have a hardware diagnostic program that specifically tests the rtc and that passes my hardware, including the rtc, as successful all the time.
However, I have noticed some dodgy handling of the systems sensors using hwmonitor. There appears to be a whole bunch of voltages and the cpu fan missing when I use hwmonitor but this is random as other times I use hwmonitor, the missing sensors are there.
So I would like to write some simplish code to test the RTC but although I know I can access the rtc, I am not sure what I can do to test it's accuracy. I am a competent C/C++ developer and have been working on linux in a commercial environment for years, including messing about with the kernel and modules.
I just need a hint on what to do to test the rtc accuracy?