[SOLVED] Constant BSODs on new Ryzen build

Status
Not open for further replies.

Adel Medhat

Distinguished
Apr 9, 2014
67
1
18,645
Solution
F11n was available on 12/03/20. I have yet to check for BIOS updates. I was able to fix my issues by changing the CPU voltage from Auto to 1.35. No blue screens anymore!

gardenman

Splendid
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/sowk2y8r/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:122320-7546-01.dmp (Dec 23 2020 - 16:16:05)
Bugcheck:KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION (157)
Probably caused by:memory_corruption (Process: csrss.exe)
Uptime:0 Day(s), 0 Hour(s), 04 Min(s), and 47 Sec(s)

File information:122320-7343-01.dmp (Dec 23 2020 - 16:26:25)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: dwm.exe)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 52 Sec(s)

File information:122320-7296-01.dmp (Dec 23 2020 - 16:18:39)
Bugcheck:ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)
Probably caused by:memory_corruption (Process: NVIDIA Share.exe)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 06 Sec(s)

File information:122320-7109-01.dmp (Dec 23 2020 - 16:23:04)
Bugcheck:KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION (157)
Probably caused by:memory_corruption (Process: csrss.exe)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 58 Sec(s)

File information:122320-6984-01.dmp (Dec 23 2020 - 16:10:23)
Bugcheck:ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)
Probably caused by:memory_corruption (Process: NVIDIA Share.exe)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 04 Sec(s)

File information:MEMORY.DMP (Dec 23 2020 - 16:26:25)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: dwm.exe)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 52 Sec(s)
Possible Motherboard page: https://www.gigabyte.com/Motherboard/B550-AORUS-ELITE-AX-rev-10
You are using BIOS version F11n. I don't see this version listed on the page. I do see a F11p. It could be that F11n was buggy and was removed from the page and later replaced by F11p. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Status
Not open for further replies.