- Aug 27, 2009
- 13
- 0
- 18,510
Hey all, I'm having issues with a recent build and I'd really appreciate some help diagnosing and fixing it.
(Specifications forthcoming, can't find them on my phone at the moment)
Background
It's a 2K AMD build that I put together about six months ago. In the beginning I had a bit of trouble with the power supply (it was the correct wattage but not properly rated), but after a proper replacement it's been running like a dream. The memory is on the list of compatible parts, and the main storage drive is one of the newer Samsung m.2s.
Issue
Fast forward to today and it was refusing to boot up. I waited a bit and now it will POST but I'm getting two short beeps (which I understand to be a memory issue). I should also mention that it's currently loading all the way into the Gigabyte (my MoBo manufacturer) splash screen and attempting an "automatic diagnosis and repair", but it's been deadlocked in that for the better part of three hours.
Additional Info
Something similar happened to my laptop (an old and crappy HP) just two weeks ago, but I had assumed it to be a hard drive issue. Seeing as my new build doesn't share anything in common with my laptop except Windows 10, am I right to now wonder if this is a Windows issue? If that's the case, how did I trigger this twice, and why am I getting the two beeps on start up?
Any insight would be much appreciated. Happy 4th to you American posters!
-HBoP
(Specifications forthcoming, can't find them on my phone at the moment)
Background
It's a 2K AMD build that I put together about six months ago. In the beginning I had a bit of trouble with the power supply (it was the correct wattage but not properly rated), but after a proper replacement it's been running like a dream. The memory is on the list of compatible parts, and the main storage drive is one of the newer Samsung m.2s.
Issue
Fast forward to today and it was refusing to boot up. I waited a bit and now it will POST but I'm getting two short beeps (which I understand to be a memory issue). I should also mention that it's currently loading all the way into the Gigabyte (my MoBo manufacturer) splash screen and attempting an "automatic diagnosis and repair", but it's been deadlocked in that for the better part of three hours.
Additional Info
Something similar happened to my laptop (an old and crappy HP) just two weeks ago, but I had assumed it to be a hard drive issue. Seeing as my new build doesn't share anything in common with my laptop except Windows 10, am I right to now wonder if this is a Windows issue? If that's the case, how did I trigger this twice, and why am I getting the two beeps on start up?
Any insight would be much appreciated. Happy 4th to you American posters!
-HBoP
Facebook
Twitter
Instagram