Is anyone running 2 x 2GB Mushkin Redline PC8000 on their P5Q-Pro? I would like to know your results with the different BIOS'!? :)
Printable View
Is anyone running 2 x 2GB Mushkin Redline PC8000 on their P5Q-Pro? I would like to know your results with the different BIOS'!? :)
Quote:
Originally Posted by carepolice
On Asus' p5q-e download page the BIOS history lists revision 1703 but the latest available for download is still 1406. :confused: ... simple URL hacking didn't get me the new BIOS, neither did searching google. Hopefully Asus pushes it out to us this week.Quote:
Originally Posted by Vazovskiiii
Lets just wait that final bios comes out, BETA's are just BETA's you know :DQuote:
Originally Posted by samsonJS
As people are still messing with the 16xx mBIOSes, I'll leave the 17xx versions for now until they become final.
Hey all. I have a P5Q Deluxe and 8GB of the G.Skill Pi DDR2-800 sticks and was wondering if anyone has been reporting any issues with the 1611 bios like Kai Robinson has with his G.Skill?
BTW, thanks for the big effort KET. I know what you do is quite time consuming and you are putting in your own sweat equity to make this happen, so I appreciate it very much.
are they pre-45nm?:rolleyes:Quote:
Modded ASUS P5Q/Pro/Deluxe/Premium BIOS
The hell kinda question is that? P5Q Series use the P45 chipset, 45nm support is the whole point in the chipset, and thus has been there from the word go :\
I suggest you READ the thread.
All subjective, try it and see is the only thing anyone can really say.Quote:
Originally Posted by Asmodeus
So what's with the new P5Q-E-BIOS?? I also saw that new thing in the BIOS history, but nothing to download (NO, it is NOT Beta)...
EDIT:
Google gave me a link to this:
ftp://ftp.asus.com.tw/pub/asus/mb/so...-ASUS-1703.zip
So, it's not on the "ftp.asus.com", but on the "ftp.asus.com.tw", I never check that out, only the "ftp.asus.com"...
Okay. I'll let you know.Quote:
Originally Posted by Ket
With 1702, all my BSOD's disappeared! As if by magic, the system is oddly stable....VERY oddly, cause it's never been so rock solid @ 4Ghz!
I'd wager that Asus buggered about with the memory tables to fix the G.Skill issue ;)
1702 also had an odd spat with my CrossFire settings, it's possible that the 8.12's on these boards MIGHT work now, but i spent the better part of a day just getting the 8.10's to work, so sod it, i'm not trying until 2009 :D
You got the Dlx, right? But sounds good, gonna try it myself on the "E"...:DQuote:
Originally Posted by Kai Robinson
Well, did the m1611 update on my p5q deluxe and it took without a problem. Didn't even have to reset the bios by pulling power, battery, cmos switch. It took well. Now I need a good overclocking recipe for my p5q deluxe, q6600 g0 watercooled, pny 8800 ultra watercooled, and my 4 x 2 (8 gig) g.skill PI ddr2-800 ram.Quote:
Originally Posted by Ket
Hey, anyone here have one? Thought I'd ask.
I'll take a look on the tw server later, got a PC I built for my folks to power up and check all is still in order (ripped it apart to do a few mods and tweaks)
What Kind of issue? I haven't noticed any problems with my HD3870 CF setup... the ATi Cats still have CF BSODs with all kinds of HD4850s still.Quote:
Originally Posted by Kai Robinson
Well CF was initially disabled and the card reported Code 43. Upon rebooting the card was fine but CF was disabled still. Then rebooting again brought the CF option back to CCC, and rebooting AGAIN enabled it.
1702 was/is final plus it now shows up on the BIOS page.Quote:
Originally Posted by Ket
Just like to say I love these modded BIOS, nice to be able to use 8Gb ram at there 1066 rated speed and 5-5-5-15 completely stable and have my quad overclocked at 400Mhz+ which never happened with the official BIOS's.
^_^
P.S. Official link http://dlcdnet.asus.com/pub/ASUS/mb/...ELUXE-1702.zip
Ket
Could you make the next BIOS more compatible with the Mushkin Redline PC8000? I can't seem to get them stable even at stock speed... When I reach ~900MHz they become unstable!
Let me know if you need more info! :) THx
Well, I've had a look at the new BIOSes.. their odd. Memory table sizes keep dropping, which suggests Asus are having some kind of memory compatibility problems (although of course theres nothing to solidly say one way or the other) so instead of what I normally do I'm going to stray away from my given path of attack and hook things up so (in theory) the new set of mBIOSes will hold a lot more compatibility.
That sounds great...! I'm looking forward to the new BIOS' then :)
Thank you for the efford!
That sounds VERY good man!! I will test it on my P5Q-E once it is out!!Quote:
Originally Posted by Ket
Thanks a lot for all your efforts!!
New mBIOSes are ready. As usual all feedback is useful, I'm particularly interested in the following regarding the new mBIOSes;
Asus 1611 P5Q memory compatibility & performance vs. P5Q mBIOS memory compatibility and performance
Asus 1613 P5Q Pro memory compatibility & performance vs. P5Q Pro mBIOS memory compatibility and performance
Asus 1703 P5Q-E memory compatibility & performance vs. P5Q-E mBIOS memory compatibility and performance
Asus 1702 P5Q Deluxe memory compatibility & performance vs. P5Q Deluxe mBIOS memory compatibility and performance
Asus 1611 P5Q Premium memory compatibility & performance vs. P5Q Premium mBIOS memory compatibility and performance
Knowing peoples results to do with these will help me greatly in tuning memory compatibility.
P5Q Series pack contents:
P5Q 1611m (updated)
P5Q Pro 1613m (updated)
P5Q-E 1703m
P5Q Deluxe 1702m
P5Q Premium 1611m (updated)
DL Linky
after using all original bios and mooding hte most stable one I have is 0703 even original or mooded
Testing the new 1613m BIOS for PQ5 Pro - will give comments when done
Two questions
1. Where is the 703m BIOS you speak of ?
2. Is there any way to unlink the FSB & memory timings - frustrated that my stable FSB for CPU only gives options for 1064 or 1067 for my 1066 mem. Would be nice to set both independantly !
1. Theres a link for 703m on the first page somewhere
2. Impossible, unfortunately.
Who already tried 1702m for Deluxe? Is it better that official 1702? And in 1702m E.Z. Flash availible BIOS downgrade?
Went from 1402 to 1703m on P5Q-E and now I have something weird.
I'm a underclock/undervolt guy (I know I'm a pariah here :D) and until now EPU served me well through many BIOS updates but now something is not right.
I have a profile for idle with FSB 264 and heavy undervolt. If I choose DDR667 in BIOS then FSB remain at 333 and not 264 as it should be. Good thing is that I can OC a little until ~ 3.5GHz.
Attachment 91045
If i choose DDR800 everything is fine but no OC because memory is drawing me back
Attachment 91046
EIST/C1E/C-State Tech enabled in BIOS. Any ideas?
BTW I'm not an OC-er and it's fine if I stay at stock speeds but I'm curious why this time EPU have this glitch. :)
another something weird
the smart fan with the final 1611m bios didnot work fine
I use it with my zalman cooler with every bios version with no trouble but with this one the fan speed still in the low speed even when I test the cpu with IntelBurnTest but with my any other version the speed increase while cpu loading
Currently running 1702m on my P5Q Deluxe, running fine so far
Intel E8200 @ 3.04
ASUS P5Q Deluxe
G.Skill 800 2x1GB
ATI HD4850
I wouldn't know on that one.. largely because EPU is rubbish and I don't use it :p: A good port of call is always to load BIOS defaults and reset CMOS. As well as make sure things like EIST, C1E etc are disabled.Quote:
Originally Posted by burebista
Fan settings have been bugged for some time on the P5Q boards. Eg; enable Q-Fan and even if you select "Turbo", the fans will still spin at low RPM.Quote:
Originally Posted by hema
I done CMOS Clear, but i still dont have boot logo. :/ What should i do to bring it back? P.S. P5Q dlx 1702m P.P.S good bios, ocing on it is better than on official 1702.
I switched from 0803 last night to the 1702m one and everything went smooth for me. I didn't have to clear the cmos or anything. I just reset to default settings and flashed and went back in and adjusted everything back to normal and set it to performance "the dreaded performance seting" and everything continued as normal for me. I played GTA IV for as long as the game would let me had to reboot " normal with game right now until patched" came back into windows and continued playing and no blue screens nothing to indicate an issue. My memory speed test came out as usual. The one thing I wanted to do is to try to push my over clock further but, I was to busy gaming :p:. I will keep posted but, it seems as if the modded 1702 is fine by me.
Thats a phantom issue, I don't know why some people can see the boot logo and others can't. I attached the boot images I use a few pages back for anyone that wants to try injecting it with asus mylogo.Quote:
Originally Posted by lexus232
:up: I'm having great results with 1611m for my Pro, I can hit 3.2GHz @ 1.35v (actual about 1.32v) where before when I had to stick with 703m I needed 1.425v (1.4v real).Quote:
Originally Posted by truehighroller
Boot images do not appear if you don't export them in correct format. So far i noticed Pain.NET exports them the best when using GIF format with default settings.
Just load the image and save it as 640x480 GIF image. Voila. Worked each and every time. Other methods usually just failed.
My battery just died. In a 5 month mobo it is really strange.
I also had , after battery replacement, some issues with the bios settings being lost after a coold boot.
Reflashed 1406 once againd and its now OK.
The images are ok, I use paint.net. I really don't know why some can see the boot logo and other don't, I'll have another look at it later probably.Quote:
Originally Posted by RejZoR
results aren't as scientific as I was hoping for and aren't finished ><
Received my Cell Shock D9GMH kit in this week and have been playing with it and 1613M updated. Attached are screens of results. Lowest I can get the memory is perf 8 3-3-3-9 800 stable, perf 6 3-3-3-9 800 SPI. at 1000Mhz + I cannot drop it below perf 10 4-4-4-12. Not the most experienced with RAM OC'ing but I was under the belief that this kit should perform better.
Stock Results:
http://img261.imageshack.us/img261/6...ultswi3.th.jpg
3-3-3-9 2T 800Mhz (1-1, E8400 @ 3.6)
http://img356.imageshack.us/img356/9...8800ti0.th.jpg
5-5-5-15 2T Perfomance level 10 1000Mhz (1-1 E8400 @ 4.775)
http://img53.imageshack.us/img53/388...rf10qo0.th.jpg
I also have a question, according to the Motherboard temp sensor, the board reports it running at 29C @1.3V for the 'motherboard sensor' Normally this would be the chipset temp no? anyone know of the safe voltage levels for this chipset? I think that is what is holding the OC back at this point but I am not sure
Something wrong with both standard 1703 and 1703m!? As soon as I do any OC´ing, the bios resets the settings so after post im back with all default settings?? Anyone know how to fix this?? As this isnt right!?
Try setting NB and SB voltage to 1.3v and working from there. I can run PL6 @ 1200MHz with my GKX kit so something in your config deffinately isn't quite right.Quote:
Originally Posted by Triage
Tried loading setup defaults and clearing CMOS? (proper clear that is, remove power cord and battery)Quote:
Originally Posted by MonsterMan
Ket, can u please add downgrade ability from EZ Flash in 17xx bioses?
I don't need to add "support", its already there. :\ Amazes me how many people don't look at the options tab in the scroll-down window of asus update. :p:
huh, try to downgrade with enabled BIOS Downgradable in options and you will see this: Warning! The BIOS image can't use in this motherboard. (The EEPROM Type incompatible) :p:Quote:
Originally Posted by Ket
Ok so I could use a little advice.
I am re-building my system to include a P5q Pro, E8600, and 4x1GB G. Skill HZ 800 RAM.
My goal is 450-470 FSB with the memory synced. I have read most of this thread and cannot come to a good conclusion as to what is the best bios for my config.
I've found this page on a BIOS of MSI P35-Neo2...
could be possible to implement the same thing [choosing IRQ for specific PCI slot] on Asus [p5q] ?
thank you
Sounds like your trying to use the wrong BIOS file :p:Quote:
Originally Posted by lexus232
Very subjective. I would start with 1613m though.Quote:
Originally Posted by Froggy
Probably, but not without some work using tools I don't have.Quote:
Originally Posted by lupo17
i tried many bioses for my mobo, and always i see this. And not only i expecting this problem with 17xx bioses, in P5Q Deluxe thread i saw other people with such problem. :yepp: That's why i asking for your help.Quote:
Originally Posted by Ket
Have you tried resetting your CMOS (remove battery and power cord) and uninstalling asus update and downloading the latest one?
i tried resetting CMOS many times (with cord removing, but without removing battery) and tried latest Asus Update, it didn't helped. Also tried to install 6th version of asus updt, but it says that no Asus mobo detected. :confused:Quote:
Originally Posted by Ket
Ok, I'd try the following and if it doesn't work.. even I'll have to have a good hard think :p:
1. Uninstall asus update
2. Uninstall video and audio drivers
3. Power down, remove battery, power cord, set CMOS jumper to "clear" position
4. Press power button 3-4 times for 3 seconds each to discharge the capacitors
5. Leave for 5-10 mins then power back up
6. Load BIOS defaults, save and exit.
7. Re-install Intel chipset drivers v9.0.0.1009 (AFAIK theres no easy way to uninstall the drivers, hence why uninstalling them isn't listed above)
8. Restart
9. Install asus update (restart if you feel it may help)
10. Try flashing your BIOS.
Intel P45 Chipset Drivers v9.0.0.1009
I have been running the m1406 bios for my p5q-e and just updated to the m1703 bios. I used asus update and the bios was applied successfully. I rebooted and then entered setup. The bios confirmed it was bios 1703. I tried to load from a saved OC profile but the settings were not applied correctly so I had to manually update all bios settings. I set everything to the way it was when running the m1406 bios but noticed that several options were missing like ez flash. I saved my settings and rebooted and now I get nothing.
Computer turns on and fans run but I just get a blank screen. I powered off the computer and removed the power cable. Set the jumper to clear cmos position for about 10 seconds and then put back to normal and tried to boot. Still I get nothing.
Is there any way to roll back to the old bios? Seems like my mb is hosed now.
Well there must be someway to get it work, maybe try another rams or even change memory slots (yellow -> black /// black - yellow)Quote:
Originally Posted by darklink
P5Q-E Got 2x bios chip, you will see em they are in right downcorner, Just swap em and it will work.
(And its possible to buy new bios chips)
Can the bios chips even be remove? I just tried what ket had mentioned in regards to another issue (pulled the power and then pressed power button several times for 3 seconds each time to discharge the capicitors and then let it sit with no power for 10 minutes). If I try the bios chip swap, which one is the primary and which one is the backup?
No need to know that, just change them like -> 1-2 TO 2-1 :up: (atleast if you just want have it work now, when you want know wich is the damaged i think its just a test-n-see)Quote:
Originally Posted by darklink
And yes bios chips can be removed, just whit a fingers
well.... i swapped the bios chips and still nothing. computer turns on and i can hear all the fans but blank screen. anything else i can try?
It's not a file issue - 1703 is just buggy (manual memory speed settings were disregarded and other weirdness on my machine). Afudos is required to roll back and the board should work as expected afterwards...Quote:
Originally Posted by Ket
not sure if that applies to my case cuz i cant even get a post screen. when i turn the computer on i just get a blank screen. gonna pull all hardware out and leave the cmos battery out for a while. hopefully i can get this going.
well.... i figured it out. mbios 1703 must have boinked my memory. i put in a pair of old mushkins and it booted up into the backup bios. i was able to flash back to mbios 1406 and then put my gskills back in but they will not post.
sticking with mbios 1406 and just ordered the 2x2gb gskill pi ddr2 1100 kit.
Quote:
Originally Posted by darklink
Quote:
Originally Posted by darklink
Quote:
Originally Posted by darklink
Right, where to start here everything is all fragmented into loads of posts :p: Firstly, its NEVER, EVER, a good idea to load saved settings from a previous BIOS, ALWAYS set things manually after a BIOS update. Secondly, its always a VERY BAD idea to update your BIOS while your system is still OCd. Things like EZ flash should deffinately not be missing. Others have used 1703m (if memory serves one such person is kai) and all is running well, so best I can come up with on that is the BIOS flash did not take properly, or asus update fudged something during the flash.
You mention your using G.Skill, BIOS versions have known to be picky about G.Skill memory, to say the least. One BIOS version all may work well, and in another not. From my experience using G.Skill (or as I now call them G.Kill) memory, they have always after 6-12 months tops, died for absolutely no reason. So I now stick to better brands like Cellshock. Another explanation is simply if you ran your memory beyond its recommened voltage specs, it overheated then died, coinciding with the BIOS update, which boils down to nothing but pure coincidence. Try upping your vDIMM to 2.1-2.2v and see if your G.Kills boot, if they do, you know your sticks have degraded. *Pant* Phew, ok I think thats got everything there.
Not all BIOSes are suitable for all hardware configurations, simply put. No idea why you needed to use AFUDOS, shouldn't of needed to use that at all, so I can only guess at what happened there.Quote:
Originally Posted by Moba
Lastly, I'll stress it again DO NOT FARK AROUND WITH BIOS UPDATES FOR THE HELL OF IT! DOING THIS WILL LEAD TO PROBLEMS IN THE END. ONCE YOU FIND A GOOD BIOS THAT WORKS WELL FOR YOUR SYSTEM, STICK WITH IT!
Blah Blah Blah :lol:. I am sitting at 485 X8 now with the 1702m :up:. I still need to check for stability but that's ok. I am still sitting at 485 x8 :up:.
I havent even got around to using 1613m yet.. I was hoping to do that today but being dragged away for the last 7 hours to find some frilly nightware stuff for Nikki for christmas scuppered that one..... Why does shopping with women take so long?
1) They look at everything
2) They look at everything!
My but you're helpful. :)Quote:
Originally Posted by Ket
I think my ballistix were just dead. So I have some OCZ Fatal1ty instead now.
Everything works fine. Flashed back to 1406m (don't think I did the bootblock thing.)
No problems other than my hard drives not appearing properly if placed in SATA 0 or 1 (I'm assuming it's a weird RAID thing... but they work fine anywhere else, so I'm not complaining.)
No other complaints thus far. I switched back to 1406 using DOS btw. Everything worked like a charm.
The "no booting" thing turned out to be because the guy shipped it to me with the CMOS jumper in the wrong position (always ME.)
MAIN reason I switched back to 1406m, though, was because I preferred their logo. :)
My system wsn't stable on that setting :(. I think this board just can't handle any more of my CPUs raw power :p:. I am just as stable on the 1702m as the 0803 though so, I am happy :up:. Good job Ket and yes it is because they like to look :lol:.
Think you reached the limits of the P45 chipset with a quad, on a DDR3 board it's even worse :( with the P5Q Dlx I could go up to 500FSB for benching with the QX. With the DDR3 EP45T UD3P I'm limited at 470ish ( and that's already with loads of tweaking reference volts )Quote:
Originally Posted by truehighroller
Looking at everything or not... thats 7 HOURS of my life that was excruciatingly BORING! Yeesh in the time it took her going round one shop I could of gone all around town! Why do we put up with it?? .... oh yeah.. sex :p: Though even that can easily be forgotten on days like yesterday lol.
@ Leeghoofd,
I have been thinking for awhile now that this is what has happened, that I just reached the limit of this board. That sucks about the EP45T UD3P board. I feel that I could do way better if I had a board that could handle more raw power.
@ Ket,
Ahhh sex, they have us by the balls there huh. I actually cut my lady off occasionally just to show her I can do it to, to keep her in check a little :lol:. It works trust me, cut them off, watch :banana::banana::banana::banana: :up:.
lol I wouldn't dare, Nikki would literally cut my balls off if I did :p: My only sanctuary is when I go round a mates, then I'm free to do as I want :D
Hello! :)
Anyone with 65nm Core 2 Duo's here?
Could use a voltage advice if possible.
Got P5Q MB (mBIOS 1611) and watercooled E6400 CPU. 8800 Ultra + 580W PSU if it helps. I seem to have problems stabilising the OC. Increased voltage for NB and SB by 0.1 (to 1.3) and by 0.1 or 0.2 for FSB seems to do the trick.
OC @ 3200 absolutely stable with 1.3125 VCore, 1.5 PLL. 35-40C tops with 100% CPU load, 27C idle.
OC @ 4000 (didn't test it higher) PC freezes during Intel Burn Test no matter how high voltage I use (1.525-1.6 Vcore, PLL doesn't seem to affect it, tried 1.5-1.8, is it just a setting for quads?) as soon as both cores are at 100% load (depending on voltage can be 2-3 mins into test as well). Can even actually run some 3D games like this but they crash within 5 mins. :D
Can't even stabilize @ 3600 - same freezing issue. Nah, can't be memory, tested it.
3600 is what I'm aiming for - any suggestions? 4000 would be sweet, but 4000 @ 1.6 VCore results in ~80C temperatures during Intel Burn Test - ouch! Should be lower using regular apps, but still ouch. Heard some peeps were getting their E6400 stable @ 4000 with 1.525 Vcore, mine would barely start with such voltage...
Perhaps I'm doing something wrong... :rolleyes:
And one more thing, how do I check NB temperature? BIOS shows motherboard temperature (whatever it means), but it's around 40C and NB seems way hotter.
Thanks in advance! :)
It may be a board limit your having. The parts on the P5Q are not as high a quality as the Pro\E\Dlx\Premium. Your best off starting from scratch again entirely. Set everything to stock, put PLL voltage @ 1.54\1.56v, NB & SB voltage @ 1.3v, start with a vDIMM of 2.1v and set timings to 5-5-5-15, set multiplier as low as it will go and use the slowest memory divider and use the 333 strap. Now start seeing how far you can push your FSB (I dont advise NB voltage higher than 1.3v without active cooling). We will need to know more details about your system for more specific advice.
Ket's new Avitar=:up:
I had a P5Q-D which I flashed to the 1402m bios which worked like a charm. Sold the board to a friend in need, still running great. After monkeying around with a DFI P45 LP JR for a while, (installed that board in an upgrade build for a co-worker) I went back to an Asus P5Q Pro, which is a far better value for me and about a hundred bucks cheaper than the Deluxe. It is an A2 rev. unfortunately, but is working well. Anyhow, it came with the 1306 bios and I have the 1613m ready to flash, but was wondering if Asus (and then Ket:p:) has a 17.. series in the works for the Pro?
Also, I read your comments on GSkill (GKill:eek:) ram, I may go back to my set of Team PC2 8000 D9GMH's if they will work well with this board/appropriate bios combo.
Whenever Asus release a new BIOS, you can bet I'll pick it apart and make my changes, don't worry about that! :up: Theres no 17xx BIOS for the Pro yet, but there will be I'm sure ;) Glad you like my new AV, its my christmas one :D Unfortunately what I say about G.Kill is no understatement, EVERY G.Kill kit I've had has died in 6-12 months for no reason. Regardless of everything else, its a pain in the arse having to RMA 1-2 times a year.
Alright! TODAY IS THE DAY! I finally get to mess around with my puter for a while :up: Will update on any significant changes such as FSB\memory improvements and if I need less or more voltage, that kinda stuff.
Heres the first set of results.
BIOS: 1611m
vDIMM: 2.2v (BIOS setting)
Strap setting: 266
I can probably do better, pretty sure I can eek 1300MHz out but I don't have the time for tweaking in that way, FSB deffinately seems a lot more stable above 401MHz. Adjusting TRFC from 42 to 30 made almost no difference across the board, biggest difference was -0.6ns latency, but you won't even notice that in the real world., the best TREF setting was 16383 for me, didn't do much in terms of bandwidth but latency went down to 50.7ns. Next test will be with 1613m, or as I'm sort of looking at it as (expecting real good things from 1613m) "the big one" :D
Sorry Ket. I was just baffled by how all of a sudden my board wouldnt boot. You were right with just about everything. Running the windows flash utility while overclocked probably did not help in a successful flash. It did work when I flashed from the plain 1406 to your mbios 1406 but I guess that was more of luck. The g.skill hz's I had have been running for well over a year and I guess it could also just be that they hit their life limit. I had been running them at 2.3v for a while on my Abit IP35pro and that probably didnt help them much (before I made a custom cooler for my RAM). Now that I am at least up and running with my mushkins on mbios 1406, before I get my new ram, i am gonna switch the bios chips back over and do a proper flash to m1703 and play with the settings a little more. m1406 has been great and I think once I flash it correctly, m1703 will be too. Thanks again Ket!Quote:
Originally Posted by Ket
Remember to at least load setup defaults then save and exit after the flash ;) I recommend anyone updating their BIOS (official or mBIOS) remove power cord and battery, and set CMOS jumper to "clear" after the flash. This is the proper way to do things for numerous reasons, regardless of what any monkeynuts elsewhere may say.
Question regarding my setup - its as the sig says but with the following settings:
CPU vCore: 1.41875
GTL Ref 0/1: 0.670
NB: 1.14
FSB Term: 1.14
PLL: Auto
DDR: 2.0
Now i'm using a 2x2gb set of G.Skill PC6400 PQ's, these have been through memtest at 5-5-5-15 @ 2.0v, 900Mhz + and they've been stable (with the CPU at stock)
However, i think i may have hit a wall of some sort - 445x9 works, but 421x9.5 is more stable. And i can't drop the voltage any lower, or else Vista will BSOD with a MACHINE_CHECK_EXCEPTION / Stop 0x0000009C Error.
my FSB hovers between 421.0 and 421.1Mhz so i dont think the PLL needs to be increased, but seemingly, increased NB/FSB Term just make it unstable. Should i be decreasing the GTL Ref when decreasing the vCore as well?
I would try decreasing the GTL Ref, yes :up:
CPU vCore: 1.41875
GTL Ref 0/1: AUTO
NB: 1.14 --> try 1.2
FSB Term: 1.14 --> Try 1.2
PLL: Auto--> Try 1.56
DDR: 2.0 --> overvolts try 1.92
Leave all the GTL's AUTO
I did as suggested and now running ORTHOS at 1.40625v, GTL set to Auto....4mins in and its not BSOD'ed yet :p
Just thinking though, the first BIOS this board had was 0803, and from that point on, i've left the GTL ref at 0.670, so i'm guessing that now at 1702, somethings changed that my GTL ref doesnt need to be that high anymore?
Leeghoofd - wouldn't i want to LOWER vFSB if i'm trying to DECREASE core voltage?
With the auto settings for the GTL's if you up or lower the FSB termination voltage the CPU and NB GTL's values are altered as they are linked (no idea how to explain this in proper english) With the GB mobo you can see this clearly with the different reference values as it shows them...I just want you to be stable first and then you can slightly go lower mate... but I only needed to tweak the GTL's on the DLx from 450FSB with the quad, with the wolfdale I needed manual tweaking from 533FSB or such... be lucky you don't own this DDR3 P45 version, they are even more sensitive ( even with a duallie ) think the strain on the P45 chipset is too much for it too handle
Also I couldn't even post with FSB Term 1.14 on my rig I needed 1.18 at least to get it going (talking 400-450FSB quad and 500-550FSB duallie), Nb voltage lowest I could go with 4gb ram was 1.18-1.2...and all depended too on how much I tweaked the ram... for 24/7 I prefered to set it a bit looser...
I have said this before the voltages I post worked for me and can be lowered for sure... take them as a guideline but your final results can be totally different from what I posted... Asus did a nice job in the bios with these GTL values...
the new bios for the E let me finaly hit 4ghz! yay. i need to tweak it some still as the volts are kinda high all around.
http://dl.getdropbox.com/u/259073/3995.jpg
@ oMek,:up: Nice job!
Larry
nice one oMek ! :D
put +1mhz in so you get rid of 3xxx Mhz club :up:
That with mBIOS or vanilla? (I'm assuming mBIOS as you posted in this thread, but just checking :p: )
Sorry for stupid question, what is vanilla?
the original version = vanilla
why it's called vanilla?Quote:
Originally Posted by Leeghoofd
Vanilla is another way of saying plain. boring. ordinary.
thanks people ^^Quote:
Originally Posted by Ket
and yea thats with mBIOS, i dont dare use stock ones now. infact your mBIOS are the only reason i kept this board. hated it before i found em :up:
Just glad I can pep these boards up for people :up:
Maybe a silly question, but does P5Q mBIOS use P5Q Premium memory table here?Quote:
Originally Posted by Ket
Indeed it does :up:
Yeah, another mBIOS where I dont get the boot image either lol.
Just wondering ket...wouldnt it be easier and less frustrating not to edit the boot image to get rid of variability? jsut saying...
anyway, merry christmas!
Just a boot logo. Not exactly that important and its easy enough to change the logo anyway just by using the asus mylogo app, hence why I'm not really bothered by the fact some people can't see the logo while others can.
This post is specifically to help those out there who have flashed their (AMI) BIOS (any manufacturer, vanilla or modified BIOS) and are finding themselves unable to revert back to an older BIOS or update their BIOS.
How this anomaly comes about I'm not sure, but one manufacturer especially are notorious for this anomaly occurring with, ASUS. To get yourself out of this bind follow these simple steps;
1. Download the AFUDOS attachment (2.11, AFAIK this process will NOT work with newer versions)
2. Make a bootable floppy \ CD \ USB \ whatever with the BIOS you want to flash to on
3. Place the downloaded AFUDOS utility on to your chosen boot media
4. Restart
5. With (for the intentions of this example) your bootable floppy loaded and ready to go, type in the following then hit enter;
AFUDOS.EXE /iXXXXXX.ROM /PBNC /N
**XXXXXX denotes ROM filename**
Thats it! The utility will now perform a comprehensive set of checks, erasing and writing procedures. Just sit back and watch it do its thing and restart your PC when prompted.
note for this comm. line AFUDOS.EXE /iXXXXXX.ROM /PBNC /N
this will kill the ethernet chip in the mobo. which have atheros lan on it
like P5Q it will damage the mac add. of it
As far as I am aware, no it will not. Tested it myself.
I am sure of it
tested it on P5K(P35) and on P5Q(P45)
THIS two mobo. have the sam lan chip and with this boot plock no check comm. the mac add. of it will damage
http://www.xtremesystems.org/forums/...1&postcount=61
this for the p5k mobo.
the link for the p5q mobo. will come soon
net prob. here sorry
As I said, I have tested that method myself on my P5Q Pro, The Atheros chip is fine. Windows detects and installs the driver for it.