EightyDuce

917w at the wall plug on the kill-a-watt while benching. Thats with everything in the signature + EK-D5 pump, 6x140mm fans, 3X Nvme SSDs.

When I get home I'll check my Kill-0-Watt to get you the powerdraw with a 7800X3D and a 4090. ... As a bonus, I'll do it without digging into my dusty pockets and bringing up a 5800X3D and DDR4 for some irrelevant reason.

Yeah, I'm not really a hat guy. So it's either the clip or the hat... Neither is perfect. That being said, can't argue with results. If Tobii tracking was 1:1 to TIR5, it would have been a slam dunk. Maybe with Tobii 6?

After close to 10 years of using TIR5, I was excited to try Tobii. After about a month of trying it out, I could never get it to the same level of smoothness/sensitivity that I had with TIR5. I tried with and without eye tracking. In the end I sold it on ebay and went back to TIR5. Now I'm almost exclusively VR. To me, the only downside to TIR5 is the janky LED pro clip they sell.

That has been the hope for years. The closest thing that came to it in recent history was the 6800/6900/6950. People thought the 7900XTX was going to be a killer product up until the day testing went live, and even when that balloon was popped, people still thought it was going to get better with drivers (it had slightly, yes). I really hope AMD gets back to the days of 290X and 5870s, I loved those cards and they were fantastic performers. But my last two purchases were Nvidia (1080ti and now 4090) just because they provide a superior, no-compromise solution that will tick away for at least two generations.

To be honest, unless you have a board that allows for an external clock generator any overclocking features on the 7800X3D are pointless as its fused max is 5Ghz. PBO will be of no benefit and neither is curve optimizer, unless your goal is efficiency and cooler temps. The only way to make the 7800X3D go above 5Ghz is with FCLK/ECLK modification. The reason curve optimizer works on other SKUs , is that other SKUs are almost always thermally limited. With CO negative offset there's less heat thus more room to boost to higher speeds. 7800X3D you're stuck at 5Ghz. Now as far as memory is concerned, it will depend on the application and whether it's bandwith/latency starved to how much of a benefit you will see. But realistically best case with an X3D chip would be 7-10%. Arguably, thats one part of the appeal of an X3D chip...you can drop it in a budget MB and will be go about as fast as a $500 MB.

Asus +7800X3D happily ticking away. Not really loyal to any brand, just my wallet and needs. Next go around, if Asus has better boards/features for the price, I'll stay with Asus. Otherwise, GIGABYTE is my runner up/tied for first place. IMO this thing got spun up by the internet from just a couple of incidents (some of which cause isn't even confirmed) to the point where common sense exited the chat. Internet is gonna internet.

While with the X3D RAM specs don't make as much of a difference, the difference in overall performance is still there when comparing potato RAM settings to EXPO/XMP to manual tune. EXPO timings are very loose overall. On my 7700X I got close to a 10-13% improvement with memory overclock and memory timing tune (beyond EXPO ); EXPO2 got me roughly 5-7%. On my 7800X3D I'm at roughly 7-10% improvement, game dependent. DCS I'm on a lower end with about 8% improvement going from EXPO/XMP DDR5 6000 32-38-38-96 at Auto IF to 6200 30-36-36-46 (and tuned secondary/tertiary timings) and IF @ 2167. In VR this may mean the difference between dropping down into a lower reprojection bracket or cruising at 90FPS. TLDR: even with the X3D, there is still a significant difference between running bad/"stock" memory settings and tuned. Just some quick 5 minute tuning bring a good uptick, I'm not even talking about min-maxing.

Asus cluster aside, the 7800X3D failure seems to be a much more of a nothing burger than originally led on. By GNs own admission they had to really work to make it fail. From the very few reported incidents it's hard to tell the nature, whether user error/manipulation (attempted OC), straight up hardware defect, failure of OVP/OCP mechanism, aggressive voltage being set by board manufacturers or a culmination of all. Asus definitely not helping AMDs mindshare, that's for sure.

Not warrantied because it is a BETA release. If you wait a couple days the stable version should be out. Shouldn't explode your stuffs any more than anything else. I would wait for a stable release.

Good video. Shows how sloppy some protections were handled. Also shows how unlikely this is to actually occur due to a cascading of issues that culminate is a catastrophic failure. As for countering the issue... I've ran at a manual SOC (1.2-1.25v) since day one due to manually tuning memory. Other than that, update the BIOS and carry on with your life.

Can you not change the values in the UEFI/BIOS?

The Windows Update block functionality is built into Display Driver Uninstaller, in the settings.

If the biggest thing you're looking for is IO then the B650E-F or the B650 Aorus Pro AX from Gigabyte are hard to beat. However, only way to get some of the overclocking features like BCLK/ECLK control is to get a high end 6+X670E chipset. So one needs to decide what features they need.

What specific features are you looking for that X670E has that B650E-F doesn't have?

With the 2080 super (very limited 6Gb Vram buffer) you will 100% be GPU limited rather than CPU. Something is not right. What are your CPU and GPU frametimes reported by XR toolkit? DCS ingame reporting of CPU/GPU limitation has been misreporting in the past, use open XR toolkit

Something is wrong with your particular setup, there's no way you should be CPU limited and at 20FPS with the 7800X3D.

One way to check is to go in the bios enable XMP or EXPO and see what it sets the voltage to. Settings aren't applied until you save the settings and reboot. No guarantee, but with 5200 I would be very surprised if it needs more than 1.2V if not less. Always verify.

Yeah just saw the bios drop. So my take on it from my experience overclocking DDR5 on AM5, SOC voltage of 1.3v is actually quite a high amount. I don't have any EXPO kits on hand and have only done manual overclocks, but the most voltage on the SOC that I needed to use to hit 6200/2167mhz on the RAM/IF between 3 sets of RAM kits and 3 different CPUs, was 1.25v. And that was on 1 of the 3, the other two did it at 1.225v. The 7700X could do 6400 at 1.3v SOC. To run at 6000 you shouldn't need more than 1.2v SOC unless the memory controller on your CPU is terrible (silicon lottery). It seems the manufacturers are being very loose with the voltage as they are with timings when it comes to higher clock speeds. If in fact they push 1.3v as part on an expo profile is a bit baffling to me unless they did very little stability testing/tuning and just cranked the voltage up to get it stable. Its unfortunate that they took a shotgun approach and straight up locked max SOC at 1.3 instead of limiting 'auto" setting to no more than 1.3v an leaving the ability to manually set voltage alone, maybe slap a warning on it.

Gotta be careful of Amazon as 3d party sellers can really jack up the prices. Not sure if PartsPicker works outside CONUS, but may be worth checking to get the best pricing.

So at best, the difference is ~2% and at worst, sub 1%....ie. Margin of error. What were the timings on the two sets of RAM, primary and secondary?

When returning to Amazon, less is more when defining a reason for a return. I've returned a motherboard and two CPUs and never had a remote issue with simply ticking the "defective" box and hitting submit. Now if it it's not defective and you know you borked it, well.. That's between you and your ethics.

From the picture kinda looks like the pin may be bent.

While I miss my sub 10 second boot times of my old 7700K, I don't see how an extra 10-15 seconds has any impact unless you're restarting your computer constantly. It does get to be a little annoying when Overclocking/tuning memory and need to reboot a lot. But day to day, at least to me, doesn't seem that bad.

They seem to be leaning hevy on the derbauer video/thoughts, which he stated are just an educated guess at that point. If it is an SOC issue, that's easy to control by just manually setting voltage.