MSI AMD Radeon 7990 missing core caused by Driver or fault?

Deviant Savant

Honorable
Dec 20, 2013
10
0
10,510
I have what seems to be a driver issues with my MSI AMD Radeon 7990. First used v12.10 and noticed a core would not appear – not displayed at all but this was usually resolved by a restart of windows and it reappeared. I installed v13.8 beta from MSI website and it installed fine and worked but then the GPU 2 or second core stopped displaying again – this time nothing I did managed to get it to display. I used Driver Fusion Premium to get rid of previous driver files and then installed again and that would not work. I tried going back to older version driver and that made no difference either.

Others seem to have the same or similar problem:

http://forums.overclockers.co.uk/showthread.php?t=18559920

I will upload screenshots of my device status from AIDA64 sometime incase it will help.

Device Manager was showing two different errors. Sometimes it would give error: this device cannot start code 10. Other times it would show error 138 I think – old driver still in memory and that windows needing to reboot before it could work. Nothing made it work, so I reinstalled windows. Vanilla clean install and installed v13.8 beta (http://www.msi.com/product/vga/R7990-6GD5.html#/?div=Driver&os=Win7 64 ) and still no GPU 2 / second core showing. So I go into my security software CIS Premium from Comodo and find it had put part of an installer into sandbox but the driver software nor Comodo complained or alerted me of this at the time. As soon as it was removed from sandbox windows said it detected new hardware and then went on to install the driver – the second core appeared – so I made a system restore point at this time and later windows freezes from a crash so I had to do a hard reset. Then GPU/core 2 is not showing again and this is where I am up to.

Note: although I did install a clean windows and installed the GPU display drivers under this condition (I double checked to make sure by looking at system restore affected software) Comodo CIS Premium seemed to still have had an affect on the installation file at a later time. ccc-core-static.msi any idea why this could be? I am a little baffled by all of this as I have never had anything like this before. I imagine a single core/card GPU would not cause this with AMD even though their driver can be buggy.

At first I thought it was buggy drivers then I thought it was a dead core and needed to RMA it but then with it starting to work I am sure it must now be a software issue and not hardware.

While the second core is missing windows thinks it is just another standard VGA GPU that it cannot install a driver for but if I use AIDA 64 I get a different GPU altogether. One is displayed as a Malta and the other is displayed as Tahita, One is listed as my 7990 and the other as a Firepro GPU. Is it possible that the BIOS of the GPU messed up during a driver install on one of the cores and is now corrupted and does not recognise the correct GPU.

The weird thing about Comodo with it blocking/sandboxing installer file ccc-core-static.msi, I always check to see nothing had interfered with so not seen this before. Anyway I moved it to trusted file and also put all ATI/AMD files into trusted section so they would be excluded from any restriction later on.

So my question is what have I done wrong to rectify this, or what could better be done?

Should I follow these steps or something similar or is using Driver Fusion Premium just as good?
http://www.overclock.net/t/988215/how-to-properly-uninstall-ati-amd-software-drivers-for-graphics-cards

I am not sure what to do and also not sure what the problem is but it seems more like a driver problem. I would try reinstalling windows again and without Comodo installed for a few days if necessary until I knew what was wrong with this. It is the first time I have owned an AMD GPU and Nvidia has never caused me any bugs before.

I really appreciate help with this. I need to know what is wrong with this and I would have done more if I had the knowledge and experience with similar issues like this. I had to rule out windows being the cause because I have had some devices install wrong sometimes and then windows just refuses to install the correct driver for whatever reason, some people say that Microsoft are not to blame but third parties are for not complying with established driver standards.

Are there any windows updates that I should be aware of that break AMD display drivers? I imagine once removed I could then fix this by reinstalling them if that was the cause but I do not expect it is because I have tried pre and post W7 x64 SP1 – that is with and without SP1 and no updates.

Last time both cores were working when ccc-core-static.msi was unblocked and windows allowed installation to go ahead I think what killed it again was high core temp that caused system to freeze. Not sure why it could not have handled it better though such as a shut down or restart of driver.

Thank you for your help.

Edit: fixed some typos and corrections made.
 

Deviant Savant

Honorable
Dec 20, 2013
10
0
10,510
There may be a few errors in my post above. I now can almost confirm that this seems to be a dead core as I have tried a few other things to diagnose this so I am going to return it.

Some things do not add up and I find this harder to diagnose myself because it is a dual GPU.

I noticed in GPU-Z that for 7990 OpenCL is not supported but under the standard VGA core it says it is supported, so this must be something to do with it not recognising the driver or a fault with the second core. Could this also be caused by faulty memory on there?

If faulty what is the likely cause, non lead solder?
 

ch3weh

Honorable
Jan 13, 2014
1
0
10,510


I'm having the same issue with the ASUS and/or XFX 7990 (I have 3 cards in one computer, one core is missing from windows device manager). Sometimes a restart fixes it, sometimes re-installing the driver fixes it. It will work for a couple of days and then bomb out again

 

Deviant Savant

Honorable
Dec 20, 2013
10
0
10,510
It might be a hardware issue with the Crossfire setup they use. Either that or drivers but I tend to think it is more on driver side. I managed to get my one working again by doing a few power cycles and then it shows up again. It probably happens when the driver crashes and doesn't recover properly. I updated the latest version drivers and it works better.

Overheating can be a big prob for 7990 GPU so best to underclock a little if you do not have liquid cooling, IMHO. Will like to see how AMD handle thermal cooling on their upcoming future release of Vesuvius dual GPU. hopefully the specs will be better for dual GPU on that than two combined single R9 290X because the computing power lacks compared to 7990. Probably not a problem for purely gaming though.