BSOD randomly few hours/days error 0x0000000000/ 0x00000000008 etc.

[ZomBob]

Hello all,

I am looking for help on this issue. I have tried everything I can think and nothing works. This computer has crashed basically out of the box. I have attempted to uninstall OBE00 which was apparently an issue with Windows defender and AMD as well as turning off TCP drivers. If anyone can llok through my dump files and help me I would greatly appreciate it.

 

[Northernsoul55]

Hi,

There are no dump files in your upload.

Please reconfigure windows to collect the correct info.
You want small memory dumps - "MiniDumps"

:ar:http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

And here are the instructions for posting:

:ar: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

   Tip

Ensure you click the "GRAB ALL" button and then wait for each window to appear in turn and then click OK

Cheers

Dave

 

[ZomBob]

Okay, what happened was I was attempting to see this dump myself and moved it to the desktop temporarily in order to find it quick....this means your program didn't grab it. I returned the file to the minidump location and am rerunning the tool in its entirety to grab all pertinent files. These are attached. Thanks again for any help you can give.

 

[ZomBob]

Okay so quick update...I now installed Asus AI suite II because a few forums stated that I needed to do an update. Not sure if this matters but just wanted to keep the situation up to date. Once again thanks for any help that comes this way.

 

[Northernsoul55]

Hi,
Thanks for the added info.
Firstly please remove Alcohol 120% and Superantispyware from your system.

From your dump files:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck CF, {fffff960006c768f, 8, fffff960006c768f, 0}

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4518f )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE (cf)
Arguments:
Arg1: fffff960006c768f, memory referenced
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation
Arg3: fffff960006c768f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, Mm internal code.
A driver has been incorrectly ported to Terminal Server. It is referencing
session space addresses from the system process context. Probably from
queueing an item to a system worker thread.
The broken driver's name is displayed on the screen.
Debugging Details:
------------------

Could not read faulting driver name

The analysis has not shown the faulting driver name, however the following
driver is known for BSOD's and is a part of Daemon tools and is installed on your computer:

sptd sptd.sys Sat Mar 03 16:45:52 2012

Go here and remove the SPTD driver itself with this tool:

:ar: http://www.duplexsecure.com/en/downloads

   Warning

If the uninstall button is grayed out when you run the program you dont need to do anything and can close the window, if it is not click it and allow it to run. DO NOT click the install button as it will install a driver known to cause BSODs onto your system.

Otherwise, go to C:\Windows\System32\drivers, look for and delete SPTD.sys manually. Reboot

Run SFC to check the integrity of all Windows 7 system files:

Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
Type SFC /scannow at the prompt
(Note: there is a space between SFC and /scannow)
:ar: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

See if this has stopped the BSOD's?
Post back any results/observations
Cheers
Dave

 

[ZomBob]

Thanks Dave! I have removed the offending programs per your instructions and manually deleted the above mentioned driver. Then restarted and am running sfc /scannow. I will leave this thread open for a few days and check eventviewer to see if these problems are corrected. If so I will mark as solved if not I will post new logs, etc.

Thanks for taking the time to help me out here....I didn't have these problems with XP man.

ZB

 

[Northernsoul55]

No problem, glad to help.

Look forward to your feedback.

Cheers

Dave

 

[ZomBob]

Update: sfc finished...no errors.

I would like to clarify what steps I took before posting here:

1) Appeared to be a Windows defender issue thanks to event viewer. Searched those errors and found that a bad/corrupted/borked install can cause instability. Found fix was to delete the offending file which defender will reproduce upon startup....worked for like a week. File for me was found at

c:/programdata/microsoft/microsoft security client/support>EppOobe.etl

I had previously attempted to completely uninstall windows security and defender but this didnt work. reinstalled and updated defender and security client and still no help.


2) Found a recurring TCP/IP error (??). Apparently this is linked to the Atheros wireless drivers. Did an uninstall/reinstall from file download and took off TCP/IPv6 which may or may not have fixed that recurring timeout issue (something about the system trying ports over and over).

 

[Northernsoul55]

Hi ZB,

Good news on the SFC and thanks for the feedback.
Give it a few days to see if you issue is completely resolved, then please pop back and
mark the thread as solved if you feel it is.

Cheers

Dave

 

[ZomBob]

Okay so came home today and computer wouldn't wake up. Hard restart and it had crashed. still seems to be something to do with win defender. I have posted new logs below.

 

[ZomBob]

Just a thought...i use a USB mouse and keyboard. Could it be that the comp isn't crashing and the comp just won't wake up do to a USB issue? Thoughts? Not really stressing this just spit balling at this point. Any help or general discussion welcome as long as it's thread relevant. I'm willing to experiment here people!

 

[Northernsoul55]

Sorry those are the same logs you posted before dated 31/3/2013

Please post the latest one.

If you feel there is a USB issue, you can try following this tutorial:

:ar: http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html

cheers

Dave

 

[ZomBob]

There isn't a latest one....that's it. Not sure what's going on.

 

[Northernsoul55]

You may have to wait for another BSOD, then post back the new logs.

Cheers

Dave

 

[ZomBob]

Okay so came home and mouse wouldn't wake computer. Hit Shift twice and it woke up but looked to be about to crash. Here's the scene:
1) Wallpaper=gone
2) White background
3) oversized icons
4) No start orb but Windows start button in upper left hand of screen
5) Click icons = no response
6) CTRL+ALT+DEL = no response

Eventually I just did a hard restart on the machine and it booted to standard "Windows shut down unexpectedly" screen. I booted normal and nothing. Also didn't post a minidump so no point in rerunning tool. Any thoughts? Could it be that my RAM is bad? I have heard this is sometimes the case.

 

[ZomBob]

Realize previous post could be ambiguous...when I restarted it booted normal. Also ran memtest 86+ for one pass and no errors detected. Ran chkdsk no errors detected....so hdd and ram okay. SFC scannow no found no errors. Could it be the MB or a bad win install? Any and all suggestions welcome.

 

[Northernsoul55]

Hi ZB,

You want to run Memtest for more than 1 pass:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight

When you boot into safe-mode does your issue still remain?
:ar: http://www.sevenforums.com/tutorials/69585-safe-mode.html

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours, it will make the system a bit slow and laggy, which is to be expected:

:ar: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Before enabling DV, ensure that you create a System restore point.

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Please uninstal CDisplay from your system.

Post back any resulting BSOD from DV/ any observations.

Cheers
Dave