0x7a and 0xF4 BSOD

Thedoctor44 said:

Did this latest BSOD happen before or after Norton's removal?

It happen before I uninstalled Norton.

Okay, see how it goes from now on after Norton has been uninstalled.

Thedoctor44 said:

Okay, see how it goes from now on after Norton has been uninstalled.

Just had a 0x7A
Attachment 321555

And here is the kernel dump.
http://1drv.ms/1qF90Xq

TehEspada said:

Thedoctor44 said:

Okay, see how it goes from now on after Norton has been uninstalled.

Just had a 0x7A
Attachment 321555

And here is the kernel dump.
http://1drv.ms/1qF90Xq

And 2 more, had another 0xF4 too so I don't think it was norton.

Attachment 321914

arc said:

is there any specific reason that you are reluctant to supply all the necessary data to troubleshoot your issue?

Asking for the third time. Click on the button below ....



it will download the dm log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

dont edit or alter the zip ... Upload it as it is.

Attachment 322073

Arc said:

The two latest crash dumps of yesterday are Norton caused network blockage.

Code:

BugCheck A, {0, 2, 1, fffff800030cec3f}

*** WARNING: Unable to verify timestamp for SYMNETS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS
Probably caused by : NETIO.SYS ( NETIO!WfpExpireEntryLru+17 )

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

Description here: Driver Reference Table - SYMNETS.SYS

So, Norton is not properly removed, and it is still contributing to the BSODs. Removal of notron is highly needed, because it is necessary to see the situation without the File System Filter eeCtrl.sys. It is around all the stop 0xF4 events.

Yesterday's rest 3 BSODs are stop 0xF4 and 0x7A. Disc corruption is directly blamed.

Code:

3756 errors : !Ntfs (fffff88001736000-fffff88001736fff)

Code:

DISK_HARDWARE_ERROR: There was error with disk hardware

You are saying that you ran WD data lifeguard which did not detect any error? You are suggested to run the quick test and the extended test once again.

Reseat the sata and power.

• 

Also make it sure that the HDD is fixed fine, there are no loose screws holding the HDD.

Apply the SATA cable to an unused port on the motherboard. Change the cable to a new one if possible.



Let us know the results.

The hard drive test passed again, I did change the sata cable and used different port on the motherboard.

Also the SATA cable doesn't lock into place in the hard drive, it's very loose. Not sure if it should lock or not, just thought you should know.