Strange Screen Corruption With 1080 TI
  1 / 3    
Hi folks, I have an MSI Gaming X 1080TI for couple of months. Last week I had a strange screen corruption while playing Destiny 2 after alt tabbed. I tried turning the screen off and on but then I got "no signal" on monitor. I had to reset and everything went back to normal. Today I had the exact same corruption right after I started Wolfenstein II. I managed to capture the corruption this time with my phone. https://youtu.be/ddVd3ZkUsQ8 After restarting the PC, everything again went back to normal. But right now I'm kind of worried. I'm on the latest driver by the way (390.65). Last week I was on the previous driver (388.71). I always DDU before installing a new driver. Anyone has an idea what might cause this? Is it a faulty graphics card? Or can it be caused by DSR or anything else? Best Update (8/4/08): Today. It happened again. It happened right after I alt tabbed while playing Vermintide 2. So it's the fifth time in the last five months. Roughly happens once a month. Now it's pretty safe to say that, it happens either right after launching a game, exiting a game or alt tabbing a game. So the problem happens in the transition between games and desktop. That's pretty clear. It's not about temperatures, load or anything else. That's all I can say about it for now. So reinstalling the Windows might solve it maybe? The new Spring update is also on its way so maybe it's better wait for it do a clean install. What are your suggestions? Update (14/03/08): Today I had this problem once again right after quitting Warhammer: Vermintide 2. I am almost certain that the issue either happens right after starting a game or quitting a game. While playing games or doing something else, the problem never happens. But since it happened only 4 times in the last 3 months it's just impossible to recreate. I played tons of games in meantime. Now i am on 391.05. But looks like the culprit is not the driver version. Or maybe something is changed after a certain driver which triggers this problem from time to time on my system. System Specs: i7 4770K MSI z87 GD65 motherboard (BIOS 1.C) 2X8 GB Corsair Vengeance 1866 (xmp) DDR3 RAM EVGA Supernova G2 750W PSU Viewsonic XG2401 monitor Windows 10 Pro (1709- 16299.192) Onboard Sound Card
Hi folks,

I have an MSI Gaming X 1080TI for couple of months. Last week I had a strange screen corruption while playing Destiny 2 after alt tabbed.

I tried turning the screen off and on but then I got "no signal" on monitor.

I had to reset and everything went back to normal.

Today I had the exact same corruption right after I started Wolfenstein II. I managed to capture the corruption this time with my phone.


https://youtu.be/ddVd3ZkUsQ8


After restarting the PC, everything again went back to normal. But right now I'm kind of worried.

I'm on the latest driver by the way (390.65). Last week I was on the previous driver (388.71). I always DDU before installing a new driver.

Anyone has an idea what might cause this? Is it a faulty graphics card? Or can it be caused by DSR or anything else?

Best


Update (8/4/08): Today. It happened again. It happened right after I alt tabbed while playing Vermintide 2. So it's the fifth time in the last five months. Roughly happens once a month.

Now it's pretty safe to say that, it happens either right after launching a game, exiting a game or alt tabbing a game. So the problem happens in the transition between games and desktop. That's pretty clear.

It's not about temperatures, load or anything else.

That's all I can say about it for now.

So reinstalling the Windows might solve it maybe? The new Spring update is also on its way so maybe it's better wait for it do a clean install.

What are your suggestions?



Update (14/03/08): Today I had this problem once again right after quitting Warhammer: Vermintide 2.

I am almost certain that the issue either happens right after starting a game or quitting a game. While playing games or doing something else, the problem never happens.

But since it happened only 4 times in the last 3 months it's just impossible to recreate. I played tons of games in meantime.

Now i am on 391.05. But looks like the culprit is not the driver version. Or maybe something is changed after a certain driver which triggers this problem from time to time on my system.


System Specs:

i7 4770K
MSI z87 GD65 motherboard (BIOS 1.C)
2X8 GB Corsair Vengeance 1866 (xmp) DDR3 RAM
EVGA Supernova G2 750W PSU
Viewsonic XG2401 monitor
Windows 10 Pro (1709- 16299.192)
Onboard Sound Card

#1
Posted 01/12/2018 10:46 PM   
I've seen this with a bad resume from hibernate, are you using Sleep? Hibernate?
I've seen this with a bad resume from hibernate, are you using Sleep? Hibernate?



In Memory of Chris "ChrisRay" Arthington, 1982-2010

Specs:
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX300 1000
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme

CPU:Intel Xeon x5670 @ 3.8Gz, Mainboard:Asus Rampage II Gene, Memory:24GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 680+ 4GB
Monitor:55" Thorn TV, Sound:Sony Muteki 7.1
SDD:Crucial MX200 250, HDD: 1TB Samsung Spinpoint F3
Case:NZXT Phantom 410, PSU:Corsair 620HX, OS:Windows 10
Cooler: ThermalRight TRUE Spirit 120M BW Rev.A

#2
Posted 01/13/2018 02:31 AM   
[quote="Sora"]I've seen this with a bad resume from hibernate, are you using Sleep? Hibernate?[/quote] Nope. They are both disabled. I just have the "turn off display" setting enabled, but at those moments display wasn't turned off. The reason I suspect from the DSR is; the corruption seems like something is wrong with the resolution. For the time being I disabled the DSR and waiting. The problem is impossible to replicate so I don't have any other choice it seems. Though I'm kind of sure that something I did is triggered this corruption. First time I alt tabbed from Destiny 2, and second time it happened right after I started a game. For long hours of gaming sessions nothing happened. Temperatures are all fine too.
Sora said:I've seen this with a bad resume from hibernate, are you using Sleep? Hibernate?


Nope. They are both disabled. I just have the "turn off display" setting enabled, but at those moments display wasn't turned off.

The reason I suspect from the DSR is; the corruption seems like something is wrong with the resolution. For the time being I disabled the DSR and waiting. The problem is impossible to replicate so I don't have any other choice it seems. Though I'm kind of sure that something I did is triggered this corruption. First time I alt tabbed from Destiny 2, and second time it happened right after I started a game. For long hours of gaming sessions nothing happened. Temperatures are all fine too.

#3
Posted 01/13/2018 12:25 PM   
Any ideas? Maybe you can get an idea of what would that be from driver team @ManuelGuzmanNV ?
Any ideas?

Maybe you can get an idea of what would that be from driver team @ManuelGuzmanNV ?

#4
Posted 01/15/2018 01:55 PM   
. [quote="supertrqmp"]Any ideas? [/quote] Try this and see if it still happens. If it does not, then you know it is DRIVER related. Download this [url=http://us.download.nvidia.com/Windows/387.92/387.92-desktop-win10-64bit-international-rs3-whql.exe]387.92[/url] driver Download [url=http://www.wagnardsoft.com/content/display-driver-uninstaller-ddu-v17075-released]DDU[/url] (get the 17.0.7.5 or NEWER) Disable the Windows 10 [url=https://www.tenforums.com/tutorials/48277-enable-disable-driver-updates-windows-update-windows-10-a.html]Driver updating[/url]. Need to apply the [color="orange"]Option 2 and 4[/color] .REG file. Search(runbox) > Msconfig > Boot(tab) > Boot Option> check the SAFE BOOT ... Apply and Reboot. Run DDU [.]Select: NVIDIA Software and drivers[/.] [.]Select: Clean, do not restart[/.] Search(runbox) > Msconfig > Boot(tab) > Boot Option> [color="orange"]Un[/color]check the SAFE BOOT ... Apply and Reboot. Back in normal Windows: Install the NVIDIA 387.92 driver [.]Select: Custom[/.] [.]Uncheck Everything except the GPU driver[/.] [.]Check the CLEAN INSTALL BOX[/.] [.]Finish the Install[/.] Reboot Im thinking Memory | Heat after that :) .
.

supertrqmp said:Any ideas?


Try this and see if it still happens. If it does not, then you know it is DRIVER related.


Download this 387.92 driver

Download DDU (get the 17.0.7.5 or NEWER)


Disable the Windows 10 Driver updating. Need to apply the Option 2 and 4 .REG file.

Search(runbox) > Msconfig > Boot(tab) > Boot Option> check the SAFE BOOT ... Apply and Reboot.

Run DDU
  • Select: NVIDIA Software and drivers
  • Select: Clean, do not restart

  • Search(runbox) > Msconfig > Boot(tab) > Boot Option> Uncheck the SAFE BOOT ... Apply and Reboot.


    Back in normal Windows:

    Install the NVIDIA 387.92 driver
  • Select: Custom
  • Uncheck Everything except the GPU driver
  • Check the CLEAN INSTALL BOX
  • Finish the Install
  • Reboot



    Im thinking Memory | Heat after that :)


    .

    My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

    Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

    ""Don't f with it if it ain't broken!""
    Constantly updating drivers is a good way to F'up the whole system.

    If the driver has an issue, don't be a fool, remove it.

    Just because you can, does not mean you should.

    #5
    Posted 01/15/2018 10:57 PM   
    The last major windows update did something to shutdown gui, that made it sleep or hibernate eventhough I turned that off. This would cause issues when I turned off my powerstrip. I don't remember the setting for sure but it could have been this [code] powercfg -qh . . Power Setting GUID: a7066653-8d6c-40a8-910e-a1f54b84c7e5 (Start menu power button) GUID Alias: UIBUTTON_ACTION Possible Setting Index: 000 Possible Setting Friendly Name: Sleep Possible Setting Index: 001 Possible Setting Friendly Name: Hibernate Possible Setting Index: 002 Possible Setting Friendly Name: Shut down Current AC Power Setting Index: 0x00000002 Current DC Power Setting Index: 0x00000000 . . [/code] If so, this might help (from a administrative command prompt) powercfg /qh scheme_current sub_buttons powercfg /setacvalueindex scheme_current sub_buttons UIBUTTON_ACTION 2 powercfg /setactive scheme_current I normally use the high performance power plan or scheme_min.
    The last major windows update did something to shutdown gui, that made it sleep or hibernate eventhough I turned that off. This would cause issues when I turned off my powerstrip.

    I don't remember the setting for sure but it could have been this

    powercfg -qh
    .
    .
    Power Setting GUID: a7066653-8d6c-40a8-910e-a1f54b84c7e5 (Start menu power button)
    GUID Alias: UIBUTTON_ACTION
    Possible Setting Index: 000
    Possible Setting Friendly Name: Sleep
    Possible Setting Index: 001
    Possible Setting Friendly Name: Hibernate
    Possible Setting Index: 002
    Possible Setting Friendly Name: Shut down
    Current AC Power Setting Index: 0x00000002
    Current DC Power Setting Index: 0x00000000

    .
    .




    If so, this might help (from a administrative command prompt)

    powercfg /qh scheme_current sub_buttons
    powercfg /setacvalueindex scheme_current sub_buttons UIBUTTON_ACTION 2
    powercfg /setactive scheme_current


    I normally use the high performance power plan or scheme_min.

    #6
    Posted 01/16/2018 06:57 AM   
    [quote="Greybear"] . [quote="supertrqmp"]Any ideas? [/quote] Try this and see if it still happens. If it does not, then you know it is DRIVER related. ... Im thinking Memory | Heat after that :) .[/quote] What's with the driver 387.92 btw? It's been a week and it never happened since I disabled the DSR. Though it happened 2 times in total anyway and there was exactly a week between them. If it happens again I'll just rollback to 387.92. I always use DDU like you explained, before installing a new driver. I don't think it's related to heat. Because; last time, it happened right after I started a game and the gpu was around 30C at that point. It barely reaches 70-72C while playing games for extended periods of times and never had an issue while playing a game. Both of the times it happened right after I did something (first time: alt tabbing - second time: starting a game) I'm not sure about memory though. Is there a way to test it? Also I had memory errors/ artifacts in the past and those weren't anything like that. In this case, games run normal but with that broken resolution, no weird artifacts going on. [quote="T-45 Goshawk"]The last major windows update did something to shutdown gui, that made it sleep or hibernate eventhough I turned that off. This would cause issues when I turned off my powerstrip. I don't remember the setting for sure but it could have been this [code] powercfg -qh . . Power Setting GUID: a7066653-8d6c-40a8-910e-a1f54b84c7e5 (Start menu power button) GUID Alias: UIBUTTON_ACTION Possible Setting Index: 000 Possible Setting Friendly Name: Sleep Possible Setting Index: 001 Possible Setting Friendly Name: Hibernate Possible Setting Index: 002 Possible Setting Friendly Name: Shut down Current AC Power Setting Index: 0x00000002 Current DC Power Setting Index: 0x00000000 . . [/code] If so, this might help (from a administrative command prompt) powercfg /qh scheme_current sub_buttons powercfg /setacvalueindex scheme_current sub_buttons UIBUTTON_ACTION 2 powercfg /setactive scheme_current I normally use the high performance power plan or scheme_min. [/quote] Thanks, I will try that as well if that happens again. I'm on balanced power plan but sleep and hibarnate seems disabled.
    Greybear said:
    .

    supertrqmp said:Any ideas?


    Try this and see if it still happens. If it does not, then you know it is DRIVER related.

    ...

    Im thinking Memory | Heat after that :)


    .


    What's with the driver 387.92 btw?

    It's been a week and it never happened since I disabled the DSR. Though it happened 2 times in total anyway and there was exactly a week between them. If it happens again I'll just rollback to 387.92. I always use DDU like you explained, before installing a new driver.

    I don't think it's related to heat. Because; last time, it happened right after I started a game and the gpu was around 30C at that point. It barely reaches 70-72C while playing games for extended periods of times and never had an issue while playing a game. Both of the times it happened right after I did something (first time: alt tabbing - second time: starting a game)

    I'm not sure about memory though. Is there a way to test it? Also I had memory errors/ artifacts in the past and those weren't anything like that. In this case, games run normal but with that broken resolution, no weird artifacts going on.

    T-45 Goshawk said:The last major windows update did something to shutdown gui, that made it sleep or hibernate eventhough I turned that off. This would cause issues when I turned off my powerstrip.

    I don't remember the setting for sure but it could have been this

    powercfg -qh
    .
    .
    Power Setting GUID: a7066653-8d6c-40a8-910e-a1f54b84c7e5 (Start menu power button)
    GUID Alias: UIBUTTON_ACTION
    Possible Setting Index: 000
    Possible Setting Friendly Name: Sleep
    Possible Setting Index: 001
    Possible Setting Friendly Name: Hibernate
    Possible Setting Index: 002
    Possible Setting Friendly Name: Shut down
    Current AC Power Setting Index: 0x00000002
    Current DC Power Setting Index: 0x00000000

    .
    .




    If so, this might help (from a administrative command prompt)

    powercfg /qh scheme_current sub_buttons
    powercfg /setacvalueindex scheme_current sub_buttons UIBUTTON_ACTION 2
    powercfg /setactive scheme_current


    I normally use the high performance power plan or scheme_min.




    Thanks, I will try that as well if that happens again. I'm on balanced power plan but sleep and hibarnate seems disabled.

    #7
    Posted 01/16/2018 08:06 PM   
    . Sometimes, things appear correctly disabled, but you re-Enable. Save. Reboot. Re-Disable. Save. Reboot and they work correctly again. .
    .

    Sometimes, things appear correctly disabled, but you re-Enable. Save. Reboot. Re-Disable. Save. Reboot and they work correctly again.


    .

    My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

    Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

    ""Don't f with it if it ain't broken!""
    Constantly updating drivers is a good way to F'up the whole system.

    If the driver has an issue, don't be a fool, remove it.

    Just because you can, does not mean you should.

    #8
    Posted 01/17/2018 04:46 AM   
    I again had this issue today. It's the third time in a 45 days period. I launched Diablo 3 today, then immediately alt-tabbed to check something and had the exact issue. Driver was 390.65. DSR was disabled so now I'm sure it's not the cause. It's been more than a month, and in meantime I finished Assassin's Creed: Origins for example, and played some other games but didn't encounter this issue. I'm seriously wondering what can be the cause. I can confirm that this issue happens randomly but only if I start a game or alt-tab from a game. Not happening during a game or anything else. It's not related to temperature or something like that. It's almost impossible to reproduce the issue though. Now I DDU'd 390.65 and installed the latest 390.77 driver. Don't know if this will change anything. Anyone else got a similar thing before?
    I again had this issue today. It's the third time in a 45 days period. I launched Diablo 3 today, then immediately alt-tabbed to check something and had the exact issue. Driver was 390.65. DSR was disabled so now I'm sure it's not the cause.

    It's been more than a month, and in meantime I finished Assassin's Creed: Origins for example, and played some other games but didn't encounter this issue. I'm seriously wondering what can be the cause.

    I can confirm that this issue happens randomly but only if I start a game or alt-tab from a game. Not happening during a game or anything else. It's not related to temperature or something like that. It's almost impossible to reproduce the issue though.

    Now I DDU'd 390.65 and installed the latest 390.77 driver. Don't know if this will change anything.

    Anyone else got a similar thing before?

    #9
    Posted 02/11/2018 12:16 AM   
    I've seen this before, something very similar. It turned out to be a dying GPU. Use MSI Afterburner to underclock both the core and memory of the GPU by as much as you can. Go all the way. Run like that for some time and see if it happens again. If it does, it's safe to say it isn't that. Although there is still a possibility this is a memory corruption defect.
    I've seen this before, something very similar. It turned out to be a dying GPU.

    Use MSI Afterburner to underclock both the core and memory of the GPU by as much as you can. Go all the way. Run like that for some time and see if it happens again. If it does, it's safe to say it isn't that. Although there is still a possibility this is a memory corruption defect.

    CPU: i7 7700k 4.8Ghz GPU: GTX 1080 Ti STRIX OC Mobo: Asus Z270 Maximus IX Hero RAM: G-Skill Ripjaws V 32GB DDR4 3200Mhz C16 PSU: EVGA Supernova 850w Titanium Case: Coolermaster HAF X O/S: Windows 7 SP1 Ultimate x64

    #10
    Posted 02/11/2018 09:04 AM   
    [quote="DaRkL3AD3R"]I've seen this before, something very similar. It turned out to be a dying GPU. Use MSI Afterburner to underclock both the core and memory of the GPU by as much as you can. Go all the way. Run like that for some time and see if it happens again. If it does, it's safe to say it isn't that. Although there is still a possibility this is a memory corruption defect.[/quote] I do not know, but Afterburner | RTSS has been known to cause issue with NVIDIA GPU in some setups. I would suggest NVIDIA INSPECTOR to do the same thing as suggested. Several softwares that can cause issues: Firefox Quantum AfterBurner Corsair Link And DISPLAY enhancer (DisplayFusion and others) ================================ The last driver I am still recommending to people is 387.92. You may be having issues due to the driver incompatibility | Instability based on hardware setup | softwares used .... ================================ Then you might also try [url=https://forums.geforce.com/default/topic/1028579/geforce-drivers/green-flickering-after-drivers-388-13-workaround-solution-included-/post/5244648/#5244648]this[/url] .
    DaRkL3AD3R said:I've seen this before, something very similar. It turned out to be a dying GPU.

    Use MSI Afterburner to underclock both the core and memory of the GPU by as much as you can. Go all the way. Run like that for some time and see if it happens again. If it does, it's safe to say it isn't that. Although there is still a possibility this is a memory corruption defect.
    I do not know, but Afterburner | RTSS has been known to cause issue with NVIDIA GPU in some setups.

    I would suggest NVIDIA INSPECTOR to do the same thing as suggested.


    Several softwares that can cause issues:

    Firefox Quantum
    AfterBurner
    Corsair Link
    And DISPLAY enhancer (DisplayFusion and others)

    ================================

    The last driver I am still recommending to people is 387.92. You may be having issues due to the driver incompatibility | Instability based on hardware setup | softwares used ....



    ================================

    Then you might also try this



    .

    My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

    Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

    ""Don't f with it if it ain't broken!""
    Constantly updating drivers is a good way to F'up the whole system.

    If the driver has an issue, don't be a fool, remove it.

    Just because you can, does not mean you should.

    #11
    Posted 02/11/2018 04:46 PM   
    I would get away from the 390.xx drivers and see if that fixes the issue. Those drivers have not been going very well for a lot of people.
    I would get away from the 390.xx drivers and see if that fixes the issue. Those drivers have not been going very well for a lot of people.

    #12
    Posted 02/11/2018 06:31 PM   
    [quote="DaRkL3AD3R"]I've seen this before, something very similar. It turned out to be a dying GPU. Use MSI Afterburner to underclock both the core and memory of the GPU by as much as you can. Go all the way. Run like that for some time and see if it happens again. If it does, it's safe to say it isn't that. Although there is still a possibility this is a memory corruption defect.[/quote] Wouldn't it be more frequent or appear in different ways as well if it was a defect or a dying gpu? I mean it happened 3 times in the last 45 days (first 2 of them in a 2 weeks period) and every single time it happened either right after I start a game or I alt-tabbed from the game. I've played very long hours of AC Origins, Wolfenstein TNC, Shadow of War, Civilization 6 and some other games in this period but nothing ever happened during a game. So setting the clocks lower won't help to pinpoint the issue. I can't use the gpu like that for a month. It's not reproduceable at all at the moment.
    DaRkL3AD3R said:I've seen this before, something very similar. It turned out to be a dying GPU.

    Use MSI Afterburner to underclock both the core and memory of the GPU by as much as you can. Go all the way. Run like that for some time and see if it happens again. If it does, it's safe to say it isn't that. Although there is still a possibility this is a memory corruption defect.


    Wouldn't it be more frequent or appear in different ways as well if it was a defect or a dying gpu?

    I mean it happened 3 times in the last 45 days (first 2 of them in a 2 weeks period) and every single time it happened either right after I start a game or I alt-tabbed from the game.

    I've played very long hours of AC Origins, Wolfenstein TNC, Shadow of War, Civilization 6 and some other games in this period but nothing ever happened during a game.

    So setting the clocks lower won't help to pinpoint the issue. I can't use the gpu like that for a month. It's not reproduceable at all at the moment.

    #13
    Posted 02/11/2018 07:14 PM   
    [quote] I do not know, but Afterburner | RTSS has been known to cause issue with NVIDIA GPU in some setups. I would suggest NVIDIA INSPECTOR to do the same thing as suggested. Several softwares that can cause issues: Firefox Quantum AfterBurner Corsair Link And DISPLAY enhancer (DisplayFusion and others) ================================ The last driver I am still recommending to people is 387.92. You may be having issues due to the driver incompatibility | Instability based on hardware setup | softwares used .... ================================ Then you might also try [url=https://forums.geforce.com/default/topic/1028579/geforce-drivers/green-flickering-after-drivers-388-13-workaround-solution-included-/post/5244648/#5244648]this[/url] .[/quote] I will definitely roll back to 387.92 if it happens again on the latest driver. First time it happened I was on 388.71. Also Afterburner is installed but it's not starting with Windows. I just use it every now and again if I want to test something or to see OSD stuff.
    I do not know, but Afterburner | RTSS has been known to cause issue with NVIDIA GPU in some setups.

    I would suggest NVIDIA INSPECTOR to do the same thing as suggested.


    Several softwares that can cause issues:

    Firefox Quantum
    AfterBurner
    Corsair Link
    And DISPLAY enhancer (DisplayFusion and others)

    ================================

    The last driver I am still recommending to people is 387.92. You may be having issues due to the driver incompatibility | Instability based on hardware setup | softwares used ....



    ================================

    Then you might also try this



    .


    I will definitely roll back to 387.92 if it happens again on the latest driver. First time it happened I was on 388.71.

    Also Afterburner is installed but it's not starting with Windows. I just use it every now and again if I want to test something or to see OSD stuff.

    #14
    Posted 02/11/2018 07:19 PM   
    . RTSS is a Service. Make sure it is set to [MANUAL] .
    .

    RTSS is a Service. Make sure it is set to [MANUAL]


    .

    My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

    Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

    ""Don't f with it if it ain't broken!""
    Constantly updating drivers is a good way to F'up the whole system.

    If the driver has an issue, don't be a fool, remove it.

    Just because you can, does not mean you should.

    #15
    Posted 02/11/2018 10:29 PM   
      1 / 3    
    Scroll To Top