Quote:
Yeah, no real reason to change BIOS unless you need to. I usually try all of them "just because" but after seeing problems with the F9c I decided not to this time. I'm still using F8 with no problems.Originally Posted by 2therock 
I want to report I have ran the BETA F9c BIOS for 24 hours. I did notice some uncalled for reboots just before or during a sleep and the event viewer is loaded with warnings and errors including a controller error for my #5 storage drive.
After reverting back to F8 the event logs have been quiet. I'll not be trying another BETA BIOS.
Some samples.
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 4
The details view of this entry contains further information.

I want to report I have ran the BETA F9c BIOS for 24 hours. I did notice some uncalled for reboots just before or during a sleep and the event viewer is loaded with warnings and errors including a controller error for my #5 storage drive.
After reverting back to F8 the event logs have been quiet. I'll not be trying another BETA BIOS.
Some samples.
- Critical: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
- Error: The driver detected a controller error on \Device\Harddisk5\DR5.
- WHEA-Logger: A corrected hardware error has occurred.
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 4
The details view of this entry contains further information.
I'm about to put my other UD5H in a Switch pretty shortly. Got most of my water cooling parts and new 3770K in.
Shoot me an email and tell me about what you ended up with in your DRAM settings. I just put the Samsung back in my rig and pulled the Trident for the new build.






















