Gigabyte p35-ds3 checksum error

gigabyte p35-ds3 checksum error

As of this morning my e7200 was still running 2x Prime95 with no errors, Speedfan reported the 2 cores @ 37C with the fan running @ 985rpm. Mismatched BIOS Version: Are you sure that the edition you are downloading does match exactly with your motherboard? Most of the time. Next, the initialization code checksum will be verified. D1h Initializing the DMA controller, performing the keyboard controller test, starting memory. gigabyte p35-ds3 checksum error

Related Videos

Gigabyte GA-P35-DS3 fault

Speaking: Gigabyte p35-ds3 checksum error

Canon mp240 error code e5
Gigabyte p35-ds3 checksum error
Printer error epson stylus photo rx500
Servererror fatal errorcode 5
Runtime error programm this application has requested
\xeb\x3d\x8b\x75\x08
Here are some facts and figures for everyone.

Part of this is a testament to the cool running of the E7200 (even when overclocked by 25%), and part of this can be attributed to the excelent Xigmatek HDT-S1238 CPU cooler.

After some time of playing a real world game (BF2), with just Core 0 and both cores running the game the cores stay at 38C. This is with a Nexus @ 5v on the cooler, and the only case fan a Slipstream 1200 @ 950 rpm (damned annoying really).

I checked the BIOS, and I have to admit that I made a mistake, whilst going through the procedure of overclocking I had the voltage up to 1.200v as a precaution, and never dropped it down to "auto" afterwards.

The Core voltage at idle according to CPU-Z 1.44.2 is 1.120/1.136v (it changes every 2 seconds).

Whilst running Prim95 2x times CPU-Z reads the core voltage at 1.136v, I will gigabyte p35-ds3 checksum error to check the BIOS again to see that everything is set correctly, or does the voltage not drop as dramatically as with AMD CPU's.?

The temp of the 2 cores are 45C and 43C, gigabyte p35-ds3 checksum error, this is more than enough even in the height of summer, and I strongly suspect that it will be perfectly cool with the case fan @ 5v as well, which will be something for tomorrow, gigabyte p35-ds3 checksum error. And if the Slipstream @ 5v displeases me I will hack my Nexus around so I can mount it using my silicone grommets.

Any more questions, or tests requested will be forthcoming.

The differences in stock settings are 3 MB cache instead bmw brake circuit error 6 MB, 266 MHz FSB instead of 333 MHz, and a PCB with a different layout that have a lower overclocking potential. Oh and price, of course.

OK, 3MB of cache, but when overclocked to 333 FSB the difference is not that great. One of the reasons why I selected the E7200 was that I could get a free performance boost with a cheapish chip and not have to worry about overclocking the RAM, chipset or motherboard. If I had bought an E8xxx CPU I would not have overclocked the CPU at all as all of the motherboards that support more than 333 FSB natively cost a mint.


Andy

Unblock BIOS of an M680G

I would like to operate core 2 extreme qx 9300 with inspiron 1545
core 2 extreme The cpuid of qx 9300 is 1067 A
In the official inspiron 1545 bios the code of 1067 A is the one of 2008/04/09 old and supports core 2 extreme qx 9300 Precision M6400 bios is 2011/10/04 that is newer than inspiron 1545
So I thought that it would be better to replace microcode and did the following

[1], I have inspiron 1545 a14 bios (https://goo.gl/U3Z5nj) and
Precision M6400 a13 bios (https://goo.gl/k1UeTk)
Downloaded.

[2], both of the two exe files
filename.exe / writehdrfile
And I got two bios gigabyte p35-ds3 checksum error files

[3], I checked the position, size and date of microcode using MCE.exe in UBU_v1_70_b8_Dev and I was convinced that the bios file of inspiron1545 contains the old microcode 

[4] Open the .hdr file using HxD Hex Editor and copy the character string of 0x2000 size from the position confirmed from the Precision M6400 bios file with MCE.exe and replace it with microcode of Inspiron 1545

[5], this worked Inspiron 1545's 1067 microcode .hdr file was replaced by the one on October 4, 2011

[6], I learned that PhoenixTool.exe can compress .hdr files into .gz and remodeled.hdr file was compressed by PhoenixTool but PhoenixTool had {no vaild checksums found}  HuhAngry

[7] Then I compressed my unmodified, gigabyte p35-ds3 checksum error. hdr file with PhoenixTool This worked fine The bios.gz file was completed

[8],When I confirmed the contents with 7-zip I confirmed the size that bios.hdr was in and it was exactly the same as the remodeled gigabyte p35-ds3 checksum error file so I overwrote it with a remodeled .hdr file

[9], usb 
not remodeled biosfile.exe
I added a modified. Hdr file
bios.gz
I entered biosfile.exe / readgzfile in the dos window I thought this would work. But the dell bios updater said {ROM file CRC - 32 is incorrect. Bad ROM file} AngryAngryAngry

I think that crc32 is checked before updating bios and it is supposed not to update unless it matches Is there a way to match crc32 with unmodified file or how to skip crc32 check?
You can use any method
I am tolerating risks
Help me
Thank you

.pngmoded.png(Size: 40.25 KB / Downloads: 3)
Thermaltake 850W PSU

Gigabyte p35-ds3 checksum error - all

\x75\x30\x44\x89\xf8

  Ocing a Q6600 and GA-p35-ds3 rev 2.1 
 

 Author 

 Date Written 

 Tools 

GtoX (capt Guns)Apr 07, 2009, 01:22pm EDTReport Abuse
Hey guys, listen, before i go into this, ive been to several sticky's, checked out several forums and what not, and im just not getting the OC that i want.

First off, as u can see in my specs, its a Gigabyte p35-ds3 REV. 2.1
which bios do i get? when i tried the 2.1's bios update, it told me checksum error or somethin like that, so it never updated it. its bios rev f2 to start with

now, the juicy part:
tried ocing, i know this quad can reach at least 2.85ghz from before, but of with my old p5n-e sli..

i got this P35 strictly cause people told me it was meant for OCing quads..

sometimes i manage to get a 333x9 oc (3.0ghz), with a 1.375something vcore. gaming works stable as ever (a good 14hr run), prime 95 no errors... but then, when i leave the computer off for a longer time, like a day, and then turn it on, it cant boot past bios and goes into original settings.. multiplier is at 2.5, so at 333x9 im at 800mhz on memory, 1.8volt.

now i turned on the comp, it couldnt boot, so i figured id lower to 2.8ghz, NOTHING works, i cant boot past! im so p**sed cause i was so excited to get a nice OC, and how come its stable in windows 7, games and all, and a reset works, but a cold start wont boot past! please help me HWA! :(


Ah, and btw, EIST, C1t or whatever its called is turned off.


EDIT: Ok, now that the computer has been on for a while, i tried 2.7ghz, at 1.325vcore (stock).. and it booted in..
also tried a F11 bios instead of F12, said the same thing "bios check error" wtf, its from their homepage, and i got the box in front of me saying "board rev. 2.1"


Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm

Want to enjoy fewer advertisements and more features? Click here to become a Hardware Analysis registered user.

microApr 07, 2009, 02:41pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

I thought a p45 was a better oc'er.

Im at 333x9 [email protected]

tweaktown.com have tons of guides for oc'ing a p35/45 mobo. I dont have the exact link, but a google search should beable to find it.

I hate to send you to another forum. I hope someone here can help you out more then i did.


GA-Z68X-UD3H-B3, 2600k @ 4.0
16 gig Corsair Vengeance
Evga gtx 260 216, samsung 2253lw"
Baracuda 7,200.12 CoolerMaster 212 +
Win 7 64, fsp fx700-gln, Razer DA,G15
Evil is powerless if the good are unafraid
Silence in the face of evil is it's self Ev
Michael CApr 07, 2009, 05:48pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

Try 389x9.0 with stock volts, seems to work for me?


BoTApr 07, 2009, 07:19pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

how do you go about oc'ing? via bios or easytune or other means?
did you raise the NB voltage? or mess with any of the other voltages besides vcore?


You can either be part of the problem or be part of the solution.
Codisha - http://www.codisha.com
Reviews - http://www.codisha.com/reviews/reviews.htm
microApr 07, 2009, 07:31pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1
BoT said:

how do you go about oc'ing? via bios or easytune or other means?
did you raise the NB voltage? or mess with any of the other voltages besides vcore?




I went to tweaktown.comand viewed some guides on my gigabite mobo/cpu combo. I changed the ram voltage slightly and the cpu. I didnt have to change any other setting and i have used my pc constalntly for 2 months stable.

I went straight to 333fsb, then dropped the vcore untill it wasnt stable, then just went up .2v.

I use bios to oc.

GA-Z68X-UD3H-B3, 2600k @ 4.0
16 gig Corsair Vengeance
Evga gtx 260 216, samsung 2253lw"
Baracuda 7,200.12 CoolerMaster 212 +
Win 7 64, fsp fx700-gln, Razer DA,G15
Evil is powerless if the good are unafraid
Silence in the face of evil is it's self Ev
GtoX (capt Guns)Apr 08, 2009, 08:22am EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

im using bios to overclock of course..
tried to make a bootable usb drive to flash using Qflash, but it doesnt work!!
i get this message after its read the bios first "Bios ID check error"

i just dont understand why i cant flash it... should i use windows to flash? since nothin else will work?

Also, should i mess with any other voltages? i havent touched anything except for vcore..

Also, to explain furter, if i do a cold start of the system i wont be able to use my OC, but when i do a warm restart and use the 3ghz oc it works fine.. until i wake up the next morning to try it again! and yes, Temps are perfectly within range, getting 35c idle, and 43-45 on load.


Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm
GtoX (capt Guns)Apr 08, 2009, 09:01am EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

ok, so now i tried updating through the internet "@bios" function...

all i get is this message using both from file and when trying to update through internet:

http://i43.tinypic.com/23kw5qv.jpg


Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm
mothowApr 08, 2009, 10:21am EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

You have the dreaded p35 cold boot bug.

http://www.google.com/search?hl=en&rlz=1T4GGLL_enUS311US31...mp;spell=1


ASRock Z97 Extreme 4 / i7 4790K / Corsair H80i / 4x4GB Crucial Ballistix Smart Tracer DDR3 1600 / 1TB Western Digital Caviar Black / 240GB Mushkin Chronos Deluxe SSD / 2x Evga GTX 670 FTW 2GB in SLI / Sound Blaster Recon3D Fatal1ty / Corsair HX1000w
GtoX (capt Guns)Apr 08, 2009, 08:37pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1
you think so?s**t.. well what can i do about it? was doin a prime95 while i was gone outside for 12 hours, no errors what so ever...


is it RMA'able ?

this guy wrote on a forum "With double boot you turned it on, it would run for 3 seconds (fans 100% and no image), turn off and on again by itself. "

it usually does that with a cold boot.. only once though, then it goes back to standard clocks..
however, when i got back now, after being in screensaver mode (3.0ghz testing prime 95) and moving the mouse the computer restarted itself and would keep doing it until i cut the power on the psu, waited a minute, then it would turn back on and boot into the 3.0ghz mode..

F*ck man, i really dont wanna have a board that gives me a problem like that. :(

Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm
G. G.Apr 09, 2009, 11:21am EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

Man ... that really sucks.... If you do in fact have the cold boot bug.... not really sure if it is fixable on your end... only possible way is to rma the board .. BUT.... that is NOT a guarranty that your problem is going to be fix with the refurbish board....

At this point.... you may consider getting a different board either with Gigabyte or another brand using the P45 chipset... If you decide to go with a new board... you should consider the GA-EP45-UD3R or UD3P. I think there are 4 of us HWA members here that have the EP45-UD3R version and have had no issues. And definately no cold boot issues. Plus updating bios works. (i have done successful bios update via bios's update manager in conjunction using a usb containing the bios files.)

I know you dont want to hear about the new mb route, but with your cold boot issue, you may have no choice... since there seems to be no fixes for it.


---------------------------------------------------------------------------------------------------------------------

-
GtoX (capt Guns)Apr 09, 2009, 02:27pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

hmm, well why wouldnt a RMA work with it?

does a cold boot damage the board in any way? cause otherwise, i think i could live with having this cold boot issue.. i mean im running 3.0ghz right now no problem, been playing crysis and other games for the past 6 hours now.. so everytime i wanna play games i restart the computer and load the 3ghz settings, and whne im just surfing i can load the stock settings.. f12 loads from cmos..

any other ideas?


Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm
G. G.Apr 09, 2009, 03:09pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

Well,

The RMA may work and may not work.... Look at this way... when you RMA that board back the Gigabyte or any other mfr for that matter, you get back a refurbish part unless otherwise stated... this refurbish part is a fix-up of someone else's issue. That issue may or may not be the same issue that you have. Let say that the board you get is where they fixed a bad LAN port.... but hidden away is the cold boot issue.... this issue shows up again when you get it... As for the mfr fixing all issue with the part may have? all I can say is who knows...... it all depends on the process they have in placed for refurbishing damaged parts...

for example... many years back... I purchased a digital camera, a HP 945 model. It worked great up until the 11th month.... the digital sensor would not focus anymore. It started out with low light only and then got progressively worse where it wouldnt focus even in full sun. Called up HP, ran through their tests..... HP determined that, yup.... we need to replace it.... RMA'd... got the replacement camera... it works great.... BUT....... a few weeks later... I noticed that whenever I would use the flash in low light situation.... my pictures was not quite the same as with my original unit.... after awhile of pondering on it... i finally determine that it was with the flash on the replacement unit... the problem was that it was not putting out as much white light as the original unit... it was a tad more yellow... which in turn my pictures using flash not as bright as it once was with the original unit. Not a big deal.... but it was not the same as with my original unit... the flash worked (replacement unit) ... no sense fixing something that appeared to be working... right????

All i am saying is that, yes.... RMA may fix it...... BUT.... you need to realize that the replacement unit may or may not fix your problem.

But at this point, if you want to have any chance to fix the issue.... RMA'n the board is a start... but if the replacement board does not fix the problem or introduce you to new issue.... you need to leave the option of a "NEW" board may be required..


---------------------------------------------------------------------------------------------------------------------

-
GtoX (capt Guns)Apr 09, 2009, 03:59pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

Hmm.. makes sense.. i guess ure right.. maybe i should just live with this board then.. i mean i get a fully stable OC, and i get really nice temps, but i would have to switch it to the "gaming mode".. it doesnt bother me as much, as windows 7 restarts reaaaaaally quick...

but, what bothers me is not being able to update the bios.. would i have better luck tryin to use a floppy disk?
i mean they say only update bios if its not working correctly... right?


Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm
G. G.Apr 09, 2009, 05:07pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1
GtoX (capt Guns) said:

but, what bothers me is not being able to update the bios.. would i have better luck tryin to use a floppy disk?
i mean they say only update bios if its not working correctly... right?



My take on updating bios is that whenever a newer bios is released, I take a look at it and see if there is anything about it that would either add features that I can use or fix a flaw/issue that I may be having or potential to have. Otherwise I stay put especially if my bios is not having any issue.

as for you not being able to flash your bios? hmmmm... that's not good unless it is user error :P

I had taken quick peek at your user guide for the GA-P35-DS3 rev 2.1.....

Look at section 4-2-1 page 68. This is exactly how I flash my bios.

1. download the bios you want to use in the flash process and extract it to a USB thumb drive. (make sure it is the normal fat format and not ntfs or anything else) Put the file in the root level.

2. boot system and hit the DEL to get into bios.

3. choose F8 Q-Flash

4. choose Update Bios from drive

5. then this is where you would choose floppy or USB

6. follow the remaining instructions...


If you decide to put the bios files on your HDD.... I think you have to hit END during initial bootup for flashing bios.

If you cant flash your bios from either the floppy or USB..... that would be an issue in addition to your cold start....

If this is the case you may want to just buy a new mb... at this point go with the P45 chipset... who knows... you may get better OC out of that Q6600....



---------------------------------------------------------------------------------------------------------------------

-
GtoX (capt Guns)Apr 13, 2009, 12:31pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

yea i just read the manual and tried saving to the harddrive and pressing end, didnt work at all, wouldnt even list my harddrive..

im still confused at how to set up a bootable usb drive since they say u should type in the commandprompt and have the bootable files moved over using a command, but i cant figure out the command.. hehe
very used to CMD, but moving files through that is a pain i realised..


Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm
G. G.Apr 13, 2009, 02:02pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

Capt,

do the usb method.... that was how i did it... first you want to do is down load the bios version you want to install... extract the files... then just transfer them over to the usb. Just make sure that the usb only contains the files from the extraction.

Then just do the normal f8 within the bios... select Qflash.... then you want to choose update bios... and then I think you will want to choose HDD-0.... (not sure at this point but I do think you need to choose HDD - I think it see the USB as a HDD)

by the way... you are not creating a bootable usb.... all you are doing is to extract the files from the download.... and then moving the extracted files over to the thumb drive.... that's it.


---------------------------------------------------------------------------------------------------------------------

-
GtoX (capt Guns)Apr 13, 2009, 08:44pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

yea but like i stated in the first post, ive done that already, another solution they stated was to make a "bootable" usb drive, which ive had a hard time doin.. but the way u stated just using the extracted files, my bios says "bios check id bad", basically stating its the "wrong" bios version...


Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm
G. G.Apr 13, 2009, 09:09pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1

Capt,

I just went over to Gigabyte's website and looked at your mb (GA-P35-DS3 rev. 2.1). In your sig, you list your mb's bios is at F2. So with this, I went and looked at bios versions for rev. 2.1, rev 2.0, and rev 1.0.

Are You Sure You Have a MotherBoard rev 2.1 ?

The reason I ask this is because:

rev 2.1, the first release of the bios is F11 (F11~F12)

rev 2.0 & 1.0, release of bios is F1 ~ F12


Now I am wondering if the reason you are getting the error "bios check id bad" is because the bios you are trying to load is incorrect with the rev of mb you have... You may want to double check your mb to see exactly what you have. Look for silk screen of the rev on your mb or any documentation for verifications.

This kinda sounds like you may have a rev 2.0 or 1.0 ....

Here are the links for the bios on each of the revision mb:

Rev 2.1 - http://www.giga-byte.com/Support/Motherboard/BIOS_Model.aspx?ProductID=2748

Rev 2.0 - http://www.giga-byte.com/Support/Motherboard/BIOS_Model.aspx?ProductID=2627

Rev 1.0 - http://www.giga-byte.com/Support/Motherboard/BIOS_Model.aspx?ProductID=2544


My suspisions now is with the rev of your mb.... hmmmmm


---------------------------------------------------------------------------------------------------------------------

-
GtoX (capt Guns)Apr 18, 2009, 02:25pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1
hehe i noticed the same thing, i thought it was a different bios revision.. and ive tried all the bios versions for all of the different mobo revisions.. nothing works, still bad id check error...
its as if its a different revision gigabyte doesnt support alltogether! :P

Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm
GtoX (capt Guns)Apr 18, 2009, 02:39pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1
lol, just got a reply from gigabyte.. appearantly my board (rev 2.1) comes in 2 different flavors!

didnt think about something as "insignificant" as 2 letters, but appearantly i got the newer EP35 and not the P35 :P

oh well im gonna go try and flash this puppy now.. anyone know if a bios update can fix a cold boot issue?

Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm
GtoX (capt Guns)Apr 18, 2009, 03:08pm EDTReport Abuse
>> Re: Ocing a Q6600 and GA-p35-ds3 rev 2.1
Well, the update worked, so im on f3 bios at the moment, as the latest one if only a beta, and i dont really want a beta bios that could prove to be unstable... but at least i managed to update it! :D

now i only need to see if my cold boot issue will be resolved.. i'm not havin too much hope here.. but but..

Main Rig--- 2700k @ 3.7ghz ,Scythe Samurai ZZ @ 54c load ASUS DCII GTX570 [email protected] load, P8P67-m Pro, 2x4gb xms3 1333mhz, 128gb SSD + 4x500gb lagring, OCZ Modxstream Pro 600watt, In-win Dragon Slayer 140mm+120+96mm,120mm


 



 
XSPC Dual 5.25in. Bay Reservoir \xeb\x30\x44\x89\xf8 Intel Core i7-2600K

Cmos Checksum Error - After Lion Install

Slightly different method of installation worked for me. First I copied AppleRTC.kext from System/Library/Extensions to ~/Documents folder. After which I deleted it from S/L/E. Then I ran:

sudo perl -pi -e 's

0 Comments

Leave a Comment