Too all those getting the BSOD

[the_randomizer]

Originally Posted by Azimer

I was receiving BSOD errors like many I've seen in the forum. It seemed to work switching to Windows XP SP 3 compatibility mode. After I finished what I was doing, I decided to run all the possible updates I could (except for drivers and IE10). I took off the Windows XP SP 3 check and reran expecting it to blue screen. It did not. I was receiving the win32sys / SYSTEM SERVICE EXCEPTION error message.

Perhaps this will help someone.

Wait....that username....don't tell me you're---!

[Azimer]

Originally Posted by nintendo1889

Wait....that username....don't tell me you're---!

A newbie who doesn't update their system? Yes.

Like others, I just figured it was buggy software. It would appear the new PJ64 is hitting a bug that is now patched. It has nothing to do with any other drivers in my case.

[squall_leonhart]

As is the conclusion i have come to Azimer, the issue was supposedly fixed in a Windows 7 SP1 fix that wasn't pushed to Windows update (but was included in sp1)

There was such an issue in Windows Vista as well, but it was fixed in SP1.

[Azimer]

Originally Posted by squall_leonhart

the issue was supposedly fixed in a Windows 7 SP1 fix that wasn't pushed to Windows update (but was included in sp1)

This wasn't the case for me. I had SP1 installed and got BSOD. It was the 85 other post-SP1 patches I needed to install. I wish I knew exactly which one but I didn't have the patience to install then test each and every patch. Bottom line, update all recommended and optional patches except those you know you won't use (IE10).

[squall_leonhart]

There has been around 10 Kernel fixes pushed to the optional list since SP1, so its possible some users are missing a couple.

i've never seen a win32k bsod out of jabo's stuff, its a weird bug, particular the function it occurs in 100% consistently is a typical windows function and is used in lots of windows apps.

[Azimer]

Funny you should bring up Jabo's stuff. I used the exact same 1.6 plugins in 2.0 and it blue screened. It wasn't Jabo's stuff doing it. It was the core emulator by recompiler and interpreter. It even happen with N64Stars. Either way... it's fixed. I just don't want misinformation out there (that it's Jabo's stuff).

[the_randomizer]

Originally Posted by Azimer

A newbie who doesn't update their system? Yes.

Like others, I just figured it was buggy software. It would appear the new PJ64 is hitting a bug that is now patched. It has nothing to do with any other drivers in my case.

No, I thought Azimer made plugins. Is that you?

[squall_leonhart]

Originally Posted by Azimer

Funny you should bring up Jabo's stuff. I used the exact same 1.6 plugins in 2.0 and it blue screened. It wasn't Jabo's stuff doing it. It was the core emulator by recompiler and interpreter. It even happen with N64Stars. Either way... it's fixed. I just don't want misinformation out there (that it's Jabo's stuff).

well that makes things even more weird, some users were adamant that it only occured with the 1.7 version of jabo's plugins.

but it would make more sense for it to come from the actual emulator since that would be where the window drawing stuff comes in.

[HatCat]

I needed to update from IE9 to IE10 but only to include websockets support for supersets of the JavaScript protocols on another website I participate at.

Good to know that it was actually just a threading issue. (As I said I never ran into it; I always seem to be the virgin with non-core-related bugs.)

[kinjo]

I am having SYSTEM SERVICE EXCEPTION problem in my pc.