Razer Blade 18 (2024) CS2 bad 1% lows and no way to fix it, after researching for weeks. | Razer Insider
Skip to main content
Question

Razer Blade 18 (2024) CS2 bad 1% lows and no way to fix it, after researching for weeks.

  • August 8, 2025
  • 1 reply
  • 89 views

EdwinWeber

Hello guys,

I hope I can find some support here, because I just can't believe it's an hardware issue or bad compatibility.
So as the title says, I have bad 1% low average FPS in CS2.

- I use CapFrameX and the well-known FPS Dust 2 Benchmark Map in CS2

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Here are my Specs, before I go deeper into the Issue:

Razer Blade 18 (2024):

Microsoft Windows 11 Home
Intel Core i9 14900HX - Cores 8P + 16E, Threads 32
GeForce RTX 4090 Laptop GPU - 16 GB, GDDR6 (Driver Version 566.14 - I read it's the best version for the 40 RTX Series, but I also tried newest Versions with no success)

Monitor: 300hz 2560x1600, G-Sync-Compatible
Mainboard: Razer KI8100
BIOS: Razer 1.04
Memory: Samsung DDR5 32GB

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

"By default, the Razer Blade 18 includes NVIDIA’s Advanced Optimus which automatically switches the laptop into discrete GPU mode when gaming, enabling the highest refresh rate available for your system. When not gaming, the refresh rate will be 240 Hz for the QHD+ (mini-LED) SKU and 120 Hz for the UHD+ SKU." - From the Razer Blade FAQ
- I have switched to dGPU in the BIOS, because I have read something about an FPS-Passthrough from the IGPU, which causes stutters and bad 1% lows, but it only improved by 3-4 FPS lows.

- I care about the temperature of my CPU and GPU, by buying an llano RGB Gaming Laptop Cooling Pad for 100 Euros, which supports 18'' Laptops and cools in max. 2800 RPM. It cools very well and I don't think I'm being thermal throttled.

- Recently, I tried to turn off HAGS, which supposedly creates stutters and instability (For CS2 atleast). It has improved my 1% lows (~100), after restarting and by changing settings in NVCP, it went back to (~60). Turning off Windows Game Mode, didn't change my 1% lows.

- I'm really not a fan of Razer Synapse and I have a bad feeling it's the main culprit of it all, but that's just my intuition, not coming from my knowledge. I tried the highest custom Performance-Mode, plus in-app build undervolt Core voltage offset -0.090 (not limit-tested yet) with no improvement.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- In NVCP, I tried many combinations, all include G-Sync ON, because G-Sync is supposed to be very good for competitive (lecture me if I'm wrong) (CS2/Steam launch options: fps_max 0, -noreflex, -allow_third_party_software)


1st Combination: V-Sync ON, Low Latency ON, Variable Refresh Rate 282 (took away 6% from my Monitor Refresh Rate) = ~270 Average FPS, ~60-80 FPS 1% lows

2nd Combination: V-Sync Fast, Low Latency ULTRA, Variable Refresh Rate 282 = ~270 Average FPS, ~60-90 FPS 1% lows

3rd Combination: V-Sync Fast, Low Latency ULTRA. = ~280 Average FPS, ~100 FPS 1% lows

4th Combination: V-Sync ON, Low Latency ON, Variable Refresh Rate 275 = ~272 Average FPS, ~100 FPS 1% lows

(5th Combination: tried these launch options, with the combinations above +fps_max -1 -noreflex -dx11 -forcepreload 1 +cl_forcepreload 1 -high -novid) = ~500 Average FPS, ~60 FPS 1% lows
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Conclusion: I just think the game is very bad optimized or I'm just coping and buying this Laptop was a mistake. If you see any mistakes I did or wrongs I said, please feel free to lecture me. I just want to play CS2 stable and without stutters, but also use my little competitive-advantage with 300 hz, if possible. I don't have a lot of knowlege in Benchmarking by the way, whatever I'm saying comes from different people with different opinions, which makes it hard for me to know, what's factual and what's not.

I will gladly add more information, if needed. I typed the details, I can remember now. Thank you for reading.

1 Reply

  • Insider Mini
  • September 16, 2025

Hi mate,

I found myself in the same boat and I have been doing a bunch of test to my system to see if I can remedy the issue. Just when it feels like I am gaining ground I am left with more questions than answers. 

That being said I experienced that certain games produced the low lows you were mentioning with the numerous variations of render settings applied. My control when testing was the display modes Optimus or Nvidia GPU only when applying settings. What I found is that depending on the game there was marginal improvements in results based off the games inclination to certain hardware. Source engine titles traditionally favour CPU rendering in older titles. Yet CS2 yields less average FPS  utilising Optimus. Also the consistent FPS lows remain regardless of the combination of video setting tweaks. Nvidia GPU only mode yielded similar results as Optimus but with the exception of higher average FPS.

Having no luck in source engine titles I moved my testing onto other titles feeling it had something to do CS2. I figured I would pick a close comparison in terms of engine performance. Quake Live and Quake Champions yielded similar results in regards to the low lows with the same control applied and rendering combinations applied respectively. But then, eureka. I found a personal remedy, being my mouse input handling method regardless of display control settings. Swapping my mouse input method to Direct input on both titles alleviated those dreaded low lows significantly.

Unfortunately CS2 and I believe CSGO are locked to raw input for one reason or the other. Raw input seemed to respond unfavourably to my systems peripherals. Disabling my touchpad and unplugging my mouse yielded less low lows suggesting that the issue was based in the processing of the input peripherals utilising raw input.

I hope this solution can help you with your issue. Oh and my NVCP settings were set to the defaults. Here are my system specs:

Razer Blade 18 (2024):

Microsoft Windows 11 Home
Intel Core i9- 13950HX - 24 Cores / 32 Threads
GeForce RTX 4080 Laptop GPU - 12 GB, GDDR6 (Driver Version 580.88)
Monitor: 240hz 2560x1600, G-Sync-Compatible
Memory: DDR5 32GB.

 

I probably will not check back here so I am sorry if I do not respond to any questions.

All the best.