Winsetup From Usb V2 2 Rarest

Heya.Specs first:Asrock P67 Pro3, bios 1.902500KXai mouseSometimes it takes 1-20 seconds for USB devices to get connected. The Xai problem with legacy USB is also present so I've turned legacy off. Extreme4 seems to have a fix for the Xai problem, any word on future updates for Pro3?Another problem is when using offset mode and overclocking. Let's say I put +0.005V there to get 1.37 vcore under prime/linx load. Under lighter load, like games, it can drop down to 1.24-1.28 V, and sooner or later there's a lock-up due to too low vcore. Because of this I have to use fixed voltage for now.The problem with the disappearing LLC setting needs fixing as well (when auto vcore is not used). Is your system OCd?

1. Winsetup From Usb V2 2 Rarest 3
2. Win Setup From Usb 2.3 Free Download

If not I'd suggest roll back to UEFI 1.9 or try UEFI 2.1E.No overclock, so I'm not sure where those freeze-ups came from. I'm a little hesitant to try the newer or older UEFIs as-for some reason-have had a bad crash that cripples Windows on boot up at the Win logo swirl (right after flashing the UEFI). I've tried clearing the CMOS, etc. Beforehand as advised and no longer use Marvell SATA drivers, but it doesn't seem to make any difference. Reinstalling Windows always clears the error though. Just an observation.with 0.110 i get crackling sound on realtek.Yes, another user had this problem with older drivers.

He found that the Etron controller was causing extremely high latency and the issue was present with several types of sound cards:I may have solved the problem. I had problems with all my audio devices (though only the two creative cards needed reboot), but mostly while playing games:- Realtek onBoard Sound - bad sound / heavy distortions- Asus Xonar DX (PCIe) - bad sound / heavy distortions- nVidia Audio (HDMI) - bad sound / heavy distortions- Creative X-Fi Titanium (PCIe) - bad sound / heavy distortions / sound crash (need reboot)- Creative Audigy 2 ZS (PCI) / bad sound / heavy distortions / system crash (need reset)I found out that I have very high DPC latencys (sometimes 100000 µs) and that the problem is the onboard Etron USB 3.0 controller. I left a game running in the background and deinstalled the Etron drivers while monitoring the DPC latency. The latency fell from red (more than 50% off the values were above 10000µs) to normal green just as the unistaller finished.See this thread, search for Etron:http://www.hardwareheaven.com/pax-drivers/210003-cracking-distortions-sound-crashes.html. In Media Res, i pinpointed down to the 1st USB3 controller.that one asrock advises to connect devices for best performance. No wonder it was the same controller, 1 year back, that gave me from start various problems. the other 2 (1 in case of Extreme4) controllers which are connected thru multiplexer chip, may work with lower performance but do work stable in general.

Also the same one controller is that which from time to time, cant find resources on windows (check pix)disabling 1 by 1 and checking) i found that just disabling it and reboot, resulted in much much better performance.noticed some correlation in dpc latency spikes, when i had enabled from realtek control panel the noise cancelation option in mic settings, with that enabled, it could pop (not so often) 1 '14k' spike, with it disabled, it was more stable. Been bored the past few days so I've been trying to overclock my setup beyond the 4.2ghz on all auto settings that I have been running to this point.Radier,I have seen your posts from earlier in this thread and my question is what bios settings are you currently running for your 5ghz OC? Are they the same from your posts earlier? If I remember correctly you recommend the following:Turbo power limits:255255300VTT:.986VCCSA:.925CPU PLL: 1.709Are you still leaving the C states to all enabled? @GripsMy settings: thanks. That is one nice chip you have.

I can't even get into windows with your settings. I've managed 4.5ghz prime95 stable so far with stock voltage and using your turbo limit settings.

Winsetup From Usb V2 2 Rarest 3

They definitely helped as 4.5ghz fails prime95 without manually setting short and long durations.edit: Now running 4 hours so far at 4.6ghz stock voltage. You would think I should at least be able to get into Windows at 5ghz since I am not adding any extra for 4.6.

Had a quick search but couldn't find much discussion about the xfast LAN or xfast Ram utilities. Are people actually using these? They appear to offer some nice benefits. However I've a few questions in case anyone has dug past the initial marketing blurb.On the XFAST RAM utility it seems too good to be true.

I've toyed with Ramdisk a few times and dropped it (considered fancycache but not tired). Mainly due to the time it added to boot up and shut down when reinstalling the backup imagine. But this Asrock utility has negligible to zero impact on these times. Also RAMDISK stuck a RAMDISK imagine size file on my SSD at shutdown (3GB!) - which I wasn't too crazy about! I can't seems to find the back up file for the Asrock utility (I suspect it's doing the right thing and compressing the data which after all should be quite small). (I have 12 gb of RAM so using a 3gb of RAM drive seems like a decent compromise as I have the page file/temp files and browser caches all there - mainly to save writes on the system SSD but also eek out some more performance - like I need it!)Also the Xfast LAN seems to be in calibration mode forever.

But I like it. Don't know why yet.Can anyone shed any light? I'm not using any of the ASRock 'extras.' Personally, I treat them like I treat all bloatware. Anything that tinkers with Windows to improve boot or internet speed = marketing hax. From what I've read, I'm not the only one who feels this way.

All I want are the bare-bones, unadulterated drivers for the 'Keep It Simple, Stupid' benefits.Edit: I could wish that manufacturers would instead spend that time on the drivers themselves; I think they have a tendency to underestimate just how critical they are to the overall stability and efficiency of a system. In ASRock's favor, they do seem to be updating their drivers pretty frequently-my hat's off to them for that!

I know marketing would never agree, but IMO fewer mobo models = more time/resources for QA = better hardware and drivers. I think its generally a good cut about bloatware - but you don't use it which is your choice. (I've had one of these boards well over a year and only just getting round to toying with it.)This isn't a one time deal with Asrock.

This software is being pushed on all their current boards (incl the x79). As I say it compares well under initial comparisons to Ramdisk (which has a proven application uses).Software driven 'tweaks' is one of the few areas left to motherboard manufactures to add performance. Especially when Haswell lands and totally cuts motherboard hardware out of the performance picture. Thanks for the heads-up!On a slightly different note, has anyone else run into the odd situation of only one of the Extreme4's front USB 3.0 ports responding to devices (even with this latest set of drivers?)I had a similar issue when testing drivers, use the 101 Etron drivers when in doubt.

Thus far in my tests they are deffinately the 'go to' driver.Yes, another user had this problem with older drivers. He found that the Etron controller was causing extremely high latency and the issue was present with several types of sound cards:See this thread, search for Etron:him to use the Etron 101 drivers to see if he has the same problem.this is with 0.111 driver. No difference at all, if i disable the upper back usb (the best performance according to asrock.) the dpc has way lower latency. (the 'spikes' are rare and up to 900-1000μs)hell thats bad. I've been trying to diagnose this problem for weeks without much joy. Have you tried the Etron 101 driver? Theres a reason why I keep telling people to use it;)I'm not using any of the ASRock 'extras.'

Personally, I treat them like I treat all bloatware. Anything that tinkers with Windows to improve boot or internet speed = marketing hax. From what I've read, I'm not the only one who feels this way.

All I want are the bare-bones, unadulterated drivers for the 'Keep It Simple, Stupid' benefits.Edit: I could wish that manufacturers would instead spend that time on the drivers themselves; I think they have a tendency to underestimate just how critical they are to the overall stability and efficiency of a system. In ASRock's favor, they do seem to be updating their drivers pretty frequently-my hat's off to them for that! I know marketing would never agree, but IMO fewer mobo models = more time/resources for QA = better hardware and drivers.I agree. Simple straightforward reliable drivers is all that anyone wants, although this MAGIX thing Asrock has going is very nice.BTW, I'm back people:D At least for now. Not a big deal (and yes, I know it's only during boot or when browsing the UEFI), but some time ago I noticed that the P67 Extreme4 (B3) UEFI splash screen does not properly detect and fill the available screen space on HD (1920 x 1080) monitors on boot, leaving a black border between the splash screen and available, full monitor screen resolution.

Here's a snapshot of what I mean:occurs on two solid-rated HD monitors: a 23' Acer G235HAbd and a 23.6' ASUS VE247H.ASRock tech support explained it to me as: 'Some model of HD monitors do not support the high BIOS resolution; therefore your screen is not completed fill the areas.' I'm curious if anyone actually has a monitor capable of properly displaying the UEFI at full resolution like they claim? Not a big deal (and yes, I know it's only during boot or when browsing the UEFI), but some time ago I noticed that the P67 Extreme4 (B3) UEFI splash screen does not properly detect and fill the available screen space on HD (1920 x 1080) monitors on boot, leaving a black border between the splash screen and available, full monitor screen resolution. Here's a snapshot of what I mean:occurs on two solid-rated HD monitors: a 23' Acer G235HAbd and a 23.6' ASUS VE247H.ASRock tech support explained it to me as: 'Some model of HD monitors do not support the high BIOS resolution; therefore your screen is not completed fill the areas.' I'm curious if anyone actually has a monitor capable of properly displaying the UEFI at full resolution like they claim?Mine shows it full screen. I'm only running a 22' LG 227WTG at 1680x1050. Honestly.it's a bios screen.

As long as you can clearly see it I don't think it's worth trying to fix. The P67 chipset is unfortunately considered old at this point so don't plan on a bios update correcting it. I believe we have the last updates for this board at this point. Aside from Etron USB 3.0 that is.:).

Win Setup From Usb 2.3 Free Download

Not a big deal (and yes, I know it's only during boot or when browsing the UEFI), but some time ago I noticed that the P67 Extreme4 (B3) UEFI splash screen does not properly detect and fill the available screen space on HD (1920 x 1080) monitors on boot, leaving a black border between the splash screen and available, full monitor screen resolution. Here's a snapshot of what I mean:occurs on two solid-rated HD monitors: a 23' Acer G235HAbd and a 23.6' ASUS VE247H.ASRock tech support explained it to me as: 'Some model of HD monitors do not support the high BIOS resolution; therefore your screen is not completed fill the areas.' I'm curious if anyone actually has a monitor capable of properly displaying the UEFI at full resolution like they claim?To elaborate on what Asrock tech support meant its a simple case of some monitors have weird seperate skewed resolution settings until they hit the login screen where the monitor switches to its native resolution. You can usually fix the issue by simply pausing the boot process at the splash screen and adjusting the height and width options on your monitor settings until the splash screen completely fills the screen.Oh, and in terms of age of the chipset, while the P67 can't be considered new anymore theres still not a lot of differences between the P67 and Z77;) The biggest are no PCI-E 3.0 or ability to use the on-die IGPU. Those really are the only major differences. Technically there isn't even any reason whay any P67 mobo can't have a UEFI update letting it support IB CPUs, you just won't get the PCI-E 3.0.

Intel as they are though will probably forbid any such UEFI update so people have to buy a Z77. To elaborate on what Asrock tech support meant its a simple case of some monitors have weird separate skewed resolution settings until they hit the login screen where the monitor switches to its native resolution. You can usually fix the issue by simply pausing the boot process at the splash screen and adjusting the height and width options on your monitor settings until the splash screen completely fills the screen.unless you have a monitor that doesn't (for some obscure reason) disable your screen height and width options.:).ahem. Note to self: stop buying cheap monitors!

Thanks for the clarification on this! +1Oh, and in terms of age of the chipset, while the P67 can't be considered new anymore there's still not a lot of differences between the P67 and Z77 The biggest are no PCI-E 3.0 or ability to use the on-die IGPU. Those really are the only major differences. Technically there isn't even any reason why any P67 mobo can't have a UEFI update letting it support IB CPUs, you just won't get the PCI-E 3.0. Intel as they are though will probably forbid any such UEFI update so people have to buy a Z77.That wouldn't surprise me about Intel; but not a problem anyway, since it seems like the best time to do a system refresh is 2-3 years after the release of your current mobo when technology again offers the biggest bang for your buck. Good to see Intel aren't forbidding UEFI updates to support their new CPUs for a change.

I have a sneaky feeling Intel are allowing it because they know first batch retail IBs are iffy and they want as many sales as possible though.Good news indeed-though us original Extreme4 owners lack the next-gen PCI-E 3.0 support that the Gen3 mobo has.? So I shut down, turn off electricity, remove battery for a while, reset jumper to clear, replace battery, power on, power off, reset jumper to save, power on?Power off.Disconnect power chord.Move jumper to clear position (or press CMOS clear button on back of PC).Move jumper back to original position.Plug in power.Power on and enter UEFI. Load Optimized defaults.

RebootEnter UEFI again and see if you can increase multiplier.I would not advise flashing a beta bios in the future especially if it is a feature that does not apply to you (adding IVY support).edit: I should read better. You already tried the button so ignore that and use the jumper. You can also pull the CMOS battery for good measure. Wait 5 minutes. Put everything back in and fire it up.

You might also try to re-flash 2.00 or 2.10 again if that doesn't work. Ket, is ASRock still accepting feedback regarding the Etron USB 3.0 drivers? If so, I have had intermittent hangs when trying to access my Hitachi Touro Mobile Pro USB 3.0 External HDD (plugged into my E4's rear USB 3.0 port). I'm using the latest 1.0.0.111 drivers. (I know you recommended the.101 drivers, but I neglected to keep a copy of them-they're not in your RapidShare DL archive or on the ASRock drivers page.)I must admit that from some of the threads on the web I've read, there's some question as to whether these bugs are primarily caused by bad drivers, or if there isn't a hardware bug in the Etron chip itself? I must admit that from some of the threads on the web I've read, there's some question as to whether these bugs are primarily caused by bad drivers, or if there isn't a hardware bug in the Etron chip itself?I tend to believe, that there is a hardware design flaw. Our EJ168A chip is already history.

Etron has already released two new controllers, EJ188 and EJ198. See this:Etron debuts new usb 3.0 host and device ics (have checked the Asrock site, there are no more new products with the old chip EJ168A, and even the new Etron chips are appearing in only very few new motherboards.I have recently installed the 0.111 driver, but the same:banana::banana::banana::banana: happens: rear Etron ports don't work and when plugging in external HDD's, the system stops responding and reset is required. So not only bad design, but some chips are wearing out too early. I think some motherboards even come with already dead Etron chips which means that bad chips are not removed from production, but they are sold to customers.Intel at least had the decency to admit the flaw in the SATA2 controller.

I don't think Etron will ever admit the flaw. Already got one of this (and i finally have usb3 that WORKS.

Without massive dpc latency and f#$@$king my sound. When gaming and skype for example.The additional PCI-E card with USB 3.0 ports is not a real solution. If you want to sell your motherboard in the future, what will you explain: 'there is a broken USB 3.0 port, but I'm giving you an additional PCI-E card?' I think we should add to the first post of this thread, that some users have issues with the Etron USB 3.0 controllers, so that no more people gets disappointed by Asrock and Etron.For the other users: yes, I know that for some users the Etron ports work correctly, you had good luck and have got a 'perfect' Etron chip, but many other users have got the faulty chips. Also, if it works correctly with specific devices, don't be sure that it will work with any other USB 3.0 or USB 2.0 devices.I am adding here my list of links with unhappy users.

I will update this list with new links. Some of the issues have been resolved but most of them are still unresolved.See these forums:ASRock and Etron USB 3.0 BSOD - How bad is it really?BSOD on new build!! HELP!BSODs on Windows 7 Ultimate 64-bitBuild on Win 7 x64, Multiple different BSODUSB 3.0blue screens helpon a new RigBSODs within few minutes of startupBSOD on wake up from sleepBSOD everytime after sleeping.a few minutes after wake from sleepall over the placejust had a BSOD lol. When i plugged something into the USB 3.0 slot on the caseErocker is there a driver i need for the USB 3.0?? Because everytime i select the playback on TS as my USB mic it BSODOkay apparently there is. Etron USB 3.0 DriverWait i already have it installed.

WtfIm going to have to change the USB 3.0 to a USB 2.0. Etron seems to causing issues for a lot of people. BSOD all over the placeWorkstation 8.0 Blue Screenscreen at shutdownGiven Up And Disabled My USB 3.0 controllers.get random BSOD's with it pointing to 'ETRONXHCI.sys' - I've looked it up and it's my 3.0 controller drivers.I downloaded them from Etron and they were outdated after checking the mobo site. I downloaded the drivers from the mobo site and it persisted.Drivers are current.I don't actually have any peripherals capable of taking advantage of 3.0 anyways, but i mean still - now I have 3 dead ports.What else can I do to trouble shoot my problem. I just disabled the controllers and am sure that that will stop my BSOD's.Tried googling, found someone with the same issue but with an ASRock mobo.Anyone got any suggestions? Otherwise computer's been fantastic and stable as ever.Random BSOD Driving me crazy!Sandybridge Build BSODs!! @radier thanks:),installation was successful (P67 Fatal1ty)no problems with missing dividers etc, migrated my settings correctly, and at last i got rid of Jonathan's face starring at me:p (no offense Fatal1ty).

I do have a problem right now with error when trying to install Intel MEI 8, but i hope i'll find a solution soon.edit: the problem was with embedded vcredist file in MEI from asrock's site, solution was to copy the entire folder from temp, replace both vcredist files with working ones from newer MEI from station-drivers, and installed ok.1 MAJOR bug i found in new UEFI (and i want Extreme4/6 users to check) is that if you disable the USB3 in uefi, you also disable the upper pci-e 1x slot.:( (the slot i use for nec usb3 controller.), if you enable it, it works, ok. I suspect this will be an easy fix., but if possible, etxreme4/6 users with updated uefi to ivy versions, try to disable usb3 in uefi and check if upper pci-e 1x slot works. As these 3 motherboards are quite similar -and share similar uefi code- i suspect they will have the same bug. Fatality professional, with the same plx switch as extreme 4/6. According to an old schematic, the Pcie 1x slots are directly connected to p67, without multiplexer except from 4x slot which is connected with quick switch to bottom 1x slot (when both populated, the 4x drops to 2x)Thanks anyway:)Sent from my U8800 using Tapatalkupdate: speaking only for the 'goodness' of this UEFI, i see nice improvement in memory compatibility (with 2.00 i couldnt even post with 1T with my gskill ares, now, boots fine, along with a small improvement in aida latency bench) and a slight higher bclk (before the need to adjust vtt).

1 MAJOR bug i found in new UEFI (and i want Extreme4/6 users to check) is that if you disable the USB3 in uefi, you also disable the upper pci-e 1x slot.:( (the slot i use for nec usb3 controller.), if you enable it, it works, ok. I suspect this will be an easy fix., but if possible, etxreme4/6 users with updated uefi to ivy versions, try to disable usb3 in uefi and check if upper pci-e 1x slot works. As these 3 motherboards are quite similar -and share similar uefi code- i suspect they will have the same bug.Kudos to Asrock, for such a great support:)I contacted the support, yesterday evening describing my problem, and today in my mailbox i found a new bios (L3.12 - Bios date 15/5/2012) which solved the issue!!!!Thanks again Asrock.

Hi, hope someone out there can help. I updated to the new uefi bios on my p67, and now I cannot overclock. In the bios I set the multi to 46, but as soon as I click to change something else, it defaults to 37 which is the highest it will allow for. It does this for any value I try and change.

Also now, it only detects 8 gig of the 12 gig that I have. I tried reverting back to an older bios but it will not let me. I have tried the full cmos clear, and no luck. Please help.Also to add, it only gives me the option to run the ram at 1066 or 1333. Just found another thread where some other people are having the same issue. Sounds like I need to replace the bios chip. Any recommendations of where to get one?

Hi, hope someone out there can help. I updated to the new uefi bios on my p67, and now I cannot overclock. In the bios I set the multi to 46, but as soon as I click to change something else, it defaults to 37 which is the highest it will allow for.

It does this for any value I try and change. Also now, it only detects 8 gig of the 12 gig that I have. I tried reverting back to an older bios but it will not let me. I have tried the full cmos clear, and no luck.

Please help.Also to add, it only gives me the option to run the ram at 1066 or 1333. Just found another thread where some other people are having the same issue. Sounds like I need to replace the bios chip. Any recommendations of where to get one? Ebay?????Your board should have a 2 year warranty on it. I would suggest an RMA. I would, but I can't go without a computer while waiting for the replacement.

Anyone else have any suggestions?Have you seen papatsonis post on pctreiber.net?I wanted to 'burn' a bit my sb this weekend and just now i realized that i had a max applicable multi of 48. Even if i use 50x for example. The small boot info says 5000 but. The reality is that in windows.

I get only 48x.One may comment that '48x is fine. You won't work the cpu everyday at 4800' and might be correct as i use it default all the time. BUT when I WANT to o/c it to bench. I want it to work. As it should:pany other user with P67 Extreme4/6, Fatal1ty Prof/Perf to notice this?update: it seems as a very strange issue, i started with all power saving options, enabled at 1st.

And booted correctly, disabled them 1 at a time and boot, and finally booted correctly with all these disabled(like my 1st attempts) and with higher multi than 48.If nothing helps, maybe you can order a new chip from Asrock.(In case of Asus motherboards I know that it is possible to order BIOS chips, perhaps Asrock does the same.). Hi, guys I have a pretty annoying issue on P67 Extreme4 B3 after flashed with 3.10. Mobo was with 1.60 uefi and exept inability sometimes to boot my HDD, and little higher vcore needed for oc, I had no problems. Exactly becasue those two, I decided to flash the new bios (and to see if higher clock is possible of course). And the problem started immediately. PC hangs all the time for a minute or so, on the logo screen.

Then for another on a black screen with the blinking dash prior to load windows. I couldn't even reenter my OC back, it will took me all week just to restart several times. And apart from that, such behaviour is not normal. So, I flashed to L3.04 - the same again. Can't flash with 3.12, because the uefi utility can't see the file.

Reverted back to 1.60, then 1.62 and 2.10. Everything is fine, exept the error with 'HECI pointer mismatch' and the other 'error! System cannot get fw version!' , but anything else is fine, booting fast, like before. And also, by mine observations the new uefi 3.XX shows incorect frequency and voltage values. I sent all the info to Asrock before 3-4 days, they didn't responded yet, so Im asking here if someone has expirienced similar things. And is it possible to remove the error when rolling back to earlier uefi versions?P.S.

When hanging occur the mobo display shows code 64. Also the CPU is 2500k.

OK, here is what I did. Flashed uefi 2.10 (1.60 is removed from the 1st post), with turnig off, unpluging, clearing cmos, etc. As I always do.

Then, powered on and loaded the default settings. Flashed to 3.10 with the win setup, the clearing procedure again, loading defaults. And still the same hangs with code 64 45secs on the logo and another 20 with blinking dash. So, of course I rolled back to 2.1, where despite the errors I recive no hangs and such sh.ts. Also in 3.10 the XMP profile is incorect (I saw someone mention that here). Any ideas, what could interfere (if any), so there are hangs in post with v.3.XX?

Missing something? And why I can't see the v.3.12 in uefi flash utility from radier's link? Asrock didn't responded for 1 week yet. Yep, I flashed with dos version of 2.1. And, what kind of hardware, when Im rendering with that system - CPU and GPU both, which means max load, memory too (12GB). But my clock/system never have/had any problems since it passed the last tests year and so ago (24/7 usage since then). CPU is at default right now, first time since I boughted when it came out.

So, I don't suspect for any problems, exept the recent - uefi related ones. The situation right now is fast loading system with no problems. The only problem is the HECI error, which make the mouse unusable in uefi.

So I think the 3.XX uefis are those with problems for some systems. I have 1 HDD and no CD/DVD. 1 classic Compaq PS/2 keyboard and MX518 USB mice. 'll try to disconnect the mouse and I have 1 wireless dongle, will disconnect it too and see. Isn't the HECI error about wrong version of MEI on the uefi rom?

The error is with 1.XX and 2.XX versions, which otherwise are working flawlessly (exept the mentioned in my case already). The error is not present on 3.XX, but I have mandatory hangs on it, and there are wrong XMP profiles -which doesn't bother me, but there are wrong value readings as well (IMHO). Furthermore, I think Asrock can't be unaware of that, they definately know for the HECI error, after rollbacks to earlier uefis.

Probably they don't know how to fix it yet, or don't want to. That's why they don't responded on my problem. And the hangs in 3.XX are (I think) random Incompatibilities with some mobos, pending to be cleared (hopefully) in the next versions.-New developments:First on the advice of unplugging anything to check if the issue with hanging with 3.XX will disapear. There is only the mouse and a wi-fi dongle. I unplugged them. So, I abandon the 3.XX until those problems are figured out.The interesting is the development in the problem with the two errors 'error! System cannot get fw version!'

And 'heci pointer mismatch' ater the rollback from 3 to earlier. In the meantime of the fore-mentioned experiments I was with V.2.1, and decided to manualy downgrade the Intel management engine interface driver in windows, just to see what will happen.

I was with 7.1.40.1161, which I downgraded from 8.0 earlier. Deleted the old one and Windows installed automatically ver.

Then I flashed uefi to v.2.1H - I already tryed that version, but now just decided to stay with it for now. Restarted, the system turned off, turned on, posted, shuted down again, posted again and after the post screen updated the ME on the rom chip, restarted again. No more errors with 2.XX uefi. I can't repeat the exact procedure, but obviously it is possible to rollback between 1.xx, 2.xx and 3.xx without errors. After loading windows I noticed, the ME driver version is updated to 7.0.0.1118. Now I have completely normal post and OS loading without any errors.

Just a small glich:) - the mouse directions in uefi are turned upside-down, but don't care. Now Im clocking back. I have 1 HDD and no CD/DVD. 1 classic Compaq PS/2 keyboard and MX518 USB mice. 'll try to disconnect the mouse and I have 1 wireless dongle, will disconnect it too and see. Isn't the HECI error about wrong version of MEI on the uefi rom? The error is with 1.XX and 2.XX versions, which otherwise are working flawlessly (exept the mentioned in my case already).

The error is not present on 3.XX, but I have mandatory hangs on it, and there are wrong XMP profiles -which doesn't bother me, but there are wrong value readings as well (IMHO). Furthermore, I think Asrock can't be unaware of that, they definately know for the HECI error, after rollbacks to earlier uefis. Probably they don't know how to fix it yet, or don't want to. That's why they don't responded on my problem. And the hangs in 3.XX are (I think) random Incompatibilities with some mobos, pending to be cleared (hopefully) in the next versions.-New developments:First on the advice of unplugging anything to check if the issue with hanging with 3.XX will disapear. There is only the mouse and a wi-fi dongle. I unplugged them.

So, I abandon the 3.XX until those problems are figured out.The interesting is the development in the problem with the two errors 'error! System cannot get fw version!'

And 'heci pointer mismatch' ater the rollback from 3 to earlier. In the meantime of the fore-mentioned experiments I was with V.2.1, and decided to manualy downgrade the Intel management engine interface driver in windows, just to see what will happen.

I was with 7.1.40.1161, which I downgraded from 8.0 earlier. Deleted the old one and Windows installed automatically ver. Then I flashed uefi to v.2.1H - I already tryed that version, but now just decided to stay with it for now. Restarted, the system turned off, turned on, posted, shuted down again, posted again and after the post screen updated the ME on the rom chip, restarted again.

No more errors with 2.XX uefi. I can't repeat the exact procedure, but obviously it is possible to rollback between 1.xx, 2.xx and 3.xx without errors. After loading windows I noticed, the ME driver version is updated to 7.0.0.1118. Now I have completely normal post and OS loading without any errors. Just a small glich:) - the mouse directions in uefi are turned upside-down, but don't care. Now Im clocking back.Hey FTA7700, I was having the exact same problems as you after flashing to 3.04 or whatever it was. My previous posts are above.

I had those issues, in addition, I was not able to overclock with a multi higher than 37, and the ram options were only 1066/1333. I also had the errors you had after trying to downgrade (which you are told not to). I tried everything, and nothing would get my system to recognize more than 8 gig of ram, or allow for high overclocks. I resolved my issue by purchasing a new bios chip with 2.0 preflashed onto it.

It cost me about $16 on ebay. It just arrived, and took 2 seconds to install, and now everything is good. Overclocked, and ram is running as it should be. Hope this helps. So, obviously the 3.XX are problematic in some cases.

Although, my problems was with hangs (something like timeouts) with constant duration. Of course, as I mentioned I saw strange readings and fluctuations in frequencies and voltages and wrong XMP. The multiplier selector was fine by my opinion. But, in the memory settings for frequency one could see numbers like 1336mhz, 1674mhz and such nonsence.

The thing with the new bios chip is good idea. But as I wrote, my problem is solved I have no error messages anymore. The real problem is Asrock are silent as a fish about that, and official way of rolling back to earlier uefis.

Thanks for posting. New developments:First on the advice of unplugging anything to check if the issue with hanging with 3.XX will disapear. There is only the mouse and a wi-fi dongle. I unplugged them. So, I abandon the 3.XX until those problems are figured out.The interesting is the development in the problem with the two errors 'error!

System cannot get fw version!' And 'heci pointer mismatch' ater the rollback from 3 to earlier. In the meantime of the fore-mentioned experiments I was with V.2.1, and decided to manualy downgrade the Intel management engine interface driver in windows, just to see what will happen.

I was with 7.1.40.1161, which I downgraded from 8.0 earlier. Deleted the old one and Windows installed automatically ver. Then I flashed uefi to v.2.1H - I already tryed that version, but now just decided to stay with it for now. Restarted, the system turned off, turned on, posted, shuted down again, posted again and after the post screen updated the ME on the rom chip, restarted again.

No more errors with 2.XX uefi. I can't repeat the exact procedure, but obviously it is possible to rollback between 1.xx, 2.xx and 3.xx without errors. After loading windows I noticed, the ME driver version is updated to 7.0.0.1118. Now I have completely normal post and OS loading without any errors. Just a small glich:) - the mouse directions in uefi are turned upside-down, but don't care. Now Im clocking back.Thats why I suggested flasing the UEFI from pure DOS with the first release UEFI;) Doing that will 'kick' the flash process into downgrading the MEI (or it should do as from pure DOS a complete ROM erase-rewrite happens) so when you then upgrade to the latest UEFI the MEI should also be updated properly.:up: Cases like this are why I keep prodding Asrock to have a backup ROM chip, but thus far its not happened so its always a good idea to have a spare ROM chip handy to just switch to.

I'm using beta UEFI 2.02 on the Z68 I have, absolutely no issues. Haven't had chance to try the beta UEFI for the P67 yet as its not set up atm. Also, if anyone couldn't flash to the UEFI via instant flash because it wasn't recognised, just change the flie extension to.rom or.bin.

I had to do that a couple of times way back when I was testing the P67.P67 Pro3 UEFI 1.90 here, I'm trying to flash to 2.02c with Instant Flash. I can't get it to recognize my UEFI file at all. I have it in my c: root and on an USB stick, I also tried renaming both to extension.rom and.bin.

All I get is 'no image file detected'.If I can't get it to work, where would I want the latest DOS flasher? Hello guys, i need some help with the performance of my new brand SSD, i will details the things that i already do.1 - Set on BIOS, AHCI Mode to the intel controller.2 - I verify on windows device manager if the driver loads ok and its ok.3 - TRIM are enabled.Now i gonna to reinstall the SO and remove the OC that i set on my 2500k and Extreme6 to see if this things are affecting to my ssd perfomance:(.(somebody help me? Have you looked for reviews of the SSD you have to compare read/write performance? It'll help give a clearer picture of things at least.

If you aren't already, also make sure you are using the latest UEFI for the Extreme6 and make sure all your drivers are up to date.I already look for pictures of benchs on my ssd and thats the reason i discover my ssd get something wrong. Im using the 2.1 bios version of my p67 extreme 6 mother.Thanks anyway, y already figured out, it seems like the ssd came with a 512k of allocation size, and when i install the os on it i forgot to format to the default allocation size, now i do that and all the numbers of all benchs change for best.The SSD seems fine to me, what problem do you think you have?In a few moments i gonna post a picture of atto with the numbers that i getting righ now after a format and reinstall all.@Tapa2&S2. So I have been following the thread for a while (I have an P67 Extreme4 Gen3) due to constant USB3.0 issues.

Nothing I did would work. I upgraded to latest BIOS v2.20 and my front header stopped working in 3.0 all together (would only work with 2.0 devices).

So I emailed ASRock and told them my delema. They emailed back and told me they would send me a BIOS chip with version 1.0 on it. It arrived yesterday so I plugged it in, powered up and guess what, it's version 2.20.

I was pissed, for a minute. Set the BIOS up the way I like it, wiped my drive and installed windows 7 64-bit. Installed etron drivers version.109 and all is well. All of my USB3.0 ports work perfectly including the front header. I don't know what gives, but all is well now. Maybe there is a corruption in the 2.2 they have on their website?

I don't know, I just know everything is currently working fine.My story and my first post, I think! ETRON EJ168/EJ188/EJ198 USB 3.0 Controller 1.00.0000.0113might be too early to 'celebrate' but my 1st impression is with these drivers and Legacy mode disabled on uefi, ALL my 6 usb3 ports work ok!!!!

After 1 year. With acceptable dpc latency, and no crakles (till now) on sound.Thanks!!!!update: during gameplay (BF3) + voice, i saw on dpc latency spikes up to 2134μs, twice as big as with NEC usb3 controller i had measured, but still acceptable. (i mean without noticeable pop and crakles on sound). I can well imagine manufacturers who chose to use the EJ168 are more than a little pissed at all the issues so its no real surprise a Etron driver appears in double-quick time when a issue is reported.

Funny enough, that 1.113 driver came out 2-3 days after me telling my Asrock contacts about the Xonar issues when its plugged into PCIE1 and a Turtlebeach headphone issue. Coincidence?:p:That should stand correct IF ONLY. That issue with EJ168 had appeared a week ago. The FACT is that issues exist SINCE march 2011 i bought this m/b. So it wasn't so 'double quick'.;)What exact issues the xonar has.? Apart from the bug (fixed via uefi update- i had kudos them in this thread) with upper pci-e 1x slot being disabled affecting all cards, (and saw that most P67 m/b had this issue with initial ivy bridge support uefi), mine works fine, in all slots.

I never had any issues with the Xonar in th top PCIE slot, although on the Z68 and Z77 boards if the Xonar is plugged into the top PCIE slot sometimes when the system boots you'll get VERY fuzzy audio and other times no audio at all. The solutions are to either simply restart the system or switch the Xonar to a different PCIE slot.

The issue is being looked into so hopefully there will be a fix soon. By double quick time, I meant how Etron seem to release a new driver every few months, or in some cases days after issues are reported to them. Sadly all I and my contacts can do is tell Etron what problems there are and how to reproduce the issue, its up to Etron themselves to come up with a fix and release a new driver. I have an ASRock P67 Extreme4 Gen3 that I haven't updated the BIOS since I purchased it. I have an ASRock P67 Extreme4 Gen3 that I haven't updated the BIOS since I purchased it.