• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Solved Pixel error when playing Rainbow Six Siege

Status
Not open for further replies.

Steven

PCHF Member
Feb 24, 2019
5
0
35
Hello all,

Hope someone here will be able to help me or clear things up for me.

Whenever I launch Rainbow Six Siege I'll get a few (2-6, but mostly just 2) dead or stuck pixels after a few games or even minutes. They appear as white or sometimes green.

It seems to be triggered by Rainbow Six Siege. And Six Siege only. I can play Overwatch, Apex Legends, Rocket League etc etc for days without any form of pixel errors but it's guaranteed that they'll appear when launching Six Siege. The pixel errors will stay after quitting Siege. Sometimes it even takes a few reboots to get them away.

I've reached out to Nvidia and they suggested a few settings I could try. I didn't have much luck with that though. Ubisoft Support says it's a monitor issue because the pixel doesn't appear on in-game screenshots. I'm sure it is a monitor issue, but I can't wrap my head around the fact that it's only Six Siege that causes the problem. I've contacted AOC to see if I can use my 36 month warranty but I doubt it as it's only 2 common pixel errors and 4 more uncommon (they happen rarely) so I doubt I'll have much luck there. So I've basically just ordered a new monitor.

But the question is still valid. Why is Six Siege the only game that causes the pixel errors? Since I "fixed" the pixel errors this friday (by rebooting a lot) I haven't touched Six Siege, and I haven't had the errors at all, and I've been playing a lot of Apex Legends this weekend!

I really hope someone can clear this up for me. I'm not expecting any fixes (although it would be great obviously) but I'm just super curious why Siege seems to doom my monitor.

Thanks!
 
Hi @Steven and welcome to PCHF :)

Can you provide us with some hardware information?

  • OS
  • Motherboard make and Model
  • CPU
  • RAM Make, Model, and size
  • Video card make and model
  • Monitor make and model

Thanks a bunch!

Windows 10
MB1151 Asus B250M-A Prime
i5-7500 3.80ghz quad cpu
DDR4-2400 8gb Crucial Ram
Nvidia 1060 6gb dual fan
AOC g2770pf
 
Hi Steven. Does the pixel video corruption occur regardless of the in game settings that you use when you launch Rainbow Six Siege?

Have you tried resetting the games video settings back to default values in the game?

Have you updated your video card's drivers to the latest version? Does lowering your monitor's resolution make any difference?

Are you overclocking any components?

Try Performing a clean boot in Windows and see if that helps to rule out any 3rd party programs interfering with your system.
 
  • Like
Reactions: jmarket
Hi Steven. Does the pixel video corruption occur regardless of the in game settings that you use when you launch Rainbow Six Siege?

Have you tried resetting the games video settings back to default values in the game?

Have you updated your video card's drivers to the latest version? Does lowering your monitor's resolution make any difference?

Are you overclocking any components?

Try Performing a clean boot in Windows and see if that helps to rule out any 3rd party programs interfering with your system.

I did a complete uninstall of the game, cleaned my monitor with screen cleaner I got, and ran a "unstuck pixel app". I've know played for alteast a few hours and haven't had the pixel errors yet. I've always made sure my driver were up to date so that has never been the problem. I'll try lowering my resolution if the problem occurs again. But for now uninstalling and maybe the app thingie worked. We'll see.
 
Status
Not open for further replies.