Hello,Quote:
Originally Posted by Sailindawg
I have no problems with "Sound effects" tab running 2.63:
http://images35.fotosik.pl/853/13e40f2434874c25.jpg
In basic mode there are predefined equalizer settings. If I want to go to manual settings, I just click the icon "Change to graphic EQ" and I have EQ with traditional sliders. I have no idea why this is not showing for you. Maybe try full uninstall of the driver, then new installation. Or maybe Driver Sweeper will help?
Corey,
Thanks for the screenshot. When I installed the 2.63, the sound effects tab never loaded. I just loaded the 2.63 over the older driver. Maybe that had something to do with it!? I didn't think to uninstall the Realtek chip and do a thorough cleaning before installing the newer driver. The driver install indicated that it would uninstall the older driver first, then install the newer driver. I'm too used to Creative's method of installing drivers over older drivers. That method seemed to work best with Creative's drivers.
I have been liking the onboard sound so far. Comparing to my X-Fi Xtreme Music, the X-Fi has a bit more separation in sound. However the Realtek onboard is very close. I haven't used on board sound since the NF2 days with nVidia's sound solution. Its a toss between the X-Fi & the onboard. I may run both for a bit for comparison.
Question about fan control and settings. In UEFI, what should I set the fans to if I want to use a Windows utility to control them? Auto, full on, or manual? I'm guessing either auto or full on. Also, how is the AsRock utility for fan control? It seems I can set a temp threshold and have it respond accordingly. Does that work for 3 pin fans as well, or just the PWM fans? Is the utility any good?
Manual says to use the top most PCIe spot for single card, and top two for 2 card setups. Is it okay to use the middle one for a single card setup, and first and third for a 2 card?
Bit-Tech review from near launch said the board had poor SATA 6.0 speeds. 10%-20% slower than the Asus Barefoot. Is that still the case?
Thanks for the help, and the wonderful thread!
To set the fans using a tool in windows, you can choose either the 'full on' or manual setting. By comparison, the 'manual' setting will make whichever fan speed you set in UEFI the maximum fan speed you can select using a windows utility. The 'full on' setting will allow the utility to set the fan speed to the highest possible setting. In my experience, speedfan is one of the best available, though it's probably going to take some time to figure out how it works.Quote:
Originally Posted by squick3n
From my experience, all of the fan headers on the motherboard are controllable with software except for the 3-pin Power fan connector that's next to the 12v atx power connector in the top-left part of the board.
For the PCI-E slots, don't use the bottom one unless you are installing a 3rd graphics card into your system. It runs 4 times slower then the other two slots. As for the SATA 6.0 speeds, i really doubt that it is generically 10% slower then the Asus board. So no, its not the case.
Thanks for the answers. Sounds like the thing to do is leave the fans at Full On and control them in Windows for performance/quiet.
Here's the bit-tech review I was talking about. Only place I've found that even tests SATA speeds, let alone notes a performance delta
http://www.bit-tech.net/hardware/mot...eme-4-review/5
Asrock Instant Boot
Does this software app enable one to get around the resume from sleep bug that seems to plague the P67 chipset?
Is anyone using this app successfully with an overclocked CPU?
Hi Ket,
Forgive my ignorance (new to this forum and Extreme4), but what is the Intel PCH Driver v9.2.0.1030 for (on your updated drivers page)? I ask, because ASRock doesn't list this as one of their official drivers?
Also, someone recently posted the steps to clearing the Extreme4's CMOS (below). Other than electrically discharging the capacitors, is the "Clear CMOS" button on the motherboard sufficient to clear it?
Steps to clearing CMOS
1. Load UEFI defaults, save and exit.
2. Flash from pure DOS via a bootable USB stick.
3. After the flash, power down.
4. Set CMOS jumper to "Clear".
5. Remove CMOS battery.
6. Remove power cord from PSU.
7. Press power button two to three times (discharges capacitors).
8. Wait one minute.
Also, (and I know I'm going out on a limb here), I realize ASRock states that: "We don't recommend users to update BIOS while the system is running well." But is there any way that ASRock would be willing to take a closer look at the content of their UEFI code since 1.70?
I ask because, for some reason, after updating to either 1.90 or 2.00, my Extreme4 crashes within seconds of restarting Win7 with a deadly BSOD Stop Error, rendering the boot table of my HDD inoperable until I reinstall Windows (even attempts to restore Windows with a full system image cannot repair it). The flashing process itself appears to work fine--no errors reported (1.90 via Instant Flash method and 2.00 via Windows method).
This presents a dilemma for some of us users as newer drivers for the Extreme4 (undoubtedly intended to fix bugs, add features, and improve performance) such as Intel Rapid Storage Technology v.10.6.0.1002 requires flashing to UEFI 1.90 or later.
I know for a fact that there is nothing technically wrong with my hardware. I have thoroughly checked my RAM, error-checked my hard drive, etc. and seeing as everything runs fine under UEFI 1.70, makes me seriously question the content/changes of UEFI 1.90 and later.
I'm sure I'm not the only user who has run into this problem. My point in all this is to encourage ASRock engineering to take another look at their code for anything that could be causing these boot table crashes and preventing users from updating their drivers/PCs.
Greg
ASRock P67 Extreme4 (B3) in XPS 630i case | UEFI 1.70 | Core i5 2500K @ 3.3GHz | CM Hyper 212 Plus | Windows 7 Home Premium 64-bit SP1 | 8GB CORSAIR DDR3 Vengeance 1600MHz | BFG Tech OCE GTX 275 896MB | ViewSonic VX1940w 19" LCD | WD Caviar Black 500GB SATA-3 | WD Caviar Blue 500GB SATA-2 | Dual x16 DVD-DL | ASUS Xonar DX 7.1 | CORSAIR 850HX 850W | Microsoft Sidewinder X3
UEFI 2.00 works just fine.
In the last days of June I have send my B2 Extreme4 for RMA to recive new B3 revision. Then I went abroad for more than one and a half month. Today I have rebuild my PC. Just after start i have updated UEFI to the latest 2.00 version. Then I have set all my old settings/OC etc. started my OS without formating. Everything works like a charm. I have also bought Crucial m4 SSD drive and I will make a clean OS install tomorrow.
@ GregoryDonner
I have flashed from 1.70 -> 1.90 -> 2.0 on the same windows 7 install with no issue.
Is it possible when you flashed the bios it reset your storage options if you had it set to something other than default? I know i've run into that issue in the past with other boards. Had the SATA emulation set to IDE and then after flashing the bios it reset to default RAID. Switching it back to IDE solved the BSOD without needing to re-install windows.
You have a point there; however, my SATA3 boot drive is on the first SATA3 port (using the Marvell SATA3 AHCI drivers), so while this seems like the most likely answer, I've always set my SATA and SATA3 modes to AHCI in the newly-flashed UEFI before booting into Windows (as required), so it makes no sense as to why the crash?
The BSOD happens so fast that it's difficult to catch (screenshot and video links of the crash below):
http://www.gregdonner.org/temp/uefi_crash.png (photo)
http://www.gregdonner.org/temp/uefi_crash.avi (video)
I'd like to think that somehow this is related to the MS fix (http://support.microsoft.com/kb/922976), but it makes no sense why, only under new UEFIs, it's not finding and booting from either the already installed Windows 7 or Marvell SATA3 drivers?
Even ASRock doesn't recommend using Marvell controller for booting. Try connecting your hard drive to Intel controller. From the movie I would say that controller settings are different. Try switching to IDE mode and see if it helps. Then apply regfix for activating AHCI, reset computer, go to UEFI, change controller to AHCI and then boot to Windows. It may be because ROM has changed in recent UEFI and now the drivers are not working so good. Did you tried booting to safe mode and uninstalling/reinstalling drivers?Quote:
Originally Posted by GregoryDonner
And what is the exact error code, because it is hard to read from picture. Is it 0x0000007B? If so, it either suggest controller mode error, or broken HDD.
Please forgive my extreme novice questions, but what are best practices for updating the drivers suite for the P67? Please tell me there are just inf files that can be updated in Device Manager, and not uninstalling exe/reinstall
I've always followed the model of uninstalling the old and installing the new. The Eltron USB 3.0 drivers are easily updated through device manager. Select update driver and then point it to the folder where you downloaded the lasted drivers. For everything else I usually uninstall - reboot - install new drivers.Quote:
Originally Posted by squick3n
Exactly what I was referring to. After watching the video I'd be 90% sure its a storage option setting or... like you said.... plugged into the wrong controller as a boot device.Quote:
Originally Posted by CoreyPL
Ok, I'll try to keep this short otherwise this post will turn into a Essay.
- PCH drivers are the "chipset" drivers, but as the "chipset" is not really a "set" anymore, its referred to as PCH (Platform Control Hub)
- Using the Clear CMOS button is generally sufficient, but the method I detailed is the cleanest way to do it, especially after a UEFI update.
- When you update the UEFI, setup defaults are automatically applied so if you are using other than setup default settings, you will need to change the settings accordingly.
- Theres nothing wrong with using the Marvell controller for boot devices, Asrock just don't recommend it mainly because it increases boot time.
- As for drivers, generally you should be fine as long as you used the latest available drivers when setting your system up at the time. The only driver I recommend to update whenever possible is the Etron driver.
Thanks for the answers! Another question, if you will indulge me. On my old Gigabyte board, most drivers were installed before/during Windows installation. Is that what is done for AsRock, or do most just run the executables once Windows boots?
After Windows installs you will need to install the LAN drivers that come on the driver disk. Once you have installed the LAN drivers grab the latest driver pack that is in this thread. Install and enjoy. The only drivers you will have to update through device manager are the Eltron 3.0 USB drivers.Quote:
Originally Posted by squick3n
So... 1. Install Windows 2. Install LAN drivers from driver disk. 3. Install latest driver pack you downloaded from a post earlier in this thread. 4. Install Windows updates. 5. Done.
Many thanks to everyone for their help--problem (finally!) solved.
Long story short: IDE mode didn't work (same crash after flashing to UEFI 2.00; BSOD was indeed 0x0000007B), so powered down, cleared the CMOS (hardware button), booted to the UEFI, setting SATA and SATA3 modes to AHCI, and reinstalled Windows. No glitches.
I've decided to forgo the Marvell drivers, and just use the Windows default. Am using the latest PCH, Intel Rapid Storage Technology, and Etron drivers. Again, many thanks to Ket and everyone for your advice and patience with me on this!
Quick question regarding RAM... (i tried to use the search function but it was too damn slow returning results)
I've just bought a Ripjaw 8 GB kit. (so 2*4Gb). I currently have a 4GB kit installed (2*2gb).
Can I expect any problems running 12GB & 1600Mhz? Both kits are CL9 1600mhz 1.5v. Or should I just go with 8GB and dispose of the 4GB kit. Obviously I'll be matching the size across the dual memory dimms.
Also will it be 4gb modules in mem position 1 & 3 or 2 & 4?
Hmm in answer to my own question and confirmation from Gskill forum.. we dont sell them in kits for no reason... Guess its going to be a crap shot if they play together..
12GB fully installed and playing nicely together so far. Knocked it down to 2T so there's an extremely minor drop in benches for the time being.
Goodbye page file! hah.
Who can explain this to me?
My back USB 3.0 ports works like a charm, but when I switch to the front ports it seems like my portable disk is working in USB 2.0 mode:
http://img695.imageshack.us/img695/3678/hdtachd.jpg
Latest Etron drivers, fresh OS installation.
Hello! I recently ordered the ASRock P67 Extreme4, and I set up the build last night. Specs as follows:
i5 2500k
ASRock P67 Extreme4 B3
EVGA 560Ti
2x ripsaw 4gb
etc
Everything appears to be working fine, except for the sound! I have tried multiple installs of windows, multiple output devices, both old and new versions of the Realtek HD Audio driver, tried it without the audio driver, tried uninstalling the front panel HD audio. All that comes out of either the frontal or rear audio jack is a very high pitched buzzing.
After spending all night researching a potential fix, I have found nothing so I figured I'd give you guys a shot to see if any of you had dealt with something similar before I ship this back to Newegg.
AFAIK, its a Etron driver issue ATM.Quote:
Originally Posted by radier
Check the UEFI settings for onboard sound. Set them to "enabled"Quote:
Originally Posted by skitt