Is it 100% certain my hard drive is failing?

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #11

    1) The logs displayed drive file system corruption and BSOD.
    2) There was a recent startup repair

    3) In the "My Computer" section please update the specifications to display: HP ENVY All-in-One - 24-n020qe CTO (Touch)

    4) The BIOS: Version/Date AMI A0.06, 9/21/2015

    Upgrade the BIOS: A0.06 > A0.13 Rev.A
    Driver - HP ENVY All-in-One - 24-n020qe CTO (Touch) | HP® Customer Support

    5) Run the HP Support Assistant > update drivers > report into the thread any drivers that were updated

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

    11) Download and install Everything: voidtools

    12) Use everything to search for: win32k.sys-20181210-1210.dmp
    Zip the file then post a share link into the thread using one drive, drop box, or google drive

    Code:
    win32k.sys-20181210-1210.dmp 12/10/2018 12:10:25 PM   1093.83

    13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    14) Open control panel > large or small icons > click troubleshooting > on the left pane click view all > run the search and indexing troubleshooter by clicking advanced > run as administrator






    Code:
    Event[7006]:
      Log Name: System
      Source: Ntfs
      Date: 2018-12-21T15:26:37.319
      Event ID: 55
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-72015KU
      Description: 
    A corruption was discovered in the file system structure on volume Windows.
    
    The exact nature of the corruption is unknown.  The file system structures need to be scanned and fixed offline.
    Code:
    Event[9589]:
      Log Name: System
      Source: Ntfs
      Date: 2018-12-27T19:48:48.340
      Event ID: 55
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-72015KU
      Description: 
    A corruption was discovered in the file system structure on volume C:.
    
    A corruption was found in a file system index structure.  The file reference number is 0x9000000000009.  The name of the file is "<unable to determine file name>".  The corrupted index attribute is ":$SII:$INDEX_ALLOCATION".
    Code:
    Event[9602]:
      Log Name: System
      Source: Ntfs
      Date: 2018-12-27T19:48:48.984
      Event ID: 55
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-72015KU
      Description: 
    A corruption was discovered in the file system structure on volume C:.
    
    A corruption was found in a file system index structure.  The file reference number is 0x9000000000009.  The name of the file is "<unable to determine file name>".  The corrupted index attribute is ":$SII:$INDEX_ALLOCATION".
    Code:
    Event[9785]:
      Log Name: System
      Source: Service Control Manager
      Date: 2018-12-27T21:14:05.569
      Event ID: 7034
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-72015KU
      Description: 
    The Windows Search service terminated unexpectedly.  It has done this 34 time(s).
    Code:
    Event[9932]:
      Log Name: System
      Source: Microsoft-Windows-StartupRepair
      Date: 2018-12-27T21:21:09.395
      Event ID: 1104
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-72015KU
      Description: 
    The system volume was corrupt.
    
    Event[9933]:
      Log Name: System
      Source: Microsoft-Windows-StartupRepair
      Date: 2018-12-27T21:21:09.395
      Event ID: 1204
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-72015KU
      Description: 
    Repaired file system errors.
      My Computer


  2. Posts : 76
    Windows 10
    Thread Starter
       #12

    zbook said:
    1) The logs displayed drive file system corruption and BSOD.
    2) There was a recent startup repair

    3) In the "My Computer" section please update the specifications to display: HP ENVY All-in-One - 24-n020qe CTO (Touch)
    Thank you for the help.

    Below are the results for everything I have done.

    - I have not updated the BIOS. I was concerned about the risk of bricking the hard drive. The fixes seem minor. Is it 100% safe to update the BIOS?

    - I have not run the HP component test yet. Will do that tonight.

    Here are the results.

    5) Launch HP PC Hardware Diagnostics Windows version 1.5.4.0

    a) Click system tests > system extensive test > run once > plan to run overnight > in the AM check the logs > post an image into the thread

    The logs opened in a Window that needed to be scrolled so I copied them.



    ** Test Logs - Long Drive Self-Test


    PollTime:10s LongDST passed: SAMSUNG MZHPV128HDGM-000H1, S1WYNYAH106394 LongDST passed: HGST HTS541010A9E680, JD100A1V3MSHTM


    ** Test Logs - Disk Read Verify - Disk_1_HGST HTS541010A9E680


    TestStarted. DeviceID: \\.\PHYSICALDRIVE0 BytesPerSector: 512 Reading 50000 sectors. UpdatePercentage 10 UpdatePercentage 20 UpdatePercentage 30 UpdatePercentage 40 UpdatePercentage 50 UpdatePercentage 60 UpdatePercentage 70 UpdatePercentage 80 UpdatePercentage 90 UpdatePercentage 100 Average reads per second: 11174 TestPassed. EndOfTest TestStarted. DeviceID: \\.\PHYSICALDRIVE1 BytesPerSector: 512 Reading 50000 sectors. UpdatePercentage 10 UpdatePercentage 20 UpdatePercentage 30 UpdatePercentage 40 UpdatePercentage 50 UpdatePercentage 60 UpdatePercentage 70 UpdatePercentage 80 UpdatePercentage 90 UpdatePercentage 100 Average reads per second: 14409 TestPassed. EndOfTest


    ** Test Logs - Video Extended Memory Check


    LogMessage Debug diagnostic: C:\Users\Administrator\AppData\Local\Temp\n210j520.i3k\video-diags.exe "" LogMessage Debug version: 8.7.0, timestamp: Aug 29 2018 15:03:30 1534, cdm: 8.10.0, ms: 8.3.0 "" LogMessage Debug -subtest=VideoMemoryTest "" LogMessage Debug -locale=en "" LogMessage Debug -debug=true "" LogMessage Debug -version=false "" LogMessage Debug -description=false "" LogMessage Debug -help=false "" LogMessage Debug -catalog=false "" LogMessage Debug -diagconf=.\diagconf.ini "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -ActivateDiscreteGPU=false "" LogMessage Debug -Caption= "" LogMessage Debug -DataCollectionFile= "" LogMessage Debug -DeviceID=0 "" LogMessage Debug -HighMode=true "" LogMessage Debug -Retries=1 "" LogMessage Debug -integratormsgfile= "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -tiledpopups= "" LogMessage Debug -tiledpopupsbutton= "" LogMessage Debug -tiledpopupsnofocus= "" UpdatePercentage 0 LogMessage Debug Completed in 31ms "" UpdatePercentage 1 LogMessage Debug Completed in 0ms "" LogMessage Subtests Test started. "" UpdatePercentage 10 LogMessage Debug Completed in 0ms "" LogMessage Debug Display Mode:3840x2160x32 "" UpdatePercentage 55 LogMessage Debug Completed in 781ms "" UpdatePercentage 60 LogMessage Debug Completed in 1016ms "" UpdatePercentage 65 LogMessage Debug Completed in 1015ms "" UpdatePercentage 70 LogMessage Debug Completed in 4047ms "" UpdatePercentage 80 LogMessage Debug Completed in 1016ms "" UpdatePercentage 85 LogMessage Debug Completed in 1219ms "" LogMessage Status MemoryPitch 15360 "" LogMessage Status ScreenPitch 7680 "" UpdatePercentage 86 LogMessage Debug Completed in 343ms "" LogMessage Status fixed pattern testing "" UpdatePercentage 88 LogMessage Debug Completed in 16ms "" UpdatePercentage 89 LogMessage Debug Completed in 31ms "" UpdatePercentage 90 LogMessage Debug Completed in 16ms "" UpdatePercentage 91 LogMessage Debug Completed in 31ms "" UpdatePercentage 92 LogMessage Debug Completed in 16ms "" UpdatePercentage 93 LogMessage Debug Completed in 31ms "" UpdatePercentage 94 LogMessage Debug Completed in 31ms "" UpdatePercentage 95 LogMessage Debug Completed in 32ms "" UpdatePercentage 95 LogMessage Debug Completed in 0ms "" LogMessage Subtests Test passed. "" UpdatePercentage 100 LogMessage Debug Completed in 3046ms "" LogMessage Debug Test execution time: 12687 milliseconds "" EndOfTest


    ** Test Logs - IRQ Test


    LogMessage Debug diagnostic: C:\Users\Administrator\AppData\Local\Temp\jroefttb.325\net-diags.exe "" LogMessage Debug version: 8.4.1, timestamp: Oct 2 2018 11:20:56 1534, cdm: 8.11.0, net: 8.0.0, ms: 8.3.0 "" LogMessage Debug -subtest=IRQTest "" LogMessage Debug -locale=en "" LogMessage Debug -debug=true "" LogMessage Debug -version=false "" LogMessage Debug -description=false "" LogMessage Debug -help=false "" LogMessage Debug -catalog=false "" LogMessage Debug -diagconf=.\diagconf.ini "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -Caption= "" LogMessage Debug -DataCollectionFile= "" LogMessage Debug -DeviceDescription=Realtek PCIe GBE Family Controller "" LogMessage Debug -DeviceID= "" LogMessage Debug -Index=1 "" LogMessage Debug -Retries=2 "" LogMessage Debug -TestRepeats=1 "" LogMessage Debug -integratormsgfile=.\net-diags.msg "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -tiledpopups= "" LogMessage Debug -tiledpopupsbutton= "" LogMessage Debug -tiledpopupsnofocus= "" UpdatePercentage 0 LogMessage Debug Completed in 31ms "" UpdatePercentage 1 LogMessage Debug Completed in 0ms "" LogMessage Subtests Test started "" UpdatePercentage 5 LogMessage Debug Completed in 78ms "" UpdatePercentage 10 LogMessage Debug Completed in 0ms "" UpdatePercentage 20 LogMessage Debug Completed in 0ms "" LogMessage Debug IRQ Number is 1 "" UpdatePercentage 80 LogMessage Debug Completed in 31ms "" UpdatePercentage 90 LogMessage Debug Completed in 0ms "" LogMessage Subtests Test passed "" UpdatePercentage 100 LogMessage Debug Completed in 0ms "" LogMessage Debug Test execution time: 109 milliseconds "" EndOfTest LogMessage Debug diagnostic: C:\Users\Administrator\AppData\Local\Temp\jroefttb.325\net-diags.exe "" LogMessage Debug version: 8.4.1, timestamp: Oct 2 2018 11:20:56 1534, cdm: 8.11.0, net: 8.0.0, ms: 8.3.0 "" LogMessage Debug -subtest=IRQTest "" LogMessage Debug -locale=en "" LogMessage Debug -debug=true "" LogMessage Debug -version=false "" LogMessage Debug -description=false "" LogMessage Debug -help=false "" LogMessage Debug -catalog=false "" LogMessage Debug -diagconf=.\diagconf.ini "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -Caption= "" LogMessage Debug -DataCollectionFile= "" LogMessage Debug -DeviceDescription=Intel(R) Dual Band Wireless-AC 7265 "" LogMessage Debug -DeviceID= "" LogMessage Debug -Index=1 "" LogMessage Debug -Retries=2 "" LogMessage Debug -TestRepeats=1 "" LogMessage Debug -integratormsgfile=.\net-diags.msg "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -tiledpopups= "" LogMessage Debug -tiledpopupsbutton= "" LogMessage Debug -tiledpopupsnofocus= "" UpdatePercentage 0 LogMessage Debug Completed in 16ms "" UpdatePercentage 1 LogMessage Debug Completed in 0ms "" LogMessage Subtests Test started "" UpdatePercentage 5 LogMessage Debug Completed in 62ms "" UpdatePercentage 10 LogMessage Debug Completed in 0ms "" UpdatePercentage 20 LogMessage Debug Completed in 0ms "" LogMessage Debug IRQ Number is 1 "" UpdatePercentage 80 LogMessage Debug Completed in 32ms "" UpdatePercentage 90 LogMessage Debug Completed in 0ms "" LogMessage Subtests Test passed "" UpdatePercentage 100 LogMessage Debug Completed in 0ms "" LogMessage Debug Test execution time: 94 milliseconds "" EndOfTest


    ** Test Logs - ROM Test


    LogMessage Debug diagnostic: C:\Users\Administrator\AppData\Local\Temp\zwxloery.lu0\net-diags.exe "" LogMessage Debug version: 8.4.1, timestamp: Oct 2 2018 11:20:56 1534, cdm: 8.11.0, net: 8.0.0, ms: 8.3.0 "" LogMessage Debug -subtest=ROMTest "" LogMessage Debug -locale=en "" LogMessage Debug -debug=true "" LogMessage Debug -version=false "" LogMessage Debug -description=false "" LogMessage Debug -help=false "" LogMessage Debug -catalog=false "" LogMessage Debug -diagconf=.\diagconf.ini "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -Caption= "" LogMessage Debug -DataCollectionFile= "" LogMessage Debug -DeviceDescription=Realtek PCIe GBE Family Controller "" LogMessage Debug -DeviceID= "" LogMessage Debug -EEPROMSize=64 "" LogMessage Debug -Index=1 "" LogMessage Debug -Retries=2 "" LogMessage Debug -TestRepeats=1 "" LogMessage Debug -VerifyCheckSum=false "" LogMessage Debug -VerifyInvalidMACPattern=false "" LogMessage Debug -VerifyMAC=false "" LogMessage Debug -VerifyMACRange=false "" LogMessage Debug -integratormsgfile=.\net-diags.msg "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -tiledpopups= "" LogMessage Debug -tiledpopupsbutton= "" LogMessage Debug -tiledpopupsnofocus= "" LogMessage ServiceErrors Test parameters VerifyMAC, VerifyChecksum, and EEPROMSize are not being used in this test and are being ignored. "" LogMessage Subtests Test started "" UpdatePercentage 5 LogMessage Debug Completed in 93ms "" UpdatePercentage 10 LogMessage Debug Completed in 0ms "" LogMessage Debug Realtek PCIe GBE Family Controller "" UpdatePercentage 20 LogMessage Debug Completed in 79ms "" LogMessage Debug MAC Adrress detected is C0-7C-D1-A3-E4-75. "" UpdatePercentage 30 LogMessage Debug Completed in 78ms "" UpdatePercentage 40 LogMessage Debug Completed in 0ms "" LogMessage Debug MACAddres is valid. "" UpdatePercentage 60 LogMessage Debug Completed in 0ms "" UpdatePercentage 80 LogMessage Debug Completed in 0ms "" UpdatePercentage 90 LogMessage Debug Completed in 0ms "" LogMessage Subtests Test passed "" UpdatePercentage 100 LogMessage Debug Completed in 0ms "" LogMessage Debug Test execution time: 219 milliseconds "" EndOfTest LogMessage Debug diagnostic: C:\Users\Administrator\AppData\Local\Temp\zwxloery.lu0\net-diags.exe "" LogMessage Debug version: 8.4.1, timestamp: Oct 2 2018 11:20:56 1534, cdm: 8.11.0, net: 8.0.0, ms: 8.3.0 "" LogMessage Debug -subtest=ROMTest "" LogMessage Debug -locale=en "" LogMessage Debug -debug=true "" LogMessage Debug -version=false "" LogMessage Debug -description=false "" LogMessage Debug -help=false "" LogMessage Debug -catalog=false "" LogMessage Debug -diagconf=.\diagconf.ini "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -Caption= "" LogMessage Debug -DataCollectionFile= "" LogMessage Debug -DeviceDescription=Intel(R) Dual Band Wireless-AC 7265 "" LogMessage Debug -DeviceID= "" LogMessage Debug -EEPROMSize=64 "" LogMessage Debug -Index=1 "" LogMessage Debug -Retries=2 "" LogMessage Debug -TestRepeats=1 "" LogMessage Debug -VerifyCheckSum=false "" LogMessage Debug -VerifyInvalidMACPattern=false "" LogMessage Debug -VerifyMAC=false "" LogMessage Debug -VerifyMACRange=false "" LogMessage Debug -integratormsgfile=.\net-diags.msg "" LogMessage Debug -paramfile= "" LogMessage Debug -paramsection= "" LogMessage Debug -tiledpopups= "" LogMessage Debug -tiledpopupsbutton= "" LogMessage Debug -tiledpopupsnofocus= "" LogMessage ServiceErrors Test parameters VerifyMAC, VerifyChecksum, and EEPROMSize are not being used in this test and are being ignored. "" LogMessage Subtests Test started "" UpdatePercentage 5 LogMessage Debug Completed in 94ms "" UpdatePercentage 10 LogMessage Debug Completed in 0ms "" LogMessage Debug Intel(R) Dual Band Wireless-AC 7265 "" UpdatePercentage 20 LogMessage Debug Completed in 62ms "" LogMessage Debug MAC Adrress detected is 48-45-20-7D-0A-14. "" UpdatePercentage 30 LogMessage Debug Completed in 63ms "" UpdatePercentage 40 LogMessage Debug Completed in 0ms "" LogMessage Debug MACAddres is valid. "" UpdatePercentage 60 LogMessage Debug Completed in 0ms "" UpdatePercentage 80 LogMessage Debug Completed in 0ms "" UpdatePercentage 90 LogMessage Debug Completed in 0ms "" LogMessage Subtests Test passed "" UpdatePercentage 100 LogMessage Debug Completed in 16ms "" LogMessage Debug Test execution time: 219 milliseconds "" EndOfTest


    ** Test Logs - CPU Stress Test


    LogMessage 14 20000 "diagnostic: C:\Users\Administrator\AppData\Local\Temp\clqdnttf.ls4\stress-diags.exe" "" LogMessage 14 20000 "version: 8.7.0, timestamp: Aug 29 2018 15:03:35 1534, cdm: 8.10.0, ms: 8.3.0" "" LogMessage 14 20000 "-subtest=ProcessorStressTest" "" LogMessage 14 20000 "-locale=en_US" "" LogMessage 14 20000 "-debug=false" "" LogMessage 14 20000 "-version=false" "" LogMessage 14 20000 "-description=false" "" LogMessage 14 20000 "-help=false" "" LogMessage 14 20000 "-catalog=false" "" LogMessage 14 20000 "-diagconf=.\diagconf.ini" "" LogMessage 14 20000 "-paramfile=" "" LogMessage 14 20000 "-paramsection=" "" LogMessage 14 20000 "-Caption=" "" LogMessage 14 20000 "-DataCollectionFile=" "" LogMessage 14 20000 "-LogicalProc=" "" LogMessage 14 20000 "-TestTime=2" "" LogMessage 14 20000 "-integratormsgfile=" "" LogMessage 14 20000 "-paramfile=" "" LogMessage 14 20000 "-paramsection=" "" LogMessage 14 20000 "-tiledpopups=" "" LogMessage 14 20000 "-tiledpopupsbutton=" "" LogMessage 14 20000 "-tiledpopupsnofocus=" "" UpdatePercentage 0 LogMessage 14 8 "Completed in 15ms" "" LogMessage 3 2 "" "" LogMessage 14 58 "8" "" LogMessage 14 69 "8" "" UpdatePercentage 1 LogMessage 14 8 "Completed in 1375ms" "" UpdatePercentage 8 LogMessage 14 8 "Completed in 16094ms" "" UpdatePercentage 25 LogMessage 14 8 "Completed in 16313ms" "" UpdatePercentage 33 LogMessage 14 8 "Completed in 16297ms" "" UpdatePercentage 50 LogMessage 14 8 "Completed in 16203ms" "" UpdatePercentage 66 LogMessage 14 8 "Completed in 16390ms" "" UpdatePercentage 75 LogMessage 14 8 "Completed in 16469ms" "" LogMessage 14 45 "96" "" LogMessage 14 46 "5" "" UpdatePercentage 100 LogMessage 14 8 "Completed in 33047ms" "" LogMessage 3 3 "" "" LogMessage 14 20000 "Test execution time: 132188 milliseconds" "" EndOfTest 90 UpdatePercentage 100 Average reads per second: 14409 TestPassed. EndOfTest

    5) Run the HP Support Assistant > update drivers > report into the thread any drivers that were updated

    Is it 100% certain my hard drive is failing?-screenshot-293-.png

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

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


    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 found corrupt files and successfully repaired them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.


    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth


    Deployment Image Servicing and Management tool
    Version: 10.0.17134.1


    Image Version: 10.0.17134.472


    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.


    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    Volume label is Windows.


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


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


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


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


    123530239 KB total disk space.
    87014508 KB in 365538 files.
    244564 KB in 69748 indexes.
    0 KB in bad sectors.
    678183 KB in use by the system.
    65536 KB occupied by the log file.
    35592984 KB available on disk.


    4096 bytes in each allocation unit.
    30882559 total allocation units on disk.
    8898246 allocation units available on disk.


    C:\WINDOWS\system32>
    12) Use everything to search for: win32k.sys-20181210-1210.dmp
    Zip the file then post a share link into the thread using one drive, drop box, or google drive

    Code:
    win32k.sys-20181210-1210.dmp 12/10/2018 12:10:25 PM 1093.83


    There were 2 such files.

    https://drive.google.com/open?id=1zABtb8t5SsLz8KuE9KVpBmdWc0W5jotj

    win32k.sys-20181210-1210.dmp - Google Drive

    13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    Is it 100% certain my hard drive is failing?-screenshot-291-.png

    The other one.

    Is it 100% certain my hard drive is failing?-screenshot-292-.png

    Search and indexing coming up
    Last edited by jwblue; 30 Dec 2018 at 20:08.
      My Computer


  3. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #13

    For the posts in the thread.

    Click edit.
    Then re-post the information.
    (not copy and paste of the existing post but copy and paste of the original information from the source)

    The second time the information is posted (after the edit) it should appear readable.

    For anything that does not post properly another option is to use share links: one drive, drop box, or google drive
      My Computer


  4. Posts : 76
    Windows 10
    Thread Starter
       #14

    Search and indexing results.

    For some reason I could print the results. Had to copy and paste.

    PrintSearch and Indexing Publisher details


    Potential issues that were checked
    Incorrect permissions on Windows Search directoriesIncorrect permissions on Windows Search directories
    When permissions on the Windows Search data directories are set incorrectly, the search service might not be able to access or update the computer's search index. This can result in slow searches or incomplete search results. Issue not present
    Search Filter Host process failedSearch Filter Host process failed
    Problems with the Search Filter Host might indicate errors in the Windows Search service, which can cause searches to fail or return incomplete search results. Issue not present
    Windows Search service shut down unexpectedlyWindows Search service shut down unexpectedly
    When the Windows Search service is forcibly shut down while performing maintenance, searches might fail or return incomplete search results. Issue not present
    Windows Search service shut down unexpectedlyWindows Search service shut down unexpectedly
    When the Windows Search service is forcibly shut down, searches might fail or return incomplete search results. Issue not present
    Windows Search service not runningWindows Search service not running
    When the Windows Search service is not running, searches might be slower, and you might not be able to find all items. Issue not present
    Windows Search service failedWindows Search service failed
    Problems with the Windows Search service can cause searches to fail or return incomplete search results. Issue not present
    Search Protocol Host process failedSearch Protocol Host process failed
    Problems with the Search Protocol Host might indicate errors in the Windows Search service, which can cause searches to fail or return incomplete search results. Issue not present


    Potential issues that were checked Detection details


    Incorrect permissions on Windows Search directories Issue not present

    When permissions on the Windows Search data directories are set incorrectly, the search service might not be able to access or update the computer's search index. This can result in slow searches or incomplete search results.

    Search Filter Host process failed Issue not present

    Problems with the Search Filter Host might indicate errors in the Windows Search service, which can cause searches to fail or return incomplete search results.

    Windows Search service shut down unexpectedly Issue not present

    When the Windows Search service is forcibly shut down while performing maintenance, searches might fail or return incomplete search results.

    Windows Search service shut down unexpectedly Issue not present

    When the Windows Search service is forcibly shut down, searches might fail or return incomplete search results.

    Windows Search service not running Issue not present

    When the Windows Search service is not running, searches might be slower, and you might not be able to find all items.

    Windows Search service failed Issue not present

    Problems with the Windows Search service can cause searches to fail or return incomplete search results.

    Search Protocol Host process failed Issue not present

    Problems with the Search Protocol Host might indicate errors in the Windows Search service, which can cause searches to fail or return incomplete search results.



    Detection details Expand


    InformationalDirectory
    Windows Search data directory
    Directory: C:\ProgramData\Microsoft\Search\Data\

    InformationalUser-reported problems
    Problem Type: FilesMissingProblem
    EmailMissingProblem
    ResourceUsageProblem
    UnknownProblem

    InformationalUser-defined problem
    Unknown

    Collection information
    Computer Name: DESKTOP-72015KU
    Windows Version: 10.0
    Architecture: x64
    Time: Saturday, December 29, 2018 1:21:43 PM


    Publisher details Expand


    Search and Indexing
    Find and fix problems with Windows Search.
    Package Version: 1.0
    Publisher: Microsoft Windows
    Search and Indexing
    Find and fix problems with Windows Search.
    Package Version: 1.0
    Publisher: Microsoft Corporation
    Last edited by jwblue; 30 Dec 2018 at 19:48.
      My Computer


  5. Posts : 76
    Windows 10
    Thread Starter
       #15

    zbook said:
    For the posts in the thread.

    Click edit.
    Then re-post the information.
    (not copy and paste of the existing post but copy and paste of the original information from the source)

    The second time the information is posted (after the edit) it should appear readable.

    For anything that does not post properly another option is to use share links: one drive, drop box, or google drive
    The HP Logs are in a Window that needs to be scrolled. When I copied the information that is how it pasted no mater what I tried.

    Are the HP Logs readable? Is there anything else that can be done?
      My Computer


  6. Posts : 76
    Windows 10
    Thread Starter
       #16

    If necessary I could use Movavi to record my desktop and upload a video of my screen in order to view the logs.
    Last edited by jwblue; 30 Dec 2018 at 21:03.
      My Computer


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

    1) Windows Resource Protection found corrupt files and successfully repaired them.

    2) Open administrative command prompt and type or copy and paste:

    3) FINDSTR /c:"[SR]" %windir%\Logs\cbs\cbs.log >%userprofile%\desktop\sfcdetails.txt
    4) sfc /scannow
    5) 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

    6) Find the file on the desktop and post a share link into the thread.

    7) These are the BIOS improvements:

    Fix and enhancements:
    - Fixed the BIOS could be corrupted if idle the system over than 14 hours.
    - Fixed issue where the system could be in recovery mode after updating BIOS.
    - Fixed issue no "CPU fan not detected" message pops up when system fast boot enabled and without the CPU fan.
    - Supported the Micron DDR3 P-die memory.
    - Updated the Intel CPU microcode 0x84 for R0/S0 stepping processor.
    - Updated the Intel ME firmware to v11.0.1.1001.
    - Updated the HP Basic Diagnostics to v1.16.
    - Updated the new HP logo

    Updated the Intel CPU microcode 0xBA for R0/S0 stepping processor.

    Updates the microcode for Intel processor security enhancement.

    Driver - HP ENVY All-in-One - 24-n020qe CTO (Touch) | HP® Customer Support

    BIOS technology has improved over the last 5 to 10 years.
    Bricking is very uncommon on HP products.
    There are never any guarantees with technology.



    8) Uninstall Intel GPU drivers Igdkmd64.sys (IGFX) and everything AMD using Display driver uninstaller and install new drivers from the HP website

    9) Enter the computer's serial or product number and the operating system to view available drivers.

    Driver - HP ENVY All-in-One - 24-n020qe CTO (Touch) | HP® Customer Support

    Driver - HP ENVY All-in-One - 24-n020qe CTO (Touch) | HP® Customer Support



    10) If the drivers are not displayed on the HP website and you use the AMD web site be sure the "clean install" box is checked and only install the graphics driver.

    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller Download version 18.0.0.4 (or newer version if available)

    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

    11) Perform Windows updates

    12) Find a flash drive that you can format ( > or = 8 GB)

    13) Create a bootable Windows 10 iso:
    Download Windows 10
    Download Windows 10 ISO File | Tutorials

    14) For startup and recovery system failure:
    a) uncheck automatically restart
    b) reboot to maintain settings

    If automatically restart is checked it can be easy to miss BSOD.
    When there is a BSOD with automatically restart unchecked there should be a BSOD window with bugcheck and : (
    Sometimes you may see a misbehaving driver in the form *.sys
    At the very beginning of a BSOD you may see a % counter.
    If you see the % counter allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file

    The Windows default setting is automatically restart.
    So after an in place upgrade repair or upgrade this setting needs to be changed to uncheck automatically restart.

    15) Some of the hardware testing can be performed overnight.
    HP extensive test
    chkdsk /r /v
    HD Tune full error scan
    etc.


    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
    This may take many hours so plan to run overnight.

    16) Use the text and images in this link to find the chkdsk report in the event viewer > copy and paste > notepad > post a share link into the thread using one drive, drop box, or google drive

    Read Chkdsk Log in Event Viewer in Windows 10 | Tutorials

    17) The computer has Windows 1803. The latest version of Windows is 1809.
    Upgrading to 1809 should fix the problems with search and the corruption that was found and fixed with scannow.

    18) So if the drive passes the hardware tests the plan is to upgrade the OS to 1809.

    When the steps are completed:
    a) operating system corruption fixed
    b) problems with search fixed
    c) BSOD fixed
    d) BIOS upgraded
    e) HP drivers up to date
    Last edited by zbook; 30 Dec 2018 at 22:07.
      My Computer


  8. Posts : 76
    Windows 10
    Thread Starter
       #18

    zbook said:
    1) Windows Resource Protection found corrupt files and successfully repaired them.
    ....
    Looks like I have some work ahead of me.

    What caused the operating system corruption? I mentioned this all started right after a wireless keyboard dongle was installed. Could this have been the cause? Could it have been a virus?
      My Computer


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

    The best information should be in the results of step #3.
      My Computer


  10. Posts : 76
    Windows 10
    Thread Starter
       #20

    zbook said:
    1) Windows Resource Protection found corrupt files and successfully repaired them.

    2) Open administrative command prompt and type or copy and paste:

    3) FINDSTR /c:"[SR]" %windir%\Logs\cbs\cbs.log >%userprofile%\desktop\sfcdetails.txt
    4) sfc /scannow
    5) 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

    6) Find the file on the desktop and post a share link into the thread.

    7) These are the BIOS improvements:

    Fix and enhancements:
    - Fixed the BIOS could be corrupted if idle the system over than 14 hours.
    - Fixed issue where the system could be in recovery mode after updating BIOS.
    - Fixed issue no "CPU fan not detected" message pops up when system fast boot enabled and without the CPU fan.
    - Supported the Micron DDR3 P-die memory.
    - Updated the Intel CPU microcode 0x84 for R0/S0 stepping processor.
    - Updated the Intel ME firmware to v11.0.1.1001.
    - Updated the HP Basic Diagnostics to v1.16.
    - Updated the new HP logo

    Updated the Intel CPU microcode 0xBA for R0/S0 stepping processor.

    Updates the microcode for Intel processor security enhancement.

    Driver - HP ENVY All-in-One - 24-n020qe CTO (Touch) | HP® Customer Support

    BIOS technology has improved over the last 5 to 10 years.
    Bricking is very uncommon on HP products.
    There are never any guarantees with technology.



    8) Uninstall Intel GPU drivers Igdkmd64.sys (IGFX) and everything AMD using Display driver uninstaller and install new drivers from the HP website

    9) Enter the computer's serial or product number and the operating system to view available drivers.

    Driver - HP ENVY All-in-One - 24-n020qe CTO (Touch) | HP® Customer Support

    Driver - HP ENVY All-in-One - 24-n020qe CTO (Touch) | HP® Customer Support



    10) If the drivers are not displayed on the HP website and you use the AMD web site be sure the "clean install" box is checked and only install the graphics driver.

    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller Download version 18.0.0.4 (or newer version if available)

    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

    11) Perform Windows updates

    12) Find a flash drive that you can format ( > or = 8 GB)

    13) Create a bootable Windows 10 iso:
    Download Windows 10
    Download Windows 10 ISO File | Tutorials

    14) For startup and recovery system failure:
    a) uncheck automatically restart
    b) reboot to maintain settings

    If automatically restart is checked it can be easy to miss BSOD.
    When there is a BSOD with automatically restart unchecked there should be a BSOD window with bugcheck and : (
    Sometimes you may see a misbehaving driver in the form *.sys
    At the very beginning of a BSOD you may see a % counter.
    If you see the % counter allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file

    The Windows default setting is automatically restart.
    So after an in place upgrade repair or upgrade this setting needs to be changed to uncheck automatically restart.

    15) Some of the hardware testing can be performed overnight.
    HP extensive test
    chkdsk /r /v
    HD Tune full error scan
    etc.


    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
    This may take many hours so plan to run overnight.

    16) Use the text and images in this link to find the chkdsk report in the event viewer > copy and paste > notepad > post a share link into the thread using one drive, drop box, or google drive

    Read Chkdsk Log in Event Viewer in Windows 10 | Tutorials

    17) The computer has Windows 1803. The latest version of Windows is 1809.
    Upgrading to 1809 should fix the problems with search and the corruption that was found and fixed with scannow.

    18) So if the drive passes the hardware tests the plan is to upgrade the OS to 1809.

    When the steps are completed:
    a) operating system corruption fixed
    b) problems with search fixed
    c) BSOD fixed
    d) BIOS upgraded
    e) HP drivers up to date
    The issue is happening again. I have been having issues with another computer that I have been trying to fix so have not had time to do all these suggestions.

    Looks like I will have to.

    Since this issues continue to occur could my hardware driver be failing? As I mentioned though by coincidence or not the issue began after installing a new keyboard.

    zbook said:
    1

    2) Open administrative command prompt and type or copy and paste:

    3) FINDSTR /c:"[SR]" %windir%\Logs\cbs\cbs.log >%userprofile%\desktop\sfcdetails.txt
    4) sfc /scannow
    5) 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

    I ran the FINDSTR command just now and nothing appeared on the desktop. The post with these instructions was submitted on the 28th of December. Was there a particular log previous to the 28th that was wanted? I was able to look into the CBS Folder. Attached is a screenshot with the logs in my Windows Explorer.

    Is it 100% certain my hard drive is failing?-screenshot-295-.png
      My Computer


 

  Related Discussions
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:31.
Find Us




Windows 10 Forums