Gavination

I'm gonna need to know where you got this...purely for educational reasons of course...

This is a long shot, but have you checked if the SATA power cable you're plugging into is actually plugged into your power supply? I've made this mistake...many times before.

So update for all those interested. I replaced my CPU cooler with the liquid AIO I'd already had (didn't do it the first time cause I'd run out of thermal paste, it's a long story). Anyways, without changing ANYTHING else, the machine wouldn't post. At first, I thought "damn did i put too much pressure on the cpu?", but that turned out to be wrong. It was the RAM. Again. Even after the BIOS update, it still came back to bite me. Swapped in the old RAM, booted no problem. Put in the new one, gets stuck on the DRAM debug light or, weirdly, the VGA light sometimes. So after leaving it for the night, coming back the next morning and trying it with one stick of the new ram, it worked. Putting in the other didn't work. Putting them both in the same channel didn't work. Was going to give up hope after doing one last thing: swapping the order of the RAM sticks. It boots. In dual channel. It also boots cold, after a shutdown. I have 0 idea why. Idk if I'm happy it works or angry it doesn't make sense. Just to be clear, this certainly isn't the first machine I've worked on, I've just never seen this issue before. My only guess is since it's not rated for any specific speed supported by the motherboard manufacturer, it's probably not *supposed* to work, and the fact that it does is sort of a fluke. Other than that, I got nothing lol. Anyways, thanks a ton for the assist, just thought it'd be fun to report back.

1000% agree. It sounds like a lot, and that's because it is. I'd also like to add that when it comes to resumes, get as many eyes on it as possible before you toss it out in front of folks you want a job or internship from. I recommend obsessing over your resume and remembering that it's a living document; it's supposed to grow and change as you gain more experience.

Hi! Software developer here, and I'm more than happy to echo some of the sentiment along with providing a very biased opinion on how tech careers should be looked at. I'll be speaking purely from the perspective of a software engineering curriculum, but I'm sure you can get some generalities as well. Firstly, before anything, remember to be passionate. You have to love what you do, and while some of it will be a slog, if you hate every moment, consider something else. When recruiting from most universities, we tend to look more at how the candidate stands out than anything. Meaning, are you just someone who did more than undergo a CS or EE curriculum in college, or did you attend hackathons, join engineering groups, maybe found a way to marry your passion for other things alongside tech? Some general pointers I'd say would be good to look into are: - Joining engineering groups: IEEE, your school's CS club, Women in Technology, etc... - Participating in student hackathons. Checkout the Major League Hacking site. put em on your resume, especially if you win - Hunting hard for internships. Make yourself as interesting as possible, start at the top of Fortune 500 companies list, and apply EVERYWHERE - Go to conferences where you know recruiting is important. The Grace Hopper Celebration and Richard Tapia conference are targeted around promoting diversity in tech, so networking with folks there would be a great opportunity. - Start a GitHub account, learn Git, and upload cool things you're building in order to learn. Recruiters LOVE to see Github accounts from students. It tells them you can walk the walk and talk the talk. - Learn. Learn everything and always be hungry to learn more. Tech changes dramatically very quickly, so you have to be prepared to always be skilling up in something. *leaves soapbox*

I certainly have it running in dual channel, but thanks for the note!

Folks, I'd like to thank you all as well as the power of the forum. A combination of updating the BIOS, clearing the CMOS, and swapping RAM in and out seems to have worked (though not individually lol). I was a bit nervous, but it looks like everything is on the up and up. You're all awesome.

Hahaha no I didn't. Just giving my perspective. I'd hope my skin was a bit thicker than a recommendation tearing me down.

Honestly, it was just the order in which i purchased things. I've had these RAM modules well before I knew I'd be going Ryzen, and well, this is where I ended up.

Many thanks for the replies. So in regards to the first comment: By "booting properly", I mean I might see a BIOS screen 1x every 5 times i try to boot. then, the screen is either frozen or input isn't registered. So sadly, changing the RAM speed wasn't possible. That's a fantastic question...that I hadn't even considered haha. Please forgive me. I'll double check BIOS version and get back with results!

Hello! So I've run into a bit of a pickle in upgrading my system. I'd been doing incremental upgrades over time, and this CPU/Motherboard (Ryzen 3900X/Aorus X570 Pro Wifi) was supposed to be the final one. Unfortunately, after quite some time troubleshooting, I found that it wasn't booting properly because of the RAM I was using (32 GB Corsair Vengeance RGB @ 3000Mhz). After switching over to some older 16GB kit, it worked without a hitch. So, I went through the Motherboard's compatibility site and saw the weirdest thing: it supports 3200 MHz and 2933 MHz, but not 3000? I thought that was weird, but I was wondering if there was any way I could overclock or downclock to match the required speeds? Problem is, I can't boot with this RAM installed. Has anyone else experienced a weird issue like this and gotten around it? Would be a shame if I have to buy another set of memory. Thanks for any help!

You are person of the year. Thanks for the update. I hadn't gotten around to OC'ing yet, but I'm amped to give it a go.

Please report back with your findings! Just picked up a 3800x and the exact same cooler lol.

I second Bob Tabor, in case you needed an extra push. A lot of .NET devs owe their careers to his work (including me)

JSON.NET is your best friend for C#. I don't know a .NET dev that doesn't use it.