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.
Hi,
There are no dump files in your upload.
Please reconfigure windows to collect the correct info.
You want small memory dumps - "MiniDumps"
https://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
And here are the instructions for posting:
TipEnsure you click the "GRAB ALL" button and then wait for each window to appear in turn and then click OK
Cheers
Dave
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.
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.
Hi,
Thanks for the added info.
Firstly please remove Alcohol 120% and Superantispyware from your system.
From your dump files:
The analysis has not shown the faulting driver name, however the following*******************************************************************************
* *
* 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
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:
WarningIf 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)
See if this has stopped the BSOD's?
Post back any results/observations
Cheers
Dave
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
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).
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
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.
Last edited by ZomBob; 04 Apr 2013 at 16:10. Reason: no attachment
Quote