Frequent BSOD after installing Alcohol 120

[Wulfy]

The very moment I installed Alcohol and its virtual drive, I got a BSOD, and they have been frequent since then.

I have managed to remove the program and the file SPTD.sys -- and updated all of my outdated drivers -- yet the problem persists. Sometimes when it crashes the HDD 'vanishes' and I have to wait a moment before it becomes available again.

I don't have a minidump at the moment because it crashes before I can even get to the file, but I do have this from WhoCrashed :

System Information (local)

computer name: ZILLA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) CPU G6951 @ 2.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6231785472 total
VM: 2147352576, free: 1974898688



Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 9/24/2013 11:20:32 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x73B73491) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009BD2B30, 0xFFFFFA8009BD2E10, 0xFFFFF800031840D0)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
A third party driver was identified as the probable root cause of this system error. 
Google query: CRITICAL_OBJECT_TERMINATION



On Fri 7/26/2013 7:46:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072613-26176-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA800ADAD038, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Fri 5/10/2013 7:50:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051013-19843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880) 
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E7180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sat 4/27/2013 11:23:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042713-51807-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880) 
Bugcheck code: 0x74 (0x2, 0xFFFFF880030DFB20, 0x2, 0xFFFFFFFFC000014D)
Error: BAD_SYSTEM_CONFIG_INFO
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that there is an error in the registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sun 3/24/2013 3:49:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032313-33961-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600) 
Bugcheck code: 0x9F (0x3, 0xFFFFFA80093B0A00, 0xFFFFF80000B9C518, 0xFFFFFA8009A97150)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[AmericanPharaoh]

Use "System Restore" to go back to the time before installing Alcohol 120.

http://www.sevenforums.com/tutorials/700-system-restore.html

 

[Wulfy]

That was one of the first things I tried, it didn't work.

 

[AmericanPharaoh]

Ok, you didn't mention earlier you had tried to Restore.

I'd imagine the next step is repair install.

http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[Wulfy]

I managed to get the minidump :