#losing 150 fps

1 messages · Page 1 of 1 (latest)

vernal rampartBOT
spare python
#

Run 3DMark and show the results here.

#

Then we can determine if your computer is running correctly. That'll determine what to do next.

meager roost
#

alr

meager roost
#

its downloading

meager roost
#

@spare python

#

which 1 do i run

#

benchmark?

#

uh

#

the game i lost all fps is fornite bc i used to get around 200 to 300 now i get stuttering and barley 150 fps even dropping under 100. and all this happend after the update

#

Its either the game driver or windows update but it cant be windows update that cooked my pc bc i reveerted that and reset pc and still same shit fps. so it has to be the game driver

#

maybe should i try a clean install and if that doesnt work then i roll back to the older version?

spare python
# meager roost
  • Something else appears to be running while 3DMark is running. For the most accurate benchmark results, make sure anything else in the background isn't running or open.
  • It looks like you're using a stretched resolution on the desktop for some reason. Be aware that this will distort everything.
  • 3DMark does indicate that your computer is running correctly at least for short benchmark runs, so let's follow up with thermal checks and stuff
vernal rampartBOT
spare python
#

Get HWINFO from here, then run it. When prompted, pick "Sensors-only", and let it open fully.

Once it opens, screenshot everything. You'll need to scroll and take multiple screenshots, then upload all of them here.

Once uploaded, leave HWINFO's windows open for a bit longer. Don't close or reset anything.

Run 3DMark's suggested benchmark, Steel Nomad, again. Once that is done and you see the results screen again, get HWINFO's stats again. The same amount of data applies

meager roost
#

Here

meager roost
meager roost
#

@spare python

hazy wolf
#

Why am I pinged.

spare python
#

Also: you can screenshot a window by ALT-Print Screren keys

#

This will immediately put the window inside your clipboard

#

This image will be pastable directly into Discord

meager roost
spare python
# meager roost

Did you close HWINFO since running the 3DMark? These stats indicate that no heavy load was run

#

To clarify, do the following in order.

meager roost
#

I had it open for 2 hrs

#

then closed

spare python
meager roost
#

It showed 1 error maybe thats the reason

spare python
#

Let's start over

#

Do it in exactly this order.

meager roost
#

Hardware error

#

I also did a clean install of the driver and changed to 1 older

spare python
#
  • Open 3DMark.
  • With the 3DMark window still open, open HWINFO.
  • Open HWINFO in sensors-only mode (you already know this.)
  • Once this window is open, start a 3DMark benchmark. DO NOT CLOSE HWINFO windows.
  • Let 3DMark's benchmark finish running.
  • 3DMark should show the benchmark result.
  • Screenshot the contents of HWINFO now. Do not close or clear anything. You'll notice that the GPU usage should now have much higher values in the "Max" columns.
spare python
spare python
meager roost
#

K

spare python
#

If you've just recently installed drivers, restart your PC first, then do the listed steps

meager roost
#

Alr

spare python
#

while we're at it: you're using the laptops' original charger or not?

meager roost
#

yes

#

But idk how all this solves the issue when its the driver that ruined my fps

#

Changing back to 1 older would fix it

#

561.09

#

The 565. 90 Is what ruined

spare python
#

Especially if it turns out the problem is with something else. Remember that 3DMark is indicating that your PC should run correctly at least for short term loads.

meager roost
#

Oh true

#

there

spare python
#

I don't see any cause for concern thermals-wise

#

If you can consistently reproduce the low FPS with only the new drivers while keeping the settings the same, you've likely found a bug or a specific problem with your laptop. Time to hit up NVIDIA's customer support (file a ticket there)

meager roost
#

hm yeah

#

imma see if i still have the problem on 561.09