Correct Solutoion for a problem with my EVGA Classified K

[AndyDalis]

I just got done setting up my new build and was test booting it. Everything went smooth till I rebooted and it continues to go straight to the BIOS. On boot, it gave off 4 beeps as a note. I checked the POST code, which was moving slowly between 30,31, and 32 in numerical order back and forth. I checked the manual and it seemed to be a memory issue. So, I checked the motherboard for the "Memory Error LED" which wasn't on. I then checked supported RAM, and couldn't find my current RAM. Is the correct solution to get new RAM? OR preferably can I make the current RAM work?

Current Build:
https://pcpartpicker.com/user/DalisMagnus/saved/3Y9t6h

 

[SkyNetRising]

Try with single ram module first.
From manual:

• 4 Beeps: This is an error relating to some small recovery errors, which can occur when coming out of sleep/hibernate.
  
  30 Reserved for ASL (see ASL Status Codes section below)
  31 Memory Installed
  32 CPU post-memory initialization is started

 

[AndyDalis]

Try with single ram module first.
From manual:

• 4 Beeps: This is an error relating to some small recovery errors, which can occur when coming out of sleep/hibernate.
  
  30 Reserved for ASL (see ASL Status Codes section below)
  31 Memory Installed
  32 CPU post-memory initialization is started

Ok, no change. I tried each stick in slot 2 one at a time. and it still goes straight to bios
UPDATE: I got to boot to windows.... kinda. the TMP config was on and i had to disable CSM. Plus I had to boot up in LEGACY. It is now "Stuck" on the screen "Geeting Devices Ready"

 

[SkyNetRising]

I'm guessing - you're using windows installation from some other pc.
You should do clean install of windows on your new pc.

 

[AndyDalis]

I'm guessing - you're using windows installation from some other pc.
You should do clean install of windows on your new pc.

Aye that's what I'm attempting right now. Problem is I don't want to lose the files on there and I don't have 480GB+ of storage laying around. It does seem to be the fact I had motherboard drivers from my old motherboard install that weren't to happy