BSOD Hal.dll with IRQL_NOT_LESS_OR_EQUAL and SYSTEM_SERVICE_EXCEPTION

So I've been running on the 2 sticks of RAM that cleared 8 passes. I did steps 1-3 in the previous post. I uninstalled the Fireface_64.sys driver but did not reinstall it. This audio interface has a USB connection as well as firewire so I've been using the USB connection for the last week and have not had any BSODs. However, the audio performance with the USB is terrible and I need to switch back soon, So if the crashes come back when I switch back to Firewire, then I think we will know why now.

The only other weird thing that's going on is that I unplugged my PC from the wall due to a thunder storm that came through. I didn't plug it back in for several days. When I went to turn it on, it had a black screen again. I restarted it and it wanted me to go through setup again like when BIOS settings change. I missed the prompt and it booted to my OS clone drive. After some futzing, it's booting normally again but this is similar to what happened before when I was out of town for a week. My computer was unplugged for that week as well. I know there's a little watch battery on the motherboard, but I was under the impression those would likely last for longer than the lifespan of my computer. So perhaps the black screens I experienced were a separate, unrelated issue from the BSODs.

Ztruker said:

Run your pic through an image editor and invert it.

I turned my head upside down and it seemed to work. Although I could read it in the first place (with +1 to concentration) come to think of it.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) 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

zbook said:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) 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.17134.165]
(c) 2018 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 did not find any integrity violations.

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

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.165

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

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

Stage 1: Examining basic file system structure ...
563712 file records processed.
File verification completed.
12165 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
17268 reparse records processed.
705788 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
17268 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
71039 data files processed.
CHKDSK is verifying Usn Journal...
41347384 USN bytes processed.
Usn Journal verification completed.

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

975286270 KB total disk space.
196705792 KB in 312672 files.
181456 KB in 71040 indexes.
0 KB in bad sectors.
708918 KB in use by the system.
65536 KB occupied by the log file.
777690104 KB available on disk.

4096 bytes in each allocation unit.
243821567 total allocation units on disk.
194422526 allocation units available on disk.

C:\WINDOWS\system32>

Looks good.

These are some links on resetting the BIOS or replacing the CMOS battery:

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

zbook said:

Looks good.

These are some links on resetting the BIOS or replacing the CMOS battery:

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

I replaced the CMOS battery.

I also reinstalled the Fireface_64.sys driver and am using the Firewire connection again with this interface. If I get another BSOD, I'll switch back to the USB and uninstall the firewire driver again and see how it goes for another week or longer.

How long has the computer been without a BSOD?
See if you can check the remaining RAM modules running most of the testing overnight.

Okay just got a BSOD. They seem to happen right when I close an application. It feels like that is the case 100% of the time.

Log Collector Beta
https://1drv.ms/u/s!AmTSH13ggSmRhjcNtwKzOh5LXuje
Memory Dump
https://1drv.ms/u/s!AmTSH13ggSmRhjigKQlnlKxMkhjc

The log collector did not collect any mini dumps.
The log files did not display the BSOD.
The memory dump is currently downloading.

Please post new images for these steps:

1) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

2) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread