Hardware & Technical Graphics card trouble

Update:
last night I updated windows and that seems to have mostly fix the problem. GTA V is working great now, Elite is updating so I’ll report back on it shortly. The graphics card fan is cranking up just like before when under load.

That was the weirdest thing ever, I don’t know how this issue happened lol.

I want to sincerely thank everyone who replied. I really appreciate you all taking the time to help me with this. I am rather computer illiterate.
I'm glad it resolved itself. As much as computers are high precision machines, sometimes they act like they have mind of their own. And it can be hard to figure out what's happening.
I've spent few weeks troubleshooting my GPU. Driver was crashing. I thought it was unstable clock. Nope. Overclocked, or not it kept crashing. Updating drivers didn't help, rolling back drivers didn't help. I thought power delivery was causing this - I've tried everything. I even changed a PSU I was so sure it was causing instability. Nothing helped. Then it just...went away. I was pulling my hair out, to this day I don't know what it was. It's been over a year, and it works perfectly. Sometimes a part of your PC just decides to take a day or two off :)
 
Update:
last night I updated windows and that seems to have mostly fix the problem. GTA V is working great now, Elite is updating so I’ll report back on it shortly. The graphics card fan is cranking up just like before when under load.

That was the weirdest thing ever, I don’t know how this issue happened lol.

I want to sincerely thank everyone who replied. I really appreciate you all taking the time to help me with this. I am rather computer illiterate.
Is it possible that you are using the same set up that you had on a less demanding GPU before installing the current one? E.G., had a 970 installed then swapped it out for a 2080 with the same case fans, PSU and ventilation?
 
Update:
last night I updated windows and that seems to have mostly fix the problem. GTA V is working great now, Elite is updating so I’ll report back on it shortly. The graphics card fan is cranking up just like before when under load.

That was the weirdest thing ever, I don’t know how this issue happened lol.

I want to sincerely thank everyone who replied. I really appreciate you all taking the time to help me with this. I am rather computer illiterate.
You also make awesome videos.
OOOPS I mean Threeofnine
Source: https://www.youtube.com/watch?v=1jnG0FMAPao
 
Last edited:
Ha, a long time indeed! :LOL:
I remember waiting for the Voodoo Banshee just to avoid having to put up with double cards and pass through (not enough space in the pc at the time), then when I finally had the money there came the Voodoo 3. What a glorious card that was.
Damn, 21 years...

Happy to hear everything seems back in order again @Threeofseven !

The Diamond Monster 3D, it worked surprisingly well, and the ooh's and aah's during our first Quake multiplayer session after getting it installed, the colours, the lights the....everything....!

And on a 15" CRT monitor.

Happy for the OP as well, probably some driver corruption, strange things still happen even after all these years of vidoe card makers trying to get things right!
 
Update:
last night I updated windows and that seems to have mostly fix the problem. GTA V is working great now, Elite is updating so I’ll report back on it shortly. The graphics card fan is cranking up just like before when under load.

That was the weirdest thing ever, I don’t know how this issue happened lol.

I want to sincerely thank everyone who replied. I really appreciate you all taking the time to help me with this. I am rather computer illiterate.
Excellent !

And Windows always faithful to its reputation since decades.

:)
 
Update:
last night I updated windows and that seems to have mostly fix the problem. GTA V is working great now, Elite is updating so I’ll report back on it shortly. The graphics card fan is cranking up just like before when under load.

That was the weirdest thing ever, I don’t know how this issue happened lol.

I want to sincerely thank everyone who replied. I really appreciate you all taking the time to help me with this. I am rather computer illiterate.
glad you got yourself sorted..... sometimes computers can infuriate the hell out of you and it does not matter if you are computer savvy or not.

I would say I am a tinkerer, and generally find my way through trial and error and am definitely not expert. funnily enough just 3 nights ago i was on the verge of ripping out my M2 SSD and installing windows on an old hdd to see if something was broke. My USB devices were all over the place, my wheel would not initialise, i could not click on icons on my desktop and the desktop kept briefly flikering. I unplugged all the devices from the back of pc which is in and of itself a pain to get at, put back in and no joy

rebooted multiple times, task manager was showing my CPU occupancy was all over the place going from 0% to 20% multiple times a second.

luckily just before i turned off and ripped apart, after ages messing about i noticed I had forgotten about my 2nd keyboard plugged into the front usb of my pc. (i cant reach my main keyboard when in my flight/driving seat and in VR, so have a small keyboard mounted next to me)..... and it seems i had taken my oculus rift off and put it ontop of the keboard and one of the keys - alt or control - had gotten stuck down. Fixed this and problem solved.
 
My bet is that something on windows registry went array.

Yo may have installed a software that made some changes to the registry, and it ed your graphics card settings.
Sadly, unless you know PRECISELY what registry caused that, an revert it, there is no practical way to fix it.
Windows registry ain't called the HIVE for nothing.

Luckily for you, the update seem to have put things straight again. :)

Next time something like this happens, it might be worthy to open the command console ("cmd" on the search engine in the task bar) and enter a "chkdsk" command.
This command will check your windows files, and repair files that are either missing, changed or corrupted
. :)

Aken corrected me, so it might be better to follow his advice. :)
 
Last edited:
Excellent !

And Windows always faithful to its reputation since decades.

:)

Honestly and to be fair, any OS can sometimes go full clown mode. And I know since now I can say that I work with Linux, Mac OS and Windows.

The difference between windows and the other 2 OS's, is that unlike Linux it allows for some error margin, (anything you do in Linux is DEFINITIVE, no going back, unless you do so manually). And unlike Mac, it allows you to tinker and tamper with it.
 
Last edited:
Honestly and to be fair, any OS can sometimes go full clown mode. And I know since now I can say that I work with Linux, Mac OS and Windows.

The difference between windows and the other 2 OS's, is that unlike Linux it allows for some error margin, (anything you do in Linux is DEFINITIVE, no going back, unless you do so manually). And unlike Mac, it allows you tinker and tamper with it.
Yes, I was mainly joking..

Windows is a good system.

It accompanies us for decades.

:)
 
Next time something like this happens, it might be worthy to open the command console ("cmd" on the search engine in the task bar) and enter a "chdsk" command.
This command will check your windows files, and repair files that are either missing, changed or corrupted. :)

Sorry in advance but that's just my professional bias kicking in. 🤓
The correct syntax is "chkdsk", it doesn't check your windows files but the general integrity of the entire filesystem. Best used with a "/f" parameter to just check and eventually fix filesystem errors (wrong table allocation, corrupted/truncated volumes and such). You can use "/r" to perform a more thorough search for physical damages to sectors, but it will take a good while.

The Windows file checking Remus refers to is best done via the "sfc /scannow" command. It does a complete check of all critical windows files and replaces them with their correct version if found missing and/or corrupted.
(It may not always work via command line from an active Windows session, there's a more complete command to be executed via recovery console but I think it's not relevant for the topic at hand).
 
Sorry in advance but that's just my professional bias kicking in. 🤓
The correct syntax is "chkdsk", it doesn't check your windows files but the general integrity of the entire filesystem. Best used with a "/f" parameter to just check and eventually fix filesystem errors (wrong table allocation, corrupted/truncated volumes and such). You can use "/r" to perform a more thorough search for physical damages to sectors, but it will take a good while.

The Windows file checking Remus refers to is best done via the "sfc /scannow" command. It does a complete check of all critical windows files and replaces them with their correct version if found missing and/or corrupted.
(It may not always work via command line from an active Windows session, there's a more complete command to be executed via recovery console but I think it's not relevant for the topic at hand).


OH! My bad!


You are of course correct! I blame my keyboard!

I'll correct my post accordingly.
 
Sorry in advance but that's just my professional bias kicking in. 🤓
The correct syntax is "chkdsk", it doesn't check your windows files but the general integrity of the entire filesystem. Best used with a "/f" parameter to just check and eventually fix filesystem errors (wrong table allocation, corrupted/truncated volumes and such). You can use "/r" to perform a more thorough search for physical damages to sectors, but it will take a good while.

The Windows file checking Remus refers to is best done via the "sfc /scannow" command. It does a complete check of all critical windows files and replaces them with their correct version if found missing and/or corrupted.
(It may not always work via command line from an active Windows session, there's a more complete command to be executed via recovery console but I think it's not relevant for the topic at hand).
Good old CHKDSK !

Happy days !

:)
 
It surely was your keyboard! Mischievous gadgets, aren't those. :LOL:
Just professional bias as I said, that's exactly the kind of low-level stuff I do on an almost daily basis.
 
And far more powerful at that. (y)
Its main flaw is that I'll never, ever remember its command parameters. I have to look up at them each and every time for some reason. 😅
 
Back
Top Bottom