Claude Code Investigates Gaming Laptop Stutter: Power, Heat and Windows Update

The setup: a laptop that should have been fine​

Abidi's machine is an HP Omen Transcend 14 with an 8GB GeForce RTX 4060, 16GB of RAM and a Core Ultra 7 155H. On paper, that should handle the game he was testing, which he calls FC27. He had already given up on adjusting its graphics settings. He also recalls that the previous edition, FC26, ran in slow motion on the same laptop whatever graphics settings he chose.

Those hardware and symptom details come from his account. They are not independently verified measurements.

What Claude Code reportedly found​

According to Abidi, Claude read the logs from his most recent session and flagged four overlapping problems:

• Power: the charger had cut out at some point during play.
• Background activity: Windows Update had been installing during the final 10 minutes.
• Thermals: the CPU reached 105°C and began throttling.
• Game and display settings: there was no frame-rate cap, V-Sync was off, and dynamic resolution was targeting 60 FPS on a 120Hz monitor.

Abidi says this changed the question from "why won't the game run?" to "why isn't the laptop delivering consistent performance?" None of the four problems is a graphics preset. That is why fiddling with the graphics menu got him nowhere.

He is also careful not to overclaim. Several of these things happened at the same time, so he says he would not treat the findings as proof that each contributed equally to the stutter.

The fixes, in order​

1. Back up first. Claude copied the game's fcsetup.ini before touching it. That gives a known-good file to restore if an edit goes wrong.
2. Cap the frame rate. It set a 120 FPS cap to match the 120Hz display.
3. Turn off dynamic resolution.
4. Leave the rest alone. Abidi says the game reported that it fit in his VRAM at its default High preset.
5. Change the OEM performance mode. Abidi switched the laptop to Performance mode in OMEN Gaming Hub himself.

He stresses that the Gaming Hub mode is not the same thing as the Windows power plan. The two can govern overlapping hardware behaviour under different limits. A laptop set to a high-performance Windows plan can still be held back if the manufacturer utility is on a balanced or power-saving profile.

HP's own community guidance points the same way, though it is forum and knowledge-base material, not a diagnosis of this laptop. An HP knowledge-base post on stuttering says to open the Performance Control section in OMEN Gaming Hub and switch to Performance mode, which allocates power dynamically between CPU and GPU. A community answer on another Omen model suggests setting the Windows power plan to High Performance and picking Performance Mode instead of Balanced in Omen Gaming Hub. The same HP guidance also advises keeping OMEN Gaming Hub updated.

Performance mode is not a guaranteed win, either. Some owners report the opposite. One Ryzen laptop owner on AMD's forum said balanced mode ran fine in games while performance mode brought back low FPS and stuttering. Another user suggested that thermal throttling could be the cause there. Those are anecdotes, but they show the profile is something to test and not assume.

The result, and why to read it cautiously​

After the changes, Abidi reports a much smoother session. Frame rate stayed between 60 and 70 FPS, and the temperature peak fell to 101°C from the 105°C seen earlier.

There are real limits on what this shows:

• No before-and-after average frame rate is given.
• Several variables changed at once, so no single edit can take the credit.
• The article does not say how temperatures were measured, over what duration, or in what room conditions.
• The runs were not repeated.
• A 120 FPS cap on a 120Hz panel is his choice, not a universal prescription. His laptop sat at 60 to 70 FPS, so the cap was not the limiting factor.

Abidi says as much himself. A lower peak temperature and a smoother feel do not by themselves establish an FPS gain.

Other games and the projector​

Claude reportedly gave tailored advice for other setups too:

• Aurzen projector: use 60Hz with either a 60 FPS cap or V-Sync, so the in-game settings match the display in use.
• Assetto Corsa: Abidi runs Custom Shaders Patch and the Sol weather mod. Claude noted that editing the base video.ini would not cover everything, so it proposed capping frame rate at the monitor's refresh rate for steadier performance and lower temperatures.
• Counter-Strike 2: Claude suggested enabling Nvidia Reflex to improve responsiveness. Abidi says he did not notice an improvement as clear as in FC27, after nearly a decade of tuning that game himself.

These are reported suggestions and one user's subjective impressions, not tested recommendations for every system.

Using Claude Code on Windows​

Anthropic's documentation says Claude Code is a terminal tool... more precisely, its setup page lists Windows 10 1809 or later or Windows Server 2019 or later among supported systems. It can be installed natively on Windows from PowerShell or CMD, or inside WSL. Git for Windows is optional but recommended so Claude Code can use its Bash tool; without it, the tool uses PowerShell. Claude Code also needs an internet connection and a Pro, Max, Ultra, Team, Enterprise or Console account, and the free claude.ai plan does not include it.

Abidi does not say how he installed or ran it, so none of that describes his setup.

On safety, the CLI reference describes permission modes and a flag that skips permission prompts. That flag is the one to avoid when the tool is pointed at your game files. Reviewing each proposed edit, as with the fcsetup.ini backup, is a sensible habit.

A cautious workflow you can reuse​

The value in this story is the method, not the particular tweaks. Whether you use an AI assistant or do it by hand:

1. Check the basics first. Confirm the laptop is plugged in with its original charger, and note whether Windows Update or other background tasks overlap with play.
2. Watch temperatures and throttling. Use a monitoring overlay or the OEM's tool. HP's knowledge base points to the System Vitals feature in OMEN Gaming Hub for CPU/GPU usage and temperatures.
3. Record the starting values. Note frame cap, V-Sync, dynamic resolution and the OEM performance profile before changing anything.
4. Back up config files. Copy any file before editing it.
5. Change one thing at a time where you can. Repeat the same in-game segment each time and compare frame-rate behaviour and temperatures.
6. Match the display. Set caps and sync options for the screen you are actually using, whether that is a 120Hz laptop panel or a 60Hz projector.

The takeaway​

Claude Code did not find a hidden setting. Abidi's own conclusion is that it connected problems he would otherwise have chased separately. He also says he has not yet tried it on his most demanding games.

Treat AI suggestions as hypotheses to check. With a laptop that stutters, the culprit may be the charger, a background update or a thermal limit as much as the graphics menu.