Getting an Odd A2 error Code Only when Overclocking

[KauksR]

Hello Expert Community

This is my first post. Ive done a lot of searching and read through a lot of posts, but I cant seem to find a solution or a thread that's been able to help me with this specific issue. This is my first ever PC build and I am still very new to this fun new world. I feel like there is either a couple of specific problems going on, or I'm making some kind of rookie mistake. I'm hoping that the knowledge you guys have can help me through this.

I recently Built a budget 1080P Gaming PC. After it was built I was able to Overclock the CPU (Intel G3258) up to 3.6 4.0 and 4.2 Ghz before the temperatures started exceeding 80°C. I created profiles for each in the BIOS and left it there for a bit. Recently, my Cooler Master Hyper 212 Plus came in along with a 1TB WD Blue HDD that I'll be using as a slave (OS is loaded on a 120GB Kingston V300 SSD). I added the two components and couple of fans then booted up my system.

I formatted the HDD and everything worked perfectly. I ran a stress test on Intel XTU and the CPU temps never went over 62°C. Naturally, I wanted to push my Processor even further because I've seen what people can do with the G3258, and wanted to try too. So being a little ambitious I went into the BIOS and Upped the ratio to 4.5, adjusted the voltage, then saved.

When my PC booted back up it stayed on a black screen and gave me the A2 error code. I Thought I fried something, but did a little searching a learned how to reset the CMOS. When I did, I had the option of selecting and booting one of my previously saved OC profiles. To be safe, I loaded the stock 3.2Ghz setup and booted up, everything was perfectly fine. I went back into the BIOS and loaded the 4.2Ghz setup, and again everything was perfectly fine. I tried to overclock again with a little more adjustment (higher voltage, lower ratios 4.4, 4.3, 4.1, 3.9 etc.) and every time I did the same A2 would happen. This is where I got stumped.

I Understand that the A2 code has something to do with a hard drive not being recognized. But I can't understand why the error only comes up when I overclock. Is there anything I didn't do? Are there more adjustments that need to be made in the BIOS to get further? Any suggestions on what I could try? I'd like to push my system a little further and I really hope you guys can help. I appreciate you taking the time to read this. I apologize for the length, but I felt I needed to be as informative as possible.

PC Specs
- Intel G3285
- MSI Z97 PC Mate
- HyperX FURY 8GB (2x4GB) DDR3 1866MHz

- EVGA GeForce GTX950

- Kingston V300 120GB SSD
- 1TB WD Blue
- Cooler Master Hyper 212 Plus
- Corsair CX500 500W 80 Plus Bronze

[Deagon]

A2 is a post code that means "IDE detect" (is looking for hard drives and disk drives) It's only hanging here because you pushed the CPU too far and it can't go passed this step. Not all CPU's from a certain line will be able to do what others from the same line will be able to when overclocking. 4.5 ghz seems to be your CPU's ceiling. 

[Captain_WD]

11 hours ago, KauksR said:

~snip~

Hi there KauksR Welcome to the community! 

 

Have you checked your motherboard's manual for the description of that A2 code? Are there any beeping sounds that accompany it? 

I believe that this and this topics will be helpful in your case.   

 

Try booting into the OS and check the health of your storage devices. For the WD Blue you can use WD Data Lifeguard Diagnostic. Check if the drive passes both the quick and the extended tests. 

 

Captain_WD.

[Deagon]

7 minutes ago, Captain_WD said:

Have you checked your motherboard's manual for the description of that A2 code?

I've actually done this bit myself and couldn't find it in the manual, MSI website describes the post-code as "IDE detect" which is honestly irrelevant to the problem because it only occurs when overclocking passed a certain point, and it hangs (from being overclocked too much I suspect).

[Captain_WD]

2 hours ago, Deagon said:

~snip~

Maybe this has something to do with the power distribution across the motherboard. Contacting the manufacturer of the motherboard seems like the easiest way to resolve this.

 

Captain_WD.