Jump to content

Went to boot up my X99 system with a 5820K on an Gigabyte SOC Champion motherboard and found out that it isn't posting. Fan spin for about a second, it shows debug code 60, and the turns off. Looked up debug code and it is DXE Core is started. That doesn't really indicate a specific problem so I decided to start troubleshooting. Swapped out RAM, reseated the CPU and GPU and still the same situation. Would anybody have any insight on this? 

Specs: Intel Core i7 2600k | Gigabyte Z68-UD3H-B3 | EVGA 1080 FTW2 Gaming | Kingston HyperX Red 16GB | Cooler Master Hyper 212 Evo | Corsair CX600 | 
Lian Li Lancool-II white

 

Laptop: ASUS ROG Zephyrus M15 (Intel i7, 16GB, RTX 2070) | 2013 MacBook Pro 15 (Intel i7, 16GB, GT750M)

 

 

Link to post
Share on other sites

3 minutes ago, Matty2048 said:

clear cmos try only using one slot of ram stuff like that 


 

Already tried that. My motherboard has a dual BIOS option and I switched it to the secondary BIOS and tired booting and the same. 

Specs: Intel Core i7 2600k | Gigabyte Z68-UD3H-B3 | EVGA 1080 FTW2 Gaming | Kingston HyperX Red 16GB | Cooler Master Hyper 212 Evo | Corsair CX600 | 
Lian Li Lancool-II white

 

Laptop: ASUS ROG Zephyrus M15 (Intel i7, 16GB, RTX 2070) | 2013 MacBook Pro 15 (Intel i7, 16GB, GT750M)

 

 

Link to post
Share on other sites

I also tried booting up with all of the RAM removed to see if it would give me a NO RAM code but it still shows code 60-DXE core started. Would this indicate a bad CPU? 

Specs: Intel Core i7 2600k | Gigabyte Z68-UD3H-B3 | EVGA 1080 FTW2 Gaming | Kingston HyperX Red 16GB | Cooler Master Hyper 212 Evo | Corsair CX600 | 
Lian Li Lancool-II white

 

Laptop: ASUS ROG Zephyrus M15 (Intel i7, 16GB, RTX 2070) | 2013 MacBook Pro 15 (Intel i7, 16GB, GT750M)

 

 

Link to post
Share on other sites

  • 4 years later...
  • 1 year later...

I follow up the necro trend with my Asus X99-E WS/USB3.1 giving me Q code 60 after work Friday. Have spent the entire weekend testing every suggestion online, and apart from testing alternative X99 CPU/MB (which I do not have), I have achieved nothing.

I did plan do do an upgrade to this 2016 rig sometime in the new year, but not in the first week..

Any way to ID if the fault is in the CPU or MBB?

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×