BSOD hal.dll IRQL_NOT_LESS_OR_EQUAL - I can reproduce it sometimes

Loqzer

Member
Joined
May 9, 2020
Posts
8
Hi,
I have BSODs since a few months. Not every day but regularly. I have tried to force the BSOD and I succeed most in a combination:
I have two screens. On the main screen I have World of Warcraft running, on the secondary screen I have the current Firefox open. When I open the following website (addon website for the game) the BSOD happens regularly:
Wago
I usually only have the BSOD when the game World of Warcraft is open and I am using Firefox at the same time.

· OS - Windows 10, 8.1, 8, 7, Vista ? Windows 10 Pro (Version 10.0.18362 Build 18362)
· x86 (32-bit) or x64 (64-bit)? 64bit
· What was the originally installed OS on the system? Windows 7
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Fullversion. I bought a key online and got the iso from Microsoft
· Age of system (hardware) ca. 2014
· Age of OS installation - have you re-installed the OS? January

· CPU Prozessor Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz, 3500 MHz, 4 Kern(e), 8 logische(r) Prozessor(en)
· Video Card NVIDIA GeForce GTX 970
This is a borrowed card from a friend, my Geforce Titan (first gen) died last November. This might also be the starting point of my BSOD odyssey.
· MotherBoard - (if NOT a laptop) MSI Z87 MPOWER (MS-7818)
· Power Supply - brand & wattage (if laptop, skip this one) Coolermaster 750w

Im also using a RME Fireface Audio Interface since I produce music on this PC.

I ran SynaptiveBSODCollectionApp but it just keeps repeating "Waiting for SystemInfo" for half an hour now.
I will attach the file after I restarted - I don't want to lose my post meanwhile

Edit: Ok Synaptive doesn't seem to create the folder and the logs. It just keeps repeating "Waiting for SystemInfo".

So here is information from whocrashed meanwhile:

crash dump file: C:\Windows\Minidump\051020-9734-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF8043282366D)
Bugcheck code: 0xA (0xFFFF830F84377448, 0x2, 0x0, 0xFFFFF8043282366D)
Error: IRQL_NOT_LESS_OR_EQUAL

And from BlueScreenView:
051020-9734-01.dmp 10.05.2020 00:48:31 IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffff830f`84377448 00000000`00000002 00000000`00000000 fffff804`3282366d hal.dll hal.dll+1b66d x64 ntoskrnl.exe+1c2390 C:\Windows\Minidump\051020-9734-01.dmp 8 15 18362 402.476 10.05.2020 00:49:07
 
Last edited:
It's normal for the message "Waiting for systeminfo" to be showing for quite some time and appearing to be freezing, it's a result of msinfo32.nfo needing quite some time to collect all information.
If the message is showing for more than 10 minutes, close the prompt and reboot Windows. After Windows has rebooted, run the app again.

We do need the files from the tool as they provide much more insight than WhoCrashed and Bluescreen view can provide.
 
It's normal for the message "Waiting for systeminfo" to be showing for quite some time and appearing to be freezing, it's a result of msinfo32.nfo needing quite some time to collect all information.
If the message is showing for more than 10 minutes, close the prompt and reboot Windows. After Windows has rebooted, run the app again.

We do need the files from the tool as they provide much more insight than WhoCrashed and Bluescreen view can provide.
Can I change the path of the zip? I found a txt file that says "we're done" but there is no zip. It might be because I redirected my documents to another partition or because my language is not english?
 
It may have to do with the user environment variables. If you redirect your documents folder, the zip will be created in the old documents folder. If the new location is D:\Documents and the variables point to C:\users\<user>\documents the zip is located at C:\users\<user>\documents.

I would not recommend to update the user environment variables in any way, I refer to those you cannot change in the control panel (homepath, homedrive, ...), because that could and possibly would complicate things in the future. It would likely complicate collecting files using the Sysnative collector tool.
 
It may have to do with the user environment variables. If you redirect your documents folder, the zip will be created in the old documents folder. If the new location is D:\Documents and the variables point to C:\users\<user>\documents the zip is located at C:\users\<user>\documents.

I would not recommend to update the user environment variables in any way, I refer to those you cannot change in the control panel (homepath, homedrive, ...), because that could and possibly would complicate things in the future. It would likely complicate collecting files using the Sysnative collector tool.
I don't understand it, what impact would if have to my system if I just change the path to where the sysnative tool is saving the zip to? Why can't it be desktop for example?
 
The sysnative tool uses 2 variables to do this, %homedrive% and %homepath%. These two combined leads to C:\users\<user> normally, then '\documents' is added to it.
I do not know where your new documents folder is located, for me it's new location is G:\documents. If I would want the sysnative tool to create the zip at G:\documents, I would need to change the code to make it use only 1 variable and the user environment variable would need to be updated to make this happen. If I were to use any small tools I have locally, I would get a lot of issues with running any of them because of the user environment variable that I updated.
 
The sysnative tool uses 2 variables to do this, %homedrive% and %homepath%. These two combined leads to C:\users\<user> normally, then '\documents' is added to it.
I do not know where your new documents folder is located, for me it's new location is G:\documents. If I would want the sysnative tool to create the zip at G:\documents, I would need to change the code to make it use only 1 variable and the user environment variable would need to be updated to make this happen. If I were to use any small tools I have locally, I would get a lot of issues with running any of them because of the user environment variable that I updated.
Hm ok it might be a language barrier for me here I don't understand what you are trying to tell me. So if the path where the tool is saving the zip can't be changed I don't know how to make it work then. It ran for a few hours today and I still don't habe a .zip file.
 
It may have to do with the user environment variables. If you redirect your documents folder, the zip will be created in the old documents folder. If the new location is D:\Documents and the variables point to C:\users\<user>\documents the zip is located at C:\users\<user>\documents.

As mentioned earlier, it's created in the old documents folder.
 
That's the content of the folder that is zipped, there's no zip file 1 folder earlier?

If there is no zip file 1 folder earlier, please select all files in the folder 'SysnativeFileCollectionApp', right-click > send to > compressed (zipped) folder and upload the zip file.
 
Please update your sound card driver if possible - Driver Reference Table (DRT) | fireface_64.sys

Rich (BB code):
0: kd> lmvm fireface_64
Browse full module list
start             end                 module name
fffff80b`2fce0000 fffff80b`2fd02000   fireface_64 T (no symbols)           
    Loaded symbol image file: fireface_64.sys
    Image path: fireface_64.sys
    Image name: fireface_64.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Feb 25 06:31:27 2019 (5C73FC3F)
    CheckSum:         0002E644
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
 
Yeah it is the latest. Is it maybe the hardware? I have the fireface connected using a firewire Pcie card. Could that be the problem? The fireface itself works like a charm in combination with my audio software. The bsods only occur while gaming and browsing.
I can't get this one site wago that I mentioned out of my head. Some element on this side seems to trigger it.
 
It depends on what's wrong if the driver is to blame. A corruption in a single line of the code can cause issues that don't necessarily show up in other operations by the card.
And, it's possible that the driver is corrupted (and there are also other possibilities - such as the hardware of the firewire card)
To check if it's corrupted - download a fresh copy of the latest drivers for that device.
Then uninstall the current software - reboot - and then install the freshly downloaded software
That'll (hopefully) replace any corrupted files (This depends if the uninstaller removes everything - and if the new installer replaces any leftover files or if it leaves them without modifying them)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top