“Operating system not found” Error on Windows 10

Page 1 of 3 123 LastLast
  1.    #1

    “Operating system not found” Error on Windows 10


    I just started to get this message on one of my computers but now I cannot replicate it. I copied all of my data off the computer last night so that I could try to get to the repair option at bootup. I shutdown my computer today after all of the files were copied and inserted my flash drive right after startup so it could boot from the usb drive but I never got the setup screen to do the repair. I have repeated tried to get to that screen but the computer will just boot normally now. I want to make sure I do not have that problem again so is there a way to run the repair without booting at startup?

    Note: I still have an open thread for another computer of mine that was having a very similar problem that I have not resolved.
      My ComputerSystem Spec


  2. Posts : 4
    Windows 10 Pro version 1809
       #2

    that sounds like a possible failing hard drive.
      My ComputerSystem Spec

  3.    #3

    First check connection to the hd and motherboard. Does the BIOS see the disk ok? Go-to disk makers website they normally have their own disk check with a bootable option failing that boot from a Linux or other rescue disk to see if you can see files on the hd
      My ComputerSystem Spec

  4.    #4

    OK. I will do that once the sea tools has completed its long generic test. It passed all of the shorter tests but to make sure I was running the long test. I will go into the BIOS and run whatever self test option I find there once the sea tools has completed.

    - - - Updated - - -

    I have run numerous tests on the hard drive of this pc and all of the test came back normal. After running the sea tools I ran the VAIO Care diagnostics on the system checking the hardware of the system and selected the repair options -- the result was that the hard drive is running normally. After running the tests I restarted the computer and it restarted normally so I do not know why I have been getting the operating not found message.

    Note: Sony Vaio Care is a utility loaded onto the laptop that scans computers for potential problems including corrupt files, a failing hard drive or other device issues. Also, I ran Crystal Disk Info and it reports that the health of my hard drive is good running at 39 degrees Celsius.

    - - - Updated - - -

    I have just installed the most current updates on this computer (this evening of May 14, 2019) that seemed to be related more to office 2013 and adobe. On April 1, 2019 I had the latest Feature update to Windows 10, version 1809 amd64 2019-03 installed successfully. Are there any suggestions on what I should do to ensure I am not in danger of some severe problem?
      My ComputerSystem Spec

  5.    #5

    What I would do is install a copy of Macrium Reflect free edition and run it so that it checks your computer for partitions, this will be displayed on screen before you do a backup, so there is no need to continue unless you wish to complete a backup of your drive/s.
    Check the drive sections on display to make sure you have a repair/recovery partition?
      My ComputerSystem Spec

  6.    #6

    I can do that if necessary but when I ran the Vaio Care Utility there were 4 partitions and the recovery/repair feature was an option. I did not select it since the system booted up normally. Also, I have already backed up all of my data but I will download the macrium -- I just do not understand the benefit of it at this time.
      My ComputerSystem Spec


  7. Posts : 25,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    1) Open disk management > by default columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view > widen the disk 0 row > upload image

    Disk Management - How to Post a Screenshot of

    2) There is a log collector used in another forum.
    Run the V2 log collector and upload into this thread:
    BSOD - Posting Instructions


    3) Open administrative command prompt and type or copy and paste:
    4) sfc /scannow
    5) dism /online /cleanup-image /restorehealth
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
      My ComputerSystem Spec

  8.    #8

    I downloaded the Macrium Reflect and it shows the 4 partitions -- one of them being the recovery partition as I mentioned.

    Note: I googled this problem and went to this link and found this to be a common problem with Sony Vaio laptops. Get the fix for “Operating System not found” boot error for Windows XP, Vista, 7, 8, 8.1 or Windows 10.
    This error is also very common for Sony VIO laptops, including T-Series ultra books and S-Series.

    Operating System not found or missing: Fix for Windows XP, Vista, 7, 8, 8.1, 10

    - - - Updated - - -

    Here is the information gathered from the scan log you requested along with the attachments:

    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.

    PS C:\WINDOWS\system32> sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.
    PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    Image Version: 10.0.17763.503

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    PS C:\WINDOWS\system32> chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    564992 file records processed.
    File verification completed.
    16462 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    28752 reparse records processed.
    671710 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    28752 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    53360 data files processed.
    CHKDSK is verifying Usn Journal...
    38636024 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    711971544 KB total disk space.
    556670672 KB in 241705 files.
    157744 KB in 53361 indexes.
    4 KB in bad sectors.
    717884 KB in use by the system.
    65536 KB occupied by the log file.
    154425240 KB available on disk.

    4096 bytes in each allocation unit.
    177992886 total allocation units on disk.
    38606310 allocation units available on disk.
    PS C:\WINDOWS\system32> wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-SAU8PFR\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
    Property(s) update successful.
    PS C:\WINDOWS\system32>
    Attached Thumbnails Attached Thumbnails Sony Vaio 2019-05-15 111238.png  
    Attached Files
      My ComputerSystem Spec


  9. Posts : 25,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    The logs displayed that the computer has been having BSOD.

    The last BSOD displayed in the logs was on 5/12/2019.

    There were no mini dump files collected by the log collector.

    The bugchecks displayed in the logs were:
    154
    A0

    Perform the following steps:

    1) Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    Use the syntax chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.
    This may take many hours so plan to run overnight.
    Run the command on all drives.

    Microsoft Windows [Version 10.0.17763.475]
    (c) 2018 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>chkdsk /r /v C:
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot

    2) Use the text and images in this link to find the chkdsk reports in the event viewer > copy and paste > notepad > post share links into the thread using one drive, drop box, or google drive
    Read Chkdsk Log in Event Viewer in Windows 10

    3) Run HD Tune: (free or trial version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan

    4) Run Sea Tools for Windows
    long generic scan

    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    5) For any BSOD:

    a) run the V2 log collector to collect new log files > upload into the thread

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive




    Code:
    Event[2309]:
      Log Name: System
      Source: Disk
      Date: 2019-05-13T13:24:28.164
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    The IO operation at logical block address 0x140aaf50 for Disk 0 (PDO name: \Device\0000002f) failed due to a hardware error.

    Code:
    Event[2031]:
      Log Name: System
      Source: Volsnap
      Date: 2019-05-12T14:52:08.149
      Event ID: 14
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    The shadow copies of volume C: were aborted because of an IO failure on volume C:.
    Code:
    4/30/2019 9:23 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 154
    P2: ffffb58b35da6000
    P3: ffff8782895be350
    P4: 2
    P5: 0
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\043019-50000-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-363750-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CD1.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CF2.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DAC.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DBD.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_154_7f649728ddcaf0aeb45bced895e215a1fa0b4_00000000_cab_039a1dfa
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 01841ea9-a9e3-494e-b6e5-5d1b01ff152d
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:52 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 100
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:46 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 100
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:39 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 100
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:31 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 100
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:18 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 100
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:13 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 100
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:09 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 100
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:08 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 100
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:07 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 100
    Hashed bucket: 
    Cab Guid: 0
    5/7/2019 9:07 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: 10a
    P3: a
    P4: ffffdd0bb6ef95f0
    P5: ffffffffc0000001
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\050719-89406-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-100625-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER612D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61EA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6312.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6380.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_a0cd4f534d5b59cb535466fe623c55c58472640_00000000_cab_038263ae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e06d34f3-2a57-4fff-a2dd-04a941191478
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    5/12/2019 7:54 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a0
    P2: c
    P3: ffffffffc0000001
    P4: ffff8989266b8a70
    P5: 0
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\051219-88250-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-94953-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER13BE.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER141D.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER142F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1450.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_e1ba2da74a81a94b657f17b647332665a1ff232_00000000_cab_0381145a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e48264f9-e61d-43ac-8da8-bcabbaaeecec
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    Code:
    Event[1132]:
      Log Name: System
      Source: Disk
      Date: 2019-04-30T16:01:07.104
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    An error was detected on device \Device\Harddisk1\DR29 during a paging operation.
    Code:
    Event[776]:
      Log Name: System
      Source: Disk
      Date: 2019-04-24T18:27:45.100
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    An error was detected on device \Device\Harddisk1\DR16 during a paging operation.
    
    Event[777]:
      Log Name: System
      Source: Disk
      Date: 2019-04-24T18:27:45.100
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    An error was detected on device \Device\Harddisk1\DR16 during a paging operation.
    
    Event[778]:
      Log Name: System
      Source: Disk
      Date: 2019-04-24T18:27:45.100
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    An error was detected on device \Device\Harddisk1\DR16 during a paging operation.
    
    Event[779]:
      Log Name: System
      Source: Disk
      Date: 2019-04-24T18:27:45.100
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    An error was detected on device \Device\Harddisk1\DR16 during a paging operation.
    Code:
    Event[2033]:
      Log Name: System
      Source: Disk
      Date: 2019-05-12T14:52:48.304
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    The IO operation at logical block address 0x2bad220 for Disk 0 (PDO name: \Device\0000002f) was retried.
    
    Event[2034]:
      Log Name: System
      Source: Disk
      Date: 2019-05-12T14:53:27.818
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    The IO operation at logical block address 0x2da5260 for Disk 0 (PDO name: \Device\0000002f) was retried.
    Code:
    Event[2612]:
      Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2019-05-14T20:08:41.662
      Event ID: 98
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-SAU8PFR
      Description: 
    Volume \\?\Volume{0cad94ff-0000-0000-0000-100000000000} (\Device\HarddiskVolume1) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
    Code:
    Windows has found problems that must be fixed offline.
    Please run "chkdsk /f" to fix the issues.
    Code:
    Event[1923]:
      Log Name: Application
      Source: Application Error
      Date: 2019-05-12T14:53:04.678
      Event ID: 1005
      Task: Application Crashing Events
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    Windows cannot access the file C:\Windows\System32\wininet.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Windows Logon User Interface Host because of this error.
    
    Program: Windows Logon User Interface Host
    File: C:\Windows\System32\wininet.dll
    
    The error value is listed in the Additional Data section.
    User Action
    1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
    2. If the file still cannot be accessed and
    	- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
    	- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
    3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
    4. If the problem persists, restore the file from a backup copy.
    5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
    Code:
    Event[2181]:
      Log Name: System
      Source: Disk
      Date: 2019-05-13T06:52:25.668
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-SAU8PFR
      Description: 
    The driver detected a controller error on \Device\Harddisk1\DR1.
      My ComputerSystem Spec

  10.    #10

    I see the I/O failures as you mentioned. I decided to run the check disk now and started it about 20-30 minutes ago. I realize it will take some time but I wanted to make sure you saw that I ran the sea tools last night and it said the drive was healthy. I ran all of the scans including the long generic. Also, as previously mentioned I have been having similar problem with my other Sony Vail. I am currently having to do an install/upgrade of Windows now because the most current Feature update of 1809 failed on March 31 and I was unaware. Found out when the update on yesterday failed. There is a separate thread for the other Vail going back to end of last year.

    - - - Updated - - -

    I apologize for any errors in spelling but I am using a tablet to reply to thread since both computers running installation/scan right now.

    - - - Updated - - -

    I am posting the results I have so far since I have not run the sea tools test again. The HD Tune just finished so I thought I should send you those results along with DM and V2 Log Collector data. I should point out that the computer during the check disk and repair the computer stayed on 13% for well more than an hour but the report seemed to have come back relatively clean. I will send the screen shots of the remaining HD Tune and sea tool in separate posts.

    - - - Updated - - -

    Attached are the screen shots of the HD Tune bench mark, health and error scans. Upon completion of sea tools I will attach those files.
    Attached Thumbnails Attached Thumbnails 15-May-2019_20-27...Benchmark of HD.png   15-May-2019_20-46...Health.png   15-May-2019_23-43...Error Scan.png   15-May-2019_23-46...Error Scan Speed Map.png  
    Attached Files
      My ComputerSystem Spec


 
Page 1 of 3 123 LastLast

Related Threads
Been searching for an answer for some time, but have an issue still not resolved. My son's PC is a self built PC, upgraded to Windows 10 when Win 10 came out. No issues until recently, when the PC started freezing at odd times (night, sleeping,...
Operating system not found in General Support
I have Sony Vaio I7, 8Gb memory. I do not have OS backup disk. I upgraded from 8 to 8.1 and then to 10. It has been running great. No problems. Use Kaspersky Internet Security. I shut down computer normally this morning. I powered back on this...
Ok, so a while back when the Windows 10 Upgrade had popped up on my computer, I upgraded with no problem at all. I wanted to do a factory restore in order to clean up my laptop completely, however while updating, the power went out and the computer...
Hi guys, I have recently upgrade to Win 10 from windows 7 and it was running fine until it started booting with the analyzing and repairing windows screen. I had tried to get out of it by windows repair and by system restore but there were no...
I have a Dell e6510 that was running Windows 7 Pro. I received the windows 10 upgrade after reserving a copy a few weeks back. Before the updated I made sure my windows update was up to date. I kicked off the upgrade to Windows 10 and left...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:40.
Find Us