Windows 10: Win 10 update (fall 2017) fails

  1.    03 Dec 2017 #1

    Win 10 update (fall 2017) fails


    Win 10 update assistant notifies to update
    goes thru update --- Fails
    HP Desktop 4gb
    Win 8 (1tb spinner) --> Win 10 --> migrate to SSD (45G used 65 G free)

    error code 0x80070057
    on another attempt
    error code 0x80070652

    allowed it to try update many times ---- always fails

    attempted win 10 iso DVD update ---- fails

    system file diag and clean up
    utilities (Glary) find errors and repair

    Not able to update to new win 10

    Help
      My ComputerSystem Spec

  2.    04 Dec 2017 #2

    I ran into a similar problem recently, and was only slowly able to figure out a failing memory module was responsible. You can read the story in my 11/1/17 blog post: Bad RAM Nixes 1709 Upgrade - Windows Enterprise Desktop, if you like. But you could also cut to the chase and follow the lead in this tutorial on testing your memory to see if it might be the culprit: Run Windows Memory Diagnostics Tool in Windows 10 Hardware Drivers Tutorials .
    HTH,
    --Ed--
      My ComputersSystem Spec

  3.    04 Dec 2017 #3

    Yes went thru that --- found bad 4G dimm
    pulled it out -- ran memory tests --- memory fine 4G good
    Still won't update

    tnx
      My ComputerSystem Spec


  4. Posts : 14,123
    windows 10 professional version 1607 build 14393.969 64 bit
       04 Dec 2017 #4

    Please update the system specs in the "My Computer" section:

    How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Site Use Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums


    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)

    Open administrative command prompt and type or copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) chkdsk /scan
    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

    4) In the left lower corner type: winver > view about windows > post an image into the thread
    5) In the left lower corner type: windows updates > click update history > post an image into the thread
    6) open the HP website > software and drivers https://support.hp.com/us-en/drivers> enter the computer's product or serial number > post a URL or hyperlink into the thread.
    7) run the DM log collector: BSOD - Posting Instructions - Windows 10 Forums
    It will automatically collect files (event viewer, mini dump, msinfo32, dxdiag, drivers, hosts, install, uninstall, startup, etc.)

    8) download and install everything search: voidtools
    This software will index everything on the computer's drives.
    Search will be much faster than file explorer.
    Look for any of these folders and files and post the files that you were able to find into the thread using one drive or drop box share links:

    C:\$WINDOWS.~BT\Sources\Panther
    C:\Windows\Panther
    setuperr.log
    setupact.log
    Setupmem.dmp ..............$Windows.~bt\Sources\Rollback\setupmem.dmp
    setupapi.dev.log ..............$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
    BlueBox.log
    $Windows.~bt\Sources\Rollback*.evtx

    C:\$Windows.~BT\Sources\Rollback

    BlueBox.log
    $Windows.~bt\Sources\Rollback\setupmem.dmp
    $Windows.~bt\Sources\Rollback*.evtx
    $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

    Setupmem.dmp
    setupapi.dev.log
    Event logs (*.evtx)

    9) Power on the computer and repetitively click the F2 key. View the HP UEFI hardware diagnostics. If available run the loop until failure or extensive tests overnight. The next day if the loop until failure is still running that is a good sign. If there has been at least 2 runs then press the keyboard escape key to abort the testing. If there was a failure there will be a HP code. The code can only be decoded by HP. Post the results of the HP UEFI hardware diagnostics loop until failure tests into the thread.
      My ComputerSystem Spec

  5.    04 Dec 2017 #5

    Microsoft Windows [Version 10.0.10586](c) 2015 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>scf/scannow'scf' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>sfc/scannowBeginning 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.C:\WINDOWS\system32>dism/online/cleanup-image/restorehealthDeployment Image Servicing and Management toolVersion: 10.0.10586.0Error: 87The online/cleanup-image/restorehealth option is unknown.For more information, refer to the help by running DISM.exe /?.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>dism/online/clean-up/restorehealthDeployment Image Servicing and Management toolVersion: 10.0.10586.0Error: 87The online/clean-up/restorehealth option is unknown.For more information, refer to the help by running DISM.exe /?.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>chkdsk/scanThe type of the file system is NTFS.Volume label is WIN10_SSD.Stage 1: Examining basic file system structure ... 419584 file records processed. File verification completed. 22555 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 512212 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 46315 data files processed.CHKDSK is verifying Usn Journal... 34908072 USN bytes processed. Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 115210239 KB total disk space. 45120108 KB in 217858 files. 179728 KB in 46316 indexes. 0 KB in bad sectors. 532435 KB in use by the system. 65536 KB occupied by the log file. 69377968 KB available on disk. 4096 bytes in each allocation unit. 28802559 total allocation units on disk. 17344492 allocation units available on disk.

    C:\WINDOWS\system32>C:\WINDOWS\system32>windows updates'windows' is not recognized as an internal or external command,operable program or batch file.

    C:\WINDOWS\system32>


    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

    Click image for larger version. 

Name:	image.png 
Views:	31 
Size:	43.7 KB 
ID:	166804


    HPPAVILLON-Mon_12_04_2017_221646_14.zip

    Click image for larger version. 

Name:	image.png 
Views:	3 
Size:	89.8 KB 
ID:	166808

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	113.3 KB 
ID:	166807
    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	127.0 KB 
ID:	166806
      My ComputerSystem Spec


  6. Posts : 14,123
    windows 10 professional version 1607 build 14393.969 64 bit
       05 Dec 2017 #6

    The about Windows image displayed Windows 10 version 1511.
    The 1511 indicates November 2015.
    Since 1511 there have been available upgrades to 1607, 1703, and 1711.

    The logs reported problems with the Video and the Drive.
    The problems include: bad block, frequent paging errors.


    There appears to be a BIOS update.
    Please double check the HP website using the computer's product or serial number to make sure the proper BIOS update is performed:

    In the link there was a BIOS update from 2013 > 2014
    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support
    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

    Please enter again the computers product or serial number and make sure that this is or is not the BIOS update:
    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support
    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

    Open administrative command prompt and copy and paste these commands:
    1) dism /online /cleanup-image /scanhealth
    2) dism /online /cleanup-image /restorehealth
    3) 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
    4) chkdsk /x /f /r
    This may take many hours to complete so plan to run overnight.

    C:\Windows\system32>chkdsk /x /f /r
    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

    Perform chkdsk /x /f /r on each partition: use the syntax: chkdsk /x /f /r C: or chkdsk /x /f /r D: changing c or d to the applicable drive letter.

    5) Find and post the chkdsk report from the event viewer using the information in this link:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
    6) Run HDTune: http://www.hdtune.com/
    to check the health,
    scan for errors, no quick scan but full scan
    run a benchmark.
    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    the health,
    the error scan,
    the benchmark incl. following
    transfer rate,
    access time,
    burst rate,
    cpu usage.
    Take Screenshot in Windows 10 General Tips Tutorials

    4) In March 2017 there was a BSOD with bugcheck 116 VIDEO TDR error.
    How was this problem worked up and fixed?

    5) Crashes were noted on 12/3; 11/11; 10/29; 10/21; 10/2; 8/25; 8/2; 4/25; 3/30. etc.
    Were these worked up?

    6) Windows error reporting displayed additional bugchecks of
    117 VIDEO TDR timeout detected
    141 VIDEO engine timeout detected
    Were these worked up?

    7) When you update the system specs in the "My Computer" section please include information about the PSU, cooler, case, and any peripherals attached to the computer by wired or wireless (mouse, keyboard, printer, headset, xbox, etc.)

    8) Please report into the thread the results of the HP UEFI hardware diagnostics.

    9) Run Sea tools for windows on your drive using long generic tests:

    How to use SeaTools for Windows
    http://www.seagate.com/support/downl...ls-win-master/
    How to use SeaTools for Windows
    http://www.seagate.com/support/downloads/seatools/






    Code:
    Event[28387]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28388]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28389]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28390]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28391]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28392]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28393]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28394]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28395]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28396]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28397]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28398]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28399]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28400]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28401]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28402]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28403]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28404]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28405]:  Log Name: System  Source: disk  Date: 2017-08-17T12:57:19.542  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.
    Code:
    Event[28407]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28408]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28409]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28410]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28411]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28412]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28413]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28414]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28415]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28416]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28417]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28418]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28419]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28420]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.041  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28421]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28422]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28423]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28424]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28425]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28426]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28427]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28428]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28429]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28430]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28431]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28432]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28433]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28434]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.Event[28435]:  Log Name: System  Source: disk  Date: 2017-08-17T12:58:30.042  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: An error was detected on device \Device\Harddisk2\DR10 during a paging operation.
    Code:
    Event[20296]:
      Log Name: System  Source: cdrom  Date: 2017-05-01T12:25:56.756  Event ID: 7  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: The device, \Device\CdRom1, has a bad block.
    Code:
    Event[35882]:  Log Name: System  Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler  Date: 2017-11-10T10:51:31.230  Event ID: 1001  Task: N/A  Level: Information  Opcode: Info  Keyword: N/A  User: S-1-5-21-1743798673-2050909126-3179886638-1001  User Name: HPPAVILLON\Cozmic  Computer: HPPavillon  Description: Windows removed bad memory regions from this PC.
    Code:
    Event[38663]:  Log Name: System  Source: disk  Date: 2017-11-23T16:06:39.022  Event ID: 7  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: The device, \Device\Harddisk2\DR5, has a bad block.
    Code:
    Event[30121]:  Log Name: System  Source: Display  Date: 2017-09-12T01:22:26.037  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: Display driver amdkmdap stopped responding and has successfully recovered.
    Code:
    Event[30438]:  Log Name: System  Source: Display  Date: 2017-09-15T11:04:13.425  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: Display driver amdkmdap stopped responding and has successfully recovered.
    Code:
    Event[30936]:  Log Name: System  Source: Display  Date: 2017-09-23T12:10:52.213  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: Display driver amdkmdap stopped responding and has successfully recovered.
    Code:
    Event[41716]:  Log Name: System  Source: storahci  Date: 2017-12-04T21:57:30.129  Event ID: 129  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: HPPavillon  Description: Reset to device, \Device\RaidPort0, was issued.
    Code:
    7/2/2017 3:12 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: d7b34602-34b2-433c-bda8-846cdde01f87
    
    Problem signature:
    P1: 141
    P2: ffffe000749ae010
    P3: fffff801a551cc54
    P4: 0
    P5: 2218
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170701-2304.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-1098341671-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER6064.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_e3ffddddf9f8453dfa62f5a37868ad8379c1e_00000000_cab_62527476
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 26672a36-5ed3-11e7-bebe-78e3b5bb020f
    Report Status: 0
    Hashed bucket:8/11/2017 10:22 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: c4c14ff1-5cc3-4120-94b3-7a54a0af3fe7
    
    Problem signature:
    P1: 141
    P2: ffffe001e3c4f4c0
    P3: fffff801f369cc54
    P4: 0
    P5: 1b64
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170811-1822.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-806237968-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER3A2D.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_383623a56322d182ca611abf2bcd37d81b9148_00000000_cab_205e50d2
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 914c4e51-7ee3-11e7-bec2-78e3b5bb020f
    Report Status: 0
    Hashed bucket:7/2/2017 3:04 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: b56c1690-78f6-4823-b1d2-4a717df5cc1a
    
    Problem signature:
    P1: 141
    P2: ffffe000717cb010
    P3: fffff801a551cc54
    P4: 0
    P5: 2218
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170701-2304-01.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-1098341109-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER5C5C.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_6ad5cfe321a23c66b48063e1d639d996c8b06bee_00000000_cab_5213788f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 26106872-5ed3-11e7-bebe-78e3b5bb020f
    Report Status: 0
    Hashed bucket:5/22/2017 4:50 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: b1623e82-766b-41c3-85aa-d7202ef93b83
    
    Problem signature:
    P1: 141
    P2: ffffe000e46ff4c0
    P3: fffff80074e9cc54
    P4: 0
    P5: 3c8
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170522-0007.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-17764765-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER1288.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8e26b86e7ceef9bd187c86e450c5262c7ab66_00000000_cab_2581a6ef
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3f9067cd-3ea4-11e7-bebb-78e3b5bb020f
    Report Status: 0
    Hashed bucket:9/12/2017 5:22 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: b14f6fda-ce82-4b5f-8cea-716cb2d3962c
    
    Problem signature:
    P1: 141
    P2: ffffe001f1807010
    P3: fffff8004170cc54
    P4: 0
    P5: 1994
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170912-0122.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-1478144187-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WERB1E4.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_18df51d2b223286a963e86bea52eeac19cc72_00000000_cab_7e8ed2ab
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 5be303ea-977a-11e7-bec4-78e3b5bb020f
    Report Status: 0
    Hashed bucket:9/15/2017 3:04 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 8394229f-4737-4fea-91b5-269c785399ec
    
    Problem signature:
    P1: 141
    P2: ffffe001dc4ce4c0
    P3: fffff8004170cc54
    P4: 0
    P5: 1f60
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170915-1104.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-1772251468-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER6A56.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_9409d9350ab9b4258391a3f77627d332667875_00000000_cab_7e928c55
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 217c6420-9a27-11e7-bec4-78e3b5bb020f
    Report Status: 0
    Hashed bucket:6/16/2017 3:48 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 80a2cdd2-226a-4da9-b269-236ebef0e8fc
    
    Problem signature:
    P1: 141
    P2: ffffe0009a57f4c0
    P3: fffff801ac34cc54
    P4: 0
    P5: 1668
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170616-1148.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-1381465765-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER7FED.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_15c77d85c484da3151fc148e2972aba7c162fc1_00000000_cab_753b94dd
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 4bda9a38-52ab-11e7-bebd-78e3b5bb020f
    Report Status: 0
    Hashed bucket:9/23/2017 4:10 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 7052e2d1-e138-4184-91e3-ef38fb7acf3e
    
    Problem signature:
    P1: 141
    P2: ffffe000310bb010
    P3: fffff801914dcc54
    P4: 0
    P5: 710
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170923-1210.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-399103968-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WERD8FA.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_80e315ea43525fe06d9e931301842403e12f467_00000000_cab_038df21f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c440cd5e-a079-11e7-bec5-78e3b5bb020f
    Report Status: 0
    Hashed bucket:6/25/2017 6:32 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 53514563-b3fc-4db9-a9b7-7908834ca92f
    
    Problem signature:
    P1: 141
    P2: ffffe0006f7e44c0
    P3: fffff801a551cc54
    P4: 0
    P5: 16b8
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170625-1432.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-549211468-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER4E56.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_ba9330f0b17f82deb23aeb50cc531a2fba712be_00000000_cab_3b7c7c0d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 9b4c416c-59d4-11e7-bebe-78e3b5bb020f
    Report Status: 0
    Hashed bucket:8/11/2017 10:57 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 3dd73c2b-5e82-40e5-9aaf-cb3c7a41258e
    
    Problem signature:
    P1: 141
    P2: ffffe001e3c4f4c0
    P3: fffff801f369cc54
    P4: 0
    P5: 970
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170811-1857.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-808332265-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER2D22.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_f0c012a322d154fd6193689970a5e7dfa6ba9a84_00000000_cab_20725a9a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 7199190a-7ee8-11e7-bec2-78e3b5bb020f
    Report Status: 0
    Hashed bucket:6/28/2017 2:03 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 3b7c1fe8-076e-4245-8178-8c043d770c52
    
    Problem signature:
    P1: 141
    P2: ffffe00070fc54c0
    P3: fffff801a551cc54
    P4: 0
    P5: 2020
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170627-2203.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-749102968-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER6872.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_539535ace86c58e2c8462403e1958378e5eea58_00000000_cab_3bf27d23
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 03e94a72-5ba6-11e7-bebe-78e3b5bb020f
    Report Status: 0
    Hashed bucket:8/11/2017 11:17 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 304d0684-db6d-425e-afcc-c9cee2d2740b
    
    Problem signature:
    P1: 141
    P2: ffffe001e3c4f4c0
    P3: fffff801f369cc54
    P4: 0
    P5: 236c
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170811-1917.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-809532203-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER7C54.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_4a6cb8d12a2c5cdc9b4425d337698d6df1465_00000000_cab_32f09143
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3cd207e2-7eeb-11e7-bec2-78e3b5bb020f
    Report Status: 0
    Hashed bucket:6/30/2017 6:01 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 1d41e962-8145-4c3f-af77-de0cd7b127ed
    
    Problem signature:
    P1: 141
    P2: ffffe00073cc9010
    P3: fffff801a551cc54
    P4: 0
    P5: 1730
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170630-1401.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-979343015-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER9792.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_809527a7ac7ee85635c6c36ecf4dcbb193a542_00000000_cab_235bab58
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 15ad0e30-5dbe-11e7-bebe-78e3b5bb020f
    Report Status: 0
    Hashed bucket:6/23/2017 11:24 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 1c941cfa-05f4-43af-bcf2-4d648fa546cb
    
    Problem signature:
    P1: 141
    P2: ffffe0006dd3d4c0
    P3: fffff801a551cc54
    P4: 0
    P5: 8fc
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170623-0724.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-350744890-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WERF253.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_53978c607494c8ca5be217ebbba6f048b08544_00000000_cab_303c0714
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 76a03b9f-5806-11e7-bebe-78e3b5bb020f
    Report Status: 0
    Hashed bucket:7/2/2017 3:12 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:9_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: cc951a26-d9dc-462f-bb42-9dd105eff1cc
    
    Problem signature:
    P1: 117
    P2: ffffe00071f24010
    P3: fffff801a551cc54
    P4: 0
    P5: 0
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170701-2304-02.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-1098342031-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER60B2.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_b4a7ccd66c4dba88c6819b5996b9be98961f24cc_00000000_cab_62528464
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 269ddfdc-5ed3-11e7-bebe-78e3b5bb020f
    Report Status: 0
    Hashed bucket:5/22/2017 4:08 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 8478fd70-6722-4c3a-a055-a786ff50a569
    
    Problem signature:
    P1: 117
    P2: ffffe000eb99a4c0
    P3: fffff80074e9cc54
    P4: 0
    P5: 3c8
    P6: 10_0_10586
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20170522-0007-01.dmp
    C:\Users\Cozmic\AppData\Local\Temp\WER-17760656-0.sysdata.xml
    C:\Users\Cozmic\AppData\Local\Temp\WER48D.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_cb397cbdf358c5a061186e912fc1ee11dcbacef_00000000_cab_0c5f3dfd
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3d18afe8-3ea4-11e7-bebb-78e3b5bb020f
    Report Status: 0
    Hashed bucket:
    Code:
    Event[41717]:  Log Name: System
      Source: disk
      Date: 2017-12-04T21:57:30.129
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: HPPavillon
      Description: 
    The IO operation at logical block address 0x717c00 for Disk 0 (PDO name: \Device\00000026) was retried.
    Last edited by zbook; 05 Dec 2017 at 00:57.
      My ComputerSystem Spec

  7.    05 Dec 2017 #7

    Thanks guys for the info
    but
    The machine has been working OK for years -- doing updates when asked
    a 8GB DIMM showed problems ---- pulled it out

    I did not think I needed to do computer MRI and colonoscopy
    just to get it to stop demanding to update

    Perhaps best to post video of bullet going thru it

    Thanks
      My ComputerSystem Spec

  8.    07 Dec 2017 #8

    My sympathies, Cozmicray. Reminds me of the old saw "Don't ask the question unless you are truly prepared to hear the answer!" From what you've posted about the target machine, there are some moderately serious issues in need of investigation and fixing. Hope you can find the time and expend the effort necessary to get things straightened out. We're here to help with input and advice should you need it. Best wishes,
    --Ed--
      My ComputersSystem Spec


 

Related Threads
Fall Creators Update fails to install in Installation and Upgrade
Attempted from 16299.15 ISO. Suspect something to do with AMD 17.7.2 driver (latest for this system) since it aborts at 33%. 158288 Edit: Today I did a clean install of Windows 10 Pro 16299.15 on a unused partition. It installed with any...
Since the Fall Update (2017) installed, the folders I have pinned to the File Explorer icon on my taskbar do not launch. I tried unpinning and then repinning but it made no difference. I also pinned a new folder which was never pinned before and it...
UPDATE 10/17: How to get the Windows 10 Fall Creators Update - Windows 10 Forums Source: Create and play this holiday with the Windows 10 Fall Creators Update coming Oct. 17 - Windows Experience Blog See also: Windows 10 Fall Creators...
Source: Build 2017: Sparking the next wave of creativity with the Windows 10 Fall Creators Update - Windows Experience Blog
Bing Maps V8 SDK Fall Update in Windows 10 News
Source: http://blogs.bing.com/maps/January-2017/Bing-Maps-V8-SDK-Fall-Update
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 02:58.
Find Us