There's plenty of info to come. Just don't form any firm conclusions on things you don't quite understand yet :)
Type: Posts; User: Raja@ASUS
There's plenty of info to come. Just don't form any firm conclusions on things you don't quite understand yet :)
Ah I see.
In that case the debug is still the same try using the motherboard output jacks instead of the USB Spitfire outputs and see if it still happens. If it does, RMA the headset.
Okay I get you now. You're referring to the mic boom and how it fits into the headset itself.
If you don't use the spitfire at all and then plug the red a green jack into the moteherboard audio...
Guys, this isn't a "problem", it's something we HAVE to do in order for the board to POST with CPUs and retain stability past those frequencies. Without it you'd have to overclock the system twice...
The headphone itself? You mean the spitfire dongle?
Might want to get the CPU itself checked out. Not much in terms of electronics between the first slot and the CPU. The transceivers are on the CPU and the GPU. It's hard to imagine how the board...
Try downloading the latest driver from Realtek if there is one.
Win 8 has some cool changes but it depends on your usage. For me, having HD and DD 5.1 in Netflix is reason enough to keep Win 8...
The Koolance Exos range might be a compromise between going full custom and closed loop. Not cheap, but makes for easy intro to water-cooling.
What are you plugging the headphone jack into - the spitfire dongle or your motherboard/soundcard?
Vulcan Pro mic should not be that quiet. The Spitfire USB dongle that comes with the Vulcan Pro is driver-free. In the mic volume tab do you have access to Mic Boost? Check all connections also.
oh yes you more than mentioned your love for whisky. just keep the tone positive and we're happy. :)
I was referring to RR forums where you appear to have a profile and often refer to whisky filled pastimes. Anyone can use Google with username.
Keep the behaviour on the good side and you won't...
God, Nvidia and a bugged firmware update - sounds pretty logical. ;)
Have fun with your card.
Just cos you dont see it, does not mean it isn't coming, capiche? :)
You did not say anything wrong. Xmanrigger needs to learn to be patient and less brash. Searched out his post history on another forum and he seems to have this demeanor there as well. Not sure if...
You have a reasonable IMC there. Thanks for chiming in the thread. :)
I'll have to ask HQ. You are the only one reporting this at current that I know of. If the system is actually working I would not worry about it too much for now. I don't know if or when HQ will...
In order to get any kind of traction on this thread the OP needs to provide a full list of parts (right down to the minutia) and driver versions. On top of that, unplugging devices one by one to...
Which timings have you adjusted? You need to be specific. Which profiles did you try? If you've tried everything already, then it's an IMC issue. Also regard what I said in my previous post about the...
Seeing as you don't like people posting their experiences on getting DDR3-2400 stable/or not, why don't you try tuning the timings yourself? Or give an account of what you've actually tried timing...
Memtweakit is counter-intuitive. A larger value = higher performance. A lower value = less performance. Why? Because during a refresh operation, the bank is inaccessible for read/write transactions....
Likely your memory modules did not play nice with the auto tuning feature. Clear CMOS and start again. Load XMP for the memory modules and start from there. Don't use auto-tuning this time. Once the...
Arne, you are correct, the base voltage is NOT fixed when using offset mode - the base voltage is only "fixed" for a given CPU multiplier ratio . The PCU (not CPU) will request a base VID according...
Good chance that some of your problems are being caused by combining two memory kits. Ideally, you should purchase a single memory kit rated at the timings and density you wish to run. Both the XMP...
Yes the clicking is the output relays switching - this should happen once the driver loads and not before.
As for the iROG update, if using a single memory module and a bare minimum of components...