Serious issue: Breaks my graphics card. Gets disabled with code 43.

Aleksoid1978 / VideoRenderer

Внешний видео-рендерер

GNU General Public License v3.0

1.1k stars 122 forks source link

Serious issue: Breaks my graphics card. Gets disabled with code 43. #163

Closed mzso closed 5 months ago

mzso commented 5 months ago

Hi!

So I tried upgrading the renderer to the newews two days ago (0.8.1.2230). It immediately broke my graphics card (Asus DUAL-RX580-O4G). It got disabled by windows with code 43. And no matter what I did I couldn't get it to work again. I had to refresh Windows from ISO to get the graphics card working again. Then I tried 0.8.3.2255, which came out in the meanwhile. It also instantly broke the graphics card. At least this time I created a system restore point.

I can't imagine why it happens, but it's appalling. Never had an issue like this with any directshow filter or such. I can play videos happily with madVR.

PS: I have been using 0.7.0.2126 before. (Probably, that's the package I have from before 0.8.1.2230) I had no problems with this.

v0lt commented 5 months ago

HEVC 4k HDR 10-bit 60 fps

MPC Video Renderer 0.8.3.2255 MPC-BE x64 1.7.1.60 dev Windows 10 22H2

Nvidia GTX 950 - OK Intel UHD 750 - OK

I think you have a driver or video card problem.

mzso commented 5 months ago

@v0lt The driver didn't change, I've been using it since last year. For a while I also suspected a video card problem. But with a fresh installation of windows it worked. It only breaks when I start using MPC video renderer in the player.

clsid2 commented 5 months ago

A DirectShow filter can not break your GPU. Nor can any other user-mode application.

It is hardware failure, driver bug, or Windows update bug.

mzso commented 5 months ago

@clsid2 Well, it was rendered non-functional. And it seems neither of the above. No Windows or driver updates happened for a long time, and the GPU still functions. In any way, it was triggered by using MPC VR, whatever way it happened.

clsid2 commented 5 months ago

Take out the GPU. Clean the fans. Clean the dust from rest of computer. Put back the GPU and make sure it is properly seated in its bracket.

Run some GPU stress tests.

A broken GPU can work fine most of the time until the part that is broken gets utilized.

v0lt commented 5 months ago

The driver didn't change, I've been using it since last year.

The driver should not break due to exposure to the client application.

v0lt commented 5 months ago

You can view the debug log and send it to AMD. https://github.com/Aleksoid1978/VideoRenderer/wiki/View-debug-log

ale5000-git commented 5 months ago

@mzso In the past I had one pc that has various crashes in the graphic driver, but after a lot of time I have discovered that the only problem was that the power supply isn't working well when "stressed" so changing it fixed everything. I'm not sure if it can be related to you but it is still a possibility.