Invoking SSL Audio Plugin in Pro Tools causes BSOD

pginther · 06 Nov 2012

I just purchased a new audio plug in from Solid State Logic for my Pro Tools recording software. Every time I try to activate that plugin on an audio channel I immediately get BSOD. Checked with the vendor (SSL) and they indicated that the contents of the minidump was too generic to point to a specific problem but they think there could be some type of hardware conflict. I'm hoping someone on the forums can help me out as I have no experience analyzing these dump files. Any assistance would be greatly appreciated. I am running the system on a Sony VAIO VPCEB26GM with a Core i5 processor and 8 gig of ram. Windows 7 Professional SP1. Files are attached.

Thank you!!

Arc · 07 Nov 2012

Hello pginther.

It is caused by PACE Anti-Piracy InterLok software.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff888010ac830, 0, fffff88001098a25, 5}

*** WARNING: Unable to verify timestamp for Tpkd.sys
*** ERROR: Module load completed but symbols could not be loaded for Tpkd.sys

Could not read faulting driver name
Probably caused by : Tpkd.sys ( Tpkd+2a25 )

Followup: MachineOwner
---------

And it is very old.

Code:

lmvm Tpkd
start             end                 module name
fffff880`01096000 fffff880`010b9000   Tpkd     T (no symbols)           
    Loaded symbol image file: Tpkd.sys
    Image path: \SystemRoot\System32\Drivers\Tpkd.sys
    Image name: Tpkd.sys
    Timestamp:        Thu Dec 24 01:02:16 2009 (4B327040)
    CheckSum:         000287EA
    ImageSize:        00023000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Support.

Let us know the results.

pginther · 07 Nov 2012

Got it in one! Fantastic job!! You pointed me to the correct solution and saved me $200.

Thanks for all your help.

Paul