Why i got a comp suspension, lost 50 SR and a entire endorsement level !

Going into game, the team looks nice we even have a nice team comp. And then the game crashes and i get the error message “your rendering device has been lost”. After that i start overwatch back up see that i have a comp suspension i lost arround 50 sr and my endorsement went from 3 to 2. Im not here to ask for a solution since ive read a million post already about this topic and they all have different “solutions” (most of them are just “did you try updating your video driver”) . But in the end non of them work. This crash/bug has been arround for a long time for a lot of people and it happends only in overwatch yet there is no clear solution for it. I’m just here trying to vent my frustration. The saddest part for me is that i lose a entire endorsement level because there is a bug in overwatch that the devs don’t know how to fix. And for someone who is trying to be nice and positive every game to get his endorsement up you might understand that its quite frustrating when it goes down after another stupid crash that i cannot prevent. I guess what im trying to accomplish with this post is that a dev reads it, feels my frustration and maybe comes up with a solution, for either the bug/crash itself or the punishment people get when it happends.

Greetings,

Tailz

Quick question, did your game crash before that incident, too?

This crash “your rendering device has been lost” has happend to me many times before if thats what your wondering. But it didnt crash before that specific game. The crash happend at the start of the match.

So you knew that your game might crash in any game and you chose to play competitive anyways.

Sorry if it sounds harsh but you deserved that penalty.
You chose to play competitive even though your game isn’t stable. The game crashed and you abandoned your team, leaving them at a disadvantage. However, it is not the game’s fault, it’s yours because you chose to risk that.

After I played some competitive games, I suddenly had connection problems and (luckily) I lost the connection in a QP match. I knew that if I went into competitive now, I might get disconnected and leave my team at a disadvantage.

If I had gotten into a competitive game with an unstable connection and I had lost the connection, I would have deserved a penalty.

Try to fix the problem and as long that problem isn’t solved, please don’t play competitive. It’s not worth risking a crash and getting penalized.

I think your kinda missing the point, or i did not explain it well. This bug is very rare to happen for example if i would play overwatch a entire week straight day in day out it might happen once or twice. Solving this bug is not a option, as mentioned above there are many many posts about this and in the end none of them solve the solution. But because its not a super populair bug it has not been fixed yet. Also for some reason the bug never happends mid game. so the only one feeling the burns from this is me since the match is always cancelled when it happends or it happends straight after a match has ended. So i get the punishments but other players at worst just have to find a new match. And you gotta trust me when i say if there was a solution for this problem i would have found it by now i read basically every post there is about this.

Choosing to not play while this bug is a thing is basically saying i will never play competitive again since there does not seem to be a solution coming any time soon…

I see,

It seems to appear rarely and there isn’t a solution for now either. Nonetheless, the penalty is deserved because you still chose to risk a crash during the game.

If you choose to continue playing competitive games and it happened again, you have to accept the deserved penalty.

Otherwise, keep looking for a solution and try to contact the support in the Technical Issues Forum and explain everything you found out (when it happens, etc.)

You can only say nothing works if you tried everything out :wink:

I tried everything…

Even asking the support themselves?

Disable all apps you have that use overlays. Discord, Steam, keyboard/mouse software, shadowplay etc. And don’t play comp until you fix it.

Do u think the issue is overlay related? Most topics about this say its a driver related problem.

It’s often overlay related, and it’s no wonder with the threading/locking strategy used in Overwatch. The common D3D hooking strategies used by external applications doesn’t work very well.

Otherwise, try switching from fullscreen to fullscreen windows, or vice versa.

funny overwatch has never crashed for me ever so i doubt it is the server or blizzards fault. so once again it seems it is someone trying to play a on-line comp game with a bad system that keeps crashing lagging , causing dc , and then complains on here when the suspensions build up , never mind all the games youve let 5 other people down !!!

To be honest, there are a lot of common third party apps that interfere with the d3d-device these days, most of them by simply hooking the present()-call and start making draw-calls with a saved device-pointer. This usually works since most games are either single-threaded, or only do d3d-interaction in the main thread, but OW runs six threads and don’t do rendering in main. Plus it appears to be quite sensitive to hooks not resetting the exact same state post- as pre-hook.

Since these apps aren’t even noticeable a lot of the time, and most people don’t know how these things work, it’s not strange if they don’t know for example Steam fiddles with Overwatch and can cause crashes.

Blizz should really add some stuff to Warden (or whatever they use in OW) to warn about these apps. But until they do, everyone should know that Discord, Steam, GeForce Experience, Windows Gamebar and PVR, and Razer software can cause issues. And other stuff too, and try disabling them.

I cant even begin to describe how, i would almost say stupid your post is. Your making the argument “overwatch has never crashed for me ever so i doubt it is the server or blizzards fault”??? so your not having trouble playing overwatch, therefore if anyone else has a problem its probably there fault… i hope you yourself can see how silly that is. Secondly you say someone with a bad system, ive got a nvidia geforce GTX 1060 in my pc and every game i play runs completely fine, i get 160 - 180 fps even in overwatch with all on epic so i highly doubt its a “bad system”. Lastly you say “never mind all the games youve let 5 other people down” even though i clearly stated MULTIPLE times that this only happends before the game actelly started or after its finished so ive never caused anyone else a loss or sr loss whatsover except me. It seems to me your just another guy coming in on the post reading it half ass and then thinking your the expert just because your own game runs fine…? So please don’t come in a random post describing me as another guy who just lost comp cause he has a bad pc and made everyone lose the game, if you can’t even take the proper time to read the entire post.

Thank god there is people like TheExodus who actually give helpful advice and know what there saying.

do you have an amd gpu, when I had one it did that a lot in qp and arcade and I didn’t play comp because of it.
iv since bought a gtx 1060 and it hasn’t happened since .
I coul;dent find any other solution

as mentioned in the post above, ive got a gtx 1060… why do people not read posts :c

I solved this issue. The culprit was a gtx1080ti that wasn’t stable at maximum boost clock.
RMA=>> all fine now.

But yeah the penalty is harder against you than against throwers cheaters etc.

a 1060 is quite unlikely to run into issues due to boost though, considering how much wider the margins are. But you never know…

OP: Try running a proper GPU benchmark and see what happens.

The issue is the GPU believe me. Put your fps limiter lower(as well as graphics) or under clock your gpu(Nvidia debug mode) and you won’t have the error. RMA if you can.
Benchmarks won’t reveal this(didn’t in my case…)

A benchmark that is maxing your GPU should show it just fine. My point is mainly that there are a number of reasons this could happen, a faulty video card being one of them.