The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Clevo M720T bios proble

    Discussion in 'Sager and Clevo' started by pirafox, Jun 29, 2015.

  1. pirafox

    pirafox Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    Hi

    i've a problem with my clevo m720t.The cmos give me this error : 0271 check date time and settings, 0251 system cmos checksum bad- default configuration used.I've changed the cmos battery with newone but when i fix the configuration and switch off the pc everytime losts the configuration.Bios version 1.02.22 kbc/ec firmware revision 1.00.09.The battery is ok and the pc battery works well.I have xp professional and if i try to change date or hours in xp i can't.Only change in bios screen.I've tryed to change gpedit.msc and remove administrators anda powerusers but i haven't no effect.
     
    Last edited: Jun 29, 2015
  2. t456

    t456 1977-09-05, 12:56:00 UTC

    Reputations:
    1,959
    Messages:
    2,588
    Likes Received:
    2,048
    Trophy Points:
    181
    Try to flash latest ec and bios (in that order):
    EC firmware 1.00.11
    System BIOS 1.02.28

    Replacing cmos battery on ' check date and time' message ought to have done the trick though, so ... maybe it's merely a bad contact? Could try sanding (or contact spray) and may bend the retainer clips back a bit so they'll have a stronger grip on the battery.
     
  3. pirafox

    pirafox Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    Thanks for your reply. I've mounted a new cmos battery with 2 pin cable but the configuration lost ever. Probably a mb defect? Why in Windows xp with admin access i can't change the dateor the hours?
     
  4. t456

    t456 1977-09-05, 12:56:00 UTC

    Reputations:
    1,959
    Messages:
    2,588
    Likes Received:
    2,048
    Trophy Points:
    181
    Yes, could be; the bios EEPROM has a limited lifespan as well, would need to solder in a new bios chip then. To be clear: it doesn't keep any settings, right? No boot order change and such?

    When trying to change Windows time; you don't get a ' Need administrator permission' sort of message, do you? That would indicate a specific service isn't running (forgot which one ...).

    Anyway, Windows' time works with an offset of +/- X seconds compared to time reported by cmos. After synchronising it updates the X value. If cmos time remains at, say, 1-1-1980 then so should Windows time remain static at 1-1-1980+54,000 seconds ( policy setting; MaxPosPhaseCorrection). Perhaps it concludes that even the maximum permitted offset isn't enough and decides to fail? Could change the registry setting to "0xFFFFFFFF":
    Or save this as .reg and run:
    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\Config]
    "MaxPosPhaseCorrection"=dword:ffffffff
    If registry didn't help, try this in a command window (service ' Windows Time' needs to be running):
    Code:
    w32tm /resync
    If that works and time still remains static (since cmos is static), then you could schedule a batch script to run at startup (or via Task Scheduler):
    Code:
    :resync
    w32tm /resync
    timeout /t 1
    goto resync
    Could hide the CMD window with this .vbs:
    Code:
    Set WshShell = CreateObject("WScript.Shell")
    WshShell.Run chr(34) & "C:\PATH\resync.cmd" & Chr(34), 0
    Set WshShell = Nothing
    Create shortcut to the resync.vbs and drop in the Startup folder, will keep running silently then. Can check it's working by looking for w32tm.exe and timeout.exe in Task Manager; they'll keep starting/stopping every second.