Hello my friends,
i'm dealing with a badly liquid damaged motherboard. In the end i additionally figured a corrupted BIOS.
After the succesful repair and flashing "manufacturing mode" BIOS (which i had set up and deavtivated manufacturing mode when done) the board is already working again but in Windows OS i get "Code 43" for the GPU as soon as drivers are being installed. I've tried many different drivers, and worked with DDU, but nothing.
I know. When everything looks normal, and it indeed does look normal, i'm probably dealing with a dead GPU. But after some research i have the feeling i could have managed to source a "wrong" BIOS or to have a corrupted VBios in addition.
What it makes even more weird: i can successfully run a benchmark software like Unigine Superposition in Linux environment with normal results.
I'll leave the corrupted dump, the "code 43" dump and the VBios here for inspection and would be glad if someone takes a look at these files.
Thank you!
i'm dealing with a badly liquid damaged motherboard. In the end i additionally figured a corrupted BIOS.
After the succesful repair and flashing "manufacturing mode" BIOS (which i had set up and deavtivated manufacturing mode when done) the board is already working again but in Windows OS i get "Code 43" for the GPU as soon as drivers are being installed. I've tried many different drivers, and worked with DDU, but nothing.
I know. When everything looks normal, and it indeed does look normal, i'm probably dealing with a dead GPU. But after some research i have the feeling i could have managed to source a "wrong" BIOS or to have a corrupted VBios in addition.
What it makes even more weird: i can successfully run a benchmark software like Unigine Superposition in Linux environment with normal results.
I'll leave the corrupted dump, the "code 43" dump and the VBios here for inspection and would be glad if someone takes a look at these files.
Thank you!
Comment