Low FPS in Borderless after crash

Juusuhako

New member
I was playing some Diablo 3 when I started getting weird graphical glitches. I noticed in Geforce Experience that my driver was an old one, even though I've just formated yesterday and installed latest drivers for everything. Somehow it had downgraded itself...

So I installed the new driver and everything was fine. A couple of hours later, my PC froze. I didnt think much of this as a random freeze can happen to anyone and there can be a ton of reasons for it.

Problem now is I cant play the game in Borderless without dropping to 30-40FPS, whereas it before the crash would run at +60. I've tried reinstalling the game (by dragging all the data from an external, as I cannot be bothered downloading 15Gig), this didnt help.

I have an 3570K running 4.3gHz, 8GB Ram and a 295GTX.

Edit:
Same thing is going on in League of Legends; a game I usually run +200fps. In borderless its at 40ish...
 
Last edited:
Did you clean out the old drivers before installing the new ones?

i.e. uninstall, reboot, reboot in safe mode, driverclean, reboot, install custom and only install drivers manually etc ?
 
Did you clean out the old drivers before installing the new ones?

i.e. uninstall, reboot, reboot in safe mode, driverclean, reboot, install custom and only install drivers manually etc ?

even though I've just formated yesterday and installed latest drivers for everything.


though i would follow Sub's advice and clean out the drivers and start again.
 
Waiting for D3 to be done downloading. For some reason this time it needs to download 5.5GB even though the Data folder I've been using is only a week old (hence all files should be up to date and playable right away). Not sure if its because I decided to install it in "Program Files" (rather than (x86)) and it needs 64bit files now.

Anyways, it game should be "Playable" after only downloading 1gig or so, and them im gonna try and see.

I used Display Driver Uninstaller (found it on Guru3d) in safe mode, and reinstalled the latest driver afterwards.

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

Things seem to be running fine now. The driver hadnt downgraded after the crash; it was before it (im guessing after I shut it off yesterday). I guess installing the new driver via Experience left some trash behind, hence the freeze crash, hence why it all became messy in the end.

I've never used the safe mode method for every new driver, I always let Experience handle it and havent had an issue. Not sure why a driver would downgrade itself automatically.

Anyways, thank you.
 
Last edited by a moderator:
PC froze again, had to reboot. When I got into Windows I no longer had a signal from HDMI (tried both gpu and mobo output). Had to uninstall driver again using safe mode, and reinstall it to get a signal.

Ran a GPU benchmark for 30minutes, no problem. Dont wanna risk running a PSU stress test as I've read some saying it can ruin it.

Not really sure what to make of this. Everything in my old setup worked fine (E8500, 8GB, 295GTX). But with the new setup its been with flaws from the very start (3570k, 8GB, 295GTX, brand new motherboard). The CPU and Ram blocks were bought used, but I did do an OCCT test that ran for 30mins (after overclocking), and it didnt freeze or anything.

Does anyone have the distinct idea of what could be going on?
 
Not sure if its because I decided to install it in "Program Files" (rather than (x86)) and it needs 64bit files now.

The Program Folder x86 is for 32bit applications. The non x86 is for the 64bit files. So it shouldn't be downloading anymore 64bit files unless its missing data( just moving the files from the folder won't move absolutely everything) so it just redownloaded them.
 
Back
Top