BSOD in Project64 v2.2

[ToonEugen6812]

Hi there. I'm new here but I saw this emulator long ago. So yeah, I got the latest version for Project64 and then SM64. First time playing was fine so I configured settings for controllers and then, an error with a plugin appear. I restarted and then, boom! Blue Screen of Death, I've tried an another try and then again the problem. Help? I've installed an important Windows update from the forums and I'm not sure if it will be fine.

OS: Windows 7 64-bit (SP1)

I will show only the OS since the graphic cards are fine for playing emulator games.

[NES_player4LIFE]

What did the error message say?

[ToonEugen6812]

Originally Posted by NES_player4LIFE

What did the error message say?

I really don't KNOW!! That's why. I've closed the error immediately. Is there a list of plugin error things?

[V1del]

If it hasn't happened again it should be fine, BSODs are a problem of Windows I doubt there's a PJ64 specific list

[theclaw135]

Originally Posted by V1del

If it hasn't happened again it should be fine, BSODs are a problem of Windows I doubt there's a PJ64 specific list

In that case something about PJ64 or its behavior, is revealing the error's presence to users previously unaware of it.

[V1del]

yes which is why you should update/complain to microsoft to get it fixed

[HatCat]

Historically, it's always been a fault in the OS that needs to be patched (and historically people would install the official patches from MS and have that fixed), and never technically a bug in the application that exploited it accidentally.

But I would tend to blame the amount of advanced WIN32-ism that pj64 does anyway. I think LuigiBlood found out even with the interpreter running a demo that never ran the RSP for anything, it still crashed .00001% of the time and there's still some weird code that Project64 uses. But nobody had the time to isolate what caused it due to having to BSOD every time just to test, so it's really easiest to just install the Windows updates to fix it that way.

[theclaw135]

Personally I wouldn't count on Microsoft fixing this.
It's not like PJ64 is of any interest to them.

[Breadwinka]

yup its caused by win32kfull.sys at least on windows 10.

[HatCat]

Originally Posted by theclaw135

Personally I wouldn't count on Microsoft fixing this.
It's not like PJ64 is of any interest to them.

um that's not the way it works.