Overclock.net › Forums › AMD › AMD Motherboards › FM2 rig won't boot - '0d' debug code
New Posts  All Forums:Forum Nav:

FM2 rig won't boot - '0d' debug code

post #1 of 8
Thread Starter 
I have an GA-F2A85X-UP4 with an a8-5600K.

When I don't try accessing the bios, the pc boots into windows and runs fine. When I try accessing the bios, I get a black screen and a debug code of: 0d. If only 0d was in the motherboard manual....I guess that would take the fun out of troubleshooting. The PC had no issues yesterday. Already tried resetting the bios via battery removal.


Ideas?
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
post #2 of 8
I ran into some issues with debug codes being thrown on my MSI 990FX GD80 and it turned out to be my memory not liking going over 1333 very well. Heres a pdf with a lot of the debug codes for those LCD readouts. They';re pretty much standard across motherboards since the backbone of the EFI is all built the same under the hood.
Quote:
13 Evolved
(9 items)
 
13
(9 items)
 
Classic
(11 items)
 
CPUMotherboardGraphicsGraphics
AMD FX-8120 Bulldozer 8-core CPU MSI 990FX GD80 v2 ASUS R9-280 Direct CU II ASUS R9-280 Direct CU II 
RAMCoolingOSPower
Kingston 16GB (4 x 4 GB) DDR3-1333 C9 1.5v Phanteks PH-TC14PE Windows 10 Antec True-power Quattro 1200W 
Case
Cooler Master CM Storm Stryker 
CPUMotherboardGraphicsRAM
1045T @4.05Ghz 1.45v [300 FSB] 3000 NB 1.26v MSI 990FXA-GD80 v2 EVGA GTX480 @820mhz Crucial Ballistix sport VLP 2x4GB @ 1333 cas 7 
CoolingKeyboardPowerCase
Thermaltake Water 2.0 Performer Logitech G710+ OCZ ZT650w CM Storm Stryker 
Mouse
CM Storm Xornet 
CPUMotherboardGraphicsRAM
Phenom II x4 965 @4.1 [2800 cpu-nb] Asus M5A97 R1 AMD 6950 Kingston HyperX 1600mhz 8-9-8-20-21 
Hard DriveCoolingOSMonitor
Too many Thermaltake Water 2.0 Performer Win7 Extreme Edition R1 64bit Acer P224W 22" 1050p 
PowerCaseMouse
Antec BP550 plus Corsair 200R CM Storm Xornet 
  hide details  
Reply
13 Evolved
(9 items)
 
13
(9 items)
 
Classic
(11 items)
 
CPUMotherboardGraphicsGraphics
AMD FX-8120 Bulldozer 8-core CPU MSI 990FX GD80 v2 ASUS R9-280 Direct CU II ASUS R9-280 Direct CU II 
RAMCoolingOSPower
Kingston 16GB (4 x 4 GB) DDR3-1333 C9 1.5v Phanteks PH-TC14PE Windows 10 Antec True-power Quattro 1200W 
Case
Cooler Master CM Storm Stryker 
CPUMotherboardGraphicsRAM
1045T @4.05Ghz 1.45v [300 FSB] 3000 NB 1.26v MSI 990FXA-GD80 v2 EVGA GTX480 @820mhz Crucial Ballistix sport VLP 2x4GB @ 1333 cas 7 
CoolingKeyboardPowerCase
Thermaltake Water 2.0 Performer Logitech G710+ OCZ ZT650w CM Storm Stryker 
Mouse
CM Storm Xornet 
CPUMotherboardGraphicsRAM
Phenom II x4 965 @4.1 [2800 cpu-nb] Asus M5A97 R1 AMD 6950 Kingston HyperX 1600mhz 8-9-8-20-21 
Hard DriveCoolingOSMonitor
Too many Thermaltake Water 2.0 Performer Win7 Extreme Edition R1 64bit Acer P224W 22" 1050p 
PowerCaseMouse
Antec BP550 plus Corsair 200R CM Storm Xornet 
  hide details  
Reply
post #3 of 8
Thread Starter 
Quote:
Originally Posted by Overkill View Post

I ran into some issues with debug codes being thrown on my MSI 990FX GD80 and it turned out to be my memory not liking going over 1333 very well. Heres a pdf with a lot of the debug codes for those LCD readouts. They';re pretty much standard across motherboards since the backbone of the EFI is all built the same under the hood.
Quote:



Hmm, I have tested three dimms that work in other pcs (and that have all worked in this pc before) and I keep getting the debug code. I'm not sure what 0d maps to on that pdf: Reserved for future AMI SEC error codes


'0x0C – 0x0F SEC errors'
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
post #4 of 8
Thread Starter 
So I have been testing all of the ram I have. The dominators 1866 give me 0d. They used to work. One dominator instead of the pair gives me 06. My one gskill 1600 bargain gives me 06 (used to work for months). My 1066 alone or both dimms gives me 06. All combinations give one beep and make it to the start up splash sceen. After that though, they all stop on one debug code or another. Ive tried resetting the cmos via battery but not longer than ~5-10 minutes.
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
post #5 of 8
Quote:
Originally Posted by Mr.N00bLaR View Post

So I have been testing all of the ram I have. The dominators 1866 give me 0d. They used to work. One dominator instead of the pair gives me 06. My one gskill 1600 bargain gives me 06 (used to work for months). My 1066 alone or both dimms gives me 06. All combinations give one beep and make it to the start up splash sceen. After that though, they all stop on one debug code or another. Ive tried resetting the cmos via battery but not longer than ~5-10 minutes.
Have you tried the DIMMs in another desktop? If it works time to RMA your mobo me thinks.
Ayase Eli
(21 items)
 
  
CPUMotherboardGraphicsRAM
Intel E5-2675 V3 ASUS X99-A/USB3.1 Sapphire R9 290X ref Corsair Vengeance LPX 2400MHz C14 
Hard DriveHard DriveHard DriveCooling
Zotac SSD Premium 480GB OCZ Vector 180 480GB Hitachi 7K3000 3TB 7200rpm Barrow 250mm Glass 
CoolingCoolingCoolingCooling
EK Supremacy MX EK-D5 X-TOP Rev.2 + Swiftech D5 Aquacomputer R9 290X "Bitspower EML" fittings 
CoolingCoolingMonitorKeyboard
Magicool 360 Ultra Magicool 240 Slim Dell U2713HM CM Storm MECH 
PowerCaseMouseMouse Pad
FSP Aurum PT 1200 Phanteks Enthoo Pro Logitech G502 Tesoro Aegis X3 Virtus.Pro 
Audio
Audio Technica M50X 
  hide details  
Reply
Ayase Eli
(21 items)
 
  
CPUMotherboardGraphicsRAM
Intel E5-2675 V3 ASUS X99-A/USB3.1 Sapphire R9 290X ref Corsair Vengeance LPX 2400MHz C14 
Hard DriveHard DriveHard DriveCooling
Zotac SSD Premium 480GB OCZ Vector 180 480GB Hitachi 7K3000 3TB 7200rpm Barrow 250mm Glass 
CoolingCoolingCoolingCooling
EK Supremacy MX EK-D5 X-TOP Rev.2 + Swiftech D5 Aquacomputer R9 290X "Bitspower EML" fittings 
CoolingCoolingMonitorKeyboard
Magicool 360 Ultra Magicool 240 Slim Dell U2713HM CM Storm MECH 
PowerCaseMouseMouse Pad
FSP Aurum PT 1200 Phanteks Enthoo Pro Logitech G502 Tesoro Aegis X3 Virtus.Pro 
Audio
Audio Technica M50X 
  hide details  
Reply
post #6 of 8
Thread Starter 
Quote:
Originally Posted by DaveLT View Post

Quote:
Originally Posted by Mr.N00bLaR View Post

So I have been testing all of the ram I have. The dominators 1866 give me 0d. They used to work. One dominator instead of the pair gives me 06. My one gskill 1600 bargain gives me 06 (used to work for months). My 1066 alone or both dimms gives me 06. All combinations give one beep and make it to the start up splash sceen. After that though, they all stop on one debug code or another. Ive tried resetting the cmos via battery but not longer than ~5-10 minutes.
Have you tried the DIMMs in another desktop? If it works time to RMA your mobo me thinks.


They all work in my other pc. Hmm, it is aware that no memory has been installed when I take it all out.
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
post #7 of 8
Thread Starter 
Now the only debug codes that appear in all mem configs are '0d'. I guess I'll have to try to RMA the board tomorrow.
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
post #8 of 8
Thread Starter 
I know its been a few months but I never really resolved this. I sent it back and gigabyte said it was fine. After trying a few keyboards and standing upside down on my head they think there might be a problem now... Anther 15$ to ship this hunk of junk back to gigabyte.. Anyone else have any ideas why I get this 0D code? This motherboard is about to get office spaced...
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
6600K
(12 items)
 
  
CPUMotherboardGraphicsRAM
i5-6600k 4.6GHz Gigabyte z170XP-SLi-CF Sapphire R9-280X Toxic Corsair DDR4 2133MHz @ 3,000MHz 
Hard DriveCoolingOSKeyboard
Intel 535 480GB SSD Noctua NH-D15 Windows 10 Pro 64bit Microsoft Natural 4000 
PowerCaseMouseMouse Pad
Corsair TX950 ThermalTake Armor Logitech G700 Ripper XXL 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › FM2 rig won't boot - '0d' debug code