BSOD after trying to print from Biodex System 3 software, win32k.sys

Hello,

When I try to print an analysis from the software System 3 PRO (which is a software used for the System 3 dynamometer for analyzing joint recovery and other stuff in patients) I recieve an error:

win32k.sys
PAGE_FAULT_IN_NONPAGED_AREA

STOP: 0x00000050

This happens when I use Microsoft XPS Document Writer and the HP DeskJet 5650, so I'm guessing it's not the printer driver's fault as I've also reinstalled that.
The problem is, that I have tried deleting the FNTCACHE.DAT file as suggested in many other threads, but it doesn't help. I've deleted it from the startup repair command prompt, but it keeps comming back. Biodex support says that the software could not be compatible with windows 7 but only windows XP so I've also tried to change the compatibility mode to Win XP and still no luck.

I will also attach the DMP file for more information

Help appreciated, thank you

Did you ever get this resolved? The problem is caused by halmacpi.dll.

Would you please go here and follow the procedure-

Blue Screen of Death (BSOD) Posting Instructions

The resulting .zip file will provide more information about the problem.

I have been trying to solve this for days, still nothing. What should I do with the halmacpi.dll?

Here's the file that provides more information.

Attachment 406773

Thanks.

Hmm... yeah the PC isn't connected to the internet at all cause it's not needed, therefore no updates were installed. I'll connect and update, see if that fixes it.

Thanks

Okay, so interesting thing happened.

I've updated the PC. When I tried to print from that Biodex software, the BSOD still occured but only for a split second (and no print of course). The SECOND time I tried to print, it miraculously worked. But the third time, BSOD again. I think this time there's a different cause for a BSOD.

thoughts?

Hey, sorry for the late reply.
Here are the latest logs

I wonder if you would go to C:\Windows\Minidump and delete all files in that folder. I think that's where the .dmp files are coming from. Then, post a new set of files when the problem occurs again.