Share via

Driver Verifier issue - Tpkd.sys

Anonymous
2015-05-01T06:16:28+00:00

I have been  getting random BSOD's with hal.dll and IRQL_NOT_LESS_OR_EQUAL notifications with the Bluescreen program and Who's Crashed.

I then tried the Driver Verification Tool and it consistently crashed with Tpkd.sys driver.

It is associated with the PACE Ilok protection system and crashes when I load a specific music plugin that has its license on a usb Ilok dongle.

I have yet to hear from  Ilok/Pace regarding their driver (it is their latest) but I am wondering if there is anything that can be done about this other than not using the driver. This music plugin requires the Ilok usb dongle so it would be a problem not being able to use the software because of this.

I have had it for a few years and it never created problems before.

I have a I7  Win 7 Premium 64 bit system and Asus P8P67 motherboard.

Thanks for any help.

Mike

This is the read out from Bluescreen:

==================================================

Dump File         : 043015-25880-01.dmp

Crash Time        : 4/30/2015 8:44:22 PM

Bug Check String  : DRIVER_VERIFIER_DETECTED_VIOLATION

Bug Check Code    : 0x000000c4

Parameter 1       : 00000000`000000f6

Parameter 2       : 00000000`0000019c

Parameter 3       : fffffa80`0bd90a70

Parameter 4       : fffff880`01d8d082

Caused By Driver  : Tpkd.sys

Caused By Address : Tpkd.sys+6082

File Description  :

Product Name      :

Company           :

File Version      :

Processor         : x64

Crash Address     : ntoskrnl.exe+72a40

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Full Path         : C:\Windows\Minidump\043015-25880-01.dmp

Processors Count  : 8

Major Version     : 15

Minor Version     : 7601

Dump File Size    : 262,144

Dump File Time    : 4/30/2015 8:46:08 PM

==================================================

This  is from Who Crashed:

On Fri 5/1/2015 3:44:22 AM GMT your computer crashed

crash dump file: C:\Windows\Minidump\043015-25880-01.dmp

This was probably caused by the following module: tpkd.sys (Tpkd+0x6082)

Bugcheck code: 0xC4 (0xF6, 0x19C, 0xFFFFFA800BD90A70, 0xFFFFF88001D8D082)

Error: DRIVER_VERIFIER_DETECTED_VIOLATION

file path: C:\Windows\system32\drivers\tpkd.sys

product: InterLok(R)

company: PACE Anti-Piracy, Inc.

description: 64bit Tpkd Device Driver

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2015-05-02T01:41:22+00:00

Mike

The full DMP was more informative.  TPKD was loaded without problem. VSTBridgeapp was obviously removed.

It appears that this driver caused an immediate crash. hdsp_64.sys Hammerfall DSP from RME  It is dated Feb 2015

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

Answer accepted by question author

Anonymous
2015-05-02T02:24:58+00:00

So now that I have diabled the VSTbridgeapp.exe the Tpkd.sys should not be an issue.

I guess I'll  wait to see if the the RME audio causes problems.

I am glad I found out about this Driver Verification program or I would have been pulling my hair out for days.

The RME driver is updated pretty regularly although that is what can cause all the issues I guess.

Update one thing and then something else doesn't work.

Thanks for your help.

Mike

Was this answer helpful?

0 comments No comments

7 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-05-01T16:22:58+00:00

    Mike

    VSTBridgeApp.exe is calling tpkd.sys in a way that corrupts the system.  If you want a deeper analysis we need a full memory DMP which would be located in C"\windows and would be called MEMORY.DMP

    The Tpkd.sys driver is circa 2012 and I wonder if re-installing the software in compatibility mode mightn't fix the issue

    To install in compatibility mode do the following:

    Right click the installer>properties>compatibility>choose OS

    http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows?SignedIn=1

    http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows?SignedIn=1

    (works in vista, win 7, win 8, and win 10)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-05-01T15:59:59+00:00

    Hi,

    Here are the MSinfo and Minidump files:

    https://onedrive.live.com/redir?resid=cda3748fdce3c7fc%215724

    Thanks for the help

    Mike

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-05-01T10:17:14+00:00

    ****We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.



    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here

    If you have any questions about the procedure please ask

    Was this answer helpful?

    0 comments No comments