Question hal.dll causing bsod

[merc476]

Hi,

I've been having the bsod happening consistently daily for the past 2 weeks or so. Today I finally had time to thoroughly make sure all my drivers, bios, disk and everything is up to date and checked for errors. I'm still getting it. When I run Bluescreen viewer, it's being caused by hal.dll. I attached a screen shot of the report. Is there any way I can get further detail to help me narrow this down? This system is my recording studio pc which has a few drives, firewire audio interface, a state raven touch and its running 3 total monitors using the onboard intel card which is up to date and i've used with no problems in the past. Any suggestions welcome!

bluescreen viewer report

 

[PC Tailor]

All processors that rendezvous have no errors in their registers. - When certain errors are detected in a multiprocessor system, a single processor takes control of the system while other processors enter a rendezvous state. The single processor performs error handling and then releases the other processors from the rendezvous state.

I don't know if that helps, I just wanted to know what it meant

@gardenman can you convert dumps and see if there is anything obvious? I wish axe wasn't so busy

In effect it is what it says, it a mechanism to prevent malicious code affecting the kernel / core OS. And allows all other logical processors to go into "rendezvous" why one processor deals with the error correction, when the error is rectified (if it can be) the processors are released. In rendezvous, the processor basically blocks all interupts to it. There is a pretty detailed view on how the OS works in that respect here:

https://software.intel.com/security...tel-analysis-microarchitectural-data-sampling

Where did you grab this excerpt from exactly?

You can also see some detail here: https://www.intel.com/content/dam/w...um-system-abstraction-layer-specification.pdf

 

[Colif]

I just realised something, crashes only show the drivers that are running during the project that fails. We are only seeing half the picture. Yes, this is obvious once you think about it.

op should download driver view. All it does is shows the drivers currently being run.
http://www.nirsoft.net/utils/driverview.html
when you open it, go to view tab and set it to hide all microsoft services.
I would run it while you are doing one of the projects that doesn't crash. upload a screenshot of the application showing the creation dates of the drivers.

We can then compare it against the list of drivers running when it does, and see if there is any difference.