Question / Help Recording framerate drops with i7 5820k[solved]

[Metum]

I have the 5820k, I tried everything from updating BIOS and every driver I could find, disabling hyperthreading -- testing it and re-enabling it, lowering graphics settings, lowering encoding settings, closing background programs, overclocking RAM and CPU by 40%, OC'ing GPU by 15%, running disk check, run registry check, defragging/optimizing drives, and prioritizing the processes involved with OBS and the game in task manager. All of this I have tried in multiple combinations having the same results, same fps drops, performance degradation, and constant stuttering.

I got the same results across the board no matter how undemanding a title was. League of Legends, Mount & Blade, Rome Total War (2005).

My previous build having an AMD FX 8350 running 1080p@45fps no problem, this is somewhat confusing to me... given that all of the hardware I have now is three years ahead of the FX line.

Specs:
i7 5820k 3.8Ghz
16GB of DDR4 2400mhz RAM
R9 280
Asus X99-A/USB 3.1 Mobo
Windows 10 64-bit
Avg FPS: Around 33

Previous specs:
FX 8350 3.92Ghz
16GB of DDR3 1600mhz RAM
R9280
ASROCK 980DE3/U3S3
Windows 10 64-bit
Avg FPS: Around 52

 

[Black Ops]

Your Log Isnt Readable. Please Repost it

Try removing the custom x264 Encoding Settings and see if the issues crop up

 

[Metum]

Your Log Isnt Readable. Please Repost it

Try removing the custom x264 Encoding Settings and see if the issues crop up

I've tried that, the same thing happens. These settings are identical to the settings I used on the 8350 processor.

I have also tried both the 32-bit and 64-bit versions of OBS.

 

[Metum]

I'm open to any suggestions if someone thinks they see something I haven't tried yet...

 

[Metum]

For anyone else struggling with similar issues, I found benchmarks that suggest that the 5820k actually performs worse at higher clock speeds in-game.

One example here: https://www.youtube.com/watch?v=n7rNq32X6cY

 

[Sapiens]

Your log shows a high number of duplicate frames which usually indicates GPU load problems. Running a game without vertical sync or a frame rate limiter will frequently cause performance issues with OBS because your GPU will be maxed out. Enable vsync or set a reasonable frame rate limit that your GPU can handle without hitting 100% usage. If that's not enough you may also need to turn down some of the video quality options in the game.

 

[Metum]

Your log shows a high number of duplicate frames which usually indicates GPU load problems. Running a game without vertical sync or a frame rate limiter will frequently cause performance issues with OBS because your GPU will be maxed out. Enable vsync or set a reasonable frame rate limit that your GPU can handle without hitting 100% usage. If that's not enough you may also need to turn down some of the video quality options in the game.

Well, if you didn't read what I said, I have had the same GPU in both setups. The game I ran the test on had a frame limit of 60fps and runes solely off the CPU, it is a very undemanding game which I had previously run with an identical setup except with the FX 8350, 16GB DDR3 memory, and motherboard. My GPU is set to force Vsync and also has a frame limit of 60fps.

I purposely chose the game I tested for it's undemanding system requirements, being able to be run on a pentium 4, I have a 5820k; which is leaps and bounds beyond the pentium 4.

 

[Sapiens]

Am I reading your post correctly that you can't maintain a steady 60 FPS in-game? Average FPS of 52?

 

[Metum]

Am I reading your post correctly that you can't maintain a steady 60 FPS in-game? Average FPS of 52?

Average fps of 52 while recording 1080p@45fps with the 8350

Average fps of 33 while recording 1080p@30fps with the 5820k

the 5820k being nearly twice as powerful as the 8350, not to mention the performance boost from DDR4 RAM
Both of which also running the crf=15 264 encoder

While not recording with the 5820k, I maintain 60fps without EVER dropping below 59.

With the FX 8350, whilst not recording I had framerates ranging anywhere from 34-59

 

[Sapiens]

So you hold 60 FPS easily when not running OBS? What does your GPU load look like before launching OBS, and while it's actively recording?

 

[Metum]

So you hold 60 FPS easily when not running OBS? What does your GPU load look like before launching OBS, and while it's actively recording?

Before OBS it is around 23%, after it is about 47%

 

[Sapiens]

Well something isn't working right. Could you test with OBS Studio and post the log results from that?

 

[Metum]

That is when I'm running League of Legends,

Well something isn't working right. Could you test with OBS Studio and post the log results from that?

Alright, I'll be back. I don't have a log but I've tried it before, and I had the same issues. This'll maybe take 10 minutes.

 

[Metum]

Well something isn't working right. Could you test with OBS Studio and post the log results from that?

Here it is. Framerate drops weren't nearly as bad, but they were still out of my comfort zone.

 

[Sapiens]

You shouldn't be seeing any frame rate drops honestly. Does the type of source used make a difference, e.g. using window capture instead of game capture? Does disabling the preview window in OBS help?

 

[Metum]

You shouldn't be seeing any frame rate drops honestly. Does the type of source used make a difference, e.g. using window capture instead of game capture? Does disabling the preview window in OBS help?

Windowed mode results in the same drops, I haven't tried disabling preview ... where do I do that?

 

[Metum]

You shouldn't be seeing any frame rate drops honestly. Does the type of source used make a difference, e.g. using window capture instead of game capture? Does disabling the preview window in OBS help?

Nevermind, found disable preview.

 

[Metum]

You shouldn't be seeing any frame rate drops honestly. Does the type of source used make a difference, e.g. using window capture instead of game capture? Does disabling the preview window in OBS help?

It didn't help at all whatsoever...

 

[Metum]

I fixed it. I just built this computer and due to some issues I was moving the gpu from slot to slot to diagnose some boot time issues, and I forgot to put it back in the first pcie slot. It turns out the issue all along was that my GPU wasn't in the first slot of the motherboard.