Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
its lucky to have made it this long
running the lower res might not have stressed the 6600 as much as the 1660s
different gpu, different games = different load on psu
There can be other reasons, of course. My second guess would be a faulty brand new GPU, it could happen. Test the GPU on another system, test your system with another GPU... To really test a GPU, run FurMark or any other kind of software that pushes your video card to its limits. Possible issues with your video card: GPU chip being broken (v unlikely), one memory module broken, a resistor being faulty, VRM faulty, a capacitor being faulty (most likely).
Nothing to add. I did nothing besides what I already posted and the issues remain the same.
Yes, I'm working on that to eliminate that factor. I already tried stressing out the GPU with Furmark. I detected no problem.
Already tried. Although I may have not done that right (I'm sort of a cave man). A quick guide on that would be great if anyone can.
------------------------------
I read a comment searching on the web from another couple guys that had the exact same issue but my english is not good enough to catch up with that specific language. Apparently they had a problem with the RAM cards. As far as I understood, one of them had it uncorrectly plugged on the socket. The second guy read that and discovered he had the same problem. Could that be a thing?
OCCT has a "GPU variable" test. When I was having issues with my GPU, that was the test that tripped it most (and it didn't even always). If that failed, Furmark (or a game) along with a hardware accelerated browser that I was actively in would also usually trip it before long.
Just adding those as scenarios to possible try.
Reseat your RAM. Is it possible it got unsettled when changing the video card?
I'd also run tests on it with MemTest86.
Great, I'll look into that.
Can technically under volt the gpu in msi afterburner.
Does playing less stressful games with the fps capped crash the system?
OCCT showed no errors. I checked both RAMs and they don't seem badly plugged although I'm no expert here. Couldn't make MemTest86 run. I don't understand how to do it.
Did that. No good. The only game that I can play with no problem is League of Legends at 300+ fps. Everything else crashes.I'm not sure what a "less stressful game" could be given that, for example, SOD 2 with the lowest possible set up is basically minecraft.
The main point here is that GPU goes to 100% even on the menu, before it starts loading stuff and rendering graphics inside the actual game. This is true, again, for everything, except Grounded. For some strange reason I can play that on ultra for like half an hour (GPU between 30 and 40%) before it suddenly spikes and goes off for no apparent reason that I can discern.
fps higher than refresh rate will have multiple tear lines, more than one frame composing of a displayed frame
new vsync, will force the gpu to idle after a frame is completed before sending it to the display
vsync off, sends the latest frame data to the display as they are drawn
it may complete 2 frames between refreshes and just display the latest completed one, dropping previous frame