Jump to content

Hello!

 

Yesterday whilst playing Overwatch my game crashed displaying the error message "Rendering device has been lost [...]". The crashed persisted and I tried several fixes that I found online. This included trying to vacuum the computer of dust, repairing the game files, searching for corrupted files in Windows (Windows 10), but the crashed persisted. During this time I also got two BSODS. The first one displayed "video tdr failure" and the second "bad pool header". I discussed this with Blizzard support but they couldn't find the issue at the time. I ran GPU and CPU analyzing tools and saw that at the time of the crash my GPU jumped up to 100% and then abrubtly down to more stable levels. It occured to me that it might be a problem with my computer and not Overwatch (because BSODS), so I tried to start Battlefront 3. This time I got a blackscreen and had to forcefully restart the computer. When trying to start it again I saw "flicker" on the screen and got another BSOD. This time it displayed the error "video scheduler internal error". When the computer automatically restarted after the BSOD I got the same BSOD again and Windows booted me to some recovery screen. I chose to tap out at this point, and ask around for help.

 

So, what do I do? Is my GPU burnt?

 

Also, apologied if I posted this in the wrong thread. Feel free to redirect me if that is the case.

 

Specs: 

CPU - i5 3470

GPU - Asus gtx 670

 

Also I have pictures of some of the BSODS and such. Just tell me if you want them.

 

Cheers!

Link to comment
https://linustechtips.com/topic/752764-bsod-on-startup/
Share on other sites

Link to post
Share on other sites

Hello.

 

I saw some posts in the Overwatch forums and some people has the same issue. Apparentley capping FPS solves the issue. 

Maybe try it and see if it works.

 

P.S you shouldn't vacuum your pc , try blowing it out with compressed air otherwise you could vacuum your ram in , haha.

Link to comment
https://linustechtips.com/topic/752764-bsod-on-startup/#findComment-9524603
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×