Solved Months of system being fine, sudden multiple BSODs this morning

[Merocor]

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

 

[Merocor]

EDIT: Here is the stop code:

***STOP: 0x000000F4

 

[Dsprague]

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:

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

Use !analyze -v to get detailed debugging information.

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

----- ETW minidump data unavailable-----
[COLOR=Red]Probably caused by : wininit.exe
[/COLOR]
Followup: MachineOwner
---------

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

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

Use !analyze -v to get detailed debugging information.

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

----- ETW minidump data unavailable-----
[COLOR=Red]Probably caused by : csrss.exe
[/COLOR]
Followup: MachineOwner
---------

Claiming that it had an I/o error

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:

*******************************************************************************
*                                                                             *
*                        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
[COLOR=Red]Probably caused by : athrx.sys[/COLOR] ( athrx+84ae7 )

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

Looking at the driver its self it is very old

fffff880`06e02000 fffff880`06f71000   athrx    athrx.sys   
    Loaded symbol image file: athrx.sys
    Symbol file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    [COLOR=Red]Timestamp:        Tue Jun 23 20:37:01 2009[/COLOR] (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.

 

[Merocor]

Just updated driver, tried a restart and got myself one BSOD before a successful boot.

I haven't updated anything recently, so I'm afraid if the codes are still the same from last time I had this problem, then my original problem is not fixed. Any thoughts??

 

[Dsprague]

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

 

[Merocor]

Well Im Looking at the list of drivers, and I can't pinpoint which one is used for Daemon. I know I tried using it as a virtual drive once, but that's it... I've attached a screenshot of the list I'm given once I open DriveSweeper.

 

[Dsprague]

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.

 

[Merocor]

Once you mentioned Daemon tools might be the cause, I uninstalled the program, so maybe that's why the driver's not showing up in the list?

I have dome all the steps. Followed the directions in the link for Driver Verifier, and on restart could not even get to splash screen for logging in. Rebooted to Safe mode, and in Verifier selected Standard settings for all unsigned drivers. The only driver on that list: Vclone.sys, or VirtualClone CD Driver. Reboot with new settings was successful. attached is my dump from the BSOD.

FROM EDIT: Ran the SPTD program, uninstall button was greyed out. I Do not have the driver I guess.

 

[Merocor]

BSOD as Pro Tools loads

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.

 

[Dsprague]

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

*******************************************************************************
*                                                                             *
*                        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
[COLOR=Red]Probably caused by : diginet.sys[/COLOR] ( 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:

*******************************************************************************
*                                                                             *
*                        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
[COLOR=Red]Probably caused by : Tpkd.sys[/COLOR] ( Tpkd+6082 )

Followup: MachineOwner

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

 

[Merocor]

I have updated both drivers. Tried loading Pro Tools again with Mbox mini plugged in, still BSOD. attached is the new dump. I'm going to do some more research on my end to see if maybe I can't load while the Mbox is plugged in?

 

[Dsprague]

My other thought would be completely removing the avid software and then trying to re-install it because the diginet.sys driver doesnt seem to be causing the problem any more its just the anti-piracy software that seems to be acting up, perhaps a fresh install of the program will help.

 

[Merocor]

Alright. Updated both drivers to latest releases. Still getting BSOD on loading of Pro Tools. Uninstalled Pro Tools entirely and re-installed it, still getting BSOD. Also got another BSOD on startup of machine. Attached is the most recent dump file, hopefully something new is in here.

I honestly cannot remember what I did to cause all of this with my Pro Tools except try loading it up with my pre-amp plugged in. Ever since, I can't even start it up without my pre-amp attached...

Unless you're able to find anything new, I think I'm just going to call Avid tech support. Perhaps they've seen this before.

 

[Dsprague]

Unfortunately the dumps are still blaming the Tpkd.sys I think speaking to the Avid Tech support would be best because the Driver causing the BSOD is prat of their anti-piracy software that seems to be causing the problem.

 

[Merocor]

Okay. I was on the phone with tech support for almost two hours. We tried uninstalling, reinstalling, the whole shebang. Nothing worked. He didn't think it was caused by the pace software because of the point it was crashing in the load-up(it had already been approved by the iLok).
I might still have Driver Verifier enabled, I'll double check that. Did some searching, enabled DEP and now my system doesn't crash anymore with ProTools. Instead, the program just closes because it cannot open. It gets stuck on the plugin screen, so I might try uninstalling all those or disabling them. Thoughts??

 

[Dsprague]

If they are reliably crashing every time you use them it sounds like then uninstalling or disabling would be a good idea as they will only be taking up space on your hard drive and not be getting used.

 

[Merocor]

FIXED! I honestly am not sure how, but here's what I did.

Noticed there was an update to Protools (10.3.3). Downloaded it. Disabled DEP because Pro Tools requires it to at least be disabled to run. However everything I read suggests that 64-bit systems cannot disable DEP. Tried it anyways through command line. Restarted machine, opened Pro Tools like a champ! Thanks for all the support!!

 

[Dsprague]

your very welcome and I am glad you got your problem solved.