Archive for December, 2009

Overclocking A Lynnfield Intel i7 860 on an Asus P7P55D-M

Wednesday, December 30th, 2009

So after all the guff I had to go through getting the Gigabyte board to post with my memory I ended up going to my tried and true brand – Asus. After dealing with the awfulness that is VIA way back in 1998 I have been using Asus boards almost exclusively. Frankly an extra two percent performance or a headache by going elsewhere is not worth it for me. Maybe I have just been lucky or maybe there is a reason Asus is the largest mainboard distributor in the world. Setting all that aside, let’s get to the point of this article. Once I had my shiny new board and processor I wanted to jump straight into overclocking… but oh how things have changed!

As features are brought directly onto the CPU (PCI-Express, memory controller, graphics in some cases) a whole new world of settings must be handled. Of course I don’t give a whit about any of that. I want to find a max cpu speed pronto. Please don’t make me read ten pages of techno jargon just to figure out if I can hit 4ghz. Before we get started make sure you install CPU-Z, Prime95 and ASUS PC Probe so that you can monitor everything. Let’s get to the meat of it.

Finding your max CPU speed w/o HT

  1. Enter BIOS and disable Full Screen Logo from “Boot -> Boot Settings Configuration -> Full Screen Logo” so that you can see what is going on when you boot
  2. Under the AI Tweaker tab set “AI Overclock Tuner” to manual
  3. Extreme Phase Full Power Mode to “Enable”
  4. Your BCLK defaults to 133. Raise this to raise your processor speed. Start out at something moderate like 166 for a 25% overclock. Stability deteriorates around 205 on most boards.
  5. DRAM Frequency – set this to the lowest non auto setting. Now you don’t have to worry about the memory introducing stability issues. For the record you should already be running high end memory for O’Cing. I would recommend DDR3-1600 at a minimum. You want this to prevent your memory from bottle necking your system stability.
  6. QPI frequency you don’t have much control over, but set it to the lower of the two values. You do not want this value over 7500 or so.
  7. VCORE over voltage to .2. This is the max safe voltage for Lynnfield – the default 1.2V + .2V = 1.4V
  8. DRAM voltage to 1.6
  9. Disable HyperThreading from “Advanced -> CPU Configuration -> Intel HT Technology”
  10. These manual adjustments should automatically disable Intel Turboboost, but if you see the options available then turn off SpeedStep and TurboBoost.
  11. Boot into Windows and open up PC Probe and CPU-Z to verify your settings. Run Prime95 and check your voltages and temps for safety.

For the records sake I was able to hit a stable 4ghz using this method. I could probably have gone further, but I was interested in a Hyperthreading O’C because I do a lot of work with digital video. Those extra four threads should make quite the media encoding difference!

Finding your HT CPU speed

  1. Downclock yourself to something reasonable like 165 BCLK again and reenable HT.  The computer does a kind of full shut down and restart when you toggle HT which was at first scary, but no worries.
  2. Go back to AI Tweaker and set your voltage offset to .1 (will have been at .2 from previous test). I found that with my processor HyperThreading did not like the extra voltage used for non-HT oc’ing at all. By doing this I was able to stably overclock to 3.8ghz instead of 3.5ghz.

Finding your max memory speed

  1. Set your BCLK back down to 133 and choose the fastest memory speed you would like to test. You can inch the speed up or down by raising/lowering the BLCK. I was able to find a stable value of DDR3-1700mhz for my DDR3-1600 memory. I kept all other memory settings at their defaults. There is a lot you can do here, but a little bit of memory bandwidth just doesn’t make that much of a difference for the majority of apps.

So now that you have all your information you can combine your max memory O’C with your max CPU O’C and scream along. I hope somebody finds this article useful!

Gigabyte P55M-UD2 and Rapid Beeping

Tuesday, December 29th, 2009

While setting up my new rig I ran into an unfortunate problem with the Gigabyte P55M-UD2 motherboard. All my attempts to boot were greeted by a rapid fire beeping sound from the motherboard (short beeps). There were four motherboard lights that lit up green green orange red. After some googling I found that the lights have nothing to do with boot error codes and everything to do with reporting how much power the mobo is currently drawing. I know for a fact that Dell uses a four light system and some other motherboard manufacturers also use it to report boot errors. Gigabyte gets some demerits for implementing a “nice thought” feature that is a red herring.

So how do you fix the rapid fire beeping problem? I tried the usual stuff first. No case, one stick of memory in first slot, video card and processor. Next up came the manual and continuous short beeps indicate a video card error. Three video cards later I determined that was not the case. So I start systematically eliminating problems. Swap memory sticks, swap psu’s, swap cpu coolers, swap video cards…. ack. Back to my friend Google and I finally determine that memory errors cause the problem. That’s funny because there is a beep code for memory errors and it sure isn’t rapid fire beeping! I was using certified memory and it was erroring. No problem, swap sticks. No dice. It turns out you have to boot with the single stick of memory in the second slot. Ai yai yai. Seriously? This motherboard wasted a good two hours of my time as I systematically pulled every component of my system apart trying to identify the error.

For those interested I was running the 1.0 version of the board and it had the F3 BIOS installed.

Update 02/15/10 – It appears that people are hitting this article fairly frequently while searching for beep codes. So hear is the full list.

1 short: System boots successfully
2 short: CMOS setting error
1 long, 1 short: Memory or motherboard error
1 long, 2 short: Monitor or graphics card error
1 long, 3 short: Keyboard error
1 long, 9 short: BIOS ROM error
Continuous long beeps: Graphics card not inserted properly
Continuous short beeps 1: Power error
Continuous short beeps 2: I found that this is a memory error. Try running a single stick in each of the slots. For me the second slot did the trick. After the first successful boot I stopped running into this error.

Chrome OS for the Masses… or is it?

Thursday, December 10th, 2009

So Chrome OS is cool and everything, but what is going to make people switch to it? Like most new user environments Chrome OS  needs a killer app. As my cousin and his wife so adeptly pointed out – Google Docs suck and my regular computer can do everything that Chrome OS does anyway. Why do we care? And the truth is getting regular people to care is going to be a problem. Fortunately for Google there is a market that will be far more receptive to the Chrome OS business model and I was surprised it wasn’t touched upon during their press conference.

Small businesses. My wife’s Uncle Mike and I were just discussing a unique problem in small to medium sized business at my wedding this summer. They have all the technology requirements of a large organization with none of the budget to manage technology problems. Outside consulting is expensive and because those consultants are not involved in the day to day operations they can’t pop over to fix Jane’s laptop over lunch. Enter Chrome OS and the perfect target market for their product.

Imagine you are a small business owner and you have a number of field agents that are reliant on a laptop for field work. They don’t need anything complicated. Email, web, and SAAS (software as a service – think gmail for business) to get their job done. You don’t want them installing World of Warcraft or Bejeweled on company property. You don’t want them downloading the virus of the week and exposing proprietary client and company data. Enter a product that does all those things. Now make it cost $300 or less. Now make it so that if a field agent’s computer goes down they can be back up again in minutes. All their data is secure. Don’t want to fix the computer? No problem, throw it out. Let’s face it, hardware is cheap and fixing and maintaining hardware is expensive. Really expensive. This is where Chrome OS can kick some proverbial butt.

This is only half the equation though. If ChromeOS is successful it creates a lucrative secondary market for SAAS and provides an incentive for third party developers to write custom applications for businesses. This economic opportunity will have a reinforcing effect on Chrome OS in much the same way the iPhone and the Apple App store have a symbiotic relationship. Each is better because of the other. On a brief aside – can you believe that iPhone apps can only be developed on a Mac? I mean seriously? Apple controls less than 5% of the OS market and yet has the most successful app store? See what happens when you create a hardware environment that people want and don’t limit your users from software applications they want and need!

I boldly predict that Chrome OS will be successful because it is inexpensive, easy to understand, solves both consumer and business needs and provides new revenue models for software developers. I think that this will happen within thirty months. So set your bookmarks, mark your calendar and come back later to see how perfect my prognostications are. Now if you will excuse me I have to get back to overclocking my divining rod.

You sure this thing works?

You sure this thing works?