Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD
that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read
most things that relate to hal.dll and kernel are either driver errors or hardware, as kernel/hal are gate keepers between software and hardware
File information: | 040119-3984-01.dmp (Apr 1 2019 - 16:34:44) |
Bugcheck: | BugCheck 100000B8, {ffffcd8454b9e080, ffffb681e7853200, 0, 0} (100000B8) |
Probably caused by: | ntkrnlmp.exe (Process: ccSvcHst.exe) |
Uptime: | 0 Day(s), 0 Hour(s), 02 Min(s), and 44 Sec(s) |
File information: | 032819-4859-01.dmp (Mar 28 2019 - 15:52:22) |
Bugcheck: | BugCheck 100000B8, {ffffa68fad9ea040, ffffd081d4d23200, 0, 0} (100000B8) |
Probably caused by: | ntkrnlmp.exe (Process: System) |
Uptime: | 1 Day(s), 1 Hour(s), 16 Min(s), and 59 Sec(s) |
File information: | 032719-6468-01.dmp (Mar 27 2019 - 14:34:46) |
Bugcheck: | BugCheck 100000B8, {ffffda00e36c4040, fffff800dbeac380, 0, 0} (100000B8) |
Driver warnings: | *** WARNING: Unable to verify timestamp for Plx9054_x64.sys |
Probably caused by: | Plx9054_x64.sys (Process: System) |
Uptime: | 53 Day(s), 17 Hour(s), 10 Min(s), and 00 Sec(s) |
File information: | 012519-6375-01.dmp (Jan 25 2019 - 14:25:45) |
Bugcheck: | BugCheck 100000B8, {ffffca0045899040, ffff95001cf49200, 0, 0} (100000B8) |
Probably caused by: | ntkrnlmp.exe (Process: System) |
Uptime: | 43 Day(s), 22 Hour(s), 06 Min(s), and 56 Sec(s) |
File information: | 121218-6093-01.dmp (Dec 12 2018 - 16:18:18) |
Bugcheck: | BugCheck 100000B8, {ffffab0843138080, ffffbd8195d49200, 0, 0} (100000B8) |
Probably caused by: | ntkrnlmp.exe (Process: ngen.exe) |
Uptime: | 0 Day(s), 23 Hour(s), 48 Min(s), and 16 Sec(s) |