BSOD-After taking out bad hard drive and fresh install

Well,as you might know,for the past weeks I've been posting BSODs on my system with one Samsung HD and WD HD.

in the end,I got frustrated and took out the SAMSUNG HD,the only thing I did for disconnecting it was to unplug the SATA cables from it and the MOBO,leaving only the WD connected.

I did a fresh intall of W7 Ultimate 64b and download all the lastest drivers.

But again,got one of those "weird" things=

Today,when I cold booted it,the WELCOME screen was not at 1024x1028,it was at 800x600!

Restarted and fine,until I got BSOD=

ArgentineBoy said:

Well,as you might know,for the past weeks I've been posting BSODs on my system with one Samsung HD and WD HD.

in the end,I got frustrated and took out the SAMSUNG HD,the only thing I did for disconnecting it was to unplug the SATA cables from it and the MOBO,leaving only the WD connected.

I did a fresh intall of W7 Ultimate 64b and download all the lastest drivers.

But again,got one of those "weird" things=

Today,when I cold booted it,the WELCOME screen was not at 1024x1028,it was at 800x600!

Restarted and fine,until I got BSOD=

Easy and quick. Not at all un-expected. Your symantec caused this one.

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\022411-24336-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50
Debug session time: Thu Feb 24 15:17:50.478 2011 (GMT-5)
System Uptime: 0 days 0:01:17.914
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {fffff8a001e32820, 82000000d346f963, fffff88006d2ab50, 2}

Unable to load image \??\C:\Program Files (x86)\Common Files\Symantec Shared\EENGINE\EraserUtilRebootDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for EraserUtilRebootDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for EraserUtilRebootDrv.sys
Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
Probably caused by : EraserUtilRebootDrv.sys ( EraserUtilRebootDrv+1069c )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a001e32820, Virtual address for the attempted execute.
Arg2: 82000000d346f963, PTE contents.
Arg3: fffff88006d2ab50, (reserved)
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006d2ab50 -- (.trap 0xfffff88006d2ab50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88004053be0 rbx=0000000000000000 rcx=fffff88006d2ad90
rdx=fffff88004053be0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8a001e32820 rsp=fffff88006d2ace8 rbp=fffff880040721c0
 r8=0000000000000000  r9=0000000000000000 r10=fffffa80052c4d00
r11=fffff8a0085c6520 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff8a0`01e32820 43003a          add     byte ptr [r10],dil ds:fffffa80`052c4d00=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d3dbcf to fffff80002cbd740

STACK_TEXT:  
fffff880`06d2a9e8 fffff800`02d3dbcf : 00000000`000000fc fffff8a0`01e32820 82000000`d346f963 fffff880`06d2ab50 : nt!KeBugCheckEx
fffff880`06d2a9f0 fffff800`02cbb82e : 00000000`00000008 fffff8a0`001e4568 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x42497
fffff880`06d2ab50 fffff8a0`01e32820 : fffff880`0406169c fffff880`02ce8800 00000000`00000000 fffff8a0`00200fa0 : nt!KiPageFault+0x16e
fffff880`06d2ace8 fffff880`0406169c : fffff880`02ce8800 00000000`00000000 fffff8a0`00200fa0 fffff880`02cdab37 : 0xfffff8a0`01e32820
fffff880`06d2acf0 fffff880`02ce8800 : 00000000`00000000 fffff8a0`00200fa0 fffff880`02cdab37 00000000`00000000 : EraserUtilRebootDrv+0x1069c
fffff880`06d2acf8 00000000`00000000 : fffff8a0`00200fa0 fffff880`02cdab37 00000000`00000000 00000000`00000000 : SYMEVENT64x86+0x26800


STACK_COMMAND:  kb

FOLLOWUP_IP: 
EraserUtilRebootDrv+1069c
fffff880`0406169c ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  EraserUtilRebootDrv+1069c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: EraserUtilRebootDrv

IMAGE_NAME:  EraserUtilRebootDrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bf6fecd

FAILURE_BUCKET_ID:  X64_0xFC_EraserUtilRebootDrv+1069c

BUCKET_ID:  X64_0xFC_EraserUtilRebootDrv+1069c

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

2: kd> lmvm EraserUtilRebootDrv
start             end                 module name
fffff880`04051000 fffff880`04076000   EraserUtilRebootDrv T (no symbols)           
    Loaded symbol image file: EraserUtilRebootDrv.sys
    Image path: \??\C:\Program Files (x86)\Common Files\Symantec Shared\EENGINE\EraserUtilRebootDrv.sys
    Image name: EraserUtilRebootDrv.sys
    Timestamp:        Fri May 21 17:44:45 2010 (4BF6FECD)
    CheckSum:         00027545
    ImageSize:        00025000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Man,I just uninstalled it.Thanks for asnwering back

But hell,does everything causes a BSOD?

Not everything causes BSOD. Usually old drivers/faulty hardware are the most common one.

Ok,this is getting UBER annoying..

Today,after having launch,I went and turned on the PC...what happened?=
1-Half the screen was in a darker tone
2-AVAST Antivirus crashed at start
3-CCC (Catalyst) Center crashed at start
4-Tried to enter to mozilla and crashed

So I restarted the machine...
When I logon,EXPLORER.EXE crashed and there was no background image,only a dark screen.

I restared,the same...

I restarted for the 4th time...this time,everything went ok,now Im here.

Weirdest Thing?=There wasnt a single BSOD

Soooo.....From my mathematical thinking,I deduce that this stuff comes from a=
A-Faulty Power Supply Unit that's making everything fail.
B-Faulty SATA cord
C-Dust in the SATA cord and in the motherboard

Also,take a look at this image,this is when I boot up the computer....this cant be happening!

EDITownload WDCHECK and....damn,this obviously has to be the PSU or the SATA cords

Start your computer in Safe Mode with Networking (f8) to makes sure there is no malware or corrupt OS files on your computer.

Download Malwarebytes: Malwarebytes
Run couple of scans

Have Avast AV scan your computer for couple scans.

Run SFC /scannow Test

No spyware

Worse yet look at the image....this getting very,but very weird.

Ok people,So what remains as the guilty now? The PSU or the MOBO?

From looking at that pic, remove Daemon Tools. They are a known cause of BSOD with Windows 7. Use this SPTD uninstaller when DT is removed: DuplexSecure - Downloads
Select Uninstall; Do not select reinstall.

You may use MagicDisc as an alternative: Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

ok,and what about those strange startups and cold boots?


EDIT:When I instaled DEAMON TOOLS,the new version,it didnt install SPTD...

I would still uninstall Daemon Tools. If you need to mount .iso or Disc Image files, MagicDisc is a good alternative.

You will want to know what drivers/programs start up when you logon.