Jump to content

Hi,

 

When playing MW, my GPU clock speed is remaining at around 700MHz rather than the 1050Mhz base clock or above that it usually gets to when gaming.

I tried the game Friday and it worked, however trying it today it's no longer working.

 

As you can see here it's ramping up a little bit, from the idle setting, however it's not even hitting the base clock let alone the boost clock.

I'm not sure what could be causing this as it's not reaching the power or temperature that it's at while playing CS:GO so it's not hitting any kind of limit.

 

I've added the game as a 3D program in the NVidia Control Panel already and that's not changed anything. I have the latest drivers and the latest game update.

 

 

Link to post
Share on other sites

12 minutes ago, DatBrummie said:

I tried the game Friday and it worked, however trying it today it's no longer working.

Have you changed settings?

Have you checked CPU usage? Might just be CPU-bottlenecked and the GPU has nothing to do.

F@H
Desktop: i9-13900K, ASUS Z790-E, 64GB DDR5-6000 CL36, RTX3080, 2TB MP600 Pro XT, 2TB SX8200Pro, 2x16TB Ironwolf RAID0, Corsair HX1200, Antec Vortex 360 AIO, Thermaltake Versa H25 TG, Samsung 4K curved 49" TV, 23" secondary, Mountain Everest Max

Mobile SFF rig: i9-9900K, Noctua NH-L9i, Asrock Z390 Phantom ITX-AC, 32GB, GTX1070, 2x1TB SX8200Pro RAID0, 2x5TB 2.5" HDD RAID0, Athena 500W Flex (Noctua fan), Custom 4.7l 3D printed case

 

Asus Zenbook UM325UA, Ryzen 7 5700u, 16GB, 1TB, OLED

 

GPD Win 2

Link to post
Share on other sites

24 minutes ago, Kilrah said:

Have you changed settings?

Have you checked CPU usage? Might just be CPU-bottlenecked and the GPU has nothing to do.

 

I've not changed any settings, it worked on Friday when I tested it, and now won't.

 

CPU was at 30%

(While in a level, laying on the floor, tabbed out to grab the screenshot. I think the spikes are from loading the game and loading the level)

Edited by DatBrummie
Adding more info

 

 

Link to post
Share on other sites

GPU-Z can show what kind of limit the GPU is hitting that is blocking it from boosting. Check that out.

HAL9000: AMD Ryzen 9 3900x | Noctua NH-D15 chromax.black | 32 GB Corsair Vengeance LPX DDR4 3200 MHz | Asus X570 Prime Pro | ASUS TUF 3080 Ti | 1 TB Samsung 970 Evo Plus + 1 TB Crucial MX500 + 6 TB WD RED | Corsair HX1000 | be quiet Pure Base 500DX | LG 34UM95 34" 3440x1440

Hydrogen server: Intel i3-10100 | Cryorig M9i | 64 GB Crucial Ballistix 3200MHz DDR4 | Gigabyte B560M-DS3H | 33 TB of storage | Fractal Design Define R5 | unRAID 6.9.2

Carbon server: Fujitsu PRIMERGY RX100 S7p | Xeon E3-1230 v2 | 16 GB DDR3 ECC | 60 GB Corsair SSD & 250 GB Samsung 850 Pro | Intel i340-T4 | ESXi 6.5.1

Big Mac cluster: 2x Raspberry Pi 2 Model B | 1x Raspberry Pi 3 Model B | 2x Raspberry Pi 3 Model B+

Link to post
Share on other sites

10 hours ago, jj9987 said:

GPU-Z can show what kind of limit the GPU is hitting that is blocking it from boosting. Check that out.

 

I tried that, I couldn't see any kind of thing that could be stopping it? 

Screenshot is taken shortly after playing a little bit of a single player level, so the time graphs would be accurate.

The only thing even close to the top is the GPU load, which surely you'd expect and the clock should ramp up to meet the load? 

It's not hitting a voltage or a temperature limit, as shown in the previous screenshots as while playing any other game the temperature and voltage both get to a higher point.

 

The weird thing is, it worked absolutely fine over the weekend of release, and for a few days earlier this week. Then I tried playing the game, and this issue occurred, but I didn't know this was the problem I just noticed bad FPS. Then the game crashed so I left it for a bit. When I went back on later that night, it worked absolutely fine.

I left it alone again until the day after, and I had the problem again. 

On Friday I did a driver update and restarted my PC, it worked, but then trying it earlier today it didn't work. And trying it now, with GPU-Z running, and after restarting. It's having the same issue.

 

I'm not sure what it could be as I've not changed anything like I said.

 

EDIT:

For reference here's what GPU-Z looks like during a game of CS

Edited by DatBrummie

 

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×