So far this year every BSOD has been for a different cause
Code:
BugCheck A, {ffff85805edf1000, 2, 0, fffff80021fd89b0}
Probably caused by : sdbus.sys ( sdbus!SdbusDataCommandWorker+1099 )
BugCheck 19, {22, ffffd10f02e00000, 0, 0}
fffff80399a2e338: Unable to get MiVisibleState
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c18a )
BugCheck D1, {ffffffffffffffff, 2, 1, fffff8017525aa34}
*** WARNING: Unable to verify timestamp for rtux64w10.sys
*** ERROR: Module load completed but symbols could not be loaded for rtux64w10.sys
Probably caused by : NETIO.SYS ( NETIO!WfpCreateReassemblyContext+28 )
BugCheck 7F, {8, ffffb20180908a30, 83f2e7d0, ffff875d0d29caa6}
*** WARNING: Unable to verify checksum for win32kfull.sys
Probably caused by : memory_corruption
BugCheck 3B, {c0000005, fffff8013d8d805d, ffff9301d9561600, 0}
Probably caused by : memory_corruption
With this sort of behaviour it suggests you have some basic driver problems but the last 2 also point to possibly bad memory modules. The latter is easy to check for:
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
Note
MemTest86+ needs to be run for
at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for
zero errors here. Even a single error will indicate RAM failure.
Make a photo of the result and post it.
Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
Let's start with that and then move onto other possible causes.
Quote