BSOD "clock interrupt not received" GA-MA790X-UD4P_F2

[AlbusD]

System configuration (built April 2009):

GA-MA790X-UD4P board
AMD Phenom 2.3 GHz Quad Core
2 sticks of 2GB each G.Skill RAM DDR2-1066 PC2-8500 CL 5-5-5-15 in DDR slots 1 and 2
Windows 7 Ultimate 64-bit since 4-30-2010

Problem: Every few days the system BSOD's overnight (only once during daily use but that caused important data loss) which began with the installation of Windows 7; never any problems with Windows XP Pro.

The message reads:

A clock interrupt was not received on a secondary processor within an allocated time.

ANY help solving this would be MUCH appreciated. I have built several desktops, but am only moderately experienced with issues this deep.

If a BIOS update will cure the problem, I'm afraid I need detailed step-by-step instructions, starting with the download process, since I have tried to do this from a floppy and received a "BIOS ID check error" message within Q-Flash Utility. After that the BSOD came back two days later, so I assume the BIOS update didn't take.

[absic]

Hi,

Not sure as to the reasons for your BSOD's but updating the BIOS would be the first step that I would take in trying to figure out exactly what is wrong. You can download the latest F10A BIOS for your Mobo here: http://www.gigabyte.com/products/product-page.aspx?pid=3038&dl=1#dl

For detailed instructions as to the best way of Flashing BIOS check this thread: http://forum.giga-byte.co.uk/index.php/topic,2084.msg9510.html#msg9510

Hope this solves the problem for you but, if it doesn't, let us know.

ATB

[Dark Mantis]

If you are still having problems perhaps you could list the programs running especially if they differ day from night.

[AlbusD]

Update:
The BIOS update went swimmingly; it's now running the F10A. Many thanks for the advice and links.

However... less than 48 hours later it blue-screened again with the same message, again overnight. What I think I'll do is close everything I can each night and see if the BSOD recurs, and one-by-one leave things running to see if I can nail down the culprit.

The only thing is that the BSOD happened once during normal daytime work, causing a data loss. I wish I could be confident that won't happen again.

One alternative approach I've seen online for this problem is to underclock the CPU. In the interim, can someone point me to the steps for that, once I've entered the CMOS setup?

[absic]

Hi,

pleased to read that BIOS update went OK but saddened to see that you are still having problems with BSOD's.

Underclocking the CPU is fairly easy. Once you are in BIOS go to the MIT section, change the CPU Clock Frequency from AUTO to Manual and then make your adjustment. Reduce the frequency slightly then save the settings (F10) and reboot. You really shouldn't have to underclock your CPU or your RAM to get your system running without fear of crashing.

But before you do that you might want to check that your memory is working OK as this can be a prime cause of such problems. If possible try running your PC with only one stick of RAM, in slot 1 and see if the problem occurs. If it is OK for a couple of days swap the RAM and see if you then have the problem. If both sticks run OK as individuals try testing them in slots 3 & 4 rather than slots 1 & 2. (Sometimes just removing the RAM and checking that the contacts are clean and then re-seating them can also help).

Your other option of closing things down is also sound but, I would eliminate hardware problems before doing that.

[Dark Mantis]

One other thing to check is all your power saving settings because they would be more likely to come into play during the night when the machine is left unattended presumably. Also are you using a UPS system?

[absic]

One other thing to check is all your power saving settings because they would be more likely to come into play during the night when the machine is left unattended presumably. Also are you using a UPS system?

Good point Dark Mantis, as I don't tend to leave my PC running I'd forgotten this!

[apache4931]

Sounds like the Tlb fix is not enabled. My 2.3 wont work with out it.

[AlbusD]

Update 6-15-10

Before going home last night, I closed everything I could, using the Windows Task Manager. This morning it had BSOD'd again, same as before.

Good thinking about the memory, and I will check it per the suggestions, but it never acted badly running Windows XP Pro for about a year. This BSOD problem only started when I did a fresh install of Windows 7 (64). I suppose that could be a coincidence, and a memory stick is starting to go bad... but only at night (seemingly; just had one crash during the day)?

Re: power settings, yes it's connected to an APC Back-UPS ES 350, but I see I have not installed their software. In the interest of changing only one thing at a time, that monitoring utility might tell me if some power issue is involved, so I'll install that presently.

[Dark Mantis]

I asked about the UPS system more that if you didn't have one it could have been power fluctuations that happened during the night that were causing problems, however if you are using one that should discount that theory. As you suggest it may be worth installing their software but later on after ruling out other things.