F5F Stay Refreshed Software Operating Systems Problem with the new PC not connecting to Windows!

Problem with the new PC not connecting to Windows!

Problem with the new PC not connecting to Windows!

S
SergeantBrul
Junior Member
32
08-15-2016, 08:21 PM
#1
I recently assembled a brand new PC and faced several issues starting with Windows installation. It would freeze on the first try, and I couldn’t even launch the setup. Fortunately, I used another machine to install Windows onto it, which allowed me to access the installation screen once before I powered off the PC. After a short break, it restarted and suddenly displayed the Blue Screen of Death. When I tried to boot back in, I encountered a black screen with a postcode beep and a looping error. While I could navigate the BIOS and it functioned properly, getting into Windows remained frustrating. I’ve been working on this for hours without success. Details: Ryzen 2200G, Asus Prime B350M-E (Bios 3803/Latest), 400W EVGA PSU, 1TB Western Digital Green DDR4, 8GB anarchy RAM, Windows 10.
S
SergeantBrul
08-15-2016, 08:21 PM #1

I recently assembled a brand new PC and faced several issues starting with Windows installation. It would freeze on the first try, and I couldn’t even launch the setup. Fortunately, I used another machine to install Windows onto it, which allowed me to access the installation screen once before I powered off the PC. After a short break, it restarted and suddenly displayed the Blue Screen of Death. When I tried to boot back in, I encountered a black screen with a postcode beep and a looping error. While I could navigate the BIOS and it functioned properly, getting into Windows remained frustrating. I’ve been working on this for hours without success. Details: Ryzen 2200G, Asus Prime B350M-E (Bios 3803/Latest), 400W EVGA PSU, 1TB Western Digital Green DDR4, 8GB anarchy RAM, Windows 10.

R
randomabby
Senior Member
476
08-16-2016, 12:14 AM
#2
Are your RAMs operating at the rates they’re labeled for? Have you attempted to run Memtest86 to identify any issues?
R
randomabby
08-16-2016, 12:14 AM #2

Are your RAMs operating at the rates they’re labeled for? Have you attempted to run Memtest86 to identify any issues?

S
147
08-16-2016, 08:53 AM
#3
My RAM is working at its rated frequency of 2133MHz. I haven’t managed to overclock it much since this issue has arisen, and I’m unable to do so because I can’t access Windows on the system.
S
Shadowxplayz23
08-16-2016, 08:53 AM #3

My RAM is working at its rated frequency of 2133MHz. I haven’t managed to overclock it much since this issue has arisen, and I’m unable to do so because I can’t access Windows on the system.

B
BriannaJ16
Member
123
08-17-2016, 02:46 PM
#4
Do you have another power supply ready? Have you experimented with various SATA cables and/or connectors on the motherboard side?
B
BriannaJ16
08-17-2016, 02:46 PM #4

Do you have another power supply ready? Have you experimented with various SATA cables and/or connectors on the motherboard side?

J
JimHogg8
Junior Member
20
08-26-2016, 09:23 PM
#5
I've tested my primary hard drive on this machine, used various SATA cables, but nothing worked. It seems like it's just overheating.
J
JimHogg8
08-26-2016, 09:23 PM #5

I've tested my primary hard drive on this machine, used various SATA cables, but nothing worked. It seems like it's just overheating.

D
Darth_Rekker
Junior Member
13
08-31-2016, 04:28 AM
#6
Checking temperatures in BIOS shows real changes. Updating the operating system causes little stress. If overheating occurs, simply restart the cooler and it resolves. Your symptoms seem linked to a drive or connection problem—you can install the OS but still can't boot. Would you like to try booting Windows from another PC using the affected drive?
D
Darth_Rekker
08-31-2016, 04:28 AM #6

Checking temperatures in BIOS shows real changes. Updating the operating system causes little stress. If overheating occurs, simply restart the cooler and it resolves. Your symptoms seem linked to a drive or connection problem—you can install the OS but still can't boot. Would you like to try booting Windows from another PC using the affected drive?

M
Muggy215
Member
147
09-01-2016, 04:29 AM
#7
You've determined the issue isn't overheating, as the CPUID reads show 29 in Windows. You can access Windows now, but it freezes after about 15 minutes of idle time. When it froze, the temperature was around 28°C. It's unclear what might be causing this behavior.
M
Muggy215
09-01-2016, 04:29 AM #7

You've determined the issue isn't overheating, as the CPUID reads show 29 in Windows. You can access Windows now, but it freezes after about 15 minutes of idle time. When it froze, the temperature was around 28°C. It's unclear what might be causing this behavior.

G
Gebbi_01
Junior Member
13
09-01-2016, 02:38 PM
#8
Trust the assessment—it's one of three options: drive, motherboard or RAM. By testing each separately (switching RAM, trying different slots, using another board, etc.), you can identify the faulty component. Just be prepared for possible bad luck if the issue stems from a defective part.
G
Gebbi_01
09-01-2016, 02:38 PM #8

Trust the assessment—it's one of three options: drive, motherboard or RAM. By testing each separately (switching RAM, trying different slots, using another board, etc.), you can identify the faulty component. Just be prepared for possible bad luck if the issue stems from a defective part.

M
miner_kid
Member
131
09-03-2016, 01:49 PM
#9
I checked the drive and confirmed it's not the issue. I also have alternative DDr4 RAM available for testing. In the worst case, I might need a new motherboard, though that's acceptable. Thanks!
M
miner_kid
09-03-2016, 01:49 PM #9

I checked the drive and confirmed it's not the issue. I also have alternative DDr4 RAM available for testing. In the worst case, I might need a new motherboard, though that's acceptable. Thanks!

C
Cadariou
Posting Freak
835
09-03-2016, 09:30 PM
#10
It seems the RAM is problematic and might not work across different platforms. If someone else has encountered this problem but the RAM functions elsewhere, it could indicate unsupported compatibility.
C
Cadariou
09-03-2016, 09:30 PM #10

It seems the RAM is problematic and might not work across different platforms. If someone else has encountered this problem but the RAM functions elsewhere, it could indicate unsupported compatibility.