Question Ryzen 5 3600 BSOD, instability?

May 25, 2020
10
1
10
0
Hi all,

I'm having instabilities and BSOD issues on a freshly installed system:

On Mon 25/05/2020 08:53:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052520-42234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xD1 (0xEE6537DBA0, 0x2, 0x1, 0x7FFB72F79508)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Games crash after 5-15min: GTA V, Anno, Assassin's Creed etc...

Fresh build:
AMD Ryzen 5 3600
MB Asrock B450M pro4, Bios 3.90 (latest)
RAM: BLS2K16G4D32AESE.000 Ballistix Sport LT Red 32GB Kit (2 x 16GB) DDR4-3200 UDIMM
Win 10 64 bits v1909 (18363.836) (3 days old install)
PSU: Antec NEO ECO 400w
SSD Adata XPG SX8200 Pro 1TB M.2 2280 NVMe PCIe
GPU: Palit GTX 1660 6GB StormX

One Drive link with:
  • Sysnative BSOD Dump
  • perfmon report
  • Minidump
  • CPU-Z, Prime95, Aida64 etc screenshots
Any help appreciated.
 
May 25, 2020
10
1
10
0
Had another BSOD today, but I was just browsing the web.
I'm not sold on the power supply being an issue here... What do you think?

On Tue 26/05/2020 15:38:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052620-20750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x5D00, 0xFF, 0xC8, 0xFFFFF80042EBACC1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
May 25, 2020
10
1
10
0
And another one :rolleyes:

On Tue 26/05/2020 18:44:00 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052620-12296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80078E0EDE5, 0xFFFFB3064FD9BB90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
 

Vic 40

Polypheme
Ambassador
Didn't ask what bios now, did ask this.

Did the bios update yourself? What version before? If you remember.
Copy paste here what was important in the whocrashed log.

Migth be best to do another fresh install, after that first get the latest chipset drivers from the AMD link which are much later and only after that install the Nvidia drivers.
 
May 25, 2020
10
1
10
0
Yes I did perform the BIOS update myself.

Here is the full WhoCrashed analysis:

--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.65
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


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

Computer name: DESKTOP-L3V0LM6
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\WINDOWS
Hardware: ASRock, B450M Pro4
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 34286026752 bytes (31.9GB)




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

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Tue 26/05/2020 18:44:00 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052620-12296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80078E0EDE5, 0xFFFFB3064FD9BB90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 26/05/2020 18:44:00 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x81D9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80078E0EDE5, 0xFFFFB3064FD9BB90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 26/05/2020 15:38:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052620-20750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x5D00, 0xFF, 0xC8, 0xFFFFF80042EBACC1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 25/05/2020 10:11:07 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052520-39625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x18 (0xFFFF968CB06C3820, 0xFFFF968CBE4754E0, 0x1, 0x1)
Error: REFERENCE_BY_POINTER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 25/05/2020 09:53:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052520-42234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xD1 (0xEE6537DBA0, 0x2, 0x1, 0x7FFB72F79508)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 23/05/2020 21:49:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052320-39406-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF802153F459B)
Bugcheck code: 0x50 (0xFFFF950A3B61A268, 0x2, 0xFFFFF802153F459B, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 

Vic 40

Polypheme
Ambassador
Yes I did perform the BIOS update myself.
And what nr was the old bios if you remember?




Migth be best to do another fresh install, after that first get the latest chipset drivers from the AMD link which are much later and only after that install the Nvidia drivers.
Would try this.

Other thing looked at that psu like RARRAF and it seems to only have one pcie 6pin connector so how are you powering that gpu?
 
Last edited:
May 25, 2020
10
1
10
0
I do not remember the version before, sry.
I am using a 6 pin to 8 pin converter to power the GPU.
Voltage measured on the GPU is 12.3V. BSODs happen when computer is idle.
 

Vic 40

Polypheme
Ambassador
I do not remember the version before, sry.
If your first bios update can you look for the old one by looking at the bioschip, there will be a small sticker on it with the bios the motherboard shipped with.




I am using a 6 pin to 8 pin converter to power the GPU.
That is never a good practice. As suggested would it still be good to upgrade that psu, if lucky if they accept send this one back.
 
May 25, 2020
10
1
10
0
The sticker says 3.90. I think I did re-apply the update from the website "just in case".
Ok understood, will look into returning this PSU. Thanks.
 

Vic 40

Polypheme
Ambassador
All bsod info points at driver issues so far, not taking into account what the psu might have to do with it and i'm not sure it is. It's still good to get a good one.\

Would do a reinstall with installing chipset drivers first (AMD link), only after that other ones like lan/sound drivers and Nvidia.
 

ASK THE COMMUNITY

TRENDING THREADS