Getting BSOD very often lately on Windows 7!
Started by
sour11
, Feb 02 2013 03:57 AM
#91
Posted 07 August 2013 - 01:16 PM
#92
Posted 07 August 2013 - 01:54 PM
OK so now we go through the testing again for another day.
#93
Posted 07 August 2013 - 03:04 PM
OK so now we go through the testing again for another day.
So far no BSODs, lets hope it lasts!
#94
Posted 19 August 2013 - 10:20 PM
Well after two weeks with no BSODs, I just got one . I was just thinking earlier how its been so long since I've gotten one, go figure. I was doing the usual browsing on youtube. At least this one seems to be straightforward. I didn't install anything new latley, so that PACE Anti-Piracy, Inc. Interlok has been there while the other BSOD's were happening. Weird that it just started messing up now. I won't do anything until I get a reply from you weather I should uninstall anything or not!
BlueScreenView Log:
==================================================
Dump File : 082013-19952-01.dmp
Crash Time : 8/20/2013 12:14:40 AM
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`000000f6
Parameter 2 : 00000000`00000244
Parameter 3 : fffffa80`07c9fb30
Parameter 4 : fffff880`014e4072
Caused By Driver : Tpkd.sys
Caused By Address : Tpkd.sys+6072
File Description : InterLok system file
Product Name : InterLok®
Company : PACE Anti-Piracy, Inc.
File Version : 5.3.2.2374
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082013-19952-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 266,320
==================================================
WhoCrashed Log:
On Tue 8/20/2013 4:12:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082013-19952-01.dmp
This was probably caused by the following module: tpkd.sys (Tpkd+0x6072)
Bugcheck code: 0xC4 (0xF6, 0x244, 0xFFFFFA8007C9FB30, 0xFFFFF880014E4072)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\tpkd.sys
product: InterLok®
company: PACE Anti-Piracy, Inc.
description: 64bit Tpkd Device Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: tpkd.sys (64bit Tpkd Device Driver, PACE Anti-Piracy, Inc.).
Google query: PACE Anti-Piracy, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION
On Tue 8/20/2013 4:12:24 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tpkd.sys (Tpkd+0x6072)
Bugcheck code: 0xC4 (0xF6, 0x244, 0xFFFFFA8007C9FB30, 0xFFFFF880014E4072)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\tpkd.sys
product: InterLok®
company: PACE Anti-Piracy, Inc.
description: 64bit Tpkd Device Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: tpkd.sys (64bit Tpkd Device Driver, PACE Anti-Piracy, Inc.).
Google query: PACE Anti-Piracy, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION
Conclusion
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
tpkd.sys (64bit Tpkd Device Driver, PACE Anti-Piracy, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
BlueScreenView Log:
==================================================
Dump File : 082013-19952-01.dmp
Crash Time : 8/20/2013 12:14:40 AM
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`000000f6
Parameter 2 : 00000000`00000244
Parameter 3 : fffffa80`07c9fb30
Parameter 4 : fffff880`014e4072
Caused By Driver : Tpkd.sys
Caused By Address : Tpkd.sys+6072
File Description : InterLok system file
Product Name : InterLok®
Company : PACE Anti-Piracy, Inc.
File Version : 5.3.2.2374
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082013-19952-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 266,320
==================================================
WhoCrashed Log:
On Tue 8/20/2013 4:12:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082013-19952-01.dmp
This was probably caused by the following module: tpkd.sys (Tpkd+0x6072)
Bugcheck code: 0xC4 (0xF6, 0x244, 0xFFFFFA8007C9FB30, 0xFFFFF880014E4072)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\tpkd.sys
product: InterLok®
company: PACE Anti-Piracy, Inc.
description: 64bit Tpkd Device Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: tpkd.sys (64bit Tpkd Device Driver, PACE Anti-Piracy, Inc.).
Google query: PACE Anti-Piracy, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION
On Tue 8/20/2013 4:12:24 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tpkd.sys (Tpkd+0x6072)
Bugcheck code: 0xC4 (0xF6, 0x244, 0xFFFFFA8007C9FB30, 0xFFFFF880014E4072)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\tpkd.sys
product: InterLok®
company: PACE Anti-Piracy, Inc.
description: 64bit Tpkd Device Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: tpkd.sys (64bit Tpkd Device Driver, PACE Anti-Piracy, Inc.).
Google query: PACE Anti-Piracy, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION
Conclusion
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
tpkd.sys (64bit Tpkd Device Driver, PACE Anti-Piracy, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Edited by sour11, 19 August 2013 - 10:23 PM.
#95
Posted 20 August 2013 - 02:04 AM
I would look and see if there is a update for this program or you may have to uninstall and reinstall to correct the issue.
#96
Posted 20 August 2013 - 06:24 AM
No update but I really think that it might of been a one time thing since this comes from a program I use very often. If it happens again I will uninstall it and report back to you!
#97
Posted 20 August 2013 - 07:02 AM
It may have been a fluke and I agree it may not happen again.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users