Looks like the cause for the failed block writes was the AWDflash version that I was using.
8.83 was giving me block write failures, I tried with AWDflash v8.94 now and it worked like a charm.
Gonna try the secondary BIOS chip now.
Looks like the cause for the failed block writes was the AWDflash version that I was using.
8.83 was giving me block write failures, I tried with AWDflash v8.94 now and it worked like a charm.
Gonna try the secondary BIOS chip now.
Coding 24/7... Limited forums/PMs time.
-Justice isn't blind, Justice is ashamed.
Many thanks to: Sue Wu, Yiwen Lin, Steven Kuo, Crystal Chen, Vivian Lien, Joe Chan, Sascha Krohn, Joe James, Dan Snyder, Amy Deng, Jack Peterson, Hank Peng, Mafalda Cogliani, Olivia Lee, Marta Piccoli, Mike Clements, Alex Ruedinger, Oliver Baltuch, Korinna Dieck, Steffen Eisentein, Francois Piednoel, Tanja Markovic, Cyril Pelupessy (R.I.P. ), Juan J. Guerrero
New G13 BIOS related bug found:
I decided to give RAID 0 a try, so I installed two Samsung SpinPoint F1 1TB ( Samsung HD103UJ ) on the ICH10R ports ( P02, P04 ports if I recall correctly, will edit the post if I'm wrong ) and left my Samsung SpinPoint T 500GB ( Samsung HD501LJ ) boot drive in port 1 ( P01 ).
I installed Vista with the ICH10R in AHCI Mode and kept using it like that.
I entered the BIOS to make sure everything's ok, and re-arrange the HDD Boot Device sequence to make sure the HD501LJ was on top.
After restarting the PC I got the classic "Disk Boot failure, blah blah" message.
So I was "OK, guess it didn't accept the changes with the new HDDs, so let's get back into the BIOS and re-arrange them & save & exit again ).
But I was so wrong, it didn't work, the same result.
Then I said, let's do it the old fashioned way, OC Gear -> Display Smart Menu = Enabled.Save & exit.
The boot menu pops up and I select HDDs -> Samsung HD501LJ and hit Enter.
Once again, Boot disk failure blah blah annoying message...
Then I decided to remove my SuperTalent Pico 8GB USB Flash Disk Drive from the USB port... all out of magic it worked like a charm.
The BIOS Boot Device sequence was kept and used properly, and the Boot Menu pop up menu worked also.
I'll check it out again later on, and give it another try with the G15 BIOS as well.
Coding 24/7... Limited forums/PMs time.
-Justice isn't blind, Justice is ashamed.
Many thanks to: Sue Wu, Yiwen Lin, Steven Kuo, Crystal Chen, Vivian Lien, Joe Chan, Sascha Krohn, Joe James, Dan Snyder, Amy Deng, Jack Peterson, Hank Peng, Mafalda Cogliani, Olivia Lee, Marta Piccoli, Mike Clements, Alex Ruedinger, Oliver Baltuch, Korinna Dieck, Steffen Eisentein, Francois Piednoel, Tanja Markovic, Cyril Pelupessy (R.I.P. ), Juan J. Guerrero
Bench, that's what fixed my RAID problem too. I just unlugged my 1TB backup drive, started the Windows install, plugged the 1TB drive back in and everything worked like a charm! I can also confirm that this is a problem on both G13 and G15.
So if I update my USB Flash Drive from 8.83 to 8.94 it should work fine? Thanks Bench!
Core i7 920 D0 @ 4833.55Mhz~EVGA "Classified" E760~XFX HD5870~6GB G.Skill Perfect Storm DDR3 2000~Corsair HX1000~2x WD Velociraptor 150GB RAID 0~WD Cavier Black 1TB~Custom Danger Den Water Box Plus~Windows 7 x64 RTM~Dell 2407WFP
H20! CPU Loop: MCP-655~Swiftech MCR-220~HEATKILLER® 3.0 LT GPU Loop: MCP-655~XSPC RS240~EK FC5870 Plexi+Nickel
Using 2 Samsung HD103UJ ( 1TB drives ) and a HD501LJ ( 500GB ) and a Samsung SH-S223F DVD+/-RW in RAID mode without a single issue here, on G13 BIOS.
Booted fine from the DVD and installed Vista x64.
Perhaps it's a HDD compatibility related issue ?
I'm preparing a 3* Samsung F1 1TB RAID 0 now.
Yes, update the AWDflash version to 8.94 ( you can download it from here ) and use the classic command ( awdflash BIOSFILENAME.BIN /py /sn /Wb /cc /cd /cp /ch /H2 )
Last edited by BenchZowner; 01-09-2009 at 04:16 PM.
Thanks Bench! I'll give it a try and report my results.
Core i7 920 D0 @ 4833.55Mhz~EVGA "Classified" E760~XFX HD5870~6GB G.Skill Perfect Storm DDR3 2000~Corsair HX1000~2x WD Velociraptor 150GB RAID 0~WD Cavier Black 1TB~Custom Danger Den Water Box Plus~Windows 7 x64 RTM~Dell 2407WFP
H20! CPU Loop: MCP-655~Swiftech MCR-220~HEATKILLER® 3.0 LT GPU Loop: MCP-655~XSPC RS240~EK FC5870 Plexi+Nickel
Core i7 920 D0 @ 4833.55Mhz~EVGA "Classified" E760~XFX HD5870~6GB G.Skill Perfect Storm DDR3 2000~Corsair HX1000~2x WD Velociraptor 150GB RAID 0~WD Cavier Black 1TB~Custom Danger Den Water Box Plus~Windows 7 x64 RTM~Dell 2407WFP
H20! CPU Loop: MCP-655~Swiftech MCR-220~HEATKILLER® 3.0 LT GPU Loop: MCP-655~XSPC RS240~EK FC5870 Plexi+Nickel
Tried flashing with ALT + F2 @ POST ( Enter AWDFLASH ), but it doesn't load AWDFLASH no matter what.
It gets stuck at a AHCI BIOS ROM screen.
I'm gonna try flashing with Fox LiveUpdate, but that thing doesn't seem to report if it performed a full BIOS flash or if it skipped or failed to write any blocks, etc.
Flashing with AWDFLASH 8.83 from a bootable USB drive worked flawlessly before, and I don't remember having any failed to write blocks at all.
Now it fails to write 4 blocks if I remember correctly on both BIOS chips.
Looks like the cause for the failed block writes was the AWDflash version that I was using.
8.83 was giving me block write failures, I tried with AWDflash v8.94 now and it worked like a charm.
Gonna try the secondary BIOS chip now.
So Benchzowner, am pleased you resolved the bios writing issue with awdflash v8.94, but am confused as to why Alt F2 the built-in bios flash procedure and Fox LiveUpdate dinot result in full and complete flash of bios?
Hi mate,
I don't know why ALT + F2 did not work for me.
It won't load, but since we can flash the BIOS fine from a USB stick I don't care
The Foxconn Live Update might have flashed the BIOS properly, I can't be sure as there's no output regarding the flashing procedure, and I didn't check the checksums when I tried it.
As for a preferred BIOS flashing method, I'd take the bootable USB + AWDflash v8.94 any day.
You can flash and stay in DOS and check the checksum, and if the flash went wrong you can still re-flash, etc.
Coding 24/7... Limited forums/PMs time.
-Justice isn't blind, Justice is ashamed.
Many thanks to: Sue Wu, Yiwen Lin, Steven Kuo, Crystal Chen, Vivian Lien, Joe Chan, Sascha Krohn, Joe James, Dan Snyder, Amy Deng, Jack Peterson, Hank Peng, Mafalda Cogliani, Olivia Lee, Marta Piccoli, Mike Clements, Alex Ruedinger, Oliver Baltuch, Korinna Dieck, Steffen Eisentein, Francois Piednoel, Tanja Markovic, Cyril Pelupessy (R.I.P. ), Juan J. Guerrero
Core i7 920 D0 @ 4833.55Mhz~EVGA "Classified" E760~XFX HD5870~6GB G.Skill Perfect Storm DDR3 2000~Corsair HX1000~2x WD Velociraptor 150GB RAID 0~WD Cavier Black 1TB~Custom Danger Den Water Box Plus~Windows 7 x64 RTM~Dell 2407WFP
H20! CPU Loop: MCP-655~Swiftech MCR-220~HEATKILLER® 3.0 LT GPU Loop: MCP-655~XSPC RS240~EK FC5870 Plexi+Nickel
G15 issues i have found:
cpuz and Aegis panel report vcore .1v higher than bios setting.
tras memory setting auto sets back to 16 after re boot.
Can not remove power from the mobo or all stored oc's will not work. This could be a hardware issue, I don't know but it is troublesome. They all work when re-booting from a power on state.
tripgood
Big hardware pile
Check the previous page.
There are two tables with measurements for the CPU Voltage ( Vcore ) settings with DMM and CPU-z info as well.
The BIOS Setting is 0.1V off.
If you set the "Target CPU Voltage" to 1.3V for example, in reality you're feeding your CPU with approx. 1.4V
The tRAS setting isn't working properly for all the listed values, it's been reported by me already in this and the other thread regarding the BIOS ( Bugs, Issues, Features to be added, and Changes/Suggestions ).
tRAS 16, 20, and 31 work fine if I recall correctly ( not sure on the latter ).
Coding 24/7... Limited forums/PMs time.
-Justice isn't blind, Justice is ashamed.
Many thanks to: Sue Wu, Yiwen Lin, Steven Kuo, Crystal Chen, Vivian Lien, Joe Chan, Sascha Krohn, Joe James, Dan Snyder, Amy Deng, Jack Peterson, Hank Peng, Mafalda Cogliani, Olivia Lee, Marta Piccoli, Mike Clements, Alex Ruedinger, Oliver Baltuch, Korinna Dieck, Steffen Eisentein, Francois Piednoel, Tanja Markovic, Cyril Pelupessy (R.I.P. ), Juan J. Guerrero
Wow. i read all of the above posts but did not quite understand the impact until experiencing them. RE your post #35 above. Does G13 mess up your stored OC's after re-boot?
It would appear that FoxConn engineers have a LOT of bios work to do.
tripgood
Big hardware pile
Are you talking about the OC "Profiles" ?
The configurations that you can save for later usage in the 8 slots ?
Elaborate a bit on that and I'll check it out
Coding 24/7... Limited forums/PMs time.
-Justice isn't blind, Justice is ashamed.
Many thanks to: Sue Wu, Yiwen Lin, Steven Kuo, Crystal Chen, Vivian Lien, Joe Chan, Sascha Krohn, Joe James, Dan Snyder, Amy Deng, Jack Peterson, Hank Peng, Mafalda Cogliani, Olivia Lee, Marta Piccoli, Mike Clements, Alex Ruedinger, Oliver Baltuch, Korinna Dieck, Steffen Eisentein, Francois Piednoel, Tanja Markovic, Cyril Pelupessy (R.I.P. ), Juan J. Guerrero
Yes, When i remove power from the board, it will not boot when powering back up. I get the short beeps or long beeps. It goes to oc recovery and I can't boot from any of my stored profiles. A couple of the settings are different from the ones i put in and I have to input everything over. I have to leave the power on and shut the board on and off to boot with the settings I had when shutting down. Ultra 1kw, single velociraptor no raid, sata dvd drive, 4870x2 and various dimms.
I think I may wait until a new bios comes out. This thing is wearing me out
tripgood
Big hardware pile
Coding 24/7... Limited forums/PMs time.
-Justice isn't blind, Justice is ashamed.
Many thanks to: Sue Wu, Yiwen Lin, Steven Kuo, Crystal Chen, Vivian Lien, Joe Chan, Sascha Krohn, Joe James, Dan Snyder, Amy Deng, Jack Peterson, Hank Peng, Mafalda Cogliani, Olivia Lee, Marta Piccoli, Mike Clements, Alex Ruedinger, Oliver Baltuch, Korinna Dieck, Steffen Eisentein, Francois Piednoel, Tanja Markovic, Cyril Pelupessy (R.I.P. ), Juan J. Guerrero
When removing power my saved OC's load just fine with a Corsair HX1000 PSU.
Core i7 920 D0 @ 4833.55Mhz~EVGA "Classified" E760~XFX HD5870~6GB G.Skill Perfect Storm DDR3 2000~Corsair HX1000~2x WD Velociraptor 150GB RAID 0~WD Cavier Black 1TB~Custom Danger Den Water Box Plus~Windows 7 x64 RTM~Dell 2407WFP
H20! CPU Loop: MCP-655~Swiftech MCR-220~HEATKILLER® 3.0 LT GPU Loop: MCP-655~XSPC RS240~EK FC5870 Plexi+Nickel
Have to say the oc profiles are working out fine for me. I have been playing around with secondary BIOS chip and I may get a thread spank for this, but the Windows utility does not properly update the BIOS. Used my USB boot and applied BIOS with no issue.
It also saves your oc profiles per BIOS upgrade, was very happy with this feature/availability.
Now I just have to work on those RAM timings.
"The only solid piece of scientific truth about which I feel totally confident is that we are profoundly ignorant about nature...It is this sudden confrontation with the depth and scope of ignorance that represents the most significant contribution of 20th century science to the human intellect."
-Lewis Thomas, The Medusa and the Snail
"The best definition we have found for civilization is that civilized man does what is best for all, the savage does what is best for himself."
-Edwin Hubble
H.E.A.T
MarioKart FID-0774-5798-8330
My oc profiles are now working also. I disabled vdroop and PRESTO!
tripgood
Big hardware pile
Uh oh, i spoke too soon. I thought my issues were related to the vdroop feature. When I removed power from the board and powered back up, it went into oc recovery. I loaded a proven stable profile and was greeted with the c1 and long beeps. None of my stored settings worked. The only way I could boot was with the optimized default settings . I know c1 usually indicates a dimm problem, but I don't think so. I get it with 3 different proven kits. Everything was working earlier today after making a couple of changes including when shutting the mobo off and on. When I shut off my ups the whole thing went to Most of the psu's i have around here are on the don't use list but i'll dig something out tomorrow and give it a try.
tripgood
Big hardware pile
LOL Thanks Sayaa @ welcome. Thanks again for the G13 bios, Bench. Im getting the same inaccurate voltage settings on my board as others are reporting. Just adding my two cents in.
Well i tried another proven psu and the same exact symtoms appeared. On start-up I can access all saved profiles until I remove power and then nothing works when trying to boot again. The weird thing is , the same thing happens when loading a different bios--it works until shutting the psu down. Will try to flash the 2nd bios chip tonight. If that doesn't work it looks like rma unless anyone can suggest otherwise.
tripgood
Big hardware pile
Sry. Late post. The 3d performance works like a charm. Having a lil bit of issues oc'ing the ram though. Using 3 x 2gb stick 1600mhz and seems to not like going over 1500 on ram when using more then 160 Bclock. Tried 190 Bclock, 18x qpi, 8x - 10x muli on mem and 16x - 20x multi on uncore and still doesnt like it. I tried popping one of the sticks out and was able to post with higher mhz but still not close to stock 1600mhz. The vdimm is at 1.65v. Tried 1.85v but really was nervous about letting that sit. Another thing is board seems to like auto setting my timings to 8 8 8 19 timings while sticks are rated 9 9 9 24. Eh. No biggie but the fact I cant post over 1600mhz is irking me. I dont get it. I'll try upping the ram slowly using a 133 Bclock and see what I max out at.
I'm also having issues with oc'ing the core ghz but Bench can tell u about that lol. Think I have been pestering him about it in another forum. Its all good. I still like this board. Good job overall.
Tremble I'll give ya a working set later on that you can try
Coding 24/7... Limited forums/PMs time.
-Justice isn't blind, Justice is ashamed.
Many thanks to: Sue Wu, Yiwen Lin, Steven Kuo, Crystal Chen, Vivian Lien, Joe Chan, Sascha Krohn, Joe James, Dan Snyder, Amy Deng, Jack Peterson, Hank Peng, Mafalda Cogliani, Olivia Lee, Marta Piccoli, Mike Clements, Alex Ruedinger, Oliver Baltuch, Korinna Dieck, Steffen Eisentein, Francois Piednoel, Tanja Markovic, Cyril Pelupessy (R.I.P. ), Juan J. Guerrero
Bookmarks