Upvote Upvoted 6 Downvote Downvoted
Unresponsive computer upon entering OS
posted in Hardware
1
#1
0 Frags +

Hi,
Following a fatal overheating issue with the laptop I used to play TF2 on, I recently built a new PC.
Specs are as follow:

Show Content
Motherboard: Asus TUF B450 PLUS GAMING
CPU: AMD - Ryzen 5 2600X 3.6 GHz 6-Core Processor
GPU: KFA2 GeForce GTX 1060 OC REDBLACK, 6 Go
PSU: EVGA SuperNOVA 550 G3, 550W
Case is Aerocool CyberX Advance. I used the hard drives that were in my laptop, which are 2 500Go HDD in RAID 0 from Hitachi, with Windows 8.1 on a separate partition.

Now for my issue. Upon building, everything worked fine, I had to install the new drivers on the new computer, and was ready to play again.
However, 3 days after I started using my computer, it randomly froze. It became completely unresponsive with a still image, and ppl couldn't hear me nor could I hear them on Mumble anymore.
After this incident, I power cycled the computer, and it has never been able to start since. I get through the BIOS, and as I reach Windows, 5 or 10 seconds in, the same freeze happens. It is worth noting that it can freeze on a screen that is still blank or right as I'm about to reach the desktop. From an exterior standpoint, the computer seems to keep working normally (fans are spinning, no particular noise from the drives). The odd thing is this freeze never occurs if I stay in the BIOS menu.
I browsed Google and tried a lot of fixes which I listed below:

Show Content
1. My first approach was taking a look at temperatures in the BIOS upon startup. Those were averaging 27/36 degrees for the Motherboard/CPU, with all 4 fans spinning.

2. Following this I started trying to fix my OS:
-Automatic repair
-Safe-mode (same thing happened)
-Use a command prompt to use bootrec, rebuild bcd, also tried to copy the registry from RegBack
-Restore to a previous save point which was dated to a time my computer was still working
-Tried starting without peripherals in order to identify USB driver issues
-Build a recovery thumb drive and tried to run the repair tool through that, which lead to the computer freezing in the same fashion.
-Eventually, since I was not getting anywhere, I decided to Refresh my PC, which supposedly resets your Windows settings while keeping all your files. After this refresh, I now get the 0x000000f error when I start Windows.

3. After that, I’ve came to the conclusion that the issue was in my hard drives. Ran a bootable HDD Regenrator, and both were said to be working fine. I unplugged both of them from the computer, installed Ubuntu Linux on a thumb drive and started trying to boot from there. Same freeze occurs. In a final attempt, I ran a MemCheck, which ran smoothly.
I also decided to buy a SSD to replace the hard drives, which hasn’t arrived yet.

I have ran out of ideas, and I am more than welcome for suggestions. I am planning to post this on specialized forums too.

Hi,
Following a fatal overheating issue with the laptop I used to play TF2 on, I recently built a new PC.
Specs are as follow:
[spoiler]
Motherboard: Asus TUF B450 PLUS GAMING
CPU: AMD - Ryzen 5 2600X 3.6 GHz 6-Core Processor
GPU: KFA2 GeForce GTX 1060 OC REDBLACK, 6 Go
PSU: EVGA SuperNOVA 550 G3, 550W
Case is Aerocool CyberX Advance. I used the hard drives that were in my laptop, which are 2 500Go HDD in RAID 0 from Hitachi, with Windows 8.1 on a separate partition.
[/spoiler]
Now for my issue. Upon building, everything worked fine, I had to install the new drivers on the new computer, and was ready to play again.
However, 3 days after I started using my computer, it randomly froze. It became completely unresponsive with a still image, and ppl couldn't hear me nor could I hear them on Mumble anymore.
After this incident, I power cycled the computer, and it has never been able to start since. I get through the BIOS, and as I reach Windows, 5 or 10 seconds in, the same freeze happens. It is worth noting that it can freeze on a screen that is still blank or right as I'm about to reach the desktop. From an exterior standpoint, the computer seems to keep working normally (fans are spinning, no particular noise from the drives). The odd thing is this freeze never occurs if I stay in the BIOS menu.
I browsed Google and tried a lot of fixes which I listed below:
[spoiler]
1. My first approach was taking a look at temperatures in the BIOS upon startup. Those were averaging 27/36 degrees for the Motherboard/CPU, with all 4 fans spinning.

2. Following this I started trying to fix my OS:
-Automatic repair
-Safe-mode (same thing happened)
-Use a command prompt to use bootrec, rebuild bcd, also tried to copy the registry from RegBack
-Restore to a previous save point which was dated to a time my computer was still working
-Tried starting without peripherals in order to identify USB driver issues
-Build a recovery thumb drive and tried to run the repair tool through that, which lead to the computer freezing in the same fashion.
-Eventually, since I was not getting anywhere, I decided to Refresh my PC, which supposedly resets your Windows settings while keeping all your files. After this refresh, I now get the 0x000000f error when I start Windows.

3. After that, I’ve came to the conclusion that the issue was in my hard drives. Ran a bootable HDD Regenrator, and both were said to be working fine. I unplugged both of them from the computer, installed Ubuntu Linux on a thumb drive and started trying to boot from there. Same freeze occurs. In a final attempt, I ran a MemCheck, which ran smoothly.
I also decided to buy a SSD to replace the hard drives, which hasn’t arrived yet.
[/spoiler]
I have ran out of ideas, and I am more than welcome for suggestions. I am planning to post this on specialized forums too.
2
#2
3 Frags +

Does your motherboard have a little display? It might give an error code when the freeze happens. Seems like a hardware issue

Does your motherboard have a little display? It might give an error code when the freeze happens. Seems like a hardware issue
3
#3
3 Frags +

Unplug the HDDs, remove the mobo from the case, place it on a non-conductive surface and try Linux again.

Unplug the HDDs, remove the mobo from the case, place it on a non-conductive surface and try Linux again.
4
#4
1 Frags +

I have an update: I can boot the computer if there aren't any USB plugged into. If I plug anything, the peripheral works for a couple of seconds then the whole computer freezes. I've managed to get to my desktop by typing my password and quickly unplugging the keyboard. I also managed to open the Peripherals window, which told me there were several unrecognized peripherals plugged into my computer. Using the "Check for new Hardware" function or trying to update the drivers failed.
Current plan is to wait for my SSD and install a fresh Windows on it.

HellbentDoes your motherboard have a little display? It might give an error code when the freeze happens. Seems like a hardware issue

It does not afaik

I have an update: I can boot the computer if there aren't any USB plugged into. If I plug anything, the peripheral works for a couple of seconds then the whole computer freezes. I've managed to get to my desktop by typing my password and quickly unplugging the keyboard. I also managed to open the Peripherals window, which told me there were several unrecognized peripherals plugged into my computer. Using the "Check for new Hardware" function or trying to update the drivers failed.
Current plan is to wait for my SSD and install a fresh Windows on it.

[quote=Hellbent]Does your motherboard have a little display? It might give an error code when the freeze happens. Seems like a hardware issue[/quote]
It does not afaik
5
#5
7 Frags +

Any news?

Any news?
6
#6
3 Frags +
SetsulAny news?

Hi,
My issue was solved very randomly, I found a couple of flashes for my BIOS, applied them, and it worked. I have no idea what caused it in the first place, when I was done with the flashes it was still giving me the same freeze. It randomly started working the next day, witchcraft basically.
Sorry for the late notice

[quote=Setsul]Any news?[/quote]
Hi,
My issue was solved very randomly, I found a couple of flashes for my BIOS, applied them, and it worked. I have no idea what caused it in the first place, when I was done with the flashes it was still giving me the same freeze. It randomly started working the next day, witchcraft basically.
Sorry for the late notice
7
#7
2 Frags +

Hi again,
When I thought my problems were actually fixed, it turns out they weren't. I no longer have the freeze issue, but my computer restarts at random times (the screen just goes black, and then returns to the bios screen).
I tried to find a pattern for when this actually happens, but couldn't. Some of the moments that are very likely to make my computer restart are listed below:
-opening a new program (although steam & mumble are 2 of the less likely programs to crash it)
-closing a program
-exiting a full screened video (this one is very odd but very consistent, if I leave a video in full screen for more than a minute my PC crashes the moment I press escape or return to desktop button)
All of the vents are spinning, CPU temps is around 45 degrees on average, Motherboard 30 degrees. I tried to take down the vent and re-apply thermal paste, didn't work.
I also tried to upgrade from Windows 8.1 to Windows 10, and the installation crashes during the final restart, while giving me the 0xC1900101 - 0x20017 "Install failed during the SAFE_OS phase with an error on the BOOT operator".
Looking for suggestions on how to fix this once and for all, any help is appreciated.
Thanks!

Hi again,
When I thought my problems were actually fixed, it turns out they weren't. I no longer have the freeze issue, but my computer restarts at random times (the screen just goes black, and then returns to the bios screen).
I tried to find a pattern for when this actually happens, but couldn't. Some of the moments that are very likely to make my computer restart are listed below:
-opening a new program (although steam & mumble are 2 of the less likely programs to crash it)
-closing a program
-exiting a full screened video (this one is very odd but very consistent, if I leave a video in full screen for more than a minute my PC crashes the moment I press escape or return to desktop button)
All of the vents are spinning, CPU temps is around 45 degrees on average, Motherboard 30 degrees. I tried to take down the vent and re-apply thermal paste, didn't work.
I also tried to upgrade from Windows 8.1 to Windows 10, and the installation crashes during the final restart, while giving me the 0xC1900101 - 0x20017 "Install failed during the SAFE_OS phase with an error on the BOOT operator".
Looking for suggestions on how to fix this once and for all, any help is appreciated.
Thanks!
8
#8
1 Frags +

Have you tried only using one stick of RAM? Swap sticks if the problem persists and see if any stick of RAM works individually. Probably won't work, but worth a try.

Have you tried only using one stick of RAM? Swap sticks if the problem persists and see if any stick of RAM works individually. Probably won't work, but worth a try.
9
#9
0 Frags +

Double check your PSU cables are plugged in correctly at both ends (PSU side and components). Also, if you didn't plug the AC wall cable in properly at the back it can cause problems on some PSUs from my experience. If you can use a known good power supply to test

Double check you plugged things into the motherboard correctly (fans, front usb, power/reset etc)

Double check your graphics card to see if it is plugged in all the way into the PCI-e slot and the power is plugged in properly too.

Double check your PSU cables are plugged in correctly at both ends (PSU side and components). Also, if you didn't plug the AC wall cable in properly at the back it can cause problems on some PSUs from my experience. If you can use a known good power supply to test

Double check you plugged things into the motherboard correctly (fans, front usb, power/reset etc)

Double check your graphics card to see if it is plugged in all the way into the PCI-e slot and the power is plugged in properly too.
10
#10
0 Frags +
_KermitHave you tried only using one stick of RAM? Swap sticks if the problem persists and see if any stick of RAM works individually. Probably won't work, but worth a try.

Just tried it, didn't work

FakeDouble check your PSU cables are plugged in correctly at both ends (PSU side and components). Also, if you didn't plug the AC wall cable in properly at the back it can cause problems on some PSUs from my experience. If you can use a known good power supply to test

Double check you plugged things into the motherboard correctly (fans, front usb, power/reset etc)

Double check your graphics card to see if it is plugged in all the way into the PCI-e slot and the power is plugged in properly too.

Gonna properly double check everything

[quote=_Kermit]Have you tried only using one stick of RAM? Swap sticks if the problem persists and see if any stick of RAM works individually. Probably won't work, but worth a try.[/quote]
Just tried it, didn't work

[quote=Fake]Double check your PSU cables are plugged in correctly at both ends (PSU side and components). Also, if you didn't plug the AC wall cable in properly at the back it can cause problems on some PSUs from my experience. If you can use a known good power supply to test

Double check you plugged things into the motherboard correctly (fans, front usb, power/reset etc)

Double check your graphics card to see if it is plugged in all the way into the PCI-e slot and the power is plugged in properly too.[/quote]
Gonna properly double check everything
11
#11
4 Frags +

pls send help I want to scrim

pls send help I want to scrim
12
#12
0 Frags +
SetsulUnplug the HDDs, remove the mobo from the case, place it on a non-conductive surface and try Linux again.

Also upgrading to W10 usually breaks things so I'm not surprised.

First step is to figure out whether or not this is a hardware problem. See the quote above.

To be honest I think windows is just fucked. Boot manager is fucked and now it's even more confused with the new microcode.

[quote=Setsul]Unplug the HDDs, remove the mobo from the case, place it on a non-conductive surface and try Linux again.[/quote]

Also upgrading to W10 usually breaks things so I'm not surprised.

First step is to figure out whether or not this is a hardware problem. See the quote above.

To be honest I think windows is just fucked. Boot manager is fucked and now it's even more confused with the new microcode.
13
#13
0 Frags +

Just for the record the Windows I use now is a non activated 8.1 version installed on the SSD I ordered after I figured something might have been up with my HDDs. i checked, everything is plugged correctly. I'm suspecting my motherboard to be faulty and I've ordered a spare one, I'll return the original one if it turns out to be the problem.

SetsulSetsulUnplug the HDDs, remove the mobo from the case, place it on a non-conductive surface and try Linux again.
Also upgrading to W10 usually breaks things so I'm not surprised.

First step is to figure out whether or not this is a hardware problem. See the quote above

I will try tonight on a non-conductive surface with the SSD unplugged. Gonna give a try to Linux with the motherboard in the case too.

Just for the record the Windows I use now is a non activated 8.1 version installed on the SSD I ordered after I figured something might have been up with my HDDs. i checked, everything is plugged correctly. I'm suspecting my motherboard to be faulty and I've ordered a spare one, I'll return the original one if it turns out to be the problem.
[quote=Setsul][quote=Setsul]Unplug the HDDs, remove the mobo from the case, place it on a non-conductive surface and try Linux again.[/quote]

Also upgrading to W10 usually breaks things so I'm not surprised.

First step is to figure out whether or not this is a hardware problem. See the quote above
[/quote]
I will try tonight on a non-conductive surface with the SSD unplugged. Gonna give a try to Linux with the motherboard in the case too.
14
#14
0 Frags +

I see you're still avoiding double posts.

I see you're still avoiding double posts.
15
#15
0 Frags +
SetsulI see you're still avoiding double posts.

Haven't had time yet to get my motherboard out of my case and test it, although I built a Linux key already and ran it with the mobo still in the case: I don't get past the Ubutu loading screen.
So far my computer doesn't crash once I'm in TF2 unless the map changes so I just disconnect while the server is changing level.
A friend of mine offered me to borrow some of his HDDs to try and run W10 on it. The spare motherboard arrived but I'm waiting to get around the non-conductive test and my friends' HDDs to try to swap.

[quote=Setsul]I see you're still avoiding double posts.[/quote]
Haven't had time yet to get my motherboard out of my case and test it, although I built a Linux key already and ran it with the mobo still in the case: I don't get past the Ubutu loading screen.
So far my computer doesn't crash once I'm in TF2 unless the map changes so I just disconnect while the server is changing level.
A friend of mine offered me to borrow some of his HDDs to try and run W10 on it. The spare motherboard arrived but I'm waiting to get around the non-conductive test and my friends' HDDs to try to swap.
16
#16
0 Frags +

Found the strength to double post.
I just tried what you told me, taking out my mobo from the case, ran it with a Linux key. Direct HDMI feed from the motherboard was giving me no signal, I then plugged my GPU and a Displayport cable, got an image and managed to get to the Ubuntu loading screen but the same usual crash shortly after. No components were hot btw.
About to swap with the spare motherboard right now.
Edit: same issue with the spare motherboard (same model I probably should've tried with a different one but w/e)
Running out of ideas :(

Found the strength to double post.
I just tried what you told me, taking out my mobo from the case, ran it with a Linux key. Direct HDMI feed from the motherboard was giving me no signal, I then plugged my GPU and a Displayport cable, got an image and managed to get to the Ubuntu loading screen but the same usual crash shortly after. No components were hot btw.
About to swap with the spare motherboard right now.
Edit: same issue with the spare motherboard (same model I probably should've tried with a different one but w/e)
Running out of ideas :(
17
#17
2 Frags +

There's no HDD/SSD plugged in, the mobo isn't shorting out and has been replaced and the PSU isn't exactly working hard during boot (not like a G3 is going to crap itself like that anyway) which means there's only 3 components left.
1. The CPU. Obviously difficult to test.
2. The RAM. Run memtest, maybe just one stick, etc., maybe replace it if you can borrow some.
3. The GPU. Sadly you've got no integrated GPU (that's why you're not getting any signal with HDMI plugged into the mobo) so you'll need a different GPU to test it. Or test your GPU in a different PC.

There's no HDD/SSD plugged in, the mobo isn't shorting out and has been replaced and the PSU isn't exactly working hard during boot (not like a G3 is going to crap itself like that anyway) which means there's only 3 components left.
1. The CPU. Obviously difficult to test.
2. The RAM. Run memtest, maybe just one stick, etc., maybe replace it if you can borrow some.
3. The GPU. Sadly you've got no integrated GPU (that's why you're not getting any signal with HDMI plugged into the mobo) so you'll need a different GPU to test it. Or test your GPU in a different PC.
18
#18
0 Frags +

I ran memtest86 for 9 hours the other night and had no errors. I can probably find some other sticks. I'll give my GPU to someone to try out. If all of this comes out negative I guess I'll just buy another CPU and eat ice cubes for the rest of the month..

I ran memtest86 for 9 hours the other night and had no errors. I can probably find some other sticks. I'll give my GPU to someone to try out. If all of this comes out negative I guess I'll just buy another CPU and eat ice cubes for the rest of the month..
19
#19
3 Frags +

Yeah, my money is on the GPU then.

I'd expect quite a few people to upgrade to Ryzen 3000 CPUs, so if there's any way I would take advantage of the market being flooded with used Ryzen 1000/2000 next month. Even if you really can't wait you could abuse return policies. Buy a new CPU, wait for the launch, buy a used CPU and return the new one.

Yeah, my money is on the GPU then.

I'd expect quite a few people to upgrade to Ryzen 3000 CPUs, so if there's any way I would take advantage of the market being flooded with used Ryzen 1000/2000 next month. Even if you really can't wait you could abuse return policies. Buy a new CPU, wait for the launch, buy a used CPU and return the new one.
20
#20
0 Frags +

Hi,
The new GPU has arrived. After I installed it, I did not get the "No signal" screen anymore, however by trying to boot on a linux key with the motheboard on a non-conductive surface it first failed and then showed me this screen: http://fr.tinypic.com/r/15wf1as/9
Any idea on what it could mean?

Hi,
The new GPU has arrived. After I installed it, I did not get the "No signal" screen anymore, however by trying to boot on a linux key with the motheboard on a non-conductive surface it first failed and then showed me this screen: http://fr.tinypic.com/r/15wf1as/9
Any idea on what it could mean?
21
#21
0 Frags +

Is that new? I mean it's always possible that there was a combination of issues.

But against all odds it seems that the CPU is FUBAR.
I mean if I read this correctly it's "Bank 6: baa0000000000118" which according to google has never happened before and according to the MCE decoder means
Bank: Floating Point Unit (FP)
Error: Physical register file (PRF) parity error (PRF 0x0)
You shouldn't even have to know what any of those words mean because none of this should ever break.

Bank 5: bea0000000000108 is fairly well known and fixed by disabling C-states, so you could try that but it shouldn't be that.
I think that's one for AMD support. It just screams warranty/DOA.

Is that new? I mean it's always possible that there was a combination of issues.

But against all odds it seems that the CPU is FUBAR.
I mean if I read this correctly it's "Bank 6: baa0000000000118" which according to google has never happened before and according to the MCE decoder means
Bank: Floating Point Unit (FP)
Error: Physical register file (PRF) parity error (PRF 0x0)
You shouldn't even have to know what any of those words mean because none of this should ever break.

Bank 5: bea0000000000108 is fairly well known and fixed by disabling C-states, so you could try that but it shouldn't be that.
I think that's one for AMD support. It just screams warranty/DOA.
22
#22
0 Frags +

First time I've seen this screen, however it flashed extremely quickly and I easily could've missed it during testing, it took me several tries to get the picture.
I'm gonna follow your previous advice and use return policies too in order to get something up & running asap, I don't want to play an official on a laptop ever again.
As well as contacting AMD support ofc.

First time I've seen this screen, however it flashed extremely quickly and I easily could've missed it during testing, it took me several tries to get the picture.
I'm gonna follow your previous advice and use return policies too in order to get something up & running asap, I don't want to play an official on a laptop ever again.
As well as contacting AMD support ofc.
23
#23
6 Frags +

Hi, finally some good news.
Turns out my CPU was indeed faulty all along, as soon as I swapped it fixed everything. I'll return what I don't need asap and contact AMD. Thanks for helping me through this Setsul, think I owe you a drink next lan.

Hi, finally some good news.
Turns out my CPU was indeed faulty all along, as soon as I swapped it fixed everything. I'll return what I don't need asap and contact AMD. Thanks for helping me through this Setsul, think I owe you a drink next lan.
24
#24
5 Frags +

Glad it works now.
Sorry that took so long, but it was the least likely thing to happen.

I won't be at LAN this year so don't worry about it. Maybe Eemes needs a drink after all the missed scrims.

Glad it works now.
Sorry that took so long, but it was the least likely thing to happen.

I won't be at LAN this year so don't worry about it. Maybe Eemes needs a drink after all the missed scrims.
Please sign in through STEAM to post a comment.