i have gotten the floppy all sorted, can anybody shead some light on why i got the C1 error after changing my HDDś ???
Andrew
i have gotten the floppy all sorted, can anybody shead some light on why i got the C1 error after changing my HDDś ???
Andrew
I know how frustrating DFI boards can be but there is always the old standby when having issues. The battery removal clear CMOS. There are so many times I have had really strange behavior and done a battery remove and problems gone.Quote:
Originally Posted by terroristone
Just the cost of using the bleeding edge boards. I also find that ehen I get really choked at these boards is the perfect time to do a bettery removal. Leave it for a couple hours minimum and come back with a more relaxed attitude. Worked everytime so far ;)
ok this is where im at, system back to normal specs, windows has installed, after first reboot to continue install i get BSOD, seems nothing i do so far will stop this....any ideaś?? i can believe the problems im having, my old dfi nf4 expert was a dream compaired to this...
Andrew
When you get the C1 error, try this.....
-Turn off and unplug PSU
-move jumper J1 from 1-2 to 2-3 and wait maybe 10 sec..
-move the jumper back to original pos. and turn your system back on....
or
-Turn off and unplug PSU
-clear cmos and the jumper right beside it, then take off the batt.; wait a few
-replace batt and both jumpers and thy to boot...
Hope this helps cos thats the only hting thats getting me going these days using my QX9650....
I swear running DFI boards is like having a really hot girlfriend thats a total b!tch....
Have you done the Battery Removal for hours? Perhaps overnight as well? I have had it where I set something too agressive in the BIOS and it screwed the CMOS just enough to hoop me. I would go back to known settings and it would still be borked. I had to clear CMOS for hours at a time to get back to normal, but after that all is back to normal.Quote:
Originally Posted by terroristone
And a Merry Christmas to you too :)Quote:
Originally Posted by Brother Esau
And as far as you missing the T2R forum, by the sounds of anything relevant on the AMD side of the camp, you will most likely be back before long :ROTF:
Tried it but my QX is still having lots of problems... only new option I saw was some countdown option....Quote:
Originally Posted by cantankerous
Max, but sbPLL is more important and set it to max also...... But its either your cpu has 600fsb in it or it doesnt;) ...Quote:
Originally Posted by mad_skills
http://ocidb.com/albums/userpics/10062/normal_600.PNG
Quote:
Originally Posted by luihed
I Love it:rofl:
so dam true man.Quote:
Originally Posted by luihed
The C1 error has gone, im doing another install using a different raid driver to see if thats whats causing the BSOD.
Thanks for all the help guys, i need to settle down sometimes and think a little more logitical.
Andrew
confirmed : im an idiot..hehehe the other raid driver worked...seems all good so far..
********QX9650 or Quad Owners, Please respond******
I recently got a QX9650 and ive been having some trouble booting after a failed overclock... I just noticed that my cpuVTT was undervolting like crazy when using the QX, my E6600 on the other hand is OK:confused:
QX9650- set at bios=1.6v actual=1.43v
E6600- set at bios=1.6v actual=1.58v
from clear cmos... ( default 1.2v)
QX9650= 1.07v
E6600= 1.2v
Actual voltage taken straight from mobo by multimeter, same figure I get from smart guardian...
Anybody tried the 12/05 Beta Bios? is it any good? any reason for shifting to it? Thanks :)
Happy Holiday Guys! Treat For You
Heres a Really Nice DFI Wallpaper and some Christmas Cheer:D Please Click Me
hehehe love it! slim santa...Merry christmas guys!
yeah, i would like to know if that beta is any good..:up:
Ok guys, I took the plunge to flash the new bios just a few moments ago since no one else had any comments on it. There are LOTS of changes in this bios. Allow me to explain.
To start, under the Onchip IDE Device settings there is now an option labeled 'special patch for JMB63'. The options are enabled and disabled. There is no description so I have no idea what it does but it relates to the JMicron onboard controller.
Second, under the Genie settings there is now an option labeled 'O.C Fail Retry Counter'. It defaults to 0 but you can change this to any number of times you want to the board to try and boot from a fail overclock. May be useful if it manages to post at all from a failed overclock as you may be able to enter bios and make changes without having to clear CMOS.
Thirdly, under the Clock Settings Fine Delay the way the options are listed is different. Before you were able to change by whole decimal numbers to your liking such as 0-10 only. Now the options are listed as follows. 133ps, 534ps etc. They look odd and I have no clue what they are but perhaps this is a way to fine tune clock delays even more?
Fourth, under the Read Delay Phase Adjust heading it now lists exactly how the Read Delay Phases are working. For example, CH1 on my setup reads 6-7-7-7-6, where as CH2 reads 7-7-7-7-6. This is a great way to see exactly what it is doing per cycle as making changes will be reflected in the numbers above.
That is all that is 'visibly' changed as bios options, who knows what other fine tuning was done in the background for performance and stability that we can't see or read with our eyes. I have only had my system up long enough to write this but so far my everest memory read has gone up 20mb/s from the 11/13 bios but this could just be due to margin of error. I will begin priming from my stable settings from 11/13 to be sure they still keep up.
Hope this helps some as the changes listed above may warrant a flash for something new to play with. If anyone can explain what some of the above listed options are please do as perhaps we can all learn a little something more about what this board has to offer.
All this yet the bios was only to have a microde update change. I love how DFI sneaks in a whole revamped bios when it lists that on the download page.
Good morning!
I was recently running through some overclocking sessions to slowly work my way towards 4GHz on my Q6700 and I've apparently got myself into some weird BIOS issue. I was happily priming and checking SPi at 333x10, 333/800 RAM, all other settings to auto (timings and voltages) with the exception of NB voltage, being bumped up to 1.4(something), two notches up from default.
When I decided to kick my FSB up to 340, after I rebooted I got error code 88. I was able to clear the error by using the clear CMOS jumper and then removing the mobo battery, this will allow me to boot and gives me a CMOS checksum error (or something, mentions bad OC as well) so I can either F1 to continue or DEL to enter BIOS. Regardless of which option I choose, when I reboot the next time (either from saving new BIOS settings or from the Windows desktop) I once again get the BIOS code 88, and I have to re-clear the CMOS to do anything.
I've tried using Winflash to update to the LP35DB07(11/07) BIOS, as well as, Tony's BTP35B07(modded 11/07), and LP35DC05 (12/05 beta). All of them show the same behavior. Should I try awdflash? I think I may have a FDD lying around which I could use if anyone thinks it will help, or I could always use Tmod/Logan's CD.
Currently my system has power removed, clear CMOS jumper set to 2-3, and the mobo battery removed. By the time I get home from work it'll have been out just over 12 hours.
Any suggestions? Please don't hesitate to ask if you think I may have left out some pertinent information.
Thanks!
I had this last week when one of my raptors went down and took my system with it after the array was broken as it was in RAID.
I was able to cure it simply but turning off the back of the PSU and removing the power cable from it. What I then did after I reattached the power cable after a good 30 mins or so is an EZ-Clear by holding the front reset and power button on my case for 7 slow seconds. I then powered up and was able to get into the bios where the first and only thing I did was load optimized defaults, saved and exited. I was fine after that to fine tune to my liking.
Although I'm pretty sure I tried your method (Yea, I read it much earlier in this thread and tried it, thanks btw!), I'll give it another go when I get home from work.
I can just about always get into the BIOS after a CMOS clear, but the main prob I'm having is that even though I can Load Optimized defaults, when I save and exit, that first reboot takes me to another 88 code again. I *may* be picking up a couple new HDs today (depending on whether BB has any in stock) so I can try running with another. It is almost as if my board is booting with some phantom bad-oc settings or some such.
hmmm I am seeing a trend here. You are getting this error over bad hard drives and I got this error after my Raptor hard drive went down. Can you try and post with no drives connected and see what happens? If it always posts then it is either the drive itself, a finicky port or a bad cable.
Yeah, I'll definitely try swapping SATA cable, and then I'll try with an old IDE drive to see if that makes a difference. As far as I know, my current drive is ok, but I'm no HD tech so I make no promises.
Haven't heard what this does as of yet.Quote:
Originally Posted by cantankerous
0 is disabled. Selecting any number of retries enables this for that amount of attempted boots at current settings. If not successful the board will revert to default settings the same as when the Home key is pressed at bootup. If memory timings are totally screwed the board most likely will not be able to recover even with this enabled.Quote:
Originally Posted by cantankerous
The BIOS now allows the delays to be set in actual picoseconds instead of a numerical representation.Quote:
Originally Posted by cantankerous
Displaying the current pull-in will give the user a known good starting point with which to modify the settings.Quote:
Originally Posted by cantankerous
Thanks for the info Praz. Pretty much exactly as I thought and listed above however with a little more detail which is what I wanted. I currently have the OC Fail Retry Counter at 0 but may set it to 1-2 just in case something goes amiss in my testing. Would be nice to know the bios has a chance of recovering itself without my intervention should it be possible.Quote:
Originally Posted by Praz
There was another bios setting that introduced back in November labeled 'shutdown after AC loss' or something along those lines. What exactly is this? I currently have this on Disabled as well. This sounds like an option that should be and actually is in the Power Configuration menu where the board will not power itself backup if the power was cut to the system by say a blackout. Why would this be listed again in the Genie settings unless it has another purpose? I like to know what all settings do exactly in case they come into need one day.
This o/c retry is a nice add-on, makes work a whole lot easier.:up:
As for support goes, it's the same as the latest one official?
Wow, lots of new posts since late last night! Cantankerous thanks very much for taking the time to go through the new BIOS and fill us all in! I also flashed to this BIOS last night but didn't notice all of those changes (then again I only played with it for about 45min).
Praz,
Do you happen to know if there is any similarities between the "Picoseconds" and the "Numerical settings" within the "Clock Settings Fine Delay" options? That is to say if I used a specific setting before, can I just convert that setting into "Picoseconds" so that I continue to have the same settings? If that makes no sense let me know, I had a hard time trying to articulate my question so that it made any sense, lol!
On a separate note the 7900GT my friend let me borrow is working flawlessly with my motherboard! Along with the other tests I did with an XFX 8800GTX and eVGA 8800GT I'm not certain it was my graphics card that was the problem. Plus I just checked UPS tracking and my replacement 8800GTX is on the truck for delivery today so I'll post back with results (I'm hoping very much that it works)!
Cantankerous,
I believe that "Shutdown after AC Loss" setting is incase the power goes out. If you have that setting enabled and the power goes out, your computer won't turn back on after the power comes back on (I think anyway). I thought about leaving it enabled and then just switching the breaker in my electrical box, waiting a few minutes, and then switching it back on. That would be a good way to test I think?
No way to correlate the numerical settings to the actual delay time. Being able to set the actual time delay does give more control over the settings. With the previous BIOS if the current setting was 3 and you manually set 3 it was assumed you were manually setting the same value but that was not the case.Quote:
Originally Posted by Roger_D25
You can easily see this now that the values are being set by the actual time delay. Look at your current setting and then compare to the time values that are available. The BIOS selected value will fall between two of the user selectable ones.
Just pull the PSU plug from the wall.Quote:
Originally Posted by Roger_D25
Duh, that would certainly be the better and easier way to test this! And to think I just started graduate school for mechanical engineering, lol! By the way thanks for helping to explain the new setting options for "Clock Settings Fine Delay", much appreciated!Quote:
Just pull the PSU plug from the wall.