Call Of Duty: Modern Warfare / Warzone (Battlenet ID's in OP)

enigma27 said:
keep crashing randomly in warzone this morning with directX error

first time i have ever had this since the game came out
Click to expand...

Yeah mate has same issue. 6338 or something. I have had dx 6068 ever since I did a clean install of the latest windows. Happens about once or twice a week.

Few work arounds on the web.
 
5VcxqUy.png


Guys this bar at the top,What does the GPU & CPU time actually mean?is that good what im getting?
Also how come my GPU is showing N/A,is that suppose to show GPU temp?

I've locked my FPS to 60 as i only have a 60Hz monitor atm (temp)
 
Its the amount of time each part (CPU & GPU) takes to render a frame. youve locked it at 60FPS which is a 17ms frame time as the game shows, but at 60FPS your only just tickling your CPU loads, its able to produce its frame in 5ms and then has an idle period of 13ms because youve forced 60hz/fps.

Once you unlock VSYCN or place max GPU load the frame times will get much closer, ie for me on 1440p with spec in sig, you get typical GPU times of ~6-7-8ms (for 100-130fps or so), and the CPU time of 5ms. So the CPU only has a ms or so spare for each frame render, it is under much higher pressure to deliver the frame in time with the GPU now storming along. Once the two values match (i.e 1080p low settings), the GPU then has to wait on the CPU to deliver its calculation before the frame is rendered, i.e you have made a CPU bottlneck scenario because the GPU can smash through 1080 resolution frames very quickly.
 
Last edited:
Acolyte said:
Its the amount of time each part (CPU & GPU) takes to render a frame. youve locked it at 60FPS which is a 17ms frame time as the game shows, but at 60FPS your only just tickling your CPU loads, its able to produce its frame in 5ms and then has an idle period of 13ms because youve forced 60hz/fps.

Once you unlock VSYCN or place max GPU load the frame times will get much closer, ie for me on 1440p with spec in sig, you get typical GPU times of ~6-7-8ms (for 100-130fps or so), and the CPU time of 5ms. So the CPU only has a ms or so spare for each frame render, it is under much higher pressure to deliver the frame in time with the GPU now storming along. Once the two values match (i.e 1080p low settings), the GPU then has to wait on the CPU to deliver its calculation before the frame is rendered, i.e you have made a CPU bottlneck scenario because the GPU can smash through 1080 resolution frames very quickly.
Click to expand...
Gotcha,Thanks for your time in explaining in detail :)

Should be receiving my 1440p 165Hz monitor tomorrow so can finally get away from 60hz :)
 
You must log in or register to reply here.
Back
Top Bottom