Jay_42

The whole draw for me with multi-core revisions was the multi-tasking potential. And of course more options for core assignment is nice when you want to be able to dedicate apps to their own cores, which i've found has made a big difference for me anyway.

I've always wondered, (since I never actually got to try it) would 3000Mhz memory actually be noticeable in day to day performance in something like a 6/8 core rig with say GTX980s & raid SSD's ?

I don't recall to be honest. Although that could have been a contributing factor. Good to know for future tho, cheers Fetzie. Are there any other tweaks for X99 that can help with stability ?

Yeah that has been the go to speed for the ram ever since Asus mentioned about issues with 2800Mhz on X99. Ever since then it's been kept at 2666Mhz always.

lol, nothing really. With the Asus board it apparently was a combination of faulty power distribution to the USB ports during P.O.S.T & glichyness with 2800Mhz speed on the RAM. Both of which I believe many of the brands have stated is a "quirk" of the X99 platform. And with the MSI board, well that one just seemed like it died after only 5 months. I don't go in for extreme OCing in my systems or even realy tax them all that much, as I tend to play most games in window mode, so mostly not even at full 1080p. The only thing I guess is the system is used everyday, thats about it really. Edit, also I see you have a sabertooth. Kind thinking about that board myself, cause isn't it meant to have much higher grade components on board and also it undergoes more rigorous factory testing before shipping for sale, is that right ? Also it looks sexy as hell

Thx for the condolences hehe Yeah X99 I guess still knida new in overall terms I suppose. Sometimes I think that I may just have horrible luck with the silicon lottery lol. Yeah that was a consideration tbh, but the PSU and GPU's have both been replaced with new between the Asus board and the MSI board, and the Memory and CPU have both passed multiple iteration testing. Besides in each occasion the boards after further testing were both apparently confirmed to have faults. Though I am getting abit worried that the on & off testing of the CPU between each new motherboard is only going end up contributing to reducing it's lifespan aswell. Yeah the Rampage is a higher tier board. I've seen alot of people recommending the Asus X99-E WS & the Sabertooth aswell. I might end up going with a workstation grade board in the end, and see if higher tier boards tend to be more reliable.

Yes, as with any thread such as this there's always a motive behind the question I'm asking because my experience of X99 Haswell-E so far has been pretty abysmal unfortunately. Had two X99 mboo's, first Asus X99-S then a MSI X99A Gaming 7 in the system. The Asus board was unstable & very unreliable. The MSI board lasted for 5 months then had a fit and began dying. Now currently having a second new MSI board going in, which i'm hoping will last. So yeah, just wondering what other peoples experience of X99 H-E has been like. Is anyone still using their launch day board ? Does the fact that it's an enthusiast platform mean that it should be exempt from the same expectations of reliability and stability as the more mainstream platforms ? And has anyone else had better or worse experiences with X99 so far ? Cheers, Jay.

Hey war raider, hope you doing ok mate. I, like yourself, have been researching this boot up issue with x99 boards as well, and I found another post by someone else with very similar spec to you and me that is also having the exact same issue as us. Here: http://www.pcadvisor.co.uk/forums/1/tech-helproom/4517076/asus-x99-s-world-of-pain/ As you can see his spec is very similar to yours and mine, and the way he describes the fault is pretty much exactly what is happening to us as well. I strongly believe now that this fault is related to the Asus X99 series boards in combination with a certain set of components, like ram, gpu, etc, and / or it's the 1103 bios version (most likely) - there are newer bios updates out now for the Asus X99, most of which state they "improve system stability" Anyway, did you have any success fixing the issue at your end war raider ? how did your taking parts out testing go ?

In that case I have a suspicion that this is a issue that can develop with the asus x99 series boards, or a specific bios version. What motherboard bios version are you on war_raider ?

Yeah exactly, thats what my system does too, like this evening it booted up first time, but the other day I had to boot it up like 4 or 5 times to get it to boot thought to windows. Like nightmare asked, yeah, is your system overclocked war_raider ? like CPU overclock I mean.

Yeah you see, mine is the same. The system seems ok once it's up and running. It's just the issue with p.o.s.t at boot up. war_raider does your system get stuck during p.o.s.t at boot up every time ? or is it more random, like sometimes it will boot with no issue ?

I would really like to know if you solve your issue war_raider. My spec is nearly identical to yours, and I also have a similar issue, only it doesn't just get stuck at just AE, it also gets stuck at other random stages of the P.O.S.T at boot up as well, most common one for me is "BF" war_raider, does your system work fine when it actually gets into windows ? like games and applications still work ok ?

Hi, i'm having weird glitchyness when using rivatuner statistics server + d3doverrider & msi afterburner and wondering if the almighty tech wizards of these here fine forums could help Basically the three applications work fine together. Like I can use all three together for most games no problem. Where the issue starts is if I run rivatuner statistics server + d3doverrider while msi afterburner is active, then if I close RTSS and D3DO it seems to mess up mis afterburner. Because if I run a game after closing RTSS & D3DO, the game always have this no error crash, and at the same time msi afterburner resets the clocks on the gpu's back to default. It's msi afterburner causing the crash, but it only happens if I have previously started and exited RTSS & D3DO. If I just start RTSS & D3DO and then leave them both on, and run any game, then everything is fine. It's the actual act of closing RTSS & D3DO while msi afterburner is active, that seems to mess with msi afterburner some how. I've been able to reproduce this glitch over and over again. It's a very consistent glitch, at least for me anyway. Also it's not an unstable overclocks on the gpu's, as all games tested run fine on the overclocks, the only time they start crashing is if I have at any point opened and then closed RTSS & D3DO while msi afterburner is active. Sometimes closing msi afterburner and restarting it cures the issue, but not with all games. Is this just me or is it just a normal glitch that happens ? And is there any settings I can change possibly to make it so that RTSS & D3DO don't interact/interfere with msi afterburner ? Thank you.

Hi, I am in need of help from the tech wizards of these here good forums. Can nvidia users please just check what language your NvOAWrapperCache.exe file is in please. The file is found in: C:\Users\username\AppData\Local\NVIDIA\NvBackend\ApplicationOntology. This is what mine looks like. As you can see the lanauage is in "Russian (Russia)" This is very suspicious, as I checked all the other background nvidia processes that usually run and they are all in "English (United States)" This NvOAWrapperCache is the only Nividia associated file that seems to be in russian. This site: http://www.herdprotect.com/nvoawrappercache.exe-785984d40f5765a66a1a01ab1a4f9117803d9247.aspx Seems to suggest that russian is the normal language for this file to be in. But i'm not sure. Please, can any of you that have nvidia cards, please just do a quick check of your copy of the file too just see if your copy is in russian as well, and post back what you find ? Also, I did the usual scans of the whole system and of the file itself. All seem to come back clean, virustotal, malwarebyes, hitmanpro, tdsskiller, ESET Online scanner. Thanks.

Ok, will do. Thanks bob. Thanks to everyone else too, your input has really helped me get my head around some of the eccentricities of g-sync.