Computer Acting Strange - X370 Gaming K4

Fixed video link: https://www.youtube.com/watch?v=pGf5kYS3ID4&t=1s

Hi,

Hubrah,


My 2cents..........

More than likely it's memory related

Most CL15 3000MHZ is Hynix ICs.



Do you remember if this began after a BIOS update?

Mem in slots A2 and B2? Try them in A1 and B1.
BUT, before changing, hell, probably a good idea to do it anyways after all you've done, clear the CMOS(battery out + jumper), not simply a BIOS clearing to Defaults.

Pull the mem and reseat it, making sure you hear two clicks/snaps. One at each end.

Hubrah wrote: Hello everyone, Below, I have provided a link to a video of the problem in action. Essentially, my computer crashes minutes after booting and I receive a Dr. Debug error code 00. I have everything set at defaults, the BIOS has been updated, I have disassembled and reassembled everything (for any seating problems), removed all unnecessary system hardware. In all respects this is a new build. I would also like to add that I have never experienced this problem in the UEFI-BIOS or Windows Safe Mode. Here is my build: Windows 10, 64 bit AMD R7 1700 Asrock X370 Gaming K4 (updated to 3.20 BIOS) Gigabyte GTX 1080 G1 G.Skill 3000 @ 15-15-15-35 EVGA B2 750w PSU I have had this build since April 2017, and at the beginning there was no problems, everything was working properly as it should after the initial build. I began experiencing this problem in early June and this problem has persisted regardless of what I have done to fix it. Does anyone have experience with this problem, or have any advice on how to fix it? I am totally at a loss as to what I can do. I have swapped my GPU with another to eliminate the GPU as a possible reason, and I have made sure the CPU cooler was properly attached (I have tried both the stock cooler and an aftermarket cooler) and ensured enough thermal paste was applied (and applied properly). I have also used SSD/HDD utilities to review the health of my drives, everything seems to indicate that my drives are healthy. I have also erased and reinstalled Windows on different SSD's and the problem still persists. Furthermore, in my system I have 2 HDD & 2 SSD attached. However, in the BIOS I can't select them in the boot options menu. I can see them in the BIOS, and I can set the boot priority, but when I try to set the boot options it does not allow me to boot all my drives. I don't know if this is a related problem to my main issue, but perhaps it is an indicator that my motherboard is bad. My gut tells me that I am going to need to RMA either my processor or my motherboard if I can't find a solution. A thing of note that I have recently discovered: Apparently, if I increase the voltage going to my CPU (1.375v), it allows my computer to boot up and stay on for a decent while, however the problem still occurs after an hour or so. If I keep my CPU at stock voltages (3GHZ @ 1.1875v) the problem occurs seconds after bootup. I have no idea what this could indicate, and I am unsure if this issue is caused by the motherboard, CPU, or power supply. Here is the video of the problem in action: https://www.youtube.com/watch?v=pGf5kYS3ID4 Thanks for the assistance! I desperately hope we can solve this problem I am having!

The link to your video does not work for me, results in a 404 not found.

After the PC crashes, what happens? Do you see the Windows BSOD screen and gathering information message? Then the PC restarts, and you get the 00 POST code? Or what else happens?

If the PC does not seem to restart, the 00 POST code display may mean nothing. POST codes will only be valid when POST runs.

If you can run the PC in the UEFI/BIOS or Safe Mode and never experience a crash, that does not sound like a hardware failure problem. This is an important difference, and you can stay in the UEFI interface or Windows Safe Mode indefinitely without the crash? Is that consistent at your stock VCore voltage, and at the increased VCore?

Given that, the question is what is the difference between running in Safe Mode or in the UEFI/BIOS, and a regular Windows boot?

What do you use to monitor VCore? My ASRock X370 Killer SLI/ac 1700X PC has an OC to 3.9GHz, with Cool n Quiet and C6 enabled. My VCore shown in HWiNFO64 drops to 0.384V at idle from its high of 1.360V, and does not crash.

When you say your stock voltage is 1.1875V, is that with everything related to the CPU and VCore set to Auto/default? The Auto VCore for stock CPU clock on my board and 1700X was much more than 1.1875V. It is also more than the VCore I use for all cores at 3.9GHz, which is ~1.360V. The Auto VCore is over 1.4V at stock CPU clock speed. So a stock VCore of 1.1875V seems very low IMO, do you set that manually?

In the UEFI/BIOS, CPU power saving options like CnQ and C6 aren't active. Are they active for you when running in Safe Mode? Does your CPU downclock at all when at idle?

The main difference between being in the UEFI/BIOS and Safe Mode, and a fully booted Windows installation, are the drivers that are loaded. We don't know what the situation is immediately after your PC crashes, whether a BSOD or whatever it is. We need to know what that situation is.

About all your drives not being listed in the boot order, what is the entry for your OS drive in the boot order now? Depending upon how you installed Windows 10, that would be "Windows Boot Manager". Do you have more drives than the target OS drive running when you install Windows? Did you select the entry in the boot order for the Windows 10 installation media you use? If the entry in the boot order for the Windows 10 installation media was, "UEFI: <device name>", then you have a UEFI booting installation, and it is normal for no other drives to be listed in the boot order. Why would drives that are not bootable be listed in the boot order? That is normal in the situation I've described.

parsec wrote: The link to your video does not work for me, results in a 404 not found. After the PC crashes, what happens? Do you see the Windows BSOD screen and gathering information message? Then the PC restarts, and you get the 00 POST code? Or what else happens? If the PC does not seem to restart, the 00 POST code display may mean nothing. POST codes will only be valid when POST runs. If you can run the PC in the UEFI/BIOS or Safe Mode and never experience a crash, that does not sound like a hardware failure problem. This is an important difference, and you can stay in the UEFI interface or Windows Safe Mode indefinitely without the crash? Is that consistent at your stock VCore voltage, and at the increased VCore? Given that, the question is what is the difference between running in Safe Mode or in the UEFI/BIOS, and a regular Windows boot? What do you use to monitor VCore? My ASRock X370 Killer SLI/ac 1700X PC has an OC to 3.9GHz, with Cool n Quiet and C6 enabled. My VCore shown in HWiNFO64 drops to 0.384V at idle from its high of 1.360V, and does not crash. When you say your stock voltage is 1.1875V, is that with everything related to the CPU and VCore set to Auto/default? The Auto VCore for stock CPU clock on my board and 1700X was much more than 1.1875V. It is also more than the VCore I use for all cores at 3.9GHz, which is ~1.360V. The Auto VCore is over 1.4V at stock CPU clock speed. So a stock VCore of 1.1875V seems very low IMO, do you set that manually? In the UEFI/BIOS, CPU power saving options like CnQ and C6 aren't active. Are they active for you when running in Safe Mode? Does your CPU downclock at all when at idle? The main difference between being in the UEFI/BIOS and Safe Mode, and a fully booted Windows installation, are the drivers that are loaded. We don't know what the situation is immediately after your PC crashes, whether a BSOD or whatever it is. We need to know what that situation is. About all your drives not being listed in the boot order, what is the entry for your OS drive in the boot order now? Depending upon how you installed Windows 10, that would be "Windows Boot Manager". Do you have more drives than the target OS drive running when you install Windows? Did you select the entry in the boot order for the Windows 10 installation media you use? If the entry in the boot order for the Windows 10 installation media was, "UEFI: <device name>", then you have a UEFI booting installation, and it is normal for no other drives to be listed in the boot order. Why would drives that are not bootable be listed in the boot order? That is normal in the situation I've described.

Hi Parsec, thanks for the response!

1) Yes, I did do a UEFI installation (for the first time actually), and I did not realize this was normal for connected drives to not be shown the boot order menu. "Windows Boot Manager" is my 480GB SSD drive that has my Windows installation on it, and it looks like even though my other HDD's are not in the boot order, they boot up and are operational (I play my games off them). I did not know this was a feature of the UEFI installation!!!!

2) I have provided an updated link to the video in one of my other comments.
    https://www.youtube.com/watch?v=pGf5kYS3ID4

3) When my computer crashes, I no longer get video output to my monitor and my PC does not restart. I just get stuck with a black screen, case fans going full blast, and Dr. Debug blinking "00".

4)  Yes, I can run inside the UEFI-BIOS and Windows Safe Mode pretty much indefinitely without crashes (at default or Auto settings for CPU voltage and VCore & CPU frequency at Auto settings). I can also run inside normal Windows mode indefinitely if I increase the voltage going to my CPU (setting Vcore voltage to 1.375). However, in this state I cannot overclock. If I go anywhere near 3700mhz (fixed frequency) my system will crash. If I leave my CPU frequency to Auto @ 1.375 VCore, my computer runs stable.

5) I monitor my voltages/temperatures with CPUID HWMonitor & Ryzen Master utility. My CPU runs at 33-36c during normal operation and around 48c running Cinebench benchmarking.

6) Yes, according to HWMonitor, my CPU does downclock when idling.

7) In regards to the differences between UEFI-BIOS/Windows Safe Mode/Windows normal operation, I have installed my OS on different SSD's to eliminate any potential driver problem. I am currently running a fresh install and it still crashes. It even crashes while installing Windows if the parameters for stable operation are not met (as mentioned previously, #4).

Thanks for your help, I sincerely hope we may continue this conversation.