Emp138

Every time I start the game it seems to work differently. Sometimes it auto goes to borderless, other times full screen. Sometimes the borderless works, other times not. HDR sometimes works, but other times I think the game, my PC, and the TV are all trying to do their own HDR and it gets very blueish and bright and kinda blurry. Sometimes DX12, DLSS, and Ray Tracing are on and work, other times not. There seems to be no rhyme or reason to it, and I just kinda check and uncheck things till it looks good. Really sucks.

Memory is fine as far as I am aware. Plugged into A2,B2 like suggested, system shows 32gb active. All other games seem to work perfectly fine.

Unfortunately I do not have a monitor at the moment. I spent quite a lot on the build and figured it would be fine on the TV for a month or whatever till I got a monitor. Also don’t have another GPU because this is my first build. I am leaning towards it being a settings/user error issue. 1. I am using the un-activated Windows 10, some videos said this is fine and only prevented you from doing personalization (themes, background etc). But a note about “activate windows to personalize device” appears in both the display and sound settings. 2. This is essentially my first time using Windows. I used ‘95 and XP growing up. But have had a Mac for the past 15 years. So it might just be a settings issue I don’t understand. When starting the PC sometimes it is zoomed, other times everything is tiny. I can’t seems to get the settings to stay consistent. One time the game sound works perfectl’y (routed via hdmi to tv and then optical to the stereo) other times nothing, no matter which way I try it (PC-HDMI-TV-Optical-Stereo or PC-optical-stereo). Can’t seem to get the mic from the headset to work (dual cabled 1mic 1audio). Tried the front case ports, tried the mobo ports, tried BT Apple AirPods, etc. So, honestly I think it is probably on my end, but it’s incredibly frustrating and makes me not want to use this brand new system I paid a ton for and stressed my ass off to build...

All drivers are up to date. Will try re-installing game!

Even after 4hrs straight of 4K, ultra gaming I have never seen the GPU break 71c and never seen the CPU break 70. Memory is is slotted in A2 and B2 as the manual recommends, and I have no problems in any other game. Was hoping this would be an easy, first timer mistake type fix, but it seems more in depth.

Build: CPU: i9-9900K GPU: MSI Gaming X Trio RTX 2080ti MB: Gigabyte Aorus Master RAM: 32gb Ripjaws V HD: 1Tb Samsung 970 Pro PSU: Corsair RM1000i CPU Cooling: NZXT x72 Kraken Display: 55” 4K LG OLED UHD 120hz So, just built this two days ago and I’m having a lot of issues. Most of them are pretty small and probably chocked up to this being my first time using Windows in over a decade. But the real killer is how choppy Battlefield V is. The game plays fine but when it gets to a cut scene it turns into a flipbook. I originally asked over on Toms Hardware, but didn’t really find a solution. It was theorized that maybe my GPU was getting peak utilization. Or my CPU was and bottlenecking everything. So I went back and ran a test. I had to drop RX12, DLSS, and Ray Tracing since for some reason my CAM monitoring software doesn’t run with that enabled. What I found was that my CPU/GPU utilization plummeted when the stuttering started and stayed there. Running 4K, Ultra graphics, RX12, DLSS and Ray Tracing I was getting 60fps at ~35-40% utilization on the GPU and CPU. Everything ran fine for playing, but as soon as that cut scene popped up CPU and GPU utilization dropped into the teens. CPU reached a low of 10% and a high of 18% during the cutscene, while the GPU bottomed out at 12% and peaked at 17% during this time. Not sure if FPS can be trusted here but it was reading 29-30fps throughout the scene, whether the stuttering was almost comical, and the same even when it was slightly smoother. As soon as the cut scene ends and it drops you back into play the FPS popped up to 60 and utilization back to high 30s. Any help would be greatly appreciated! Thanks