Long time BSODS and freezing

hazelgray · Dec 15, 2020

Hello

I had my pc built in late 2018 by a local guy with an IT business, it had BSODS from the get go, he replaced the ram in case it was faulty but didn't receive any further support and kept getting them.
The issue is very on and off, I have reset my PC countless times and also run memtest and CPU, GPU tests numerous times in the past as well. Updated the bios, cleaned out and reinstalled drivers etc.
The case has also been thoroughly cleaned out and everything reseated three times (including once by the pc repair shop, who charged me without fixing anything lol).

Since the pc was built I did upgrade the graphics driver once and the BSODS continued.

Obviously it's difficult to address all the past issues and results so I just want to start again somewhere and I found this forum which seems really helpful and responsive!

The BSODS vary and I have not been able to find a way to reliably replicate them, they have MOSTLY happened on booting up or when I'm just browsing the internet. I also have freezing issues where the audio buzzes out (especially during youtube videos) the GPU LED just flashes like something is failing. I always have to do a hard reset when this happens.

No system manufacturer
Desktop
Windows 10 home
x64
The originally installed OS was also Windows 10.
I am not sure if the OS is OEM or retail, the person who built my pc installed the OS.
Age: 2 years (GPU 1.5 years)
I have reset and reinstalled the OS a couple of times before via USB

CPU: Ryzen 5 2600
RAM (brand, EXACT model, what slots are you using?): 16GB GSkill RAM
Video Card: GIGABYTE RX580
MotherBoard - (if NOT a laptop): ASRock B450M-HDV
Power Supply - brand & wattage (if laptop, skip this one): ThermalTake SmartPro RGB 650W
Is driver verifier enabled or disabled? Disabled - not currently installed.
What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth): Just Windows defender
Are you using proxy, vpn, ipfilters or similar software? Not currently.
Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software): No
Are you currently under/overclocking? Are there overclocking software installed on your system? No, nothing except the RADEON software which I don't use to do anything but update drivers.

Any ideas?

Kind regards

hazelgray · Dec 15, 2020

Sysnative zip file is attached.

philc43 · Dec 15, 2020

Hello hazelgray,

Welcome to Sysnative!

There is a not a lot I can glean from your crash dump files as to any specific driver that it causing this. It could be unknown hardware, either faulty components or settings in the BIOS that are not optimum.

This is a high level summary of the crashes:

Code:

BugCheck 3B, {c0000005, ffffcf91d6d73887, ffffa007ee64be30, 0}
Probably caused by: win32kfull.sys ( win32kfull!NtGdiAlphaBlend+a57 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 4E, {2, 17666c, 41f37f, 2000}
Probably caused by: memory_corruption ( nt!MiUnlinkPageFromList+c89 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff8016623df41, ffffcd8206da81c8, ffffb68063130920}
Probably caused by: amdkmdag.sys ( amdkmdag+1df41 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff806350c95f4, ffffa98ebd160028, ffffa98ebd15f860}
Probably caused by: Pool_Corruption ( nt!ExFreePool+9 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000005, fffff802845fc5e2, 0, ffffffffffffffff}
Probably caused by: ntkrnlmp.exe ( nt!SwapContext+372 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Please test your RAM using memtest86 as shown in the following tutorial run for 4 passes and repeat:
Test RAM with PassMark MemTest86 | Sysnative Forums

Also can you tell me how long you have been using NordVPN? I wonder from the logs if this might be part of the problem.

hazelgray · Dec 16, 2020

Hello thank you philc43!

Hmm ah ok, I had been using NordVPN for a few years but not for the past few months. I'll uninstall it as I'm not paying for it at the moment anyway and see what happens. I'll run memtest tonight and update here :).

I've attached some additional dump files if that's helpful but most of them are from August.

philc43 · Dec 17, 2020

I'd prefer to wait for new dumps rather than spend a lot of time going over old dumps from 4 months ago. A lot of updates and changes mean that these older dumps might not be relevant anymore.

I ran the dumps through our app and the high level summary is shown below. The variety of different codes does make me wonder if a hardware problem is the cause.

Code:

BugCheck 133, {1, 1e00, fffff8023a344380, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+144865 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 139, {3, ffffba0b61101a20, ffffba0b61101978, 0}
Probably caused by : MbamChameleon.sys ( MbamChameleon+c0d6 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck EF, {ffff878eee0e6500, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+fd )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 7F, {8, ffffab81a35db170, 0, fffff8051cd25c6c}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+2ae )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff806757272a8, ffff968ac87ef0a0, 0}
Probably caused by : ntkrnlmp.exe ( nt!RtlpHpVsChunkSplit+a38 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000005, fffff8054fee3ca7, 0, ffffffffffffffff}
Probably caused by : FLTMGR.SYS ( FLTMGR!FltpPassThroughCompletionWorker+27 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck EF, {ffffbe8584b15140, 0, 0, 0}
Probably caused by : unknown
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {ffffc20b7bd53294, 2, fffff8078051ecca, 0}
Probably caused by : dxgmms2.sys ( dxgmms2+2928 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff80236a22ef2, ffffb98d21b32da0, 0}
Probably caused by : hardware ( dxgkrnl!NtTokenManagerOpenSectionAndEvents+272 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000005, fffff8026c852b1a, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1ba1d5 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff80577ad452f, ffff800767f55930, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+84f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff80044efbc60, ffff81076760bf80, 0}
Probably caused by : win32kbase.sys ( win32kbase!EtwTraceUIPIMsgError+17b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

hazelgray · Dec 18, 2020

I understand, thanks for having a look anyway!

I ran memtest for 17 hours and it completed 6 passes with 0 errors over this time. Apologies I couldn't see a way to save the results from the configuration menu.

After I hit ESC and booted up my computer, another BSOD occurred while I was typing my reply here (I had only opened Chrome). I ran the BSOD collection app again and have attached the zip.

zbook · Dec 18, 2020

Run Memtest86 version 8.4 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.

MemTest86 - Official Site of the x86 Memory Testing Tool

Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)

Memtest86 has a feature to produce a text report.
Please post this in addition to the images.

philc43 · Dec 19, 2020

Hello hazelgray,

It continues to look like memory issues. Sometimes the test programs do not pick up the problem and the only way to track this down is to remove one stick of RAM at a time and see if the system works reliably with one or the other. It may take a day or two of testing but hopefully you can operate your system with just 8GB of memory.

xilolee · Dec 25, 2020

Hi!

You should have not updated the BIOS to (P)3.30.
The latest UEFI BIOS for your configuration should be 3.10.
Why?
Asrock wrote in the notes of the newer BIOS versions:

ASRock do NOT recommend updating this BIOS if Pinnacle, Raven or Summit Ridge CPU is being used on your system.

And yours is Pinnacle.
I don't know if now you will be able to flash previous BIOS 3.10.
Before you'll try that one, install AMD drivers:
- AMD B450 chipset driver version 2.10.13.408, Oct 19 2020
- Adrenalin 2020 Edition 20.12.1, Dec 8 2020
I'd choose to do a clean install with adrenalin.
Later, you can remove the folder where the installer extracted its files (usually in c:\amd).
I can't find information about your RAM (model or manufacturer... Golden empire, maybe?).
RAM frequency is supported by your CPU and MoBo.
LAN driver can be updated (realtek.com).
MBAV seems to be updated.

hazelgray · Dec 25, 2020

Hello

Thanks for your reply, I didn't know my CPU was a Pinnacle CPU. It was suggested to me previously to update my BIOS as I had BSODS before that (not here) just to explain why I updated it.

I documented the events that happened while following your suggestions:

I had two BSODS while browsing
I downloaded and installed the 2.10.13.408 AMD chipset drivers, had another BSOD after restart
then another BSOD while browsing
I downloaded and installed 20.12.1 through my Radeon Software app - (how do you recommend I should do a clean install?)
I ran the BSOD collection app then had another BSOD while replying here
installed and ran the Realtek PCIe auto install program

I've run and attached the collection app again.

I thought my RAM was GSkill but I took one of my RAM sticks out and have attached a pic. They are both 8gb pc4-19200 Geil.

xilolee · Dec 25, 2020

So unstable... Try to use Windows in safe mode and see if bsod appears.

zbook · Dec 26, 2020

1) Open administrative command prompt (ACP) and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) Uninstall Malwarebytes using the applicable uninstall tool:
https://downloads.malwarebytes.com/file/mb_clean

14) When available display results for post #7.

15) For any BSOD:

a) run the Sysnative log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

hazelgray · Dec 29, 2020

zbook said:
1) Open administrative command prompt (ACP) and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Microsoft Windows [Version 10.0.19041.685]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19041.685

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19041.685

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
607488 file records processed.
File verification completed.
Phase duration (File record verification): 9.29 seconds.
11839 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.38 milliseconds.

Stage 2: Examining file name linkage ...
23165 reparse records processed.
898568 index entries processed.
Index verification completed.
Phase duration (Index verification): 30.13 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 2.38 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.08 milliseconds.
23165 reparse records processed.
Phase duration (Reparse point and Object ID verification): 53.77 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 35.99 milliseconds.
145541 data files processed.
Phase duration (Data attribute verification): 0.39 milliseconds.
CHKDSK is verifying Usn Journal...
37001568 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 299.26 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

233798714 KB total disk space.
107467396 KB in 449636 files.
362200 KB in 145542 indexes.
0 KB in bad sectors.
717042 KB in use by the system.
65536 KB occupied by the log file.
125252076 KB available on disk.

4096 bytes in each allocation unit.
58449678 total allocation units on disk.
31313019 allocation units available on disk.
Total duration: 42.22 seconds (42223 ms).

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-SHQNNJV\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-SHQNNJV\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE

C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Windows\system32>

hazelgray · Dec 29, 2020

zbook said:
15) For any BSOD:

a) run the Sysnative log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Thanks zbook, sorry it takes me a few days to respond. I haven't had any recent BSODS since Saturday (but to be fair I've been on the PC maybe one full day since).

My zipped memory.dmp is at this link: MEMORY.zip

About to do the Malware bytes uninstall and will do the further memtest-ing next.

hazelgray · Dec 29, 2020

xilolee said:
So unstable... Try to use Windows in safe mode and see if bsod appears.

philc43 said:
Hello hazelgray,

It continues to look like memory issues. Sometimes the test programs do not pick up the problem and the only way to track this down is to remove one stick of RAM at a time and see if the system works reliably with one or the other. It may take a day or two of testing but hopefully you can operate your system with just 8GB of memory.

Thank you I will put these on my list of things to test!

zbook · Dec 29, 2020

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:
Windows Resource Protection did not find any integrity violations.

Open administrative command prompt (ACP) and type or copy and paste:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

Find the new text files on the destop > post share links using one drive, drop box, or google drive

Memtest86 can be ran overnight.
Memtest86 is substantially faster than Memtet86+.

Code:

Debug session time: Fri Dec 25 21:37:40.837 2020 (UTC - 6:00)
System Uptime: 0 days 0:06:48.500

Temp4_MEMORY.zip\MEMORY.DMP

Bugcheck code 00000101
Arguments 00000000`00000010 00000000`00000000 fffff805`35f4e180 00000000`00000000



ffffb58f`607644c8  ffffba8c`3666c080
ffffb58f`607644d0  00000000`00000000
ffffb58f`607644d8  fffff805`37603451*** ERROR: Module load completed but symbols could not be loaded for farflt.sys
farflt+0x13451
ffffb58f`607644e0  00000000`0001d818
ffffb58f`607644e8  ffffca80`ff19b170


farflt.sys   Tue Sep 29 11:30:15 2020 (5F736117)

hazelgray · Dec 29, 2020

zbook said:
Open administrative command prompt (ACP) and type or copy and paste:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

Find the new text files on the destop > post share links using one drive, drop box, or google drive

Memtest86 can be ran overnight.
Memtest86 is substantially faster than Memtet86+.

sfc details: sfcdetails.txt
cbs: cbs.txt

Ok I've rewritten my USB with Memtest86 and will run today.

hazelgray · Dec 31, 2020

I couldn't get the regular memtest86 to work, I rewrote it a couple of times onto the USB and every time I tried to boot into it I didn't get a bootable UEFI just 'USB: Sandisk' which then threw up a "Reboot and Select proper Boot device" message.
So I used the older version again which worked fine.

Again searched through the menu options this morning and could not find an appropriate report function. Completed 10 passes with 0 errors.

File_001.jpeg

xilolee · Jan 1, 2021

hazelgray said:
I downloaded and installed 20.12.1 through my Radeon Software app - (how do you recommend I should do a clean install?)

When you open adrenalin setup, you have that option available:

Are you using safe mode?
Or are you still running the OS the normal way?

In both cases, did you get other BSODs?

x BlueRobot · Jan 1, 2021

Rich (BB code):

0: kd> !ipi
IPI State for Processor 0

    As a receiver, unhandled requests are pending from processor(s) 8.

    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]

    From processor 8, active request of type: flush multiple
        Flush Count b0  Flush List ffffffdac7b03b1f  (dp ffffffdac7b03b1f lb0)

IPI State for Processor 1
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for Processor 2
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for Processor 3
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for Processor 4
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for Processor 5
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for Processor 6
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for Processor 7
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for Processor 8

    As a sender, awaiting IPI completion from processor(s) 0.

    TargetCount          1  PacketBarrier        1  IpiFrozen     0 [Running]


IPI State for Processor 9
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for Processor 10
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for Processor 11
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]

As we can see, we're awaiting completion of a TLB flush from processor 0, however, we don't receive a response within the allocated timeout and therefore crash. The interesting part is what is happening on processor 0 during the time of the crash.

Here's the call stack for processor 0; the hung processor:

Rich (BB code):

0: kd> knL
# Child-SP          RetAddr           Call Site
00 fffff805`3de85dd0 fffff805`3a00363c nt!KiPageFault
01 fffff805`3de85e00 fffff805`3a00363c nt!KiPageFault+0x3c
02 fffff805`3de85f90 fffff805`3a00363c nt!KiPageFault+0x3c
03 fffff805`3de86120 fffff805`3a00363c nt!KiPageFault+0x3c
04 fffff805`3de862b0 fffff805`3a00363c nt!KiPageFault+0x3c
05 fffff805`3de86440 fffff805`3a00363c nt!KiPageFault+0x3c
06 fffff805`3de865d0 fffff805`3a00363c nt!KiPageFault+0x3c
07 fffff805`3de86760 fffff805`3a00363c nt!KiPageFault+0x3c
08 fffff805`3de868f0 fffff805`3a00363c nt!KiPageFault+0x3c
09 fffff805`3de86a80 fffff805`3a00363c nt!KiPageFault+0x3c

[...]

The entire call stack is filled with page faults. Now I believe this is because the flush list pointer is an invalid memory address and therefore leads to the page fault. However, while attempting to resolve the first page fault, we encounter another segmentation/page fault we attempt to resolve. Although, bear in mind, page faults are technically considered as exceptions and exception occurring during an exception will lead to a double fault which is considered a fatal error.

Rich (BB code):

0: kd> dp ffffffdac7b03b1f L1
ffffffda`c7b03b1f  ????????`????????

Here's another excerpt from the call stack of the hung processor:

Rich (BB code):

0: kd> knL
  *** Stack trace for last set context - .thread/.cxr resets it
# Child-SP          RetAddr           Call Site
00 fffff805`3de82f20 fffff805`3a00363c nt!KiPageFault+0x10
01 fffff805`3de830b0 fffff805`3a00363c nt!KiPageFault+0x3c
02 fffff805`3de83240 fffff805`3a00363c nt!KiPageFault+0x3c
03 fffff805`3de833d0 fffff805`3a00363c nt!KiPageFault+0x3c
04 fffff805`3de83560 fffff805`3a00363c nt!KiPageFault+0x3c
[...]
36 fffff805`3de88380 fffff805`3a00363c nt!KiPageFault+0x3c
37 fffff805`3de88510 fffff805`3a00363c nt!KiPageFault+0x3c
38 fffff805`3de886a0 fffff805`3a00363c nt!KiPageFault+0x3c
39 fffff805`3de88830 fffff805`3a00363c nt!KiPageFault+0x3c
3a fffff805`3de889c0 fffff805`3a00363c nt!KiPageFault+0x3c
3b fffff805`3de88b50 fffff805`3a00363c nt!KiPageFault+0x3c
3c fffff805`3de88ce0 fffff805`3a0022fc nt!KiPageFault+0x3c
3d fffff805`3de88e70 fffff805`3a003610 nt!KiDoubleFaultAbort+0x3c << Another one!
3e fffff805`3de82f20 fffff805`3a00363c nt!KiPageFault+0x10
3f fffff805`3de830b0 fffff805`3a00363c nt!KiPageFault+0x3c
40 fffff805`3de83240 fffff805`3a00363c nt!KiPageFault+0x3c
41 fffff805`3de833d0 fffff805`3a00363c nt!KiPageFault+0x3c
[...]
79 fffff805`3de88b50 fffff805`3a00363c nt!KiPageFault+0x3c
7a fffff805`3de88ce0 fffff805`3a0022fc nt!KiPageFault+0x3c
7b fffff805`3de88e70 fffff805`3a003610 nt!KiDoubleFaultAbort+0x3c << Fatal error!
7c fffff805`3de82f20 fffff805`3a00363c nt!KiPageFault+0x10
7d fffff805`3de830b0 fffff805`3a00363c nt!KiPageFault+0x3c
7e fffff805`3de83240 fffff805`3a00363c nt!KiPageFault+0x3c
7f fffff805`3de833d0 fffff805`3a00363c nt!KiPageFault+0x3c
80 fffff805`3de83560 fffff805`3a00363c nt!KiPageFault+0x3c
[...]

If you take a look at the stack frame for the double fault, you'll also notice that the address which it's attempting to reference is also invalid, which causes a segmentation fault which again is another exception.

Rich (BB code):

0: kd> .frame /r 7b
7b fffff805`3de88e70 fffff805`3a003610 nt!KiDoubleFaultAbort+0x3c
rax=00000e0d4146dec0 rbx=0000000000000000 rcx=000064818c8a82c0
rdx=000064818c89cd20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8053a0022fc rsp=fffff8053de88e70 rbp=fffff8053de88ef0
r8=000064818c8a82c0  r9=000064818c89cd20 r10=000064818c914000
r11=000000000000ee20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na pe nc
cs=0010  ss=0000  ds=0000  es=0000  fs=0000  gs=0000             efl=00010082
nt!KiDoubleFaultAbort+0x3c:
fffff805`3a0022fc 65f604257802000001 test  byte ptr gs:[278h],1 gs:00000000`00000278=??

You can dump the segment descriptor for a segment register by using the dg command:

Rich (BB code):

0: kd> dg gs
                                                    P Si Gr Pr Lo
Sel        Base              Limit          Type    l ze an es ng Flags
---- ----------------- ----------------- ---------- - -- -- -- -- --------
0000 00000000`00000000 00000000`00000000 <Reserved> 0 Nb By Np Nl 00000000

Since the present flag is cleared, then the processor will raise an exception when we attempt to access it. From the Intel documentation it states the following:

A contributory exception or page fault that subsequently referenced a not-present segment would cause a double fault (#DF) to be generated instead of #NP.

Rich (BB code):

0: kd> u nt!KiPageFault+0x3c
nt!KiPageFault+0x3c:
fffff805`3a00363c 65f604257802000001 test  byte ptr gs:[278h],1
fffff805`3a003645 7508            jne     nt!KiPageFault+0x4f (fffff805`3a00364f)
fffff805`3a003647 0faee8          lfence
fffff805`3a00364a e96c020000      jmp     nt!KiPageFault+0x2bb (fffff805`3a0038bb)
fffff805`3a00364f 650fb604257a020000 movzx eax,byte ptr gs:[27Ah]
fffff805`3a003658 b948000000      mov     ecx,48h
fffff805`3a00365d 33d2            xor     edx,edx
fffff805`3a00365f 0f30            wrmsr

Have you ran any SSD diagnostics tests? This certainly appears to more of a hardware issue rather than software in my opinion.

Long time BSODS and freezing

Member

Member

Attachments

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

Member

Attachments

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

Member

Attachments

Member

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

Moderator

Member

Attachments

Moderator

Member

Member

Member

Member

Member

Member

Member

Moderator

Administrator