Dolphin crashes when calling pid.dll

[Qaazavaca Qaanic]

I've started getting Dolphin crashing issues on my laptop. DolphinWX closes after the window shows up, DolphinQT crashes before the window pops up. I tried debugging in Visual Studio and got error:

Unhandled exception at 0x00007FFA16292456 (pid.dll) in Dolphin.exe: 0xC0000005: Access violation reading location 0x0000021295D10010.

> pid.dll!00007ffa16292456() Unknown
  pid.dll!00007ffa16293e1c() Unknown
  pid.dll!00007ffa162947f0() Unknown
  dinput8.dll!00007ffa096f8f63() Unknown
  dinput8.dll!00007ffa096fd87f() Unknown
  dinput8.dll!00007ffa096fd185() Unknown
  dinput8.dll!00007ffa096f5830() Unknown
  Dolphin.exe!00007ff6dfb30338() Unknown
  Dolphin.exe!00007ff6dfb2ef79() Unknown
  Dolphin.exe!00007ff6dfb2e530() Unknown
  Dolphin.exe!00007ff6dfb2e001() Unknown
  Dolphin.exe!00007ff6dfb286fc() Unknown
  Dolphin.exe!00007ff6dfa8f87d() Unknown
  Dolphin.exe!00007ff6dfa8e84b() Unknown
  Dolphin.exe!00007ff6dfe58234() Unknown
  Dolphin.exe!00007ff6dfdcd396() Unknown
  [External Code]

Dolphin 5.0-7289 at 1ec3a4db6c7c6d090bb682513f53cefa2db6d412. Nobody has reported pid.dll crashes in the forums. Installing 64-bit Visual C++ redistributable for Visual Studio 2017 did not help. 5.0-7601 also crashes.

[mstreurman]

I've started getting Dolphin crashing issues on my laptop. DolphinWX closes after the window shows up, DolphinQT crashes before the window pops up. I tried debugging in Visual Studio and got error:

Unhandled exception at 0x00007FFA16292456 (pid.dll) in Dolphin.exe: 0xC0000005: Access violation reading location 0x0000021295D10010.

> pid.dll!00007ffa16292456() Unknown
  pid.dll!00007ffa16293e1c() Unknown
  pid.dll!00007ffa162947f0() Unknown
  dinput8.dll!00007ffa096f8f63() Unknown
  dinput8.dll!00007ffa096fd87f() Unknown
  dinput8.dll!00007ffa096fd185() Unknown
  dinput8.dll!00007ffa096f5830() Unknown
  Dolphin.exe!00007ff6dfb30338() Unknown
  Dolphin.exe!00007ff6dfb2ef79() Unknown
  Dolphin.exe!00007ff6dfb2e530() Unknown
  Dolphin.exe!00007ff6dfb2e001() Unknown
  Dolphin.exe!00007ff6dfb286fc() Unknown
  Dolphin.exe!00007ff6dfa8f87d() Unknown
  Dolphin.exe!00007ff6dfa8e84b() Unknown
  Dolphin.exe!00007ff6dfe58234() Unknown
  Dolphin.exe!00007ff6dfdcd396() Unknown
  [External Code]

Dolphin 5.0-7289 at 1ec3a4db6c7c6d090bb682513f53cefa2db6d412. Nobody has reported pid.dll crashes in the forums. Installing 64-bit Visual C++ redistributable for Visual Studio 2017 did not help. 5.0-7601 also crashes.

Did you try uninstalling all of your VS redist and reinstalling them? seems to me it's a broken file. Since I do not have any issues. If you're the only one having the issue then of course no one will report it in the forums.

[Blackened15]

Did you try uninstalling all of your VS redist and reinstalling them? seems to me it's a broken file. Since I do not have any issues. If you're the only one having the issue then of course no one will report it in the forums.

I have the same problem. Tried uninstalling all VS redist, and reinstalling the one listed on the download page, didn't fix the problem.

Here is the error code from the event viewer (Windows 10 Pro)

Code:

Faulting application name: Dolphin.exe, version: 0.0.0.0, time stamp: 0x5b4d5acd
Faulting module name: pid.dll, version: 10.0.16299.15, time stamp: 0xb0251cfc
Exception code: 0xc0000005
Fault offset: 0x0000000000002456
Faulting process id: 0xd54
Faulting application start time: 0x01d41d4c02258ecc
Faulting application path: D:\emu\Dolphin-x64\Dolphin.exe
Faulting module path: C:\Windows\System32\pid.dll
Report Id: f8edfc67-4524-4fed-b874-7378a901873a
Faulting package full name:
Faulting package-relative application ID:

Edit: Fixed, was one of my USB controller (more accurately, a blizz-box 4-play) plugged it that caused the crash.

[Meekepee]

I have the same problem. Tried uninstalling all VS redist, and reinstalling the one listed on the download page, didn't fix the problem.

Here is the error code from the event viewer (Windows 10 Pro)

Code:

Faulting application name: Dolphin.exe, version: 0.0.0.0, time stamp: 0x5b4d5acd
Faulting module name: pid.dll, version: 10.0.16299.15, time stamp: 0xb0251cfc
Exception code: 0xc0000005
Fault offset: 0x0000000000002456
Faulting process id: 0xd54
Faulting application start time: 0x01d41d4c02258ecc
Faulting application path: D:\emu\Dolphin-x64\Dolphin.exe
Faulting module path: C:\Windows\System32\pid.dll
Report Id: f8edfc67-4524-4fed-b874-7378a901873a
Faulting package full name:
Faulting package-relative application ID:

Edit: Fixed, was one of my USB controller (more accurately, a blizz-box 4-play) plugged it that caused the crash.

Hey man I'm having the same error and I've tried unplugging all of my USBs besides my mouse and I keep getting the same error.

[rod.stuart1945@gmail.com]

how did u end up fixing this ?

i have exact same issue

when blissbox usb controller is plugged in dolphin crashes anderror reports point to pid.dll error

if i unplug blissbox then all works fine

however i need the blissbox plugged in for gamecube control so how can i resolve and have plugged in still?


please advise

thnaks joe

I have the same problem. Tried uninstalling all VS redist, and reinstalling the one listed on the download page, didn't fix the problem.

Here is the error code from the event viewer (Windows 10 Pro)

Code:

Faulting application name: Dolphin.exe, version: 0.0.0.0, time stamp: 0x5b4d5acd
Faulting module name: pid.dll, version: 10.0.16299.15, time stamp: 0xb0251cfc
Exception code: 0xc0000005
Fault offset: 0x0000000000002456
Faulting process id: 0xd54
Faulting application start time: 0x01d41d4c02258ecc
Faulting application path: D:\emu\Dolphin-x64\Dolphin.exe
Faulting module path: C:\Windows\System32\pid.dll
Report Id: f8edfc67-4524-4fed-b874-7378a901873a
Faulting package full name:
Faulting package-relative application ID:

Edit: Fixed, was one of my USB controller (more accurately, a blizz-box 4-play) plugged it that caused the crash.

[Shonumi]

The person you're trying to get a response from doesn't have an account here anymore, so it's unlikely you'll get any answers from them. Additionally, given the information in their last post here, it doesn't seem like there is a solution (at least on their end) that worked with a Bliss Box plugged in.

Due to our rules about necroposting and the fact that Blackened15 is no longer here, this thread will be closed. If you need further assistance, please consider making a separate thread and providing as much information as possible. Again, I'll reiterate that it looks like the only solution found thus far is to unplug the Bliss Box, which doesn't appear to be an option for you.