Months of system being fine, sudden multiple BSODs this morning

Howdy all! I was here in the past a while ago with getting semi-frequent BSODs on boot after the splash and login screen. The issue I found was a loose power connector. I snugged it in place, and then my system is fine for many months (maybe four or five). Now this morning, I had quite a few BSODs after the splash screen and logging onto my computer. I was finally able to get a successful boot after many attempts. I checked power connections, tried to make the connections secure, yet still got BSODs. Dump is attached. You guys are awesome. Thanks!
***STOP: 0x000000F4

Ok after looking through your crash dumps and after looking back at the last thread you started it seems that most of the dumps are the exat same error as last time you posted here:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008bb0b30, fffffa8008bb0e10, fffff800031d1460}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

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

However one of your dumps cited a different program as the cause:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008bddb30, fffffa8008bdde10, fffff800031db460}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

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

Claiming that it had an I/o error

Code:

EXCEPTION_CODE:  (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at  0x%p. The required data was not placed into memory because of an I/O  error status of 0x%x.

But there was one dump that blamed you Atheros network adapter driver:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 0, fffff880014a9566}

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+84ae7 )

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

Looking at the driver its self it is very old

Code:

fffff880`06e02000 fffff880`06f71000   athrx    athrx.sys   
    Loaded symbol image file: athrx.sys
    Symbol file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Timestamp:        Tue Jun 23 20:37:01 2009 (4A41752D)
    CheckSum:         00172E8E
    ImageSize:        0016F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would advise updating the driver either from your computer manufacturers website, or from this link to the Atheros website.

Looking at your dumps a second time I noticed a driver related to Daemon tools which has been known to cause BSODs Try following this tutorial you can skip part A of step 2 if you have already uninstalled the program:

Drivers - clean leftover files after uninstalling

Post back your results

It looks like for what ever reason the driver is not showing up in driver sweeper but i also noticed that you don't seem to have the SPTD.sys installed which leads me to believe that it is not what is causing the problem. Instead i would like you to enable Driver Verifier.

Diver Verifier - Enable and Disable

If you can not boot into your PC once it is enabled try booting into safe mode and then disabling it then post back your new crash dumps once you get the blue screen.

Edit:
You may want to also try using this program, download it and run the executable if the uninstall button is greyed out and you can not click on it then the Daemon tools drivers have been successfully uninstalled. DO NOT click on this install button it will re-install the problematic drivers.

I realize I already have a thread here for a BSOD, but I just encountered another, completely unrelated one. Attached is the dump. Whenever I try loading Pro Tools, BSOD appears. I haven't been able to use this program for a while due to not having my pre-amp working. Just got it back from being repaired, so first time I am powering it up while connected to machine is causing it.

Ok after looking over both of your new crash dumps the first set seem to be caused by diginet.sys:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff9800305ef90, fffff9800305effc, 814074, 24}

*** WARNING: Unable to verify timestamp for diginet.sys
*** ERROR: Module load completed but symbols could not be loaded for diginet.sys
Probably caused by : diginet.sys ( diginet+1525 )

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

which is part of the Avid technology pro programs, I would try first updating the driver from here if the Blue screen persists you may simply want to do a clean install of the program.

Now the new set of BSODs that you are getting are being caused by Tpkd.sys:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 93, {ffffffff7fffffff, fffff8a000001910, 0, 1}

*** WARNING: Unable to verify timestamp for Tpkd.sys
*** ERROR: Module load completed but symbols could not be loaded for Tpkd.sys
Probably caused by : Tpkd.sys ( Tpkd+6082 )

Followup: MachineOwner

which is part of PACE anti-piracy software, the drivers to updates this can be found here.