Modded ASUS P5Q/Pro/Deluxe/Premium BIOS

[carepolice]

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)

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)

[darklink]

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?

[carepolice]

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 (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)

And yes bios chips can be removed, just whit a fingers

[darklink]

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?

[Moba]

Sounds like your trying to use the wrong BIOS file

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...

[darklink]

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.

[darklink]

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.

[darklink]

sticking with mbios 1406 and just ordered the 2x2gb gskill pi ddr2 1100 kit.

[Ket]

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.

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.

Right, where to start here everything is all fragmented into loads of posts 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.

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...

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.

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!

[truehighroller]

Blah Blah Blah . I am sitting at 485 X8 now with the 1702m . I still need to check for stability but that's ok. I am still sitting at 485 x8 .

[Ket]

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?

[samsonJS]

1) They look at everything
2) They look at everything!

[norain]

If you flash from DOS be sure to include the switch for reprogramming the bootblock as well. I'm not sure if its the same scenario with you but when I got my replacement Pro (CPU fan header seemed like it was on its way out on my first board) the jumper for the chassis intrusion wasn't making proper contact with the pins, and hence wouldn't complete POST. A similar thing may be happening with your CMOS jumper, try switching it for a jumper you have that fits very snug over the pins

There are also still plans for that uber BIOS, just too much to do and not enough time. Lastly, the links do work, their just very popular so a little patience is needed sometimes.

My but you're helpful.

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.

[truehighroller]

My system wsn't stable on that setting . I think this board just can't handle any more of my CPUs raw power . I am just as stable on the 1702m as the 0803 though so, I am happy . Good job Ket and yes it is because they like to look .

[Leeghoofd]

My system wsn't stable on that setting . I think this board just can't handle any more of my CPUs raw power .

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 )

[Ket]

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 Though even that can easily be forgotten on days like yesterday lol.

[truehighroller]

@ 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 . It works trust me, cut them off, watch :banana::banana::banana::banana: .

[Ket]

lol I wouldn't dare, Nikki would literally cut my balls off if I did My only sanctuary is when I go round a mates, then I'm free to do as I want

[zalbard]

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.
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...

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!

[Ket]

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.

[Retro]

Ket's new Avitar=
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) has a 17.. series in the works for the Pro?
Also, I read your comments on GSkill (GKill) 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.

[Ket]

Whenever Asus release a new BIOS, you can bet I'll pick it apart and make my changes, don't worry about that! 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 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.

[Ket]

Alright! TODAY IS THE DAY! I finally get to mess around with my puter for a while Will update on any significant changes such as FSB\memory improvements and if I need less or more voltage, that kinda stuff.

[Ket]

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"

[darklink]

Right, where to start here everything is all fragmented into loads of posts 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.

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!

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!