Computer Stuck In Weird Loop

Discussion in 'Malware Help (A Specialist Will Reply)' started by Chaos Annihilator, Jul 29, 2026.

  1. Oh My!

    Oh My! Malware Expert Staff Member

    Great.

    Each time I review the FRST and Addition reports new issues pop up....

    Please do this.
    • Expand System devices
    • Right click on Intel® Serial IO GPIO Host Controller - INT34C5 and select Uninstall
    • Click Uninstall
    • Right click on Intel® Management Engine Interface #1 and select Uninstall
    • Click Uninstall
    • Reboot the computer and let me know if the mouse and touchpad issue is resolved
     
  2. Chaos Annihilator

    Chaos Annihilator Specialist

    Doesn't shift+F10 right click? When I try that it jumps me down farther on the list. Can I left click? I cannot see a context key on her keyboard.
     
  3. Chaos Annihilator

    Chaos Annihilator Specialist

    I had to do shift+fn+F10, I'm getting it now.
     
  4. Chaos Annihilator

    Chaos Annihilator Specialist

    I uninstalled both, and rebooted. Now we are preparing automatic repair and restarting. I shut it down and turned it on 3 times, and the loop is still going. Should I replace the files, or do something else since we think the backup I did this morning worked?
     
  5. Oh My!

    Oh My! Malware Expert Staff Member

    Go back to the backup registry files in FRST.
     
  6. Chaos Annihilator

    Chaos Annihilator Specialist

    It took a minute, but we are back. Still no cursor, though. The task bar is completely gone now. Maybe it needs more time? I'll be back to check it in 20 minutes.
     
  7. Chaos Annihilator

    Chaos Annihilator Specialist

    Time did not help, the task bar is still completely missing, and the mouse does not work. For some reason Firefox crash reporter came up, I haven't tried to open firefox on this computer in days. I have to go for about an hour, I'll check back in after that.
     
  8. Oh My!

    Oh My! Malware Expert Staff Member

    No problem.

    We need to delete them again but rather than reboot do the below.
    • Press the alt and A keys at the same time
    • Navigate to Action then select Scan for hardware changes
    Let me know what happens
     
  9. Chaos Annihilator

    Chaos Annihilator Specialist

    I was able to do this, but nothing happened as far as I could tell. I scrolled back down through the System Devices list, and the two Intel things you had me uninstall are back already. There are also two other things in this list that have exclamation points, and when I select them they say Windows can't get it to work (or something more technical than that).
    Working with the device manager is more difficult than last time because the list keeps blinking away, but if I wait it comes back.
     
  10. Oh My!

    Oh My! Malware Expert Staff Member

    I was hoping to get your mouse back but it didn't help.

    Please take a picture of the items with exclamation points then attempt to complete the GSmart and Memtest steps from Post #242.
     
  11. Chaos Annihilator

    Chaos Annihilator Specialist

    Here is the picture of the other things with exclamation points. The device manager is not blinking today, that was helpful. I'm working on GSmart now, sorry it's taking me so long.
     

    Attached Files:

  12. Chaos Annihilator

    Chaos Annihilator Specialist

    Here are the GSmart results. I'll need some time to work on the memory test next.

    smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-w10-b26200] (sf-6.6-1)
    Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Device Model: ST1000LM035-1RK172
    Serial Number: WKPKV4EQ
    LU WWN Device Id: 5 000c50 0d58a8ee5
    Firmware Version: LFM3
    User Capacity: 1,000,204,886,016 bytes [1.00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 5400 rpm
    Form Factor: 2.5 inches
    Device is: Not in smartctl database [for details use: -P showall]
    ATA Version is: ACS-3 T13/2161-D revision 3b
    SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Mon Aug 17 15:54:43 2026 CDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    AAM feature is: Unavailable
    APM level is: 128 (minimum power consumption without standby)
    Rd look-ahead is: Enabled
    Write cache is: Enabled
    DSN feature is: Unavailable
    ATA Security is: Disabled, NOT FROZEN [SEC1]

    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED

    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 0) seconds.
    Offline data collection
    capabilities: (0x71) SMART execute Offline immediate.
    No Auto Offline data collection support.
    Suspend Offline collection upon new
    command.
    No 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: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 169) minutes.
    Conveyance self-test routine
    recommended polling time: ( 2) minutes.
    SCT capabilities: (0x3035) SCT Status supported.
    SCT Feature Control supported.
    SCT Data Table supported.

    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
    1 Raw_Read_Error_Rate POSR-- 050 043 034 - 73869111
    3 Spin_Up_Time PO---- 099 099 000 - 0
    4 Start_Stop_Count -O--CK 037 037 020 - 65535
    5 Reallocated_Sector_Ct PO--CK 099 099 036 - 208
    7 Seek_Error_Rate POSR-- 088 060 045 - 569741030
    9 Power_On_Hours -O--CK 074 074 000 - 22818 (232 176 0)
    10 Spin_Retry_Count PO--C- 100 100 097 - 0
    12 Power_Cycle_Count -O--CK 098 098 020 - 2091
    184 End-to-End_Error -O--CK 100 100 099 - 0
    187 Reported_Uncorrect -O--CK 001 001 000 - 148
    188 Command_Timeout -O--CK 100 099 000 - 8590065683
    189 High_Fly_Writes -O-RCK 100 100 000 - 0
    190 Airflow_Temperature_Cel -O---K 065 047 040 - 35 (Min/Max 26/41)
    191 G-Sense_Error_Rate -O--CK 100 100 000 - 554
    192 Power-Off_Retract_Count -O--CK 100 100 000 - 168
    193 Load_Cycle_Count -O--CK 001 001 000 - 549144
    194 Temperature_Celsius -O---K 035 053 000 - 35 (0 16 0 0 0)
    196 Reallocated_Event_Count -O--CK 099 099 000 - 208
    197 Current_Pending_Sector -O--C- 100 100 000 - 0
    198 Offline_Uncorrectable ----C- 100 100 000 - 0
    199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
    240 Head_Flying_Hours POSR-- 081 081 030 - 16706 (65 248 0)
    254 Free_Fall_Sensor -O--CK 100 100 000 - 0
    ||||||_ K auto-keep
    |||||__ C event count
    ||||___ R error rate
    |||____ S speed/performance
    ||_____ O updated online
    |______ P prefailure warning

    General Purpose Log Directory Version 1
    SMART Log Directory Version 1 [multi-sector log support]
    Address Access R/W Size Description
    0x00 GPL,SL R/O 1 Log Directory
    0x01 SL R/O 1 Summary SMART error log
    0x02 SL R/O 5 Comprehensive SMART error log
    0x03 GPL R/O 5 Ext. Comprehensive SMART error log
    0x04 GPL,SL R/O 8 Device Statistics log
    0x06 SL R/O 1 SMART self-test log
    0x07 GPL R/O 1 Extended self-test log
    0x09 SL R/W 1 Selective self-test log
    0x10 GPL R/O 1 NCQ Command Error log
    0x11 GPL R/O 1 SATA Phy Event Counters log
    0x21 GPL R/O 1 Write stream error log
    0x22 GPL R/O 1 Read stream error log
    0x24 GPL R/O 512 Current Device Internal Status Data log
    0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
    0x80-0x9f GPL,SL R/W 16 Host vendor specific log
    0xa1 GPL,SL VS 24 Device vendor specific log
    0xa2 GPL VS 8160 Device vendor specific log
    0xa8 GPL,SL VS 136 Device vendor specific log
    0xa9 GPL,SL VS 1 Device vendor specific log
    0xab GPL VS 1 Device vendor specific log
    0xb0 GPL VS 8920 Device vendor specific log
    0xbe-0xbf GPL VS 65535 Device vendor specific log
    0xc0 GPL,SL VS 1 Device vendor specific log
    0xc1 GPL,SL VS 16 Device vendor specific log
    0xc2 GPL,SL VS 240 Device vendor specific log
    0xc3 GPL,SL VS 8 Device vendor specific log
    0xc4 GPL,SL VS 24 Device vendor specific log
    0xd3 GPL VS 1920 Device vendor specific log
    0xdf GPL,SL VS 1 Device vendor specific log
    0xe0 GPL,SL R/W 1 SCT Command/Status
    0xe1 GPL,SL R/W 1 SCT Data Transfer

    SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
    Device Error Count: 148 (device log contains only the most recent 20 errors)
    CR = Command Register
    FEATR = Features Register
    COUNT = Count (was: Sector Count) Register
    LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
    LH = LBA High (was: Cylinder High) Register ] LBA
    LM = LBA Mid (was: Cylinder Low) Register ] Register
    LL = LBA Low (was: Sector Number) Register ]
    DV = Device (was: Device/Head) Register
    DC = Device Control Register
    ER = Error register
    ST = Status register
    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 148 [7] occurred at disk power-on lifetime: 22792 hours (949 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 01 c5 ae 20 00 00 Error: UNC at LBA = 0x01c5ae20 = 29732384

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 01 c5 ae 20 40 00 1d+11:11:08.448 READ FPDMA QUEUED
    61 00 00 00 10 00 00 00 09 50 90 40 00 1d+11:11:08.434 WRITE FPDMA QUEUED
    61 00 00 00 08 00 00 00 1f 0d b8 40 00 1d+11:11:08.434 WRITE FPDMA QUEUED
    61 00 00 00 08 00 00 00 1c f5 b8 40 00 1d+11:11:08.434 WRITE FPDMA QUEUED
    60 00 00 00 60 00 00 09 ea 04 4a 40 00 1d+11:11:08.434 READ FPDMA QUEUED

    Error 147 [6] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 62 00 00 00 88 69 b8 40 00 15:53:52.715 READ FPDMA QUEUED
    61 00 00 00 10 00 00 00 65 bf 78 40 00 15:53:52.713 WRITE FPDMA QUEUED
    60 00 00 00 07 00 00 00 88 24 18 40 00 15:53:52.713 READ FPDMA QUEUED
    60 00 00 00 80 00 00 00 77 a2 20 40 00 15:53:52.710 READ FPDMA QUEUED
    60 00 00 00 05 00 00 00 7c 8a a8 40 00 15:53:52.709 READ FPDMA QUEUED

    Error 146 [5] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 80 00 00 18 2a 55 68 40 00 15:53:52.461 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 20 40 00 15:53:52.461 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 88 69 b0 40 00 15:53:52.277 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 88 24 10 40 00 15:53:52.277 READ FPDMA QUEUED
    60 00 00 00 80 00 00 18 2a 58 f8 40 00 15:53:52.277 READ FPDMA QUEUED

    Error 145 [4] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 77 a2 20 40 00 15:53:51.996 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 88 69 b0 40 00 15:53:51.996 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 88 24 10 40 00 15:53:51.996 READ FPDMA QUEUED
    60 00 00 00 80 00 00 18 2a 58 f8 40 00 15:53:51.996 READ FPDMA QUEUED
    60 00 00 00 58 00 00 04 1a 50 40 40 00 15:53:51.996 READ FPDMA QUEUED

    Error 144 [3] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 77 a2 20 40 00 15:53:51.856 READ FPDMA QUEUED
    61 00 00 00 08 00 00 40 e2 8b 28 40 00 15:53:51.846 WRITE FPDMA QUEUED
    60 00 00 00 08 00 00 00 88 69 b0 40 00 15:53:51.846 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 88 24 10 40 00 15:53:51.846 READ FPDMA QUEUED
    60 00 00 00 80 00 00 18 2a 58 f8 40 00 15:53:51.846 READ FPDMA QUEUED

    Error 143 [2] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 88 69 b0 40 00 15:53:51.772 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 88 24 10 40 00 15:53:51.772 READ FPDMA QUEUED
    60 00 00 00 80 00 00 00 77 a1 e8 40 00 15:53:51.760 READ FPDMA QUEUED
    60 00 00 00 80 00 00 00 68 d0 d0 40 00 15:53:51.753 READ FPDMA QUEUED
    60 00 00 00 80 00 00 18 2a 58 f8 40 00 15:53:51.751 READ FPDMA QUEUED

    Error 142 [1] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 6f 3c 50 40 00 15:53:51.593 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 6f 7c b0 40 00 15:53:51.593 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 7e e3 48 40 00 15:53:51.590 READ FPDMA QUEUED
    60 00 00 00 50 00 00 03 a0 76 a8 40 00 15:53:51.579 READ FPDMA QUEUED
    60 00 00 01 00 00 00 04 1a 49 40 40 00 15:53:51.567 READ FPDMA QUEUED

    Error 141 [0] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 01 00 00 00 03 c5 e3 00 40 00 15:53:51.436 READ FPDMA QUEUED
    60 00 00 01 00 00 00 03 c5 e2 00 40 00 15:53:51.436 READ FPDMA QUEUED
    60 00 00 01 00 00 00 03 c5 e1 00 40 00 15:53:51.436 READ FPDMA QUEUED
    60 00 00 00 08 00 00 03 c5 e4 88 40 00 15:53:51.434 READ FPDMA QUEUED
    60 00 00 00 08 00 00 04 1a 50 98 40 00 15:53:51.425 READ FPDMA QUEUED

    Error 140 [19] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: WP at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    61 00 00 00 30 00 00 00 65 bf 38 40 00 15:53:51.009 WRITE FPDMA QUEUED
    61 00 00 00 28 00 00 00 67 a9 00 40 00 15:53:51.006 WRITE FPDMA QUEUED
    60 00 00 00 f8 00 00 01 ff 02 f0 40 00 15:53:51.006 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 20 40 00 15:53:51.006 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 91 95 e8 40 00 15:53:51.006 READ FPDMA QUEUED

    Error 139 [18] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 91 95 e8 40 00 15:53:50.962 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 20 40 00 15:53:50.953 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 69 99 a8 40 00 15:53:50.942 READ FPDMA QUEUED
    60 00 00 00 09 00 00 00 b6 c5 d8 40 00 15:53:50.940 READ FPDMA QUEUED
    60 00 00 00 f8 00 00 00 b6 c3 c0 40 00 15:53:50.939 READ FPDMA QUEUED

    Error 138 [17] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 f0 00 00 00 77 a1 f8 40 00 15:53:50.644 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a1 f0 40 00 15:53:50.632 READ FPDMA QUEUED
    60 00 00 00 72 00 00 00 8a 88 c8 40 00 15:53:50.629 READ FPDMA QUEUED
    60 00 00 00 0e 00 00 02 bb fa 48 40 00 15:53:50.534 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 e8 40 00 15:53:50.533 READ FPDMA QUEUED

    Error 137 [16] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 8a 88 c0 40 00 15:53:50.475 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 69 3b c0 40 00 15:53:50.475 READ FPDMA QUEUED
    60 00 00 00 28 00 00 02 a9 38 b8 40 00 15:53:50.471 READ FPDMA QUEUED
    60 00 00 01 00 00 00 02 a9 37 b8 40 00 15:53:50.471 READ FPDMA QUEUED
    60 00 00 01 00 00 00 02 a9 36 b8 40 00 15:53:50.471 READ FPDMA QUEUED

    Error 136 [15] occurred at disk power-on lifetime: 18210 hours (758 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 60 00 00 00 77 9f e8 40 00 15:53:50.254 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 68 d0 f8 40 00 15:53:50.254 READ FPDMA QUEUED
    60 00 00 00 08 00 00 04 02 f3 e0 40 00 15:53:50.248 READ FPDMA QUEUED
    60 00 00 01 00 00 00 04 02 f2 e0 40 00 15:53:50.248 READ FPDMA QUEUED
    60 00 00 01 00 00 00 04 02 f1 e0 40 00 15:53:50.248 READ FPDMA QUEUED

    Error 135 [14] occurred at disk power-on lifetime: 18129 hours (755 days + 9 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 77 a2 20 40 00 22:34:47.133 READ FPDMA QUEUED
    2f 00 00 00 01 00 00 00 00 00 10 28 00 22:34:47.119 READ LOG EXT
    60 00 00 00 08 00 00 00 77 a2 20 40 00 22:34:47.012 READ FPDMA QUEUED
    2f 00 00 00 01 00 00 00 00 00 10 28 00 22:34:46.998 READ LOG EXT
    60 00 00 00 40 00 00 00 77 a2 20 40 00 22:34:46.969 READ FPDMA QUEUED

    Error 134 [13] occurred at disk power-on lifetime: 18129 hours (755 days + 9 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 77 a2 20 40 00 22:34:47.012 READ FPDMA QUEUED
    2f 00 00 00 01 00 00 00 00 00 10 28 00 22:34:46.998 READ LOG EXT
    60 00 00 00 40 00 00 00 77 a2 20 40 00 22:34:46.969 READ FPDMA QUEUED
    60 00 00 00 80 00 00 00 77 a2 60 40 00 22:34:46.948 READ FPDMA QUEUED
    60 00 00 00 08 00 00 21 38 2f 42 40 00 22:34:46.942 READ FPDMA QUEUED

    Error 133 [12] occurred at disk power-on lifetime: 18129 hours (755 days + 9 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 40 00 00 00 77 a2 20 40 00 22:34:46.969 READ FPDMA QUEUED
    60 00 00 00 80 00 00 00 77 a2 60 40 00 22:34:46.948 READ FPDMA QUEUED
    60 00 00 00 08 00 00 21 38 2f 42 40 00 22:34:46.942 READ FPDMA QUEUED
    60 00 00 00 2c 00 00 21 38 2b 1a 40 00 22:34:46.940 READ FPDMA QUEUED
    60 00 00 00 20 00 00 21 38 2d de 40 00 22:34:46.939 READ FPDMA QUEUED

    Error 132 [11] occurred at disk power-on lifetime: 18129 hours (755 days + 9 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 77 a2 20 40 00 22:34:46.675 READ FPDMA QUEUED
    2f 00 00 00 01 00 00 00 00 00 10 28 00 22:34:46.666 READ LOG EXT
    60 00 00 00 08 00 00 00 77 a2 20 40 00 22:34:46.626 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 18 40 00 22:34:46.625 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 10 40 00 22:34:46.625 READ FPDMA QUEUED

    Error 131 [10] occurred at disk power-on lifetime: 18129 hours (755 days + 9 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 77 a2 20 40 00 22:34:46.626 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 18 40 00 22:34:46.625 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 10 40 00 22:34:46.625 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 08 40 00 22:34:46.624 READ FPDMA QUEUED
    60 00 00 00 08 00 00 00 77 a2 00 40 00 22:34:46.623 READ FPDMA QUEUED

    Error 130 [9] occurred at disk power-on lifetime: 18129 hours (755 days + 9 hours)
    When the command that caused the error occurred, the device was active or idle.

    After command completion occurred, registers were:
    ER -- ST COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 80 00 00 00 77 a1 e0 40 00 22:34:46.225 READ FPDMA QUEUED
    60 00 00 00 02 00 00 00 77 a1 c0 40 00 22:34:46.224 READ FPDMA QUEUED
    60 00 00 00 05 00 00 00 77 a1 b8 40 00 22:34:46.223 READ FPDMA QUEUED
    60 00 00 00 03 00 00 00 77 a1 b0 40 00 22:34:46.221 READ FPDMA QUEUED
    60 00 00 00 08 00 00 1e 07 1d e8 40 00 22:34:46.220 READ FPDMA QUEUED

    Error 129 [8] occurred at disk power-on lifetime: 18062 hours (752 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 COUNT LBA_48 LH LM LL DV DC
    -- -- -- == -- == == == -- -- -- -- --
    40 -- 51 00 00 00 00 00 77 a2 20 00 00 Error: UNC at LBA = 0x0077a220 = 7840288

    Commands leading to the command that caused the error were:
    CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
    -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
    60 00 00 00 08 00 00 00 77 a2 20 40 00 1d+20:59:35.808 READ FPDMA QUEUED
    2f 00 00 00 01 00 00 00 00 00 10 28 00 1d+20:59:35.794 READ LOG EXT
    60 00 00 00 08 00 00 00 77 a2 20 40 00 1d+20:59:35.688 READ FPDMA QUEUED
    2f 00 00 00 01 00 00 00 00 00 10 28 00 1d+20:59:35.662 READ LOG EXT
    60 00 00 00 40 00 00 00 77 a2 20 40 00 1d+20:59:35.632 READ FPDMA QUEUED

    SMART Extended Self-test Log Version: 1 (1 sectors)
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Short offline Completed without error 00% 22818 -
    # 2 Short offline Completed without error 00% 22578 -

    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.

    SCT Status Version: 3
    SCT Version (vendor specific): 522 (0x020a)
    SCT Support Level: 0
    Device State: Active (0)
    Current Temperature: 34 Celsius
    Power Cycle Min/Max Temperature: 25/41 Celsius
    Lifetime Min/Max Temperature: 16/53 Celsius
    Under/Over Temperature Limit Count: 0/113
    Vendor specific:
    00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    SCT Temperature History Version: 2
    Temperature Sampling Period: 1 minute
    Temperature Logging Interval: 11 minutes
    Min/Max recommended Temperature: 0/ 0 Celsius
    Min/Max Temperature Limit: 0/ 0 Celsius
    Temperature History Size (Index): 128 (74)

    Index Estimated Time Temperature Celsius
    75 2026-08-16 16:28 31 ************
    76 2026-08-16 16:39 31 ************
    77 2026-08-16 16:50 31 ************
    78 2026-08-16 17:01 32 *************
    79 2026-08-16 17:12 ? -
    80 2026-08-16 17:23 33 **************
    81 2026-08-16 17:34 ? -
    82 2026-08-16 17:45 33 **************
    83 2026-08-16 17:56 ? -
    84 2026-08-16 18:07 33 **************
    85 2026-08-16 18:18 ? -
    86 2026-08-16 18:29 33 **************
    87 2026-08-16 18:40 ? -
    88 2026-08-16 18:51 25 ******
    89 2026-08-16 19:02 ? -
    90 2026-08-16 19:13 30 ***********
    91 2026-08-16 19:24 37 ******************
    92 2026-08-16 19:35 39 ********************
    93 2026-08-16 19:46 40 *********************
    94 2026-08-16 19:57 41 **********************
    95 2026-08-16 20:08 40 *********************
    96 2026-08-16 20:19 41 **********************
    97 2026-08-16 20:30 40 *********************
    ... ..( 2 skipped). .. *********************
    100 2026-08-16 21:03 40 *********************
    101 2026-08-16 21:14 39 ********************
    102 2026-08-16 21:25 38 *******************
    103 2026-08-16 21:36 39 ********************
    104 2026-08-16 21:47 39 ********************
    105 2026-08-16 21:58 38 *******************
    106 2026-08-16 22:09 39 ********************
    107 2026-08-16 22:20 40 *********************
    ... ..( 2 skipped). .. *********************
    110 2026-08-16 22:53 40 *********************
    111 2026-08-16 23:04 41 **********************
    112 2026-08-16 23:15 38 *******************
    113 2026-08-16 23:26 38 *******************
    114 2026-08-16 23:37 39 ********************
    115 2026-08-16 23:48 36 *****************
    116 2026-08-16 23:59 32 *************
    117 2026-08-17 00:10 31 ************
    118 2026-08-17 00:21 31 ************
    119 2026-08-17 00:32 31 ************
    120 2026-08-17 00:43 35 ****************
    121 2026-08-17 00:54 34 ***************
    122 2026-08-17 01:05 32 *************
    123 2026-08-17 01:16 31 ************
    124 2026-08-17 01:27 31 ************
    125 2026-08-17 01:38 30 ***********
    ... ..( 4 skipped). .. ***********
    2 2026-08-17 02:33 30 ***********
    3 2026-08-17 02:44 31 ************
    4 2026-08-17 02:55 31 ************
    5 2026-08-17 03:06 30 ***********
    6 2026-08-17 03:17 29 **********
    7 2026-08-17 03:28 28 *********
    8 2026-08-17 03:39 28 *********
    9 2026-08-17 03:50 27 ********
    10 2026-08-17 04:01 27 ********
    11 2026-08-17 04:12 27 ********
    12 2026-08-17 04:23 28 *********
    13 2026-08-17 04:34 29 **********
    14 2026-08-17 04:45 29 **********
    15 2026-08-17 04:56 29 **********
    16 2026-08-17 05:07 28 *********
    ... ..( 3 skipped). .. *********
    20 2026-08-17 05:51 28 *********
    21 2026-08-17 06:02 29 **********
    22 2026-08-17 06:13 29 **********
    23 2026-08-17 06:24 28 *********
    24 2026-08-17 06:35 27 ********
    25 2026-08-17 06:46 26 *******
    26 2026-08-17 06:57 25 ******
    27 2026-08-17 07:08 26 *******
    28 2026-08-17 07:19 26 *******
    29 2026-08-17 07:30 26 *******
    30 2026-08-17 07:41 27 ********
    ... ..( 2 skipped). .. ********
    33 2026-08-17 08:14 27 ********
    34 2026-08-17 08:25 28 *********
    ... ..( 2 skipped). .. *********
    37 2026-08-17 08:58 28 *********
    38 2026-08-17 09:09 27 ********
    ... ..( 10 skipped). .. ********
    49 2026-08-17 11:10 27 ********
    50 2026-08-17 11:21 28 *********
    51 2026-08-17 11:32 29 **********
    52 2026-08-17 11:43 31 ************
    53 2026-08-17 11:54 33 **************
    54 2026-08-17 12:05 35 ****************
    55 2026-08-17 12:16 36 *****************
    56 2026-08-17 12:27 37 ******************
    57 2026-08-17 12:38 37 ******************
    58 2026-08-17 12:49 35 ****************
    59 2026-08-17 13:00 34 ***************
    60 2026-08-17 13:11 33 **************
    61 2026-08-17 13:22 37 ******************
    62 2026-08-17 13:33 38 *******************
    63 2026-08-17 13:44 39 ********************
    64 2026-08-17 13:55 38 *******************
    65 2026-08-17 14:06 35 ****************
    66 2026-08-17 14:17 35 ****************
    67 2026-08-17 14:28 32 *************
    68 2026-08-17 14:39 33 **************
    69 2026-08-17 14:50 31 ************
    70 2026-08-17 15:01 31 ************
    71 2026-08-17 15:12 32 *************
    72 2026-08-17 15:23 35 ****************
    73 2026-08-17 15:34 34 ***************
    74 2026-08-17 15:45 34 ***************

    SCT Error Recovery Control command not supported

    Device Statistics (GP Log 0x04)
    Page Offset Size Value Flags Description
    0x01 ===== = = === == General Statistics (rev 1) ==
    0x01 0x008 4 2091 --- Lifetime Power-On Resets
    0x01 0x010 4 22818 --- Power-on Hours
    0x01 0x018 6 60222835936 --- Logical Sectors Written
    0x01 0x020 6 1473173042 --- Number of Write Commands
    0x01 0x028 6 109223695065 --- Logical Sectors Read
    0x01 0x030 6 2112093695 --- Number of Read Commands
    0x01 0x038 6 - --- Date and Time TimeStamp
    0x03 ===== = = === == Rotating Media Statistics (rev 1) ==
    0x03 0x008 4 2337684850 N-- Spindle Motor Power-on Hours
    0x03 0x010 4 2337683717 N-- Head Flying Hours
    0x03 0x018 4 549144 --- Head Load Events
    0x03 0x020 4 208 --- Number of Reallocated Logical Sectors
    0x03 0x028 4 890 --- Read Recovery Attempts
    0x03 0x030 4 0 --- Number of Mechanical Start Failures
    0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors
    0x04 ===== = = === == General Errors Statistics (rev 1) ==
    0x04 0x008 4 9714 --- Number of Reported Uncorrectable Errors
    0x04 0x010 4 19 --- Resets Between Cmd Acceptance and Completion
    |||_ C monitored condition met
    ||__ D supports DSN
    |___ N normalized value

    SATA Phy Event Counters (GP Log 0x11)
    ID Size Value Description
    0x000a 2 3 Device-to-host register FISes sent due to a COMRESET
    0x0001 2 0 Command failed due to ICRC error
    0x0003 2 0 R_ERR response for device-to-host data FIS
    0x0004 2 0 R_ERR response for host-to-device data FIS
    0x0006 2 0 R_ERR response for device-to-host non-data FIS
    0x0007 2 0 R_ERR response for host-to-device non-data FIS
     
  13. Chaos Annihilator

    Chaos Annihilator Specialist

    I have a question about the memory test. I get confused regarding my computer (which I am using this second) and my friend's computer (which this thread is about). In your steps for the memory test, which I pasted below just to make life easier, I first download this onto my working desktop, then put the USB in my computer and complete the steps through
    Once completed click OK, then Exit
    and then I put the USB into my friend's broken computer, right? I don't want to get it wrong and accidentally erase my C drive.
    I'm going to reuse the first Windows installation media USB, since we haven't needed it in a while. Do I need to do anything to reformat it, or will the steps you outlined just clear it out and make it usable for this automatically?
    Thanks


    Testing Computer Memory Using MemTest86 USB

    --------------------

    Warning! This step will remove all existing information from your USB device.
    • Download MemTest86 Free for USB and and save it to your Desktop
    • Unzip the folder onto your Desktop
    • Open the memtest86-usb folder
    • Right click on imageUSB.exe and select Run as administrator
    • Insert your USB into your affected computer then click Refresh Drives
    • Place a check mark in the USB drive now listed under Step 1
    • Confirm the image of the downloaded file is listed as Desktop\memtest86-usb\memtest86-usb.img under Step 3
    • Click Write under Step 4, then click Yes twice to confirm
    • Once completed click OK, then Exit
    • Insert the USB into the compromised computer
    • Boot to the USB device
    • Allow the program to load, start automatically and complete the 4 passes. This process may take some time to complete
    • Report the results of the test
     
  14. Oh My!

    Oh My! Malware Expert Staff Member

    For some reason I am not being notified of your posts. I will look into that.

    Correct, create the Memtest USB on the working computer then transfer it to the compromised computer and boot to the USB.

    Creating the Memtest bootable USB will remove the current information on the device and write the Memtest on it. No need to format.
     
  15. Chaos Annihilator

    Chaos Annihilator Specialist

    Okay, thanks. I'll need some time to work on this, I was too confused to try. I probably overloaded your notifications with my 3-5 post freak outs, and they decided they couldn't take it anymore and just quit notifying you.
     
  16. Oh My!

    Oh My! Malware Expert Staff Member

    I have reviewed the GSmart data and it indicates the drive is failing. The computer will need a new hard drive.
     
  17. Chaos Annihilator

    Chaos Annihilator Specialist

    Oh. So should I not bother with the memory test then? Is it worth replacing the hard drive, or should she buy a new computer? I don't know anything about replacing hard drives.
     
  18. Oh My!

    Oh My! Malware Expert Staff Member

    Run the Memtest to see if there are any errors. We should see those results before discussing what to do.
     
    Chaos Annihilator likes this.
  19. Chaos Annihilator

    Chaos Annihilator Specialist

    It says there are no errors, and it passed. I took some pictures if you need them, and at the end there seems to be some Memtest menu, I don't know if we need to do anything there, so I left it up.

    Didn't we run a different hard drive test before and it passed? I couldn't find the post.
     
  20. Oh My!

    Oh My! Malware Expert Staff Member

    Glad there were no memory errors. That makes it easier to opt for keeping the computer if she'd like.

    Yes, we did run a hard drive test through Hirens. Hard drive tests are different from one another and results do not always match category for category. I tend to lean on GSmartControl more than other programs.

    These numbers above are not good. With this drive it is impossible for us to return the system to a healthy status.

    If she has been satisfied with the performance of this computer while it was working properly keeping it and installing a new drive is the least expensive route.

    Although it will cost a bit more, I would recommend purchasing a faster 500GB SSD (might be able to get away with 256GB) and a special adapter ($10) needed to internally connect the SSD to the computer. You can get a 256 SSD for about $40 and above. A 512GB SSD is about $80 and above. You can also get a 500GB drive to replace the 1TB, which is far bigger than she needs, for about $25 and up. You can sift through Amazon for options.

    Installing a fresh operating system would be the same on any drive she selects. We can work our way through the process which will result in a clean operating system needing installation of programs and apps that don't come automatically with a new install.

    Chat with her and see what you guys think.
     
    Chaos Annihilator likes this.

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds