Question Computer not fully working after attempted overclocking

[SniperWolfOrtiz]

This is a custom built tower with the following specs

Motherboard: Bio star tz77ex3
CPU: I5 3570k
GPU: Radeon vision tech hd 7950
Ram: 4x g.skill ripjaw 4G

This tower was working just fine up until I attempted to overclock it. After the attempted overclock the computer will now not fully boot at times in sit on postcode 32 or d0.

I have tried just about everything including removing all RAM sticks but one removing video card and even completely removing the power supply to reset the cmos.

Im not too sure what to do anymore and just really need any help i can get.

 

[JRock247]

Have you checked your mobo manual to see what post code 32 or d0 actually means?

 

[SniperWolfOrtiz]

Have you checked your mobo manual to see what post code 32 or d0 actually means?

It is not listed. Which is extremely annoying.

 

[jay32267]

This is a custom built tower with the following specs

Motherboard: Bio star tz77ex3
CPU: I5 3570k
GPU: Radeon vision tech hd 7950
Ram: 4x g.skill ripjaw 4G

This tower was working just fine up until I attempted to overclock it. After the attempted overclock the computer will now not fully boot at times in sit on postcode 32 or d0.

I have tried just about everything including removing all RAM sticks but one removing video card and even completely removing the power supply to reset the cmos.

Im not too sure what to do anymore and just really need any help i can get.

I don't think that removing the power supply ensures you reset the CMOS as the battery would still be there. I would reset the CMOS by either pulling the battery for a while or jumping the motherboard if you have that option.

 

[SniperWolfOrtiz]

I don't think that removing the power supply ensures you reset the CMOS as the battery would still be there. I would reset the CMOS by either pulling the battery for a while or jumping the motherboard if you have that option.

Already did that. Before the leds on the board wouldnt turn on but after resetting the cmos they turned back on

 

[jay32267]

I found this post.
It turns out the D0 code was caused by bad RAM in this case.

https://forums.tomshardware.com/threads/updated-is-it-time-to-rma-this-post-code-d0.397055/

 

[SniperWolfOrtiz]

I found this post.
It turns out the D0 code was caused by bad RAM in this case.

https://forums.tomshardware.com/threads/updated-is-it-time-to-rma-this-post-code-d0.397055/

Alright i had a feeling two were bad as when I was able to boot into my bios it was showing 8 gigs of ram not 16. But im still having the problem where my computer will sit at postcode 32 for a while before restarting.