New Ryzen Build Freezes/BSODs randomly

Toggle sidebar Toggle sidebar
B

basedgob

Prominent
Nov 9, 2017
7
0
510
My new build crashes sometimes when the computer is bumped, and sometimes it just freezes on its own while I'm using it. I've never overclocked it. Any help would be greatly appreciated!

Here's the build:

Motherboard: MSI X370 GAMING PRO CARBON https://www.neweggbusiness.com/product/product.aspx?item=9b-13-144-017

CPU: AMD RYZEN 7 1800X 8-Core 3.6 GHz https://www.neweggbusiness.com/product/product.aspx?item=9b-19-113-430

GPU: GIGABYTE AORUS GeForce GTX 1080 Ti https://www.neweggbusiness.com/product/product.aspx?item=9b-14-125-953

RAM: G.SKILL Ripjaws V Series 32GB (2 x 16GB)
https://www.neweggbusiness.com/product/product.aspx?item=9b-20-232-091

Power Supply: CORSAIR RMx Series RM850X 850W https://www.neweggbusiness.com/product/product.aspx?item=9b-17-139-141

SSD (no HDD): WD Black 512GB Performance SSD https://www.neweggbusiness.com/product/product.aspx?item=9b-20-250-085

CPU Fan: CRYORIG H5 Ultimate https://www.neweggbusiness.com/product/product.aspx?item=9siv0m55795170

Case: Phanteks Evolv PH-ES515E_BK https://www.neweggbusiness.com/product/product.aspx?item=9b-11-854-021

Here's a screenshot of my bios: https://i.imgur.com/zURFvo0.png

I'll paste the WhoCrashed information below. The UNEXPECTED_KERNEL_MODE_TRAP errors happen when I bump it I believe, and the WHEA_UNCORRECTABLE_ERROR errors happen just randomly when I'm using my computer, it will just freeze. In this case, the screen goes black, all of my peripherals lose power, and I can see my GPU light flashing rather than smoothly transitioning through various colors.

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-3QL3D84
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\Windows
Hardware: MS-7A32, Micro-Star International Co., Ltd, X370 GAMING PRO CARBON (MS-7A32)
CPU: AuthenticAMD AMD Ryzen 7 1800X Eight-Core Processor AMD586, level: 23
16 logical processors, active mask: 65535
RAM: 34304204800 bytes total


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 11/8/2017 9:56:04 PM your computer crashed
crash dump file: C:\Windows\Minidump\110817-19343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x7F (0x8, 0xFFFFF8003E88BE70, 0xFFFFF8003E875FD0, 0xFFFFF8003C589ED4)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Wed 11/8/2017 9:56:04 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFF8003E88BE70, 0xFFFFF8003E875FD0, 0xFFFFF8003C589ED4)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Sat 11/4/2017 5:15:11 PM your computer crashed
crash dump file: C:\Windows\Minidump\110417-18468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7211BB)
Bugcheck code: 0x124 (0x0, 0xFFFFD882FEA928F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Wed 10/25/2017 5:04:11 AM your computer crashed
crash dump file: C:\Windows\Minidump\102517-19859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7211BB)
Bugcheck code: 0x124 (0x0, 0xFFFFC7079D94C8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Sat 10/14/2017 3:41:39 AM your computer crashed
crash dump file: C:\Windows\Minidump\101417-17812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7211BB)
Bugcheck code: 0x124 (0x0, 0xFFFFB882466268F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Solution
P
Did you update the bios? Yup it maybe a wattage / voltage prob according to some sites

This I think is the cause of the crash X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

The CPU maybe faulty. I would return it / get it replaced. See if that fixes it
Sort by date Sort by votes
B

basedgob

Prominent
Nov 9, 2017
7
0
510


I don't think so. If I did, it must have been completely accidentally. Will go try changing that now, thank you!
 
Upvote 0 Downvote
B

basedgob

Prominent
Nov 9, 2017
7
0
510


Things aren't looking good... to give you a hint I'm now posting from my laptop..

So I changed both the CPU core and CPU NB voltage to 1.2, rebooted, and it froze after bios. Rebooted again. It said something along the lines of it was trying to repair, so I went into the bios again, turned both of those voltages down to 1.05. Rebooted again. Froze before the bios prompt. Like the lights on my keyboard are all on (only numlock is on usually), all the fans are spinning but the screen is black and spamming the bios key (delete) does nothing. Rebooted several more times to the same effect. Screenshots of the process: https://i.imgur.com/4NAyPge.png

Now seemingly I can't even boot my computer! I noticed the EZ debug LED on my mobo is flashing indicating a problem with the CPU. Not sure what to do now... any help would be greatly appreciated




Will do once I'm able to boot my computer again lol
 
Upvote 0 Downvote
B

basedgob

Prominent
Nov 9, 2017
7
0
510


As I mentioned, I seemingly can't get into the bios anymore. My screen stays black even as I'm spamming the key to enter the bios (delete). What can I do now? I'm a bit scared that I'll be out $400 with a fried CPU
 
Upvote 0 Downvote
B

basedgob

Prominent
Nov 9, 2017
7
0
510


Didn't know I could reset the CMOS battery to reset the BIOS, will google search how to do that now. Thanks for the quick reply!
 
Upvote 0 Downvote
vapour

vapour

Champion
Aug 28, 2017
12,398
98
57,540
Do this:
1. power off
2. turn off 'o-' switch on psu
3. touch metal and then remove cmos battery: https://www.google.com/search?q=cmos+battery&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiVlszAuLLXAhUl7YMKHdVfAn0Q_AUICygC&biw=1920&bih=949#imgrc=uToBcSDlezfimM:
4. wait for 30 secs and put it back in
5. turn on 'o-' switch
6. wait for 15 secs, press power button
 
Upvote 0 Downvote
B

basedgob

Prominent
Nov 9, 2017
7
0
510


That worked, thank you! My computer is running again. Any idea why such a small increase in voltage would cause problems like that? Perhaps I should have only increased one of the CPU voltages, instead of increasing CPU core and CPU NB voltage?

And the next step is to reinstall my OS/test RAM now?

 
Upvote 0 Downvote
B

basedgob

Prominent
Nov 9, 2017
7
0
510


I'm back with some new errors! These guys are from me just leaving my computer on the lock screen and going afk for a few hours. This is probably the most consistent way for me to cause it to crash. Would it be worth changing just the voltage again, except this time, only doing vcore? Here's the WhoCrashed data:

On Mon 11/20/2017 3:04:11 PM your computer crashed
crash dump file: C:\Windows\Minidump\112017-18468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x9F (0x3, 0xFFFFC600EE20D2A0, 0xFFFFD9811B2AD8F0, 0xFFFFC600F9B67A60)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 11/20/2017 3:04:11 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFC600EE20D2A0, 0xFFFFD9811B2AD8F0, 0xFFFFC600F9B67A60)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 11/20/2017 2:26:58 PM your computer crashed
crash dump file: C:\Windows\Minidump\112017-17984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF820884CB4400, 0xFFFF9780056AD910)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 11/20/2017 1:51:28 PM your computer crashed
crash dump file: C:\Windows\Minidump\112017-19890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72145B)
Bugcheck code: 0x124 (0x0, 0xFFFF820888FE58F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 11/20/2017 2:09:17 AM your computer crashed
crash dump file: C:\Windows\Minidump\112017-19281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72145B)
Bugcheck code: 0x124 (0x0, 0xFFFF9A8CD8EAD8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






Here's the dmp files https://mega.nz/#F!hY8wGaDT!-hsxKnByI6XVFf06OAUVGA
 
Upvote 0 Downvote
P

Paul NZ

Polypheme
Sep 15, 2014
20,779
3
61,010
Did you update the bios? Yup it maybe a wattage / voltage prob according to some sites

This I think is the cause of the crash X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

The CPU maybe faulty. I would return it / get it replaced. See if that fixes it
 
Upvote 0 Downvote
Solution
M

muovituoli

Prominent
Dec 3, 2017
3
0
510


Soz, didn't read the dump files yet but I thought my 5 cents here might help you out.

I've had my fair share of problems with the Ryzen TR 1950x on an AsRock Taichi x399 board. I've also got similarities to your system in terms of the SSD (having the same one here) and I think that might be the culprit here. Not the SSD itself but it seems that many manufacturers were taken by surprise with the m.2 SSD's.

Alrigh so, this is what I've done to get a lag/freeze-free Ryzen Environment (for now at least):

1. Flash your BIOS, should be possible for you to update it straight away when you've accessed it at start-up.
2. Enable SATA Hot Plug
3. Re-install your Win10, wipe the drive a couple of times before you do this.
4. On first boot, GO STRAIGHT to Windows updates and get the latest ones in.
5. After a reboot, use a driver manager (I used 2 different ones, Driver Booster and Driver Pack Solution) to install all the needed drivers.
6. After another reboot, go get your GPU drivers.
7. Get and install the MOBO all-in-drivers.
8. Get and install AMD chipset drivers.
9. Disable HPET (google this one up).

I'm still experiencing some stuttering (noticed while writing this). Not as much as before though.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom