I realize you're fixed here, but just for the case of having a 'searchable' solution, I'd like to leave a couple notes...
If you are replacing a working CPU on a GB motherboard, you want to visit GB's main page here:
http://www.giga-byte.com/Products/Motherboard/Default.aspx
and use the socket column on the left to select your board's home page (you actually should have done this, and bookmarked it, when you bought the board - it's
the source for BIOS and driver updates for your system), then check the CPU support list to see that: A - your intended processor
is on the list, and B - whether there are
multiple 'steppings' requiring different BIOS...
The deal here is that processors are never perfect; actual human beings have not actually designed the photo-lithography (well, actually excimer-laser-lithography, as we've also left behind the sizes you could get with ordinary light...) processor mask that
is the CPU for decades - computers have been designing the next generation of computers for some time now (there are nearly two billion individual transistors on an i7-1366, and the hex-cores are due for release!), and there are always a large number of problems. These problems are documented in something called the 'errata' list, each processsor has one, and most of the problems are dealt with at the BIOS level. This is one of the reasons Intel 'pre-releases' engineering samples of new processors; their customers will do things with them that they can't envision (it's the
nature of 'Turing machines'[q.v.] - they can 'be' anything!), and they need to find the problems to see if they can be worked around - if not, they go on to a new mask before commercial release.... When Intel decides to fix a batch of these known problems, or finds a somewhat major advance in a family of chip's architectures, they make a new mask, and release what is referred to as a new 'stepping'; these are usually defined by a letter and a number, so: C0, E1, etc. This is the reason that subsequent steppings may be more 'overclockable', or have better memory stability (in the case of the i5/i7s). Each processor stepping contains a hex code that serves as its 'name'; pretty much the first thing the BIOS does when it 'fires up' your processor is query for that ID string, which allows it (the BIOS) to make the necessary adaptations for the errata
for that mask - and if it gets a string it is
not equipped to handle, it pretty much is screwed, with a WTF? error! The processor may or may not initialize on a BIOS that doesn't 'know' it, and may or may not run stably - which can be a problem in 'burning' a BIOS that
does recognize it - when you flash a BIOS (which is inherently 'risky business') you want the
most stable environment you can
possibly achieve (which is one of the overwelming reasons to NOT use @BIOS!); a lot of people go so far as only flashing with the machine on a UPS!
So, the trick to getting your new CPU working correctly is to visit GB to check which BIOS is required to support the new processor's 'stepping', and then flash that version with your old CPU - one that is currently stable!
Now, on to the windoze issues: windoze, is, essentially and at its heart, an API - an
application
programmer's
interface; if I'm writing a program, and I need to store a file on disk, I don't need to know
how your disk is organized - how many platters by how many cylinders by how many sectors - all I have to do is dispatch a message to windoze telling it what I want, and it (hopefully) returns me a 'file handle', having already dealt with all those details... This 'dealing with the minutiae' is done by windoze in something called the HAL -
hardware
abstraction
layer, which is comprised, mainly, of your BIOS, and your drivers - these do the 'talking to' the hardware, and windoze 'massages out' the details, and returns info from standardized fuctions. Your BIOS is stored in EAROM, or EEPROM, or some such - and access to these kinds of memory is orders of magnitude slower than DRAM, so the first thing your BIOS does, after initializing the memory controller and the memory, is 'copy itself' to RAM, for faster execution - and the BIOS is designed specifically with this in mind - its code is 'relocateable', not depending on absolute addresses. Because a large piece of the HAL is dependent on BIOS code, it, also, makes a 'working copy' of your BIOS, and, once again, because the BIOS physical memory is sloooowww, to avoid doing this at every start-up, windoze stores this copy at install, to re-load at every boot... A new install, or a 'repair' install, will force windoze to 'freshen' that stored copy of the BIOS; until this is done, it may run (no major differences in the BIOS); it may stumble along (occasional BSODs, hangs, and peculiarities - from non-functioning BIOS calls); or it may simply refuse to start...