I seem to have random BSOD's that seem to suggest memory errors but windows memory diagnostics, memtest86 and memtest86+ all passed with no errors
the BSOD's seemed to be more frequent with memory context restore enabled in the bios and i have since disabled it and the bsods are less frequent
i think the memory context restore was a separate issue that caused the same kind of memory related BSOD's
but now i still do occasionally get BSOD's
event viewer has the following trail each time the BSOD happens
it may also be related to qbittorrent as both times I've witnessed it happening i had qbittorrent open downloading
Kernel-PnP 219 (212)
The driver \Driver\WUDFRd failed to load.
Device: HID\VID_1377&PID_600D&MI_03&Col01\b&10c33cb3&0&0000
Status: 0xC0000365
With Nirsoft DevManView and device manager with the devices by container view I've narrowed it down to "HID-compliant headset" under my heaphones (which are senheiser PXC 550-II if thats relevant)
I have disabled "HID-compliant headset" for now to see if that fixes it but have to wait and see
Ntfs (Microsoft-Windows-Ntfs) 98
Volume G: (\Device\HarddiskVolume8) is healthy. No action is needed.
Wininit 14
Credential Guard configuration:
Registry Configuration: 0x0
Test Configuration: 0
Auto Enablement: 0
IsolatedUserMode 5
Secure Trustlet NULL Id 0 and Pid 0 started with status STATUS_SUCCESS.
IsolatedUserMode 1
Secure Trustlet \??\C:\WINDOWS\system32\lsaiso.exe Id 1 and Pid 1472 started with status STATUS_SUCCESS.
Wininit 18
VBS Key Isolation was started and will protect VSM-isolated keys.
Wininit 12
LSASS.exe was started as a protected process with level: 4.
BugCheck 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffff920c27c60152, 0x0000000000000000, 0xfffff8008571010a, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\032825-18031-01.dmp. Report Id: a603ed54-86ee-4fde-b52d-a81997e67a94.
This is where the computer crashes and reboots
EDIT:
Using Nirsoft BlueScreenView i was able to get the following information:
spoiler
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x00000050 (0xffff920c27c60152, 0x0000000000000000, 0xfffff8008571010a,
0x0000000000000000)
*** ntoskrnl.exe - Address 0xfffff800858b7ce0 base at 0xfffff80085400000 DateStamp
0x783a7a83
spoiler
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff805ae3c33a0,
0x0000000000000000)
*** ntoskrnl.exe - Address 0xfffff805ad8b7ce0 base at 0xfffff805ad400000 DateStamp
0x783a7a83
spoiler
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
SYSTEM_SERVICE_EXCEPTION
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff8049c681250, 0xffffad0146de08d0,
0x0000000000000000)
*** ntoskrnl.exe - Address 0xfffff8049c4b7ce0 base at 0xfffff8049c000000 DateStamp
0x783a7a83
"ntoskrnl.exe" shows up consistently in all the dumps listed in BlueScreenView
Yeah same, some days I want to be feminine-feminine but other days I want to be cool-feminine