9C and A2 Debug Codes

Hello a few days ago i turned on my computer and in the bottom right these two digit debug codes appeared i thought everything was normal but when i got up to the windows 8.1 login screen my screen went black but i could see the cursor i backed my files up (Long Story) and reformatted my HDD and re installed windows and ever since then i and still receiving these to debug codes i tried to find them in the Manual but i could not find them. Ever since then i have realized i have been getting LOTS of error on my computer when installing programs and my computer not running to it fullest. So i was wondering if anyone here could help me. I have also reset the CMOS and also booting my computer takes alot longer now.
Thank You in Advanced
My Specs:
CPU: i5 4440 Quad Core 3.1 Ghz
Motherboard: Z87 GD-65 Gaming Motherboard (Socket LGA 1150)
Graphics: AMD Radeon HD 6800 Series
Ram: Corsair Vengeance 8 GB
PSU: FSP Aurum 750 W Gold Power (Modular)
HDD: Seagate Barracuda 1 TB

I had 9C a few times when i had a USB Sata Dock plugged in and turned on after working on some hard drives and shutting down and coming back the next day booting up i got a long pause on 9C... I unplugged the dock and rebooted and it was back to normal boot speed and no issues.
The A2 code could be a few things, but do you have optical drives? AKA CD or DVD drives? Is there a disc in either of them? I left a disc in one of my drives one time and it hung on A2 and took forever to boot, i think if it detects a disc in the drive it checks to see if its a bootable disc and causes the hang. Since i randomly leave a disc in there now and then, i hate optical drive use compared to flash drives but its a necessary evil for dealing with customers sometimes, i went into the BIOS and changed the boot order so that my SSD is first and and made sure everything else is either disabled or after the SSD in the boot order. You can always tap F12 on boot to get to the optical drive if needed to boot, although i generally boot anything i need other then windows from flash drives, including windows installation.
The A2 could also be a problem with the SSD... Do you have it plugged into one of the White 6gb Sata ports? Thats where it should be if you don't. If none of this fixes it and your still booting slow and the SSD is under warranty i would check with the manufacturer. I have had a few bum SSD's that worked great for a bit then suddenly had issues.
Also make sure the firmware on your SSD is the latest! But back up before you try to update it if its not, because i have had firmware updates corrupt the SSD and then had to reinstall windows after that.

Similar Messages

How can i fix the A2 and 99 debug code of on the X 79-a GD 65 8 dimm

İ am tryed the very different ways but nothing work i love the msi brand but i am very tired now, i dont wanna see any code or error mesages with my x 79 mobo when starting.

Quote from: masterten on 30-May-12, 20:24:25
You were arleady told that these codes are NOT error codes, but just checkpoint codes. MANY motherboards are using this codes to show us what are they doing at PC startup. I have Z77A-G45 and I'm also seeing the codes.
99 - this is the first code that shows up on the monitor after turning PC on
A2 - mobo is detecting IDE devices (hard discs, optical drives).
B4 - mobo is detecting USB devices.
If your PC is booting and working ok - you have nothing to worry about. But if your PC is hanging during a specific startup code, then you can identify the source of the problem.
sorry my brother for that sure not error codes strange! ?? but i am why waiting for seeing boot screen 15 second black screen? later post mobo screen later w7 boot total 34-40 second but i think must be more lower thank you for your help.

Debug codes and black screen on boot

I restarted my computer and the debug code on the motherboard says "99"
I also get a black screen on boot up and it does not advance. In the bottom right of the screen is the same "99"
What is the problem. Thanks in advance.
I have the MSi Military Class II 990FXA-GD80

Quote from: badboy2k on 21-August-12, 11:35:53
ok so from that id suspect mainly that your Graphics card may be the cause! what graphics card/s are you using?
I am using the ASUS HD 6670

Debug code 70 , mpower z87

Hi,
yesterday a friend of mine bought the mpower z87 mobo and
everything was fine until today.
The debug leds show the code 70 and the video output doesn't come out.
I'm really desperate and sad for him, I dont know what to do.
The configuration is:
msi mpower z87
i5 4670k
corsair cx750
samsung evo 840
msi gtx 770 lightning

thanks for the reply.. but I knew that the 70 code means Late South Bridge Inizialization
but I didn't know what does it mean .
Anyway we tried with only 1 RAM plugged and the debug code sometimes is A2 (Ide detected) sometimes A0 or A3.
With 2 RAMs the code is 99 (Super IO Inizialization).
We also tried to unplug the video card and the hdd and do the CMOS, with no results .
little update:
the computer now turns on but after 3 mins turns itself off...

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?

New Build, Won't POST, Debug code stays at 00

I just got done building a new MPOWER MAX with an I5-4670K. The build is a new power supply, motherboard, CPU, RAM. Video card I was using was in an old system and worked fine. 24 pin power, and the 2x 8 pin power supplies are all hooked up.
I have torn the PC back apart to where it's now just Motherboard, and CPU. No RAM, no Video card, no HDD's, no DVD drive. The system will not POST, and the Debug code never changes from 00. I have even pulled off all the front panel Power/LED/Speaker connectors.
I have also tried switching the BIOS toggle switch, and cleared BIOS from the back panel. I don't know where to go with this since it won't even give me a code of any kind.

Quote from: Sea Dog on 08-August-14, 02:31:23
Since the OP hasn't been back for half a year, maybe it is best for you to open a new thread listing all of your particulars of system components, etc..
Exactly, therefor: -- LOCKED --

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.

Z97 Gaming 5 Debug Codes 41, 42, 43, and 44

Just built my first PC and I am having issues with it.
I have it plugged into a monitor and it does not display anything but I am getting codes on debug codes on the motherboard.
My build is below in case it helps.
CPU: Intel Core i7-4790K 4.0GHz Quad-Core Processor
CPU Cooler: Cooler Master Hyper 212 EVO 82.9 CFM Sleeve Bearing CPU Cooler
Motherboard: MSI Z97-GAMING 5 ATX LGA1150 Motherboard
Memory: G.Skill Ripjaws X Series 8GB (2 x 4GB) DDR3-1600 Memory
Storage: Western Digital Caviar Green 1TB 3.5" 5400RPM Internal Hard Drive
Video Card: MSI GeForce GTX 970 4GB Twin Frozr V Video Card
Case: Thermaltake Level 10 GT Snow Edition ATX Full Tower Case
Power Supply: EVGA SuperNOVA 1000G2 1000W 80+ Gold Certified Fully-Modular ATX Power Supply
Optical Drive: *LG UH12NS30 Blu-Ray Reader, DVD/CD Writer
Operating System: Microsoft Windows 8.1 (OEM) (64-bit)
Like the subject said I am getting a few error codes.
It starts at the lower numbers than sticks around for a bit eventually moving to the higher ones and seems to cap at 44.
Any help on this issue would be immensely appreciated.
Also as a side note I have checked the users manual error code listings but it doesn't seem to contain these specific codes. If I am wrong on this could you tell me where on the manual it lists these?
Thank you very much for your time.

Quote from: brettrodie on 22-March-15, 04:26:05
I get visual output when I unplug my video card.
When entering the boot menu and selecting UEFI: Built-In EFI Shell I get the following
EFI: Shell version 2.31 [4.655]
Current running mode 1.1.2
Device mapping table
blk0 :BlockDevice - Alias (null)
PCiRoot(0x0)/PCi(0x1f,0x2)/Sata(0x0,0x0)
blk1 :BlockDevice - Alias (null)
PCiRoot(0x0)/PCi(0x1f,0x2)/Sata(0x0,5x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue
Shell>
Doesn't matter what I press it doesn't do anything
Entering setup instead of the EFI shell takes me to MSi's click bios 4
When I enter the board explorer it shows all the components that I have plugged in as running.
I am at a complete loss to what I need to do to install updates, OS, and to get my video card working.
listed above sounds correct
you need to boot from a bootable device who contain your OS installation disk to proceed with OS install.
about your Video card
when you install it, in which slot is placed?
and have you connected your display to it after that? [not to onboard GPU]
and have you attached all power cables for it?

MSI X99S Gaming 7 and debug code 67

Hi,
I have MSI X99S Gaming 7 motherboard, Crucial 2x8GB 2133 DDR4, MSI GTX970 Gaming 4G, Corsair RM650, i7-5820k setup.
When I am trying to boot the machine it always stops and the debug led shows code 67. I have tried to take everything out, reseated processor and to boot with just the minimum set of components. Result is always the same code 67.
I am running out of ideas. Do you have any hints or should I just return the mobo and processor?
Best Regards,
juha

Quote from: shadow85 on 22-December-14, 19:40:31
So are you going to RMA the board or just use it with 2 sticks? Thats means you are not planning on using it in quad channel, would be a waste.
Anyways if I were you I would definatly RMA it asap. This error 67 problem people are having seems to be widespread. MSI really need to look into this.
As has been said previously, contact MSI. Should they look into it? Yes, but the moderators here are not MSI employees, and while we can bring issues to their attention, we cannot make them look into problems.
So if you have this problem, please contact MSI directly: >>How to contact MSI.<<

990FXA-GD80V2 Debug Code "FF" and What it Means.

So my uncle stopped by today and said that his 990FXA-GD80V2 wouldn't post and I asked him if he went through the usual checks like re-seating the graphics card, resetting the CMOS, and trying only 1 memory module. He had done all that and no post, he then told me that he got a debug code of FF on the readout.
So I thought I would search the web and see what I could find out. "Nothing".
So I contacted MSI USA Technical Support and the technician let me know that "FF" Means no system input "Power".
If you get the "FF" code, try removing power and re-seating both the 24pin (Main) and 8pin (CPU) power connectors, if you have another power supply try that. Also check the CPU for any damaged pins.
If neither of those two options work, the board comes with a 3 year warranty and you should send it in for RMA. (Directly to MSI, not reseller).
If this has been posted somewhere else, my apologies, but I did search for it.

Thanks for the report, I think we saw a bad cpu do this as well but most often a bad bios.
Someone had told me it was actually supposed to be for future use, but each time it comes up, it isn't good.

MSI Z77 MPower - Boot issues (A2 debug code and more)

Hey guys,
I've been trying to get my new computer build working but I have encountered several issues when trying to boot the computer.
Before putting everything inside my case, I tested the motherboard + CPU + 1 stick of ram to make sure everything was working. I had issues in the past where I had to remove everything once I had things mounted.
Everything seemed to work and I got into the BIOS and looked like everything was good.
I mounted it in the case with the same configuration and I was able to get into the BIOS again. So I thought everything must be ok.
Fast forward a couple hours later after I finish plugging everything in, I try to turn it on but it just gets into this boot loop.
Turn on > Fans spin for a couple seconds > turns off > repeat. This just kept going on and on and I wasn't exactly sure what was going on.
I started to unplug components and when I only had the Mobo + CPU + 2 sticks of ram in I was able to get into the BIOS.
I plugged things in one at a time and when I plugged in my SSD it would work.. but when I added another drive I would start getting the A2 Debug message on my board.
I would continually get this A2 debug message and I am not sure what to do to get it to work.
I have updated my BIOS to the latest ones and it is still not working.
Could this be an issue with my PSU? I really hope it's not the MOBO..
My System:
i7 3770k
CoolerMaster 212 Evo
MSI M77 MPower
16GB DDR3 Ram
7870PCS+ Tahiti LE
Corsair HX650 PSU

Quote
I've tested it with one stick and 2 SSDs and it doesn't give me the A2 debug code.
Do you have any different ram to test with?
What ram exactly are you using?
You may perhaps be able to set the ram timings in bios to JEDEC standard 9-9-9-24 1600 perhaps

790FX-GD70 not POSTing no debug code all LEDs on

Hi
I have had my 790FX-GD70 for almost the past 2 years and it has given me no real problems. But yesterday whilst playing Fallen Earth, my computer froze so I gave it a restart and it froze during windows start up. At this point I opened my case and watched the debug display and this time it froze during post, can't remember the debug code it froze on. I tried restarting a few more time and it would freezes at different points during post. At this point I remove it from its case and start barebones testing it. If I left it for a time I could get into the bios and go to the hardware monitoring page and look a the tempter of the CPU for it froze. There it reported that the tempter was 34C. Stopped testing it last night and when I turned it one this morning it would not even start to post. When I turn it on all the LEDs on the board turn on even the overclocking LED and the overclocking switch also turns and to turn off the system I have to do a hard switch off and UPS.
I have tried it with a different UPS with no effect, tried a different graphics card with no effect. Also tried with different RAM and no RAM no effect.
Computer secs:
MB: MSi 790FX-GD70
CPU: AMD Phenom 2 X4 955 Black Edition
UPS: Antec TRUEPOWER Quattro 850 watt
RAM: Corsair XMS3 4Gig DDR3 can not remember the speed.
GPU: MSI AMD Radeon R6950 twin Frozr 2
CPU Heat Sink: Cooler Mater Hyper N520
Any help would be great.

Quote from: Svet on 06-May-12, 02:30:14
try with another video card then
Also done that to no effect, currently I don't have a spare CPU that will work on my motherboard. I was hoping that some one has had this problem before because I have never seen my computer start up with all the LEDs on as it starts up. Also the hard drive LED is on constantly even when there is no hard drive plug in.

Hot swap and JSP debugging for Weblogic in exploded format?

Hi,
I'm trying to use JDeveloper for JSF development to be deployed to a weblogic server.
I must say JDeveloper is a great tool for JSF development as none of the free IDE in the market can do what JDeveloper does.
However, I have a question on hot swap and JSP debugging.
I have managed to setup JDeveloper to debug my JSF application deploy to my Weblogic server's applications folder in exploded format.
I can step through the java code.
However, I didn't manage to do a hot swap and the break point set in the JSF-JSP does not seems to take effect.
I would appreciate any advice on the problem.
Thanks.
Han Ming

How did you setup the server to handle exploded format? Appreciate the help. Sorry can't help with your question though.
Thnx.
Soni

Region Monitoring iOS 7 : didEnterRegion method is not calling when app is killed by user or by OS in iOS 7 only. It is working fine when it is in background. and the same code is working fine with iOS 6 for both app in suspended mode and background mode.

Region Monitoring iOS 7 : didEnterRegion method is not calling when app is killed by user or by OS in iOS 7 only. It is working fine when it is in background. and the same code is working fine with iOS 6 for both app in suspended mode and background mode. What changes I have to made to work great in iOS 7 also.

I rewrote code for debugging purpose and tried to catch error using GetLastError();  method,
but it only printed 0. Below is code snippet; I think Create() throw an exception
and code goes to catch block.
LONG ConnectTS(CString strIP, UINT n_Port)
try{
          ErrorLog(0,0,"ConnectTS is calling Create [is going to call]","");
          if(!Create())
// Exception Line
n_Err = GetLastError();
return NET_INIT;
catch(...)
                   DWORD errorCode = GetLastError();
                   CString errorMessage
                   errorMessage.Format("%lu",errorCode);
                   ErrorLog (0, 0, "Image
System", (LPTSTR)(LPCTSTR)errorMessage);
                   return  IS_ERR_WINDOWS;
Output: -
ConnectTS is calling Create [is going to call]
Image System
0

DEBUG code in LR 4.0

My windows installation of LR4 is generating a LrCatalog.log file containg DEBUG messages.
Indicates to me there is some left-over debug code in the executable.
It might run faster without this.
Sample of file
04/08/2012 11:14:28 DEBUG removing item about to be processed from queue: "Add c40-8927_8_9.tif to catalog"
04/08/2012 11:14:28 DEBUG executing "Add c40-8927_8_9.tif to catalog"
04/08/2012 11:23:55 DEBUG immediate execution of "Add c40-8924_5_6.tif to catalog"
04/08/2012 11:23:55 DEBUG removing item about to be processed from queue: "Add c40-8924_5_6.tif to catalog"
04/08/2012 11:23:55 DEBUG executing "Add c40-8924_5_6.tif to catalog"
04/08/2012 12:00:10 DEBUG immediate execution of "Add c41-5206_7_8.tif to catalog"
04/08/2012 12:00:10 DEBUG removing item about to be processed from queue: "Add c41-5206_7_8.tif to catalog"
04/08/2012 12:00:10 DEBUG executing "Add c41-5206_7_8.tif to catalog"
04/08/2012 14:34:52 DEBUG initializing writeAccessQueue
04/08/2012 14:34:52 DEBUG immediate execution of "Add c41-4625_6_7.tif to catalog"
04/08/2012 14:34:52 DEBUG removing item about to be processed from queue: "Add c41-4625_6_7.tif to catalog"
04/08/2012 14:34:52 DEBUG executing "Add c41-4625_6_7.tif to catalog"

Another user just reported this as well:
http://forums.adobe.com/message/4326750
He gave details of where the LrCatalog.log file was located (c:\users\<user>\documents), and with that I could see that I have one too and quickly figure out what's probably going on:
- The logging appears to be initiated by LR itself, not by plugins. It occurred without the presence of a "config.lua" file.
- The logging appears to come from the LR SDK's LrCatalog module, which provides plugins with access to the catalog. For example, these two lines:
03/17/2012 09:50:23 DEBUG initializing writeAccessQueue
03/17/2012 09:50:23 DEBUG immediate execution of "Tag: apply keywords"
correspond to the Any Tag plugin invoking catalog:withWriteAccessDo ("Tag: apply keywords", function). My log file had entries from other plugins that accessed the same SDK method.
- The logging may be disabled in LR 4.1RC. The last entry in my LrCatalog.log file occurred just before I upgraded from LR 4.0 to LR 4.1RC.

9C and A2 Debug Codes

Similar Messages

Maybe you are looking for