New build "0d" error code. Swap MB same code!!

marttimat

Commendable
Mar 18, 2016
19
0
1,520
Hello forum!

I recently had an issue with my first gaming pc build. It all worked with the original ASRock MB but then I got debug 19 and then finally 0d before installing the OS. It all started once I moved the tower to its final install location.

I finally decided to RMA the first board and ordered a new MSI titanium gaming MB (Since ASRock has known '0d" issues).

After install of all the components on the new MSI board tonight, boot goes go from "00" to "0d". Moved the RAM to all DIMMS same result. Even without GPU installed same result. Nothing on screen

Since this is the exact same situation from the ASRock MB, I wonder if it would be my memory or CPU?

I do have a water cooler installed Corsair H80i. (no issues installing)

I checked the MB pins prior to installing CPU, all looked great under the magnifying glass.

Please help!

Here is my build spec:
Motherboard: MSI XPOWER GAMING TITANIUM LGA 1151 Intel Z170
Motherboard BIOS version: Stock
Processor: Intel Core i5-6600K 6M Skylake Quad-core 3.5 GHz LGA 1151 Intel Z170
Memory: G. SKILL TridentZ Series 32GB (2 X 16GB) 288 Pin DDR4 SDRAM F4-3000C15D-32GTZ
GPU: EVGA GeForce GTX 980 Ti Kingpin
SSD #1: Samsung 950 Pro M.2 512GB
SSD #2: Crucial MX200 1TB SATA SSD
Case: Fractal Design Define R5
Cooler: Corsair H80i V2
Mouse: Logitech G502 Proteus
Keyboard: Corsair Gaming K70
Power Supply: SeaSonic Platinum SS-860XP2 860W
Monitor: Dell Ultrasharp 34” U3415W
OS: Windows 10 Home 64 bit
 


Thanks. I found this article before I posted. I tried updating but the '0d" happens instantly. I do not even have Windows installed yet.

MSI responded to check for bent pins and possible RMA the board. I still feel the odds are unlikely that the same code would arise on two different brand MB?

Could it be my Corsair water cooler being on too tight? Could the CPU be faulty?

Just hard to figure out when there is no definition for "0d"
 
Did you ever get a solution to this? I am in the same situation.




 


I had a bad processor... RMAd the Skylake and all worked out.