Multiple BSOD after power outage w/ music CD in DVD drive ntoskrnl.exe

About a year ago, I had a music CD in my DVD Rom drive and there was a power outage. This caused the computer to shut down improperly. Upon start up, I was greeted with a message to place a disk in the boot drive to boot the computer. The only way I was able to boot the computer was to press F10 upon start up and arrow over to the boot menu and tell it to boot from the HDD.

Soon after I started getting BSOD screens as soon as I logged in to windows. I could sit on the desktop for a few minutes without anything happening, but as soon as I clicked any desktop icon, the computer would crash and restart.

I did everything I could and ran Start up Repair, which could not fix the start up files. Frustrated, I went into safe mode, pulled all my files off and put them on a flash drive. I turned the computer off and left it off for almost a year, while contemplating taking it to a repair shop. That never happened, our computer tech guy changed locations. We thought about taking it to Staples to see if they could fix it.

I ended up re-installing Windows 7, back in June. This did not fix the boot issue. I still have to press F10 every time I start the computer. Start up repair was ran again and found nothing to fix. It fixed the BSOD errors and I was able to use the computer the normally. Until July when the computer crashed again.

I have ran CHKDSK countless times. It either found no errors or fixed a few bad clusters.

I have ran the Memory Diagnostics Tool, it came back without errors.

I am now back to point where the computer crashes as soon as I try to do anything.

I've been using WhoCrashed to see what is causing the errors. The Analysis is below. Two of them happened while the computer was hibernating, I believe they are the August entries. Somehow the computer lost 2 crash entries that occurred this morning, when I was browsing the Internet.

All the info from the SF Diagnostic Tool is attached below.

WhoCrashed


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: MICKEY
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: p6610f, Hewlett-Packard, FOXCONN, 2AB1
CPU: AuthenticAMD AMD Athlon(tm) II X4 635 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4025782272 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 9/19/2014 2:37:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091914-42463-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA800371D7C8, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 9/19/2014 2:05:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091914-21122-01.dmp
This was probably caused by the following module: usbfilter.sys (0xFFFFF88004E5A1AA)
Bugcheck code: 0xD5 (0xFFFFF980321DAE40, 0x0, 0xFFFFF88004E5A1AA, 0x0)
Error: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
file path: C:\Windows\system32\drivers\usbfilter.sys
product: AMD USB Filter Driver
company: Advanced Micro Devices
description: AMD USB Filter Driver
Bug check description: This indicates that a driver has referenced memory which was earlier freed.
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: usbfilter.sys (AMD USB Filter Driver, Advanced Micro Devices).
Google query: Advanced Micro Devices DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL



On Sun 9/14/2014 1:40:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091414-27378-01.dmp
This was probably caused by the following module: sftfslh.sys (Sftfslh+0xBB088)
Bugcheck code: 0x7A (0xFFFFF6FC400396C8, 0xFFFFFFFFC000009D, 0x147D6860, 0xFFFFF880072D9088)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\sftfslh.sys
product: Microsoft Application Virtualization
company: Microsoft Corporation
description: Microsoft Application Virtualization File System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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.
Google query: Microsoft Corporation KERNEL_DATA_INPAGE_ERROR



On Thu 8/28/2014 5:46:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082814-239258-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80063327C8, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 8/21/2014 12:34:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082014-27721-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA0 (0x9, 0xFFFFFFFFC0000001, 0x1, 0x0)
Error: INTERNAL_POWER_ERROR
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 power policy manager experienced a fatal error.
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 Fri 7/25/2014 3:23:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072514-28392-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA0 (0x9, 0xFFFFFFFFC0000001, 0x1, 0x0)
Error: INTERNAL_POWER_ERROR
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 power policy manager experienced a fatal error.
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. 2 third party drivers have 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:

sftfslh.sys (Microsoft Application Virtualization File System, Microsoft Corporation)
usbfilter.sys (AMD USB Filter Driver, Advanced Micro Devices)

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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.




The USBfilter.sys crash occurred while running Driver Identifier before the computer got to the start up screen.

The most recent ntoskrnl.exe crash also happened while Driver Identifier was running.

The WhoCrashed report says drivers are responsible for the crashes. I am lost when it comes to finding the correct driver updates.

Driver Identifier will NOT turn off. Says no settings were changed or something to that effect. I am in Safe Mode.

EDIT: Crashed while writing this post. I need to get new a new SF zip file.