[Win7SP1 x64] Issues with avast and the Windows media player having corrupt manifests

Re: Issues with avast and the windows media player having corrupt manifests

It does not restart unepectedly. It may have given me 2 - 3 bluescreens in the last month.
 
Re: Issues with avast and the windows media player having corrupt manifests

after 30 seconds the response is: Test result: completed with unknown failure. Check the self test log for more information.
 
Re: Issues with avast and the windows media player having corrupt manifests

Here are the results from the file FUJITSU_MHY2250BH_K432T8328L7H_2016-08-15.txt

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)-sp1] (sf-5.43-1)
Copyright (C) 2002-12 by Bruce Allen, smartmontools


=== START OF INFORMATION SECTION ===
Model Family: Fujitsu MHY BH
Device Model: FUJITSU MHY2250BH
Serial Number: K432T8328L7H
LU WWN Device Id: 5 00000e 041c22cd1
Firmware Version: 0085000B
User Capacity: 250,059,350,016 bytes [250 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 3f
Local Time is: Mon Aug 15 20:27:25 2016 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.


General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 73) The previous self-test completed having
a test element that failed and the test
element that failed is not known.
Total time to complete Offline
data collection: ( 1009) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 143) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.


SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 037 046 Pre-fail Always In_the_past 17982
3 Spin_Up_Time 0x0003 100 100 025 Pre-fail Always - 1
4 Start_Stop_Count 0x0032 094 094 000 Old_age Always - 130629
5 Reallocated_Sector_Ct 0x0033 075 075 024 Pre-fail Always - 882 (1391 609)
9 Power_On_Hours 0x0032 045 045 000 Old_age Always - 1654023
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3942
191 G-Sense_Error_Rate 0x0012 100 100 000 Old_age Always - 576
192 Power-Off_Retract_Count 0x0032 098 098 000 Old_age Always - 669
194 Temperature_Celsius 0x0022 100 075 000 Old_age Always - 42 (Min/Max 15/65)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 40242 (0 23)
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 22099760906244
198 Offline_Uncorrectable 0x0032 100 100 000 Old_age Always - 193967929294852
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 269193221
200 Multi_Zone_Error_Rate 0x0032 100 100 000 Old_age Always - 986257272


SMART Error Log Version: 1
Warning: ATA error count 65535 inconsistent with error log pointer 2


ATA Error Count: 65535 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.


Error 65535 occurred at disk power-on lifetime: 27566 hours (1148 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 0b c8 ad 2c 40 Error: WP at LBA = 0x002cadc8 = 2928072


Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 20 a8 a0 ad 2c 40 00 10:00:23.518 WRITE FPDMA QUEUED
61 36 08 28 12 4c 40 00 10:00:23.518 WRITE FPDMA QUEUED
60 20 a0 40 ca 77 40 00 10:00:23.518 READ FPDMA QUEUED
60 20 98 ca 11 7e 40 00 10:00:23.518 READ FPDMA QUEUED
61 7c 90 e0 73 83 40 00 10:00:23.518 WRITE FPDMA QUEUED


Error 65534 occurred at disk power-on lifetime: 27566 hours (1148 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 0b 89 f0 17 40 Error: UNC at LBA = 0x0017f089 = 1568905


Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 20 98 ca 11 7e 40 00 10:00:18.269 READ FPDMA QUEUED
61 7c 90 e0 73 83 40 00 10:00:18.269 WRITE FPDMA QUEUED
61 46 88 40 51 7c 40 00 10:00:18.269 WRITE FPDMA QUEUED
61 02 80 58 b8 a5 40 00 10:00:18.269 WRITE FPDMA QUEUED
61 20 78 40 d0 fe 40 00 10:00:18.269 WRITE FPDMA QUEUED


Error 65533 occurred at disk power-on lifetime: 27566 hours (1148 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 0b 89 f0 17 40 Error: UNC at LBA = 0x0017f089 = 1568905


Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 20 98 ca 11 7e 40 00 10:00:12.926 READ FPDMA QUEUED
61 7c 90 e0 73 83 40 00 10:00:12.926 WRITE FPDMA QUEUED
61 46 88 40 51 7c 40 00 10:00:12.926 WRITE FPDMA QUEUED
61 02 80 58 b8 a5 40 00 10:00:12.926 WRITE FPDMA QUEUED
61 20 78 40 d0 fe 40 00 10:00:12.926 WRITE FPDMA QUEUED


Error 65532 occurred at disk power-on lifetime: 27566 hours (1148 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 0b c1 6f 2f 40 Error: UNC at LBA = 0x002f6fc1 = 3108801


Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 20 a0 ca 11 7e 40 00 10:00:07.677 READ FPDMA QUEUED
61 7c 98 e0 73 83 40 00 10:00:07.677 WRITE FPDMA QUEUED
61 46 90 40 51 7c 40 00 10:00:07.677 WRITE FPDMA QUEUED
61 02 88 58 b8 a5 40 00 10:00:07.677 WRITE FPDMA QUEUED
61 20 80 40 d0 fe 40 00 10:00:07.677 WRITE FPDMA QUEUED


Error 65531 occurred at disk power-on lifetime: 27566 hours (1148 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 0b 25 87 2f 40 Error: WP at LBA = 0x002f8725 = 3114789


Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 20 08 a0 ad 2c 40 00 10:00:02.419 WRITE FPDMA QUEUED
60 20 b0 ca 11 7e 40 00 10:00:02.419 READ FPDMA QUEUED
61 7c a8 e0 73 83 40 00 10:00:02.419 WRITE FPDMA QUEUED
61 46 a0 40 51 7c 40 00 10:00:02.419 WRITE FPDMA QUEUED
61 02 98 58 b8 a5 40 00 10:00:02.419 WRITE FPDMA QUEUED


SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: unknown failure 90% 27567 0
# 2 Extended offline Completed: unknown failure 90% 27567 0
# 3 Extended offline Completed: unknown failure 90% 27566 0
# 4 Extended offline Completed: unknown failure 90% 27561 0
# 5 Short offline Completed without error 00% 4 -
# 6 Extended offline Completed without error 00% 2 -
# 7 Short offline Completed without error 00% 0 -


SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 
Re: Issues with avast and the windows media player having corrupt manifests

this is the error message that I get for c++ 2005 (x64) Microsoft Visual C++ 2005 redistributable (x64) Error 1935.An error occurred during the installation of assembly policy. 8.0 Microsoft. VC80.atl.type="win32-policy, version="8.050727.42".
 
Re: Issues with avast and the windows media player having corrupt manifests

It would appear that the disk may be failing by the SMART stats and that it cannot complete a self test. I would recommend replacing the drive if possible.

Do note that a drive can completely fail at any time without warning. Running repair utilities such as checkdisk can cause data loss.
Be absolutely certain that you have a backup of any important data on that drive before continuing.

chkdsk /f

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    chkdsk /f

  4. Reboot
  5. Download ListChkdskResult.exe (by SleepyDude) from the link below:

    https://dl.dropboxusercontent.com/u/12354842/My Tools/ListChkdskResult.exe
  6. Double click on it to run it. It will take a few seconds to scan, then it will open a Notepad window with the log. Copy and paste the contents of this into your next post please!
 
Re: Issues with avast and the windows media player having corrupt manifests

I will back the whole harddrive up to DVDS. Then I will look for a replacement harddrive and swap the old one out and copy from harddrive to harddrive using the copy command. I will be back when I am caught up.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top