Share the love! Or are you NDA'dQuote:
Originally Posted by Splave
Printable View
Share the love! Or are you NDA'dQuote:
Originally Posted by Splave
Any one experianced sudden BSOD 0x124 during daily use / web browsing after overclocking?
My P8P67-Pro with 2600k can pass LinX @5Ghz with 1.4v for 20 loops but BSOD when idle or web browsing... this issue likely happen in windows 7 but seems not in XP
looks to me a BIOS issue...
Yeah, that's SB. Load goes down, voltage goes down but the clock stays same and boom - BSOD. Tweak voltage for low loads with LinX 1 thread. No LLC is better.
Yes it happened to many people and they solved it by upping the vcore.Quote:
Originally Posted by ci2kla
Happened to me as well but i'm using offset now so its a different story.
the test was done with win 7 + sp1 ?
20 Pass Linx is not 24/7 stable. Thats what I use to narrow down my max oc. I run a 8hr small fft and then 8hrs blend to make sure my rig is 24/7 stable.
I realize this, but when member who represents ASUS says its coming in a week and then silence, it leads me to wonder.Quote:
Originally Posted by Praz
same for me, cant even build raid0 on SATA3 port 0,1 as raid manager fails to detect SSD on port0. marvell ports works fine though..Quote:
Originally Posted by Utnorris
Quote:
Originally Posted by nvous23
I think just Win 7 only, no SP1.Quote:
Originally Posted by Sevenz
The bottom Line is, I used another i5-2500k which require quite the same voltage as 2600k to get 5Ghz stable for testing, but didn't experiance any BSOD so far. Also if running the system under Windows XP with the same setting will not have any problems/reboots/BSODs...kind of weird...
Yes I have to admit by upping the vcore will help, but it only mitigates the issue which delay the 0x124 BSOD occur time but still cannot solve completely, which leads to me to suspect it's a BIOS problem...
that's what happen when big corporations stop making money on particular platform..they simply don't care :down:Quote:
Originally Posted by crazyea
lol silly ppl
next time check hwbot forum for the new bios
M4e 1090
btw no prob here running two raid's
Marvel Port - Asus DVDRW
port 0,1 - Crucial C300 128gb x2 Raid 0
port 2,3,4 - Intel X25m 80gb x 3 Raid 0
port 5 - WD 1tb Black
Just waiting to defy that 15 percent chance lol
Listen "silly" boy..i should't have to check on hwbot forum or any other mf forum for bios,there is your mobo maker side where they should be wildly available ,some of us just want some type of response here from the rep.Quote:
Originally Posted by cstkl1
Get back Jack
With the new chips if all that is being done is to isolate some transistor(s) then other than increasing the firmware stepping of the chip is there any reason the BIOS would need to be much different?
In other words I can not see why the current BIOS would stop being developed as there is so little change in hardware as far as the BIOS is concerned.
This is not officially supported by Asus ( title might be misleading), Bingo13 and Praz do it in their free time... Meaning if they lack time, they won't post here or answer to all the posts... nothing to do with ; "they don't care..."Quote:
Originally Posted by coolhandluke41
Lots of testers/benchers/reviewers got their hands on the new(er) bios(ses), maybe it isn't suited yet for us to use or try... Some of them just leak the biosses, some don't...just chill... If you know ya way around the web you will find them, since you are such a smart kid, that shouldn't be any problem at all...
Ok guys, comeon... please stop the flaming, or Fugger will bring out his pet Tiger and restore order...the last few posts above lee's were really uncalled for.
All you had to say was look on hwbot for leaked bioses, without calling someone a "kid".
And yes, they are LEAKED or beta bioses. if they were official, they would be on Asus' webpage. How would you feel if Asus released a beta bios officially and it bricked your board and destroyed your CPU in the process? You already saw what Nvidia did, TWICE last year, right? Sent out drivers that DESTROYED video cards. And you saw all the drama resulting from that...
Seriously, a LOT of overclockers here are over age 40. Some are in their 60's. Going around and calling us "Silly boys" is just asking for trouble. If you want teenage heaven, there are other sites (Like FM)...
Sorry, I'll try not to ask such questions again. :(Quote:
Originally Posted by Falkentyne
I'm not a mod. I just want to avoid some of the flaming that occurs on the [H] and elsewhere. There was alot of this stuff here back, like during the days when some people thought SNDS/GNDS was a myth, and thank God those days are over....
It's fine to ask questions, and it's fine to be upset at the slow pace of bios releases, even to vent about it. But anything that resembles a personal sort of attack gets uncomfortable. So much going on in the world lately....
I don't have an asus board, but I do know about the problems people are having with them, even on latest bios versions, and not related at all to the PCH issue...
BTW the people who release the beta bioses, if not released by the reps themselves, are often the overclockers/testers...it would indeed be useful if there was a thread always updating the latest test bioses...
BTW: a small word of history:
It took companies about 6 months (I could be very wrong; feel free to correct me) or so to release bioses that would stop the 975X strap "power off/on" cycle above 320 FSB, though some boards (like p5w64) never got one. That was annoying to anyone who had a cooling system that had to remain powered. The SB boards have been out just over a month, just to keep things in perspective...though the companies have had more of a presence now than in the early core 2 days...
And the hard work done by truehighroller helped fix a serious issue on the P45 board. It's sad though that Asus never did ANYTHING about the ram subtimings that were missing on the 975x, but were present on the 965p...the bios fully would support it....it's like Asus simply didn't CARE about 975x users at all back then....
Quote:
Originally Posted by ci2kla
Could be that you miss a hotfix for Win 7, this is what Gary Key (ASUS Technical Marketing Manager) say and suggest about it.
"If you are receiving random BSOD (Blue Screen of Death) under Windows 7 OS without any warning at stock or what appears to be stable OC settings, please download the following patch from Microsoft to have the problem fixed (98% fix rate): This hotfix will be in SP1.
http://support.microsoft.com/kb/979444"
Source
:shakes:Quote:
Originally Posted by Falkentyne
I'm still trying to figure out where in my post I fit in there. My question was about BIOS for the B3 stepping chips yet to be released and try and offer some comfort in that I believe BIOS development is still continuing in hope to try and dispel the thought that it might have come to a stop by some people.
Seems you have misunderstood my post. If you going to come in waving a stick at least try to point it in the right place.
u guys are asking too much from asus infact from any manufacturer.
heck for 4 months for m4e to reach bios 10xx
when in the past lol that took a year or two.
I don't think it's asking too much. Just because customer support was slow in the past doesn't mean it should stay that way.Quote:
Originally Posted by cstkl1
Asus or any other manufacturer want to sell their product, customers provide feedback to make the product better and help the manufacturer sell more. :)
My board is stable but Im waiting for a few bugs I have tested out so far.
1 fix the sleep when pll overide is on(computer will not wake back up)
2 cant run tight timings at all with 4 sticks of gskill 2200 cl7 running 8-10-10-27 2t and with just 2 sticks I can run 7-9-7-26 1t and bench at 6-7-7-24
3 fix the stupid double boot everytime you reset the computer and fix the endless restarts it does when the oc settings are too much.
4 fix the reset,the last 3 asus boards Iv owned never worked when reset was pushed,it would double boot,endless boot or just boot and say oc failed.
Im waiting for the next bios just like all you guys and hope some of my issues get resolved
I had a LinX stable 5GHz CPU, it wasn't Prime95 stable (BSOD 124 and 101) so yeah, LinX is good but it's not the be all and end all of system stability.Quote:
Originally Posted by ci2kla
On the POST Issue:
Resetting the CMOS using the switch (Deluxe) or jumper (vanilla) has just worked on a group of six PCs of which at least 4 had exhibited the no POST issue.
Has anyone noticed any changes in cpu temps either more or less with the bios changes i.e. 1053 vs 1253 vs 1204 vs 1302 ? I'm on 1053 and temps avg 75-80 C @ 1.43vlts on load
Was wondering if updating might help temps. By th way 1302 is posted here http://hardforum.com//showthread.php?t=1578865
Any experiences on the UEFI 1302 versus 1204?
Looking for P8P67 Deluxe users :)
No 1600Mhz any longer, the new BIOS is Idling @4.5GHz.Quote:
P8P67 LE UEFI 1003
Change Log -
- Removes full reset at POST (double post) on cold boot or auto overclocking routine.
- Improved OC performance using Auto Overclocking
- Improved BCLK and DRAM OC capabilities when enabling the “Internal PLL Overvoltage” option in BIOS.
- Minor Bug Fixes including Auto Rule for C3, C6 being disabled when overclocking and improved USB compatibility.
- Enabling Internal PLL Voltage will still cause resume/hibernate issues (Intel related) but we are working with Intel on any potential workarounds.
http://img.techpowerup.org/110215/Capture033395.jpg
I didn't touch the C3, C6 or other power managements, but it's using ~32w at Idle now (VS ~9w before), both according to Real-temp. CPU-temp is up a few degrees too, at Idle.
I'm still evaluating this, and may enable those manually, but I don't like the Idle power-usage for now. At least if real-temp is right/accurate. Is it?
Still testing the old OC, but a short Prime-run seams to need same setting/vCore as for 1204.
EDIT:
At least, the C-state can be turned on manually, and the power usage is back to ~7w :)
http://img.techpowerup.org/110215/Capture034639.jpg
I'm still wondering if Real-temp is right/accurate tho. That's a big difference for idle power usage. Anybody knows?
are C3 and C6 enabled ?
Edit;never mind
1302 warning! I've got tow random BSOD, at idle with manual vCore.
One with 4.5GHz and one with 4.2GHz. Both using the same settings as 1 hour Prime-tested on 1204. At least I mean I'm using the same settings, and then I've never had any random BSOD.
EDIT (I ran a 10-min Prime and they both seams to be doing OK at load, tho)
Anybody else can confirm we got a really crappy BIOS?.
Yes my 5.1Ghz settings with 1.416v aren't satble... They used to pass 25LinX runs with [all], now they give error on the 2nd iterationQuote:
Originally Posted by Sam_oslo
After random-BSOD #3 at idle, I've flashed back to 1024. The back-flash has worked fine in EZ-flash, tho.
True I also backflashed again :up: back to 1204
It was mentioned auto c-state behavior was changed when OC'ing. If before the auto state was enabled sounds like now it is disabled.Quote:
Originally Posted by Sam_oslo
It would probably be better to say if Intel was accurate. The reading is taken from the CPU itself but may for instance be based on VID rather than Vcore. It also depends on how good the manufacturers info from the VRM is (i.e. current draw).Quote:
Originally Posted by Sam_oslo
Not that big a difference considering and doesn't seem way off. Try disabling all Windows c-states and you might see ~60W while not doing much at 4.5GHz.Quote:
Originally Posted by Sam_oslo
///1302 WARNING\\\ as well...
Thanks for providing a beta bios which totally f***ed my system.
I updated the bios through EZ-flash as always; after the update my system now hangs on power on with the code "03" on the board, which basically states: "System agent initialization before microcode loading"
Seems kind of serious to me.
I've tried basically everything to fix it, although nothing has worked.
- Reset CMOS with battery, switch on the rear panel
- Power cord out for several minutes
- MemOK! button (this just makes the led mem led blink without anything happening, says in manual it takes aprox. 30 sec. between each test - which clearly didn't happen with me)
- Not even the CRASHfreeBios worked, attempted both USB-pin and MB CD, my CD-ROM is in SATA port 5-6 - spins up correctly and reads the CD, but nothing happens.
Basically sitting with a system, that doesn't work - and just powers up with code "03"
I WOULD NOT recommend updating to this bios, wait for the official 13xx from asus support site.
This sux :(
///WARNING END\\\
Using offset mode and ultra-high LLC, I noticed that my load CPU voltages were basically a notch lower than before. I was running +.03V on the offset (1.195V in AI Suite II) for 1.384V under load. With the 1302 BIOS, I'm now seeing 1.376V under load.
Those of you with borderline stable OCs could probably bump up your CPU voltage by a .005V step.
My failed overclock crashed with wtv voltage... I went from 1.400v-1.416v(stable before)-1.44v and all of them crashed LinX with error on the 2nd run...
Do NOT flash to 1003.
What a mess. Clear CMOS is not working after flashing to 1003, after going back to 1204. Either with or without power cord.
But that's not all, I keep getting Post Code 59 on ALL cold boot. That's RAM-related, but I've tested the same setting with memtest before.
Clear CMOS doesn't do a sh*t. If I keep turning it on and off, then if I'm lucky, sometimes I get a double boot with "failed OC message" and can press F1, and save the same setting and then it will boot.
I don't know how they manged to mess up Clear CMOS, that's the last thing you want to mess with. But the bigger question is, how can another BIOS mess up this one so fundamentally.
EDIT:
I thought maybe EZ-flash had messed up the back-flash, so I've flashed (to 1024) again using BUPDATER, but the problem remains.
Updated 1305 UEFI on First Page
Can you please have better elpida hyper ram support on p8p67 :/ M4E can do it easily
With 1305 Bios, you can now turn OFF Bluetooth.
It has set my RAM to proper timing and voltage as well.
Bluetooth could be also turned off in 1302 version ;)
It wasnt in the release notes and i skipped 1302.
running new 1305,not any different from 1204
This is a feature I'm glad they added!!Quote:
Originally Posted by KGB7
Would it be possible in the next release to add power fan to the fan control and lower the minimum chassis fan % to 20 instead of 40% ?
Any alternative way to Clear CMOS on Deluxe ?
I've flashed to 1305, but still getting Post Code 59 at cold boot, after 1003-mess up. I need to Clear CMOS to reset ME inside PCH to resolve it, otherwise I have to go down to 1333Mhz RAM. But 1033 has messed up Clear CMOS too. :p:
It there any other way, a jumper or something, to Clear CMOS on Deluxe ?
Unplug all the power cords, take out the battery and hold the reset button on the mobo for 30sec.Quote:
Originally Posted by Sam_oslo
Anyone see a jump in temps with the new 1304 bios? I never hit 80c or high 70s with my 24/7 oc settings and now they do in stress tests.
Thx, it worked :)Quote:
Originally Posted by KGB7
It's not the easiest way, but it's good to know it's there.
Post Code 59 is resolved after a Clear CMOS too :) so I guess all 1302-mess up is more or less resolved, somehow.
1305 seams to be working fine here, I've tested with just a little 10-min prime tho.
Temps upped by 3c for meQuote:
Originally Posted by Peter949
okay...i dont like this bios version. i'm constantly booting into windows at 1.42 volts then it goes to my bios inputted 1.38v when stressed. wtf. then randomly jumps to 1.42v when stressing too.
arg...can't flash back to 1204.
Definitely not a happy camper. Idle/load temps is +6-10c now because the boot in voltage now. Stays like that until speed step kicks in.
No way back from 1305 to 1204 ?? Guess I'm not updating since the 1302 fiasco...
Seems with 1305 they not also upgraded the HW version of PRO/EVO.. again but also the Deluxe got an increment so they will no longer be able to easily flash back to older versions.
Does 1305 fix the sleep issue? I tried 1302 on the EVO and that gets as far as turning the fan on when waking from sleep and stops there. Does this even with PLL overvoltage disabled. Currently running 0402.
my opinion is still 1204 is the best so far. Less odd bugs
0402 is the worst by far. I dont even think it was supposed to be released as the first official bios is 0804. My first board came with 0402, bought back in December. A newer board I got came with the 0804 bios, so my guess is that the very first motherboards that went out had the old bios.
What's that saying about "One man's meat is another man's poison" :ROTF:Quote:
Originally Posted by EniGmA1987
Yes, 0402 came with the board but the oldest is on the CDROM disk (0303). 0402 wakes up from sleep, no double boots, hasn't got PLL overvoltage but since my chip doesn't look like making it much past 4.5GHz for 24/7 then not a problem.
Went through a problematic EFI BIOS with the laptop for over the last 2 years. It seems while they fixed some things they would break something else so ended up staying on one of the very early versions. I don't think the UEFI will be as bad as that but seems it's going to take a while to iron everything out.
EDIT: I didn't buy the board that long ago, now I'm wondering if it might be old or returned stock. hmmm. Well I guess it's going to be swapped ~April so np.
Really? 0402 had the worst double boot issue of them all for me and couldn't overclock past 200 MHz
Hoping for lower temps or lower stable voltages on 1305.
Sleep is working fine on Deluxe now, that's with PLL overvoltage disabled tho, I didn't try with enabled.Quote:
Originally Posted by some_one
1305 is working fine on Deluxe. Except Clear CMOS, which is not working after 1302, and flash back to 1024. That may be some kind of HW-problem on my MB too, I'm not sure what's up, but removing battery and pressing reset for 30 sec is doing the trick.
Whenever there is a increment, it's a good idea to have a little warming in release note to let people know they may get in trouble with flash back, tho.
Anyone got Hypers work on these P8P67 boards yet? Still having lot of problems with my g.skill perfect storm, hard times getting these stable @ 2133 CL8, even 1866 CL7 needs +1,70v..
I hope this will be fixed in future bios updates..
remember that this memory is in the asus QVL! 2133 cl8 g.skill perfect storm!
Well I agree 0402 is not perfect but some of the later releases were worse for me. I tried 1305 and initially it doesn't seem too bad so far.Quote:
Originally Posted by EniGmA1987
At the moment trying to decide whether fixed Vcore or offset would be better. With fixed the load line can be used to give higher Vcore with just 1 or 2 cores running (3 or 2 cores idle) and hence use the traditional way of turbo boosting scaled up a few notches. Here's some results with 0402 using 46,46,48,50 staggered turbo ratios. It's a bit higher than I would likely end up running 24/7 with this system.
SuperPi running one thread so ~5.0GHz
http://i1181.photobucket.com/albums/...itanic/Spi.png
Same settings as above running Linx using 4 cores hence 4.6GHz.
http://i1181.photobucket.com/albums/...tanic/Linx.png
The advantage of offset is that Vcore can be reduced a lot while idle but would mean running flat multi's, which isn't so bad really.
You welcome. :up:Quote:
Originally Posted by Sam_oslo
Thanks for the info. Sleep does not work with PLL overvoltage enabled as expected but since it looks like I will not be going over 5GHz thats okay, looks like 1305 is a keeper, for now. :)Quote:
Originally Posted by Sam_oslo
used 1305 but i noticed that my cpu is always @3.8ghz, any idea how to fix this ?
Edit: fixed by enabling CE1
nope still waiting for thisQuote:
Originally Posted by Kimi.Rk
So, I updated the bios on my deluxe to 1305 and now I am having my RAM issues again. If I have my PERC5i RAID card in the x4 slot, the bios never goes past the RAM test, regardless of what I set it too. This is friggin frustrating as heck. I had it working, but now it does not like 4 sticks of ram and that PERC card all installed. Anyone have any ideas? On a side note, it's nice to be able to disable the BT module. Oh, and I almost forgot, I need more voltage to get the same OC. If I put it at 1.44v I get a BSOD with an error code of 0016, at 1.46v I don't get it. This setup is friggin quirky.
Thats why I dont update my bios past 1204. It works great for me post wise and with my RAM, and I am stable at almost the speeds I want on the CPU. Id rather not chance problems elsewhere (like many/most report) to get a few more MHz from my CPU.
Well I updated to 1305 hoping it would fix some random BSOD issues, but I think I am in the same boat if not worse now with 1305.
Im still in 1253 and like you stoned im thinking im going to stick with giga next round. Let's wait and see after the b3 arrivesQuote:
Originally Posted by Utnorris
Still trying 1305, still looks like some improvements could be made but seems to be moving in the right direction. There also seem to be a few horror stories
too with bad flashing. Hope they get to the bottom of it.
Something I found in the 13xx BIOS is that you can take a screenie of your BIOS setup using F12 and a FATTY USB. Has that ever been mentioned? I don't remember reading about it.
Can anyone confirm that the 1305 bios supports the DDR3 2000Mhz step?
Currently I need to set my GT's to 1866 speed.
EDIT: for those of you who have flashed to 1305, and seriously considering switching back, could have a look here
//tentpole
Not on EVO
The lack of 2000MHz memory speed is an IMC limitation not the board.Quote:
Originally Posted by tentp0le
I didn't see any 1155 boards listed, however, I guess this could be an option if you absolutely need to flash back and could not. I wouldn't go this route personally, I would rather the BIOS be fixed or the board, whichever is the issue.Quote:
Originally Posted by tentp0le
http://bios-repair.co.uk/ref/Asus.html -> 11XX-P7-P8 -> 1155 -> There you have listed every Sandy Bridge MB available, from Asus.Quote:
Originally Posted by Utnorris
The new MB from Asus use 8 pin pdip eeprom, and are relatively easy to change. I've already used 1 chip, since the 1305 bugged my board - also have 2 in reserve just in case
Is the Pro BIOS chip located next to SATA6_E12 with the imprinted "MX" name on it? Also, is the BIOS chip from the link above flashed with the English EFI BIOS or is it with the Britsh?Quote:
Originally Posted by tentp0le
He flashes with the latest official bios from your boards manufacturer, or a bios of your choice - if you ask him.Quote:
Originally Posted by jcniest5
Bioschip is located as shown in the picture below - on the deluxe:
http://bildr.no/thumb/830447.jpeg
Ok, so I officially do not like 1305. I have been having weird issues, one of which when I went into the BIOS the first screen had "**********" everywhere there was supposed to be data such as clock speed. Fixed it by unplugging the power, pulling the battery and resetting the bios. On top of that, at default settings, meaning voltages and multi on Auto it will not boot into Windows, I get either a lock up or a BSOD stating it needs more voltage even though the auto sets it at 1.22v vcore. I actually have to manually configure it for my overclock at which point it boots fine. Now some other non-bios related issues:
1 - The front USB 3.0 Module is loose on the board and if I am not careful putting the ram fan on I can knock it loose and it doesn't work. I figured it would snap in, but it does not.
2 - I spent the last day running memtest on my ram thinking I had a bad module, but it looks like Slot 4 is bad. I tested each stick individually in slot 1 and they came back with no errors after 8-10 passes. I then put a stick in each slot and tested one at a time, so one stick in slot 2, tested for 8-10 passes, then slot 3 and then slot 4. All the slots report my CAS settings correctly except for slot 4, so I am thinking I have a bad slot.
3 - I cannot run my PERC5i RAID card in the x4 slot with 4 sticks of memory, however this may have to do with the above issue.
Now, I do not know if issues 2 and 3 are Bios related or HW related. Either way, I cannot wait till Asus starts swapping out the boards. Microcenter has already told me they will swap it out once the new boards come in and I may just go with the Maximus if they get it in. This is the first non-ROG board I have had in a long time and it seems to have a lot of issues. If anyone has any ideas about the above issues please feel free to advise me on a solution.
So 1204 still best all around bios for p8p67 pro?
Yeah, that was one the best, at least for me on Deluxe.Quote:
Originally Posted by melnd
It's a good idea to Keep it there until they fix the bugs out of 13xx.
Yeah, don't upgrade to 1305. Hopefully they will get some of these things worked out. I doubt I will update to another bios that isn't first listed on the Asus site. I don't really have the time to be a guinea pig.
I've random BSOD with 1305, makes me regret upgrading from 1204
I hope they release new one soon :(
My double boot is back with 1305 :(
Any idea where we can get the new Asus Suite listed on the first page? I keep getting timed out do to the slow transfer rates with the link provided.
21.02.2011:Quote:
Originally Posted by Utnorris
ftp://ftp.asus.com.tw/pub/ASUS/misc/...pVistaWin7.zip
Somehow I think 10.0.16 is older than 10.1.14.Quote:
Originally Posted by stasio
No 1305 release for the WS Revolution?
You do not want it. Stick with the current bios, you will be happier.
On a side note, one of my drives in my RAID array is now showing an "Error has Occurred" message. I can still get into Windows, but I am not sure what is happening. I was planning on doing a rebuild tonight anyway, but it makes wonder if the board's SB controller is starting to fail. Hopefully Asus will start shipping next week and I can get a replacement.
Ok, so I fixed the drive error with Intel Matrix storage interface. Just really weird as to why it happened. Also, I have had two instances where my video driver suddenly failed and caused a BSOD. This happened on both my old W7 build and my fresh install. I am going to swap out my Corsair PSU with my Enermax Revolution to see if the PSU is causing the issues. Otherwise I have a very buggy board.
check for win update KB2454826:down:Quote:
Originally Posted by Utnorris
I hope someone can help if it's an easy fix. Hope there's nothing wrong with the CPU or mobo (mobo will get swapped anyways come March/April). I guess if nothing works I'll find out if it is the CPU once the mobo has been swapped.
When I get from multi 41 & up Hyperthreading stops working properly.
Intel Burn Test set to 8 threads only shows 50% of the CPU working (1st and every 2nd thread after that in Task Manager). Same as folding at home set to -smp 8 and this shows in drop of Time per frame that only the Cores are working and not HT.
However the only program I can get to use 100% of the CPU from multi 41 & up is Prime95.
Any help would be awesome as I can get 4.5-4.7GHz stable and would like my 2600K to work properly on the higher multi's.
-Lucus
I'm new on WS Revolution and flash bios 1253 with EZ-flash.
When I'm in windows 7(clean install) and install the intel management drivers and other drivers from the cd and after reboot it won't boot into windows (bsod) needed to repair the OS and restore to a previous point.
I'm I missing something? Do u also need to update the firmware of IME in the bios? (that was needed with my previous mobo (msi p67 gd65) for a newer biosversion.
Great news, waiting impatiently for it :rofl:Quote:
Originally Posted by bingo13
Very bad!! P8P67 pro 1305 bios does not support GTX 570 SLI.Quote:
Originally Posted by danielkza
Maybe you'll get lucky and they'll fix whatever is wrong with this new BIOS.Quote:
Originally Posted by yym789
Is that 1305 the same 1305 from over a week ago? (P8P67 Pro)
Yeah, but (apparently) there will be a third 13xx version (after 1302 and 1305) on the next days.Quote:
Originally Posted by my87csx481
CPU : I7 2600k @ 105.5x46(bios),105.57x46(Real)
Ram : Corsair Dom GT 3x2gb Kit 2000 8-9-8-24 @ 2x2gb 2250 7-10-7-27 1N
1.66v Bios Set (DMM load Read 1.6506v )
M/B : Asus Maximus IV Extreme
BIOS : 1101:up:
PSU : AX1200
http://i287.photobucket.com/albums/l...1/cc7246dc.png
^^ How is BCLK-OCing working for you generally? I've heard rumors, some says it can effect impact the life span and durability of CPU, but I don't know how accurate they are.
I've tried to play with it, but any other BCLK than 100 results in a strange reboot behavior on my Deluxe. It shuts down and waits a couple of seconds before rebooting.
Ure prob is RTL.Quote:
Originally Posted by sam_oslo
BTw bro, if u need help can guide u since DRam clocking on P67's are reproducible on different proc on similar mobo setup
H67, WS, and P67M updates in the first post now.
So still no "official" release again for the Pro?
ha , I fixed my SLI problem.Quote:
Originally Posted by bingo13
I just changed another p8p67 pro MB. SLi is working well right now.
Thanks ASUS.