PC freezes/locks up at Windows startup!

I am not sure if this is the right place to ask, but I haven’t found much help elsewhere.

My Windows 10 pc with ryzen 1300x crashes during windows startup or if luckily it manages to start, then freezes up soon after. This is all with default bios settings. I have also reinstalled windows to see if it goes away but it doesn’t.

However I have found a temporary fix, if I set the CPU clock at 3Ghz then it boots up fine and works normally, until it doesn’t, that is when I do something heavy or play video games for more than 20-30 minutes. It will freeze up. I have tried checking event log, found that nvcontainer has some issues along with kernel power error etc, I reinstalled the drivers with ddu but it doesn’t seem to get rid of the freezing. I am still using the pc, but I have no spare parts to test if my cpu, gpu or motherboard is broken, I need to buy a replacement part probably but I am not sure what to replace. Can you help me?

1 Like

Bunch of questions:

  • Do you get a blue screen? If so, what is the error message?
  • Did you install any new hardware recently?
  • Have you tried booting the computer in “Safe Mode”? If so, does it work for more than 30 minutes?
  • For when you manage to get your computer stable for 30 minutes or so - can you run Prime-95 in both CPU-only and CPU+Max RAM? Do you get any error?

Couple of questions I have!

Have you run a memtestx86 for at least 3 complete passes?
Have you reseated your memory?
Have you reseated your cpu and cooler and added new thermal paste?
Have you booted into a linux live cd and do the issues persist?
Is the boot drive an ssd or a conventional spinning drive?

Honestly it sounds like 1 of 3 things to me. a thermal issue / your memory / cpu is coming out of the socket (it happens over time to thermal expansion and cooling) / memory starting to go bad / bad conventional drive!

1 Like
  • Since I reduced the clock to 3Ghz, I have not gotten any blue screens. When it does freeze up now due to heavy workload, it does not go to the blue screen, applications become unresponsive at first, then windows itself freezes.

  • No, the only thing I added after the initial build was an SSD years ago.

  • I did not use “Safe Mode” in the reduced clock speeds. In default clock speeds I did use “Safe Mode” because improper shutdowns due to crashes made windows not boot up, I am also running dual windows, due to the fear if something critical gets messed up with one installation I can easily switch to the other.

  • I ran P95 some time ago with the default clocks with max ram, but I do not remember exactly what happened, I will redo the test and let you know.

Thanks.

  • I did run memtestx86 and got no errors, but I do not exactly remember if it was 3 complete passes or not.

  • Yes, I had reseated the memory, it did not affect things.

  • No, I did not reseat my cpu, or change the thermal paste since I made my build.

  • Yes I have booted into a linux live cd, it also crashed after some time, as far as i can remember.

  • The boot drive is on an 500GB Samsung 970 Evo SSD.

That fact alone makes me believe it’s hardware!

Did you by chance check you power connectors / reseat them while you were in your case?

I’d start with the reseating of the cpu / cooler / thermal paste and all the power connectors.

1 Like

No, I did not check the power connectors. I have to get my hands on same thermal paste first, I will update after doing that.

Have you checked the motherboard’s VRM temperatures under load to make sure it’s not overheating?

No, I havent, can I check it with the overlay in rivatuner/afterburner?

Yes, you can check VRM temperatures with MSI Afterburner or RivaTuner.

I was able to get the system to crash today after a few hours of mixed usage. It crashed while a install/decompress task was going on an external hard disk. I had hwinfo running while it was going on so I am attaching it and an event viewer screenshot after a forced power off.


Those disk warnings what does the error details say?

The rest were similar to this

Honestly I’d say that’s your culprit! Replace the drive. It’s retiring a lot of blocks so it’s on it’s way out.

1 Like

How do I know if this drive is my SSD, where the OS is, or the External HDD, where the install was going on?

If Windows is crashing, it is not the external HDD

But this requires the assumption that the cause of the warning is causing the crash. I don’t think the ssd is causing the crash. I don’t get any crashes during light usage for long hours with the cpu base clock reduced.

Think about it: why the entire system would crash if it was an external disk drive. It’s not Windows 9X. Also you have an indicator there in your screenshot, it’s Disk 1:

  1. Run diskpart as an admin in a console/terminal
  2. Use the command select disk 1
  3. Use the command detail disk - This should give you some descriptor for you to recognize what physical drive it is
  4. Run exit to close diskpart

Edit: A little bit of clarity and tone adjustment. Sometimes the symptoms are good telltale signs of what the system is going through. You clearly have an event log that’s telling you there’s something with Disk 1. Let’s start from there.

Well, it was the external HDD. So maybe those disk errors are unrelated to the crash, on the other hand if the hdd is going kaput, I am in trouble, I have backups there.
In the screenshot see that there were some more errors I forgot to include, these I get a lot, even in the other windows install.

1 Like

That’s interesting, there are also warnings with the USB Attached SCSI Protocol (USAPStor.sys). If you run your computer without that drive connected - does it stay on?