Asrock P67 Extreme4 UEFI & Drivers thread [Extreme6 & Pro3 owners welcome]

[paschov]

I find it weird that you didnt know how to do a full cmos reset but yet your moving things around inside the case like you know whats going on.. Stop to think maybe you dont kno whats going on and you shouldnt mess with things you dont know what they do

Before giving lecture to the people you don't know, you must learn to read attentively. The person who don't know how to do a full reset is "pythonse", not me. I built dozens of systems AMD and Intel alike, and perfectly know how to move things around. Most of the systems were overclocked and all overclocked were rock stable except the Sandy Bridge system. And I am still convinced that it's totally unfinished product, CPU and chipset alike. Intel pushed too hard to get it on the market before AMD Bulldozer. ASRock guys are doing their best, thank you guys, but they cannot jump above their heads. Again I built dozens of systems, but never ever any system gave me such a lot of headaches as Sandy Bridge, and I can see from the posts that I'm not alone, by far. Exchanging MB for B3 was a huge mistake, B2 was way more stable.

[paschov]

I am experiencing the exact same issue. I thought it was from running my ram at the rated speed of 2133. People on the forum suggested to downclock the memory to 1600. I tried it, and I was able to run @ 4.8, ran IBT, no issues, played games no problem. I thought I had the problem solved. Turned off the computer, turned it on the next morning, and got the blinking cursor. I went out and got another board, and cpu (which happened to have the same batch number as the one I was currently using), and tried to narrow it down, but whatever combination I used, it did the same thing. Also, like you, the 43 multi is the only stable setting I can get. Anything over 43 requires PLL Enabled, just to get into windows. None of the preset overclocks will work past 4.2. From my experimenting, I think that it's just a bad batch of cpu's from intel. Not saying they are faulty cuz they work fine at stock, just not very good overclockers. What batch number is your processor?

Batch# L040B705. But on B2 MB it was very stable on 48. The weird things started when I exchanged it for B3, stupid me

[mean6]

Have you tried disconnecting your SATA devices and trying a standard HDD? Just trying to narrow down the root cause of the problem

Well Ket, I tried what you suggested, and still same issues when oc. past 4.3. I overclocked it to 4.8 (and a couple multis inbetween) and ran 20 passes of IBT, no problems. Shut it down, came back 5 mins later, turned it on, and got the double boot, and the blinking cursor. I restarted the computer, and held delete button down to enter into the bios, left settings unchanged, and exited, and the computer booted straight into windows. Ran IBT again, and passed. I am at a loss here.

[Ket]

Can you run 48x without PLL overvoltage? What about if you enable spread spectrum?

[mean6]

This cpu will not run any multi over 43 without having PLL enabled no matter how much voltage you throw at it. I tried both auto and disabled for Spread Spectrum, and it doesn't make a difference. I think it is just a case of being a poor overclocking chip, which sucks cuz I have 2 off them. I tried to return the newest one, but the vendor will not return open box processors.

[Ket]

Can you post some screens of your UEFI settings? Maybe something is slightly sqewed.

[mean6]

Which is the best way to do that, I don't see the option in the bios anymore?

[paschov]

Which is the best way to do that, I don't see the option in the bios anymore?

Plug in USB flash stick, keep it there and hit F12 when in UEFI.

[mean6]

Here's some screens,

[Ket]

Try setting your LLC to level 2 and try using 8-10-8 mem timings.

[mean6]

Try setting your LLC to level 2 and try using 8-10-8 mem timings.

LLC on level 2 gave me a TRIPLE boot, and blinking cursor. Loosening the timings didn't change a thing. Boots fine from bios, but cold boot gives the blinking cursor. Any more ideas? I am pretty convinced it's just a crappy cpu.

[Ket]

Yeah I'm out of ideas for that chip. Deffo seems like its a weak one

[Nw0rb]

Before giving lecture to the people you don't know, you must learn to read attentively. The person who don't know how to do a full reset is "pythonse", not me. I built dozens of systems AMD and Intel alike, and perfectly know how to move things around. Most of the systems were overclocked and all overclocked were rock stable except the Sandy Bridge system. And I am still convinced that it's totally unfinished product, CPU and chipset alike. Intel pushed too hard to get it on the market before AMD Bulldozer. ASRock guys are doing their best, thank you guys, but they cannot jump above their heads. Again I built dozens of systems, but never ever any system gave me such a lot of headaches as Sandy Bridge, and I can see from the posts that I'm not alone, by far. Exchanging MB for B3 was a huge mistake, B2 was way more stable.

Whoops man I am very sorry I did not read name correctly my bad my bad but still what i said to you is def true for him heh

[Ket]

Can we all be friends again now? ^_^

[radier]

@Ket

You've made me scared with this possible flaw in B3 revision SATA ports.
Go ahead and test Z68 Extreme4 because I am still waiting with swap of my beloved B2

[Ket]

I wouldn't call what intel have done with the B3 chipset a flaw, but any paramaters intel might of changed may of made the chipset a bit more fickle with SATA device detection under certain OC conditions.

[pythonse]

hey lets keep my name in a positive light here... lmao...just kidding
any ideas on the triple boot im getting? i have core limit on stock setting do i need to increase it to 255?
also pch,vtt,PLL,and vccsa are all left on auto

[Ket]

Theres really no reason you should be getting a triple boot. If there is no problem with stock settings the problem is with your OC. I've tried really hard to duplicate your triple boot and I can't.

[pythonse]

http://solo-elite.com/Forum2/index.php?topic=2937.90
check this thread...triple boot is a memory issue. my clan mate helped me on this hope this helps out

[BranFB]

copy paste here
Don't want to register to another forum just to chesk something out!

[pythonse]

crap...sorry

[elonm]

I need some help!

My ASRock Extreme 4 died so i RMA'd and got a new one. I installed the new one and now I can't get the system to boot. I keep getting the black screen with a blinking cursor. Here is me config:

C300 256GB SSD as primary boot drive running Win7 X64
Samsung 1TB data drive
2X 256GB WD as RAID 0 (previous boot drive on old motherboard)
All of the above are connected to the Intel SATA ports with the C300 and Samsung in the 6GB ports

I have tried AHCI mode, RAID mode and even IDE mode. No joy booting from the SSD. Interestingly enough, I can boot from the RAID0 partition. With my previous Extreme4 attempting to boot from the RAID0 partition would blue screen. Another thing that appears different is that on my previous Extreme4 I had an option to use Windows boot manager(?) as a boot device. In fact, i had to use this to be able to boot from the SSD.

I am wondering if some type of UEFI boot partition is stored on the MB and is now missing from the new board. This is my first UEFI board and I admit to not fully understanding the differences.

I am hoping someone has some suggestions. I would really prefer not to reinstall the OS again. I would also like to figure this out so I know what to watch out for in the future.

Thanks in advance for the assistance.

David

[piquadrat]

Are you sure that C300 is not accidentally connected to Marvel controller?

[elonm]

Thanks for the response Piquadrat. I double checked the ports and it is definitely not plugged in to the Marvel ports.

Update:

I was finally able to get the Windows Repair tool to run. It had previously told me it could not repair the version of Windows...not sure why it suddenly decided it now could repair my version...anyway, I ran repair and it recognized the the C300 as the boot partition but did not find any issues. I rebooted and it attempted to load Windows but blue screened. I went back into BIOS and the Windows Boot Manager is now listed as a boot device. I switched from RAID to AHCI and the system booted! Woot!

The strange thing is that my 2 WD drives that are configured as RAID0 show up under my computer like they normally do (as a single RAID0 drive). I thought setting the BIOS config to AHCI from RAID mode would break the set. Any idea why the drives are still RAID'ed together in AHCI mode?

Sorry for being long winded here. There is something going on that I don't completely understand...

David

[Ket]

Load UEFI defaults and indeed make sure you aren't using the Marvell controller for your OS drive. You are using a hell of a lot of drives as well, I would sort them into some kind of "order" when connecting them to the SATA ports to make troubleshooting easier. Eg; RAID drives on the Marvell controller, OS drive on SATA1 port, DVD drives on SATA2/3 ports, etc.