Funnily enough i was just playing with PG Tips and i had a BSOD using DX11, Bad Pool Header was the message.
lol ironic.
Bad Pool Header is (or was) something to do with system memory allocation. Got the igpu on your 2700K disabled?
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
***THE BF4 BENCHMARKS THREAD***
- Thread starter pgi947
- Start date
lol ironic.
Bad Pool Header is (or was) something to do with system memory allocation. Got the igpu on your 2700K disabled?
I think its just how BF4 handles the CPU/Memory, I could have an OC that will run anything else for hours on end fail in BF4, especially on the memory side of things.
I did manage some results, eventually
What a pain to do under the pressures of battle, kept forgetting to close the command and thinking '**** sake i've lost control again!!!!'
I did manage some results, eventually
What a pain to do under the pressures of battle, kept forgetting to close the command and thinking '**** sake i've lost control again!!!!'
Yeah was around the same frame rates for most of the round, though the GPU line does funny things when I hit the 200 frame wall, outside stresses enough to go under 200 giving me a better line.
Can you force dx11.0 in the config file? I'm on win 8.1 too.
Well, from some digging, Kepler supports 11.1 code and runs it, but only fronts its self as supporting the feature set up to 11.0 so thats what it shows.
In other words it technically IS running 11.1 though will only ever show 11.0 due to it not meeting the full feature set specs.
In other words it technically IS running 11.1 though will only ever show 11.0 due to it not meeting the full feature set specs.
Haven't tested 1440 yet though suspect more consistent times is likely due to not hitting 200fps so often. My GPU line sometimes gos mental sitting at 200. A pair of 780's is deffo overkill at 1080 for this game.
Not sure if it happens in amddx/mantle, but with nv, never do screenshot.render while running framefilelogenable, the split second after the command is sent it generates an almighty spike on the CPU line.
Tbh if mantle wasn't beating both of our read outs then its not doing its job
Not sure if it happens in amddx/mantle, but with nv, never do screenshot.render while running framefilelogenable, the split second after the command is sent it generates an almighty spike on the CPU line.
Tbh if mantle wasn't beating both of our read outs then its not doing its job
It doesn't always happen but I'll try grab a screen of it. Rather then flat line (as the CPU does) it jumps up and down quite quickly by a small amount for the duration of hitting the wall.
You watch, I bet it won't bloody do it now.
You watch, I bet it won't bloody do it now.
Depends what you play and specifically with bf4 what maps you play. For 1080-60 a pair of 780's is overkill for bf4, at 1080-120 its slightly more justified as the heavy maps like shanghai can bring frames almost down to double digits in places.
I fully expect the witcher 3 (like crysis 3) to annihilate a pair of 780's at 1080 fully maxed out.
The downside is im running the latest PB.
I won't bother to do the Mantle frame variance test to compare to our DX results until its working properly.
In other news - http://www.escapistmagazine.com/new...munity-Test-Platform-for-Battlefield-4-Update
Have you made sure in windows services pnkbustrA and pnkbustrB have been forced enabled. I had a problem with one of them not starting up with bf4.
As if the CPU spikes are related to pb its likely pb is trying to send some commands repeatedly (perhaps trying to restart one of the above?).
Just a thought
