Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Months of system being fine, sudden multiple BSODs this morning


04 Jan 2013   #1

Windows 7 Home 64-bit
 
 
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

My System SpecsSystem Spec
.

04 Jan 2013   #2

Windows 7 Home 64-bit
 
 

EDIT: Here is the stop code:

***STOP: 0x000000F4
My System SpecsSystem Spec
04 Jan 2013   #3

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

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.
My System SpecsSystem Spec
.


04 Jan 2013   #4

Windows 7 Home 64-bit
 
 

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??
My System SpecsSystem Spec
04 Jan 2013   #5

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

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
My System SpecsSystem Spec
05 Jan 2013   #6

Windows 7 Home 64-bit
 
 

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.
My System SpecsSystem Spec
07 Jan 2013   #7

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

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.
My System SpecsSystem Spec
07 Jan 2013   #8

Windows 7 Home 64-bit
 
 

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.
My System SpecsSystem Spec
07 Jan 2013   #9

Windows 7 Home 64-bit
 
 
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.
My System SpecsSystem Spec
08 Jan 2013   #10

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

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.
My System SpecsSystem Spec
Reply

 Months of system being fine, sudden multiple BSODs this morning




Thread Tools



Similar help and support threads for2: Months of system being fine, sudden multiple BSODs this morning
Thread Forum
Solved Multiple BSODs over the last few months system service exception or me BSOD Help and Support
Multiple BSODs after booting from hibernation in morning BSOD Help and Support
BSOD all of a sudden after 3 months after installing Windows 7, 0x124 BSOD Help and Support
Solved multiple OS installs on both HDD & SSD over 6 months...still BSODs BSOD Help and Support
Multiple BSODs in the last couple of months BSOD Help and Support
sudden "operating system not found" (but reboot is fine!) BSOD Help and Support
No printers? Really? Been working fine for months! Hardware & Devices

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:25 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33