X99S GAMING 9 AC Not booting - Debug 94 code - Issue with GTX 980 SLI in WoW

Hello, I bought the X99S GAMING 9 AC motherboard but have ran into some issues.
The computer won't boot when I put my second MSI GTX 980 Gaming 4 GB card in the last PCEI 3.0 port (PCIE port 5) and I get the debug LED message 94 on the motherboard. I have a SLI setup.
The first card I have in the second PCIE 3.0 port due to the Noctua U14S CPU fan takes up space for the first slot. So I have been running my grafic cards in PCIE slot 2 and 4 with some issues.
First the card in slot 2 gets really warm over 86 celsius. And second: SLI runs really poorly in World of Warcraft. I get a lot higher performance with just one card activated. I am not sure if it's cause I am not running my cards in the recommended PCIE 3.0 ports or because WoW has some issues with SLI, but I heard other people have no issues at all with WoW in SLI.
I got the same issue with 3Dmark firestrike, the cards perform really poor in SLI. I get higher score with SLI turned off..
Though SLI seems to run pretty well in 3dmark 11 and Diablo 3 Reaper of Souls.
But the main issue right now, is that the computer won't boot with the grafic cards in PCIE port 2 and 5. The solution to run them next to each other is not good, cause it gets really hot and I get bad performance in WoW and Firestrike.
Picture of my setup before I switched places with the grafic cards as you can see, it is really tight:
Any upcoming bios updates (got v1.3) that will solve this issue on the horization? Hopefully this get sorted out really soon..
My whole computer setup:
Intel i7 5820K | MSI X99S Gaming 9 AC (bios 1.3) | SLI MSI GTX 980 Gaming 4GB | Samsung 850 Pro 512 GB | WD Red 4TB | G.Skill Ripjaws DDR4 3000MHz 4x4GB | EVGA SuperNOVA P2 1000W | Noctua NH-U14S PnP | Fractal Design Define XL R2 | 5 Noctua NF-A14 PWM 140mm fans | Windows 7 Pro 64 bit

You must use the recommended PCIE slots as the manual says for your CPU type, PCIE #1 and PCIE #4 if I remember, just open the manual :P for optimal 2Way SLI, also your 5820k will limit to 28 pcie lanes only if you plan to add more vgas...the other problem is your giant CPU air cooler blocking PCIE#1, do a favor to yourself, buy a watercooler for your 5820k and your problems are gone, add some overclock in your system, low noise and better temps.
Here I use 3x980 in SLI with X99S Gaming 9 AC, going soon to WC the VGAs with EK blocks.....3way is far more temperature critical than 2way spaced one.
Cheers

Similar Messages

HT4061 I have an iphone 5s, does not boot, blinking white screen with black logo, when trying itunes restore from mac and pc, error code 4013 which is usb error, any ideas?

I have an iphone 5s, does not boot, blinking white screen with black logo, when trying itunes restore from mac and pc, error code 4013 which is usb error, any ideas? Does a totally dead battery have that effect? I have had it plugged in to a computer overnight, but maybe does not charge when totally dead?
Please help, thanks in advance all1

Hi eggroll77,
Welcome to Apple Support Communities.
That alert codes does suggest there is a USB related issue. If you haven’t already, try the troubleshooting suggestions in the article linked below.
iOS: Restore errors 4005, 4013, and 4014
I hope this helps.
-Jason

IOS 7.0.3 did not fix the mirroring issue with ATVs and AirServer. Anyone have an idea what needs to be done?

iOS 7.0.3 did not fix the mirroring issue with ATVs and AirServer. Anyone have an idea what needs to be done? The only solution we have found is to reboot the iPad. We don't have the option of restarting the wireless as so many people are on and it would further disrupt classes.

iOS 7.0.3 did not fix the mirroring issue with ATVs and AirServer. Anyone have an idea what needs to be done? The only solution we have found is to reboot the iPad. We don't have the option of restarting the wireless as so many people are on and it would further disrupt classes.

Mac will not boot up, white screen with turning gear for hours on end

mac will not boot up, white screen with turning gear for hours on end

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.
There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
a. Boot into the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. The easiest way to deal with the problem is to boot from an external drive, or else to use either of the techniques in Steps 1b and 1c to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a boot failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
Boot in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 6.
If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
Step 9
Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 10
Repeat Step 9, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
Step 11
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a boot failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 12
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

BRAND NEW MSI x99s Gaming 7 Won't Boot, Debug Code 00

Just completed my build and my pc won't boot. Everything plugged directly into the psu is working but fans plugged into mother board don't spin and getting debug code 00 nothing displayed on screen.

Hmm ok.
What you could do is: try each stick on its own, in every single DIMM slot. Make note which slots/sticks work or dont work. Then add to 1 (known to work) RAM stick and try moving this single one around all DIMMs again. Do the same until you get a failure or if works fine.
Which slots did you use by the way?
Quote from: robbie.bowden on 18-May-15, 04:23:08
I then added the 4th one back in and now it boots. Any ideas why just switching those 2 positions would change anything??
Maybe for the first time it didnt go all the way down?

MSI X99S GAMING 7 - slow booting; HDD aren´t recognized in BIOS

Hi,
i´m facing a similar Problem as it is described in "MSI X99A Gaming 7 and Samsung SM951 PCI-e very slow boot time" https://forum-en.msi.com/index.php?topic=255919.0
My rig:
- i7 5930k
- X99S Gaming 7 (BIOS h90)
- PALIT GTX 980 Super Jetstream
- OCZ revodrive 3 x2 240 GByte (System disk)
- Corsair Force 3 120 GByte (game disk)
- 2x SAMSUNG HD501LJ 500 GByte (SATA 3GB/s)
- 1 LG Electronics BH16NS40
- 16 GByte Corsair Vengeance LPX schwarz DIMM Kit 16GB, DDR4-2666, CL15-17-17-35 (CMK16GX4M4A2666C15)
- 1000W power supply
- ANTEC P193 case
- G19 Keyboard
- MX518 Mouse.
I assembled it yesterday and during the first booting sequence it restarted 3 times.
After that it took 5 minutes to be on the Windows Desktop. Furthermore I recognized that all the HDDs and the optical drive weren´t available.
I tried to activate them in the Windows System - with no result. Than I checked the BIOS, they weren´t present there.
At the end i checked the HDDs only with the power supply, they booted. As soon as I connect them with the SATA cable they stand still - no spin up hear-able.
Now The BluRay and the HDDs are disconnected, the booting sequence is a Little bit faster (still 3 minutes).
In the BIOS I only activated the XMP-Profile für the RAM and I changed the booting sequence for the REVODRIVE.
May someone has any hint for me, how to deal with this Problem - but as I stated at the very beginning: it sounds similar to me.
Best regards from Austria
Gerald
P.S.: I apologize for "hijacking" - I tried to simplify the Forum by merging similar issues.

Your explanation isn't very helpful.
Your third try you got the Revodrive, corsair, and optical running? Meaning that you could boot multiple times and have it all work correctly?
I hate saying it, but if you aren't going to be descriptive, we aren't going to be very much help.
For what it's worth, I'm starting to think that the Revodrive and the motherboard do not work well together.
Personally, I would also consider contacting MSI directly about the issue. They might be able to issue a new BIOS that improves compatibility.
>>How to contact MSI.<<

790FX-GD70 not Booting, FF code

Hello, new to the forum... I signed up on here because I am having a rather difficult time with my MSI motherboard; I haven't been able to find any help elsewhere. I put together a machine using the MSI 790FX-GD70 socket AM3 board (not winki ed.) and a Phenom-II X6, the 1090T. Here is the full configuration:
AMD Phenom-II X6 - 1090T @ 3.2Ghz
MSI 790FX-GD70, latest BIOS
2x4GB (8GB) Corsair XMS3 DDR3-1600 RAM
ATI FirePro V5700 512MB (2x) *these do not require aux power
500w Corsair CX500 power supply 80+ cert.
500GB HDD, 7200rpm
DVD burner
This setup was working fine when I first assembled it around a month ago, but since the motherboard has been giving me the "FF" code and will not POST. The only way I can get the board to POST and boot the OS is to clear the CMOS and strike F2 to load defaults. I am able to enter and access the BIOS (and update it) but if I change or save any settings the motherboard will not POST and will display FF code again. If I clear the CMOS and strike F2 the board will POST, boot Windows, and work just fine without crashing--but if I restart the computer or shut it down properly the same thing occurs and I must clear CMOS again in order for it to work. This is very frustrating...
At this point I have switched CMOS batteries, tried a different PSU, taken one of the graphics cards out, and used only a single stick of RAM. I have also tried a different 1333mhz module and flashed the BIOS to the latest version without error. Nothing has fixed the problem and I am getting the hint that the board could be toast. When I power on the board, the FF code displays, the HDD LED flashes once, and then the FF code quickly returns and it hangs with no video to the monitor. All of the board's other LEDs are ON but nothing happens until the CMOS is cleared. This is very bizarre to me and I've never had a board that just stopped working. I am not trying to OC anything (dial is disabled and OFF) and all of the other hardware tests good. The computer has worked perfectly fine before so I can't guess as to why it has suddenly become problematic. It still works, but only after clearing CMOS and using F2.
I would greatly appreciate any help with this as I am out of ideas... thanks in advance for any support.

I think you are of the mistaken impression that we are MSI. This is a user to user forum and run by users like you--not MSI employees. We are all volunteers including the Mods and the Admin. None are paid or work for MSI. There are a few MSI employees that come in here but they do not read the forums very often and post even more rarely. M-Flash and Live Update are official MSI products. The MSI HQ Forum Flasher is a product of these forums, specifically Svet and tested by the other Mods--the USB Forum Flasher is not part of MSI. The flasher though only supports MSI products and was designed as such. The issue with LU and M-flash is, one, LU flashes within the Windows environment and that is a very dangerous practice, and two, M-flash has the ability to flash your BIOS with any file---you could well end up with your BIOS flashed with a document or Mp3 file. Originally, the forum flasher was developed as a very safe means of flashing the BIOS and to avoid the issues using LU. It is also far safer than using M-Flash as the forum flasher has many checks and safety measures built in.

Z77 Mpower - No video signal on boot - Debug code "Ad"

Hi, I can't get any video signal from my mobo, it seems that it can't boot at all.
I just plugged CPU (i7 3770k), CPU cooler (Noctua NH-D14) and 1 RAM (8gb DDR3 2400MHz), no vga, hd or dvd writer, then I obviously plugged the 24 pin connector from the PSU and the 8 pin connector for additional CPU power.
I have my monitor directly plugged to motherboard but when I turn on my pc, even if fans are working and motherboard leds are on, I still don't have any video signal and on the motherboard I can see the debug code "Ad".
Please can you explain what is happening?
Thank you very much for any advice and sorry for my bad english.

I tried to reseating the CPU and nothing changed, then I reset the CMOS, waited for a couple of minutes, restored the power, and the debug code became "A0", but after about another minute I retried to turn on the PC and the Debug code returned "Ad".
I'm quite frustrated.
Side Note: For my try I didn't use the boxed cpu cooler, I just installed my cooler without plugging the fan cable to the "CPU fan" pins, i thought it was sufficient to see if my motherboard boots, isn't it?
Update: I tried ro reset bios again and plug change the RAM stick in solt2 with the other one. Again the system was unable to boot but the debug code became B4. After a couple of minutes I tried to boot again without touching anything and the debug code returned "Ad", I can't give an explanation to these apparently random debug codes
Update 2:Now I switched ram slot, from slot 2 I mounted ram stick to slot 4 and reset cmos again. The first boot after resetting gave me debug code "64" then again, shout down, wait a couple of minutes, turn on Pc and... debug code "Ad" again.
It seems that first boot after cmos reset the mobo gives me a random debug code, then it returns "Ad" as always for the following boots.

MSI X99S MPOWER won't boot (Debug 00) after installing Transcend 256 M.2 SSD

Hey all, as the subject suggests I bought a new MSI X99S Mpower mobo. I put together a new system with it without any problems using my old SSD. I received a new M.2 SSD (Transcend 256 GB) once I installed it the system would no longer boot. I removed the M.2 SSD and the unit will now still not boot. I power on and the LED just displays 00.

what bios version you are using?
can you list the exact M.2 SSD (Transcend 256 GB) mode/part number?

ADDT Code issues with w2k8 IIS7/FastCGI?

Has one else experienced any issues with the ADDT Dynamic List code not working with IIS7/FastCGI on w2k8?
Fresh install of 2k8 ent, w/iis7 and fastcgi running. Most applications work just fine but there semes to be issues with pages that have ADDT dynamic list/forms. IE when you try to click on edit from the list it takes you to a blank form insted of the individual record.

Thread moved to Dreamweaver Application Development forum.

HT5306 I do not want to give remote access to anyone but myself as privacy is my friend. Can this remote desktop software still be for me personally unless I allow access and for my MAC lap top only? What if I do not update? compatibility issues with wh

Hello:
Thank you for the update for remote access for desktops.
Personally, I do not want to give remote access to anyone but myself as privacy is my friend. Can this remote desktop software still be for me personally unless I allow access and for my MAC lap top only? What if I do not update? I do use this lap top in other countries. compatibility issues with what?

Apple Remote Desktop is off be default. It has to be enabled for some one to be able to remotely connect to the computer. And then, you still have to have a user name and password on the computer to remotely connect with.
If you want to see if remote access has is enabled for Apple Remote Desktop; you can find the setting in, Apple Menu, System Prefrences, Sharing. If it's enabled, Remote Management or Screen Sharing will be checked.
Beucase Apple Remote Desktop Agent is part of the Mac Operating System; even if your not using it, Apple Software Updates will from time to time offer updates for ARD Agent. Software Updates can some times be stacked ontop of each other; so chosing not to install an update, can mean other updates you may want may not be offered. At least until you install the updates those updates require. Also software updates can improve the security of your computer.

Battery not recognised - and other issues with 867MHz Ti Book

Ok - here`s my story - I wonder if anyone can give me advice
on what to do next.
A week ago I started having trackpad issues with my tibook.
On 2 consecutive mornings the trackpad seemed to have frozen, held down. So that it brought up menus if the mouse was moved over one of the bars at the top of the screen. I wasn`t however, able to `click` on anything. An external
mouse, when plugged in, also didn`t work, though I was able to navigate the display using the keyboard shortcuts.
The first morning this happened, the OS also appeared to reset itself. ie the screen display picture went back to its original state - and all of the applications that i subsequently opened gave me a first time user `welcome` message.However, all of my files/photos/music etc were intact.
When the trackpad was working I backed everything up, ran
the hardware test cd, which came up clear, and called apple. They picked up the computer, which is under
warranty, on Friday, and at the time it was working fine.
I got the computer back yesterday, but unrepaired, and
with a new set of faults. Apple told me that they had checked the computer and had found
some evidence on the logic board, power in and bottom case
of past liquid spillage - but no other problems with the
computer. I don`t deny the liquid spillage ( a few ml of
water), although it
occurred 11 months ago and I have not had any problems with
the computer since 24 hours after the spill.
The state of the computer now that Apple have sent it back
is as follows: The trackpad is working. However, the computer is not recognsing the battery, or the wireless
networking Buffalo pc card. The clock also resets one out
of every 2 or 3 times that I restart the computer. These problems did not occur before I sent the computer to Apple.
Yesterday I erased and reinstalled 10.4 just in case that had
something to do with it - but it has not helped
So - my questions.
1. Could my current problems be to do with the spillage
on the logic board 11 months ago?
2. Could my new problems be to do with something that Apple
did when testing the computer this week?
3. Is there anything else that I should try in order to solve the issues that I`m having with the computer?
4. If it is a logic board problem, can anyone recommend
a UK repair centre that would deal with this cheaply (otherwise i will probably buy a new computer - as this
one is coming up for 3 years)?
Thanks,
Antony

Hi Antony,
1. Could my current problems be to do with the spillage
on the logic board 11 months ago?
Yes. Corrosion occurs over time, and it could have taken 11 months to reach "critcal mass."
2. Could my new problems be to do with something that Apple
did when testing the computer this week?
Theoretically, any time anyone does anything inside your PB, they could have caused additional issues, however, this would not be "normal."
3. Is there anything else that I should try in order to solve the issues that I`m having with the computer?
4. If it is a logic board problem, can anyone recommend a UK repair centre that would deal with this cheaply (otherwise i will probably buy a new computer - as this one is coming up for 3 years)?
Before paying for a new LB or a new PB, try a PMU Reset and Test PB Backup Battery.

IWeb not opening after some issues with an existing site...

Hi there~
I’m a relatively new Mac user and a former PC/Dreamweaver user. I’m having a bit of an issue with iWeb. I’ll do my best to keep what happened relatively brief:
1. I had created and published a site a couple of months ago, but the page that contained photo albums seemed to have become corrupted. Every time I tried to open that page, iWeb would crash.
2. I recreated that page but then was not able to delete the corrupted version. So I recreated the whole site.
3. I published the new site, and everything seemed to be working well in the live version.
4. To avoid confusion in the future, I wanted to get rid of the old site. When I deleted that site, I saw that it said something about deleting it from the Web as well. I realized that this may cause problems because most of the pages would have the same names, but I was hopeful that since the new site had all of the pages I could just republish.
5. The new site did indeed get messed up after I deleted the old site. So I set the new site to republish, and then I got an error message.
6. I figured just for safety’s sake I would undo the deletion of the old site and just leave it for a while in the hopes that the new site would then work again.
7. After I did this, the old files reappeared, but then iWeb froze. (I think... My memory is a little fuzzy here...)
8. I closed and reopened iWeb, but all that appeared was that little right-hand box that lets you see the properties of certain things (Page, Photos, Text, etc). I also restarted the computer, and now when I open iWeb, that little box is still all that I’m getting.
I grabbed what I could from the live version and my history files so that I can recreate the site from scratch if I need to, so I’m not terribly worried about getting my files back. I did have another site created in iWeb that seemed to be fine, it would be nice to not have to start over with that one, but obviously I can if needed. Maybe those files can be found elsewhere on my computer?
So will I be able to get iWeb back? Do I need to reinstall it? If so, how do I do that? (Maybe that’s a question for another forum. iLife was installed on the Mac when we got it, I looked briefly for the files on the Applications CD but got a little scared off when I saw something about bundled applications...)
Thanks so much for any help. I called tech support and was directed here, this is new for me, so I hope I’m going about this in the right way. I’ll spend some time looking around to see if anyone has addressed this elsewhere, I just wanted to get things down while it was all relatively fresh in my head.
Thank you!
Jen

Welcome to the Apple Discussions.
. Every time I tried to open that page,
That sounds like the problem described here with potential fixes: iWeb & iWork: Applications may suddenly quit after updating to Mac OS X v10.6.2. This is another possible fix: The million dollar trick or how to fix iWeb in 10.6.2
OT

My MacBook si not booting displaying a folder with question mark

The very latest development in My Macbook that is not booting, it now displays a gray screen with blinking folder and a question mark inside then it turns off after few minutes.
It is not responding to any option+C,S,V, shift and I cannot boot from the install CD or diskwarrior.
Any thoughts??
Thanks,
AT

If DW can't see the hard drive then it does not bode well for the drive. Try booting from the CD and run Disk Utilities from the CD to see if the drive shows up there. I am not optimistic though since usually DW stands a better chance at this than DU.
If neither DU nor DW work, try using an application such as [Data Rescue II|http://www.prosofteng.com/products/data_rescue.php] or [FileSalvage|http://subrosasoft.com/OSXSoftware/index.php?mainpage=product_info&productsid=1]. Both have free trial versions that let you see if the software will help before you decide to buy. In this regard you can use them as an analytical tool to see if they can see the drive.
There is also this free tool which supposedly runs on OSX and does recovery of popular media and Office files. [http://www.cgsecurity.org/wiki/TestDisk_Download] I have only done a bit of reading about this tool so I really know almost nothing about it - maybe it only works on Intel processor computers.

After kernel .27 is not booting...even with pci=nomsi

After my upgrade...
My arch is not booting anymore...
Even trying to use the pci=nomsi option...is not working..
It just freezes on "Loading UDev uevents".
Does anyone has any idea??

I did it.. put the verbose at the end of the line...
It stopd at:
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0x3e0-0x4ff:
And nothing else happnes...
o.O
I'll try to downgrade my kernel now.. if doesn't work...I'll have to reinstall everything from zero...

X99S GAMING 9 AC Not booting - Debug 94 code - Issue with GTX 980 SLI in WoW

Similar Messages

Maybe you are looking for