hal.dll Driver Causing BSOD. Here's what I've tried to fix it....

So this issue has been happening for over a year. I have no clue what initially caused the BSOD and have tried troubleshooting it the best I can. I am now about to lose my mind as the issue happens so randomly. I thought it might have to do with the wifi card, but I replaced that and it just happened again. It seems to happen the most when I’m uploading or downloading a large file online. This is why I initially replaces the wifi card. Now I have no clue what to try. Here is what I have done so far to try and fix the issue.

Replaced the wifi card

Performed a memtest for about 2 hrs with no issues (I know 4hr min is suggested)

Did a stress test on my machine to see if it was overheating – it performed at manufacturer spec temp.

Ended up buying new sticks of RAM just in case there was an issue with one of them. Before doing so I tried
removing just one stick – it BSOD’d I then swapped my other one out and it did it again.

Updated all of my drivers using multiple software programs to identify what was out dated. This includes wifi drivers and graphics drivers.

I’ve also tried using another power source as one site suggested it may be a power issue

My logs are attached as required. My machine is older but I’ve upgraded the RAM and put in a SSD so its performance is still very suitable for me. I’m hoping I can resolve this issue and continue to use the o’l girl.
Thanks for reading and hopefully helping me resolve this ongoing issue.

Thanks for the response. I removed daemon tools lite, free'd up space so I now have 32% free space on my drive. I also checked the setting you had mentioned to ensure my configuration was setup to save a kernel dump and it was setup correctly. I checked the log location and only see the older logs which you mention. Is there any other setting I can check to ensure the kernel dump files are properly being saved? Thanks!

It is not a setting, but check the system files for problems

Please do the following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation",

Only if sfc did NOT say that it is requested

No problem,

Are you still experiencing BSOD's?
If so, please check {windows partition}\windows\minidump for dump files and if there are dump files, use the tool again and upload the zip.