Random Freezing

Page 2 of 4 FirstFirst 1234 LastLast

  1. Kelltech
    Posts : 16
    Windows 10 Home 1709 build 16299 64-bit
    Thread Starter
       New #11

    Whew...I think I did everything correctly.
    Updates my system specs, attached the BSOD, ran the troubleshooter, continuing to monitor performance, and pasted the following:

    Microsoft Windows [Version 10.0.16299.64](c) 2017 Microsoft Corporation. All rights reserved.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 found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.64[===========================86.8%================== ]Error: 0x800f0950DISM failed. No operation was performed.For more information, review the log file.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.Stage 1: Examining basic file system structure ... 440832 file records processed.File verification completed. 4758 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 340 reparse records processed. 511762 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 340 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 35466 data files processed.CHKDSK is verifying Usn Journal... 40275448 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 248675117 KB total disk space. 54800592 KB in 150210 files. 120784 KB in 35467 indexes. 0 KB in bad sectors. 558321 KB in use by the system. 65536 KB occupied by the log file. 193195420 KB available on disk. 4096 bytes in each allocation unit. 62168779 total allocation units on disk. 48298855 allocation units available on disk.C:\WINDOWS\system32>Microsoft Windows [Version 10.0.16299.64]'Microsoft' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>(c) 2017 Microsoft Corporation. All rights reserved.2017 was unexpected at this time.C:\WINDOWS\system32>C:\WINDOWS\system32>C:\WINDOWS\system32>sfc /scannow'C:\WINDOWS\system32' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>Beginning system scan. This process will take some time.'Beginning' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>Beginning verification phase of system scan.'Beginning' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>Verification 100% complete.'Verification' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>Windows Resource Protection found corrupt files but was unable to fix some'Windows' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For'of' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not'example' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>supported in offline servicing scenarios.'supported' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthAccess is denied.C:\WINDOWS\system32>C:\WINDOWS\system32>Deployment Image Servicing and Management tool'Deployment' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>Version: 10.0.16299.15'Version:' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>Image Version: 10.0.16299.64'Image' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>[===========================86.8%================== ]'[' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>Error: 0x800f0950'Error:' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>DISM failed. No operation was performed.Error: 87DISM doesn't recognize the command-line option "failed.".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>For more information, review the log file.more was unexpected at this time.C:\WINDOWS\system32>C:\WINDOWS\system32>The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log'The' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>C:\WINDOWS\system32>chkdsk /scan'C:\WINDOWS\system32' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>The type of the file system is NTFS.'The' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>Stage 1: Examining basic file system structure ...'Stage' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 440832 file records processed.'440832' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>File verification completed.'File' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 4758 large file records processed.'4758' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 0 bad file records processed.'0' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>Stage 2: Examining file name linkage ...'Stage' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 340 reparse records processed.'340' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 511762 index entries processed.'511762' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>Index verification completed.'Index' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 0 unindexed files scanned.'0' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 0 unindexed files recovered to lost and found.'0' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 340 reparse records processed.'340' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>Stage 3: Examining security descriptors ...'Stage' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>Security descriptor verification completed.'Security' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 35466 data files processed.'35466' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>CHKDSK is verifying Usn Journal...Invalid parameter - verifyingC:\WINDOWS\system32> 40275448 USN bytes processed.'40275448' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>Usn Journal verification completed.'Usn' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>Windows has scanned the file system and found no problems.'Windows' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>No further action is required.'No' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32> 248675117 KB total disk space.'248675117' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 54800592 KB in 150210 files.'54800592' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 120784 KB in 35467 indexes.'120784' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 0 KB in bad sectors.'0' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 558321 KB in use by the system.'558321' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 65536 KB occupied by the log file.'65536' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 193195420 KB available on disk.'193195420' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32> 4096 bytes in each allocation unit.'4096' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 62168779 total allocation units on disk.'62168779' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32> 48298855 allocation units available on disk.'48298855' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\WINDOWS\system32>C:\WINDOWS\system32>
    Random Freezing Attached Files
      My Computer
    Quote Quote

  3. zbook
    Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       New #12

    The test results and the logs displayed:
    1) Windows operating system corruption
    2) Possible drive file corruption
    3) Drive paging errors
    4) Drive controller errors
    5) 9 crashes between 11/18/2017 and 12/6/2017
    6) 1 BSOD with bugheck 9F Driver power state failure


    For all tests please post images into the thread. If there is any problem posting images please use one drive or drop box share links.


    Perform the following steps:
    1) Create a bootable windows 10 iso:
    Download Windows 10

    2) Open administrative command prompt and copy and paste:
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    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


    5) chkdsk /x /f /r c:
    This may take many hours so plan to run overnight.
    Run the command on every partition changing the drive letter c: > d: > e: to the applicable drive letter
    6) Use the information in this link to find the chkdsk report in the event viewer and post the results into the thread using a one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

    7) If the Restorehealth command displays corruption that it was not able to fix or displays errors > perform an in place upgrade repair:
    Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials

    8) 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

    9) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab in startup and recovery click system > post an image into the thread.
    and under performance click settings > click on the advanced tab > under virtual memory click change > post an image into the thread

    10) If you use Ccleaner > click on the windows tab > scroll down to system and advanced > post an image into the thread

    11) In the left lower corner search type clean > open disk cleanup > scroll up and down and post images into the thread.

    12) download and install: Whocrashed: http://www.resplendence.com/whocrashed

    13) On Whocrashed above analyze click on tools > crash dump test > type: ACCEPT

    14) After the crash > click analyze > post the results into the thread

    15) run the DM log collector after the test dump and post a zip into the thread:
    BSOD - Posting Instructions - Windows 10 Forums

    16) perform the whocrashed test before the in place upgrade repair.

    17) open the website for the computer's drivers and post into the thread the URL or hyperlink for the website

    18) report into the thread with images the results of the Microsoft easy fix (troubleshooters: hardware, video, audio)



    Code:
    Event[1844]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-11-26T18:47:52.736  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: IRISH-SAGER-NP6852  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume8.(A device which does not exist was specified.)
    Code:
    Event[1872]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-11-26T18:47:52.738  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: IRISH-SAGER-NP6852  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume9.
    Code:
    Event[1873]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-11-26T18:47:52.739  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: IRISH-SAGER-NP6852  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume8.
    Code:
    Event[2019]:  Log Name: System  Source: NTFS  Date: 2017-11-26T20:37:24.318  Event ID: 50  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
    Code:
    Event[2039]:  Log Name: System  Source: volmgr  Date: 2017-11-26T22:59:13.100  Event ID: 161  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: Dump file creation failed due to error during dump creation.
    Code:
    Event[4293]:  Log Name: System  Source: Display  Date: 2017-12-06T18:18:34.934  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: Display driver nvlddmkm stopped responding and has successfully recovered.Event[4294]:  Log Name: System  Source: Display  Date: 2017-12-06T18:18:37.343  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: Display driver nvlddmkm stopped responding and has successfully recovered.
    Code:
    Event[882]:  Log Name: System  Source: Application Popup  Date: 2017-11-20T10:04:09.297  Event ID: 26  Task: N/A  Level: Information  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: IRISH-SAGER-NP6852  Description: Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.
    Code:
    Event[1845]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.737  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1846]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.737  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1847]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.737  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1848]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.737  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1849]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.737  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1850]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.737  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1851]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1852]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1853]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1854]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1855]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1856]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1857]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1858]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1859]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1860]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1861]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1862]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1863]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1864]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1865]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1866]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1867]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1868]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1869]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1870]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[1871]:  Log Name: System  Source: Disk  Date: 2017-11-26T18:47:52.738  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.
    Code:
    Event[2208]:  Log Name: System  Source: Disk  Date: 2017-11-26T23:22:27.176  Event ID: 11  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: IRISH-SAGER-NP6852  Description: The driver detected a controller error on \Device\Harddisk2\DR2.
    Code:
    11/27/2017 4:59 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000009f
P2: 4
P3: 12c
P4: ffffa086062992c0
P5: ffffdc0e5425f810
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112617-9531-01.dmp
\\?\C:\WINDOWS\TEMP\WER-13437-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4304.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4313.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4324.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000009f_3c91a774b5b133e664347041aff57fdd35871c99_00000000_cab_191043bf

Analysis symbol: 
Rechecking for solution: 0
Report Id: 45c86fda-b6c7-4915-a13e-10352910d49d
Report Status: 2049
Hashed bucket:11/27/2017 4:59 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000009f
P2: 4
P3: 12c
P4: ffffa086062992c0
P5: ffffdc0e5425f810
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112617-9531-01.dmp
\\?\C:\WINDOWS\TEMP\WER-13437-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4304.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4313.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4324.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000009f_3c91a774b5b133e664347041aff57fdd35871c99_00000000_03a84323

Analysis symbol: 
Rechecking for solution: 0
Report Id: 45c86fda-b6c7-4915-a13e-10352910d49d
Report Status: 4
Hashed bucket:
    Last edited by zbook; 07 Dec 2017 at 14:28.
      My Computer
    Quote Quote

  4. mb1280
    Posts : 87
    Windows 10 Pro 64-bit
       New #13

    Try a hard reset:

    HP Notebook PCs - Computer Does Not Start and Emits an LED or Beep Code | HP® Customer Support . . . Keyboard doesn't work - Do a Hard Reset . . . To perform a hard reset on a computer with a removable battery, use the following steps: . . . HP Notebook PCs - Computer Does Not Start and Emits an LED or Beep Code | HP® Customer Support
      My Computer
    Quote Quote

  6. Kelltech
    Posts : 16
    Windows 10 Home 1709 build 16299 64-bit
    Thread Starter
       New #14

    2) Open administrative command prompt and copy and paste:
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    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.16299.64](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.64[==========================100.0%==========================] The component store is repairable.The operation completed successfully.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.64[===========================86.8%================== ]Error: 0x800f0950DISM failed. No operation was performed.For more information, review the log file.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>

    Looks like the DISM failed with an error, I can move on to the in place repair, or do you need to see that DISM log?
      My Computer
    Quote Quote

  7. zbook
    Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       New #15

    1) Please post the DISM log using a one drive or drop box share link.

    2) Insert the Windows 10 iso into any USB port
    3) open file explorer > view the drive letter for the iso and change the drive letter in the commands below to the applicable drive letter

    These DISM commands may take substantially longer to complete: (one may be able to fix the corruption instead of the in place upgrade repair)
    Before the in place upgrade repair please run the whocrashed test dump and then post the DM log collector zip.

    3) open administrative command prompt and copy and paste:
    4) DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:E:\Windows /LimitAccess
    5) Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\Sources\Install.esd:1 /limitaccess
    6) Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:E:\sources\install.wim:1 /limitaccess
      My Computer
    Quote Quote

  8. Kelltech
    Posts : 16
    Windows 10 Home 1709 build 16299 64-bit
    Thread Starter
       New #16

    zbook, thank you very much for all of this help by the way.

    Here's that link for the DISM log: Dropbox - dism.log

    As for the Windows 10 iso, I'm still waiting for the download tool to finish and it is crawling! Right now it's at 25% so it's going to be a while.
      My Computer
    Quote Quote

  9. zbook
    Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       New #17

    Take your time.
    The other steps can be performed while the iso is downloading.
      My Computer
    Quote Quote

  10. Kelltech
    Posts : 16
    Windows 10 Home 1709 build 16299 64-bit
    Thread Starter
       New #18

    HD Tune:

    Random Freezing-hdtune_benchmark_nvme.png.pngRandom Freezing-hdtune_error_scan_nvme.png.pngRandom Freezing-hdtune_health_nvme.png.png
    Random Freezing-secondary_drive_1_hdtune_health.png.pngRandom Freezing-secondary_drive_2_hdtune_health.png.pngRandom Freezing-secondary_drive_hdtune_benchmark.png.png

    CCleaner and Disk Clean:

    Random Freezing-ccleaner.pngRandom Freezing-disk_clean1.pngRandom Freezing-disk_clean2.png

    System:

    Random Freezing-sys1.pngRandom Freezing-sys2.png
      My Computer
    Quote Quote

  12. Kelltech
    Posts : 16
    Windows 10 Home 1709 build 16299 64-bit
    Thread Starter
       New #19

    Drivers Page: https://www.sagernotebook.com/drivers.php?cat=664

    Whocrashed plus post crash DM Log:

    IRISH-SAGER-NP6-Thu_12_07_2017_182628_82.zip

    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.



    On Thu 12/7/2017 6:14:34 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\120717-7796-01.dmp
    This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
    Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19ACFDF1, 0x3C2A58ED)
    Error: MANUALLY_INITIATED_CRASH1
    file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
    product: WhoCrashed
    company: Resplendence Software Projects Sp.
    description: Resplendence WhoCrashed Crash Dump Test
    Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



    On Thu 12/7/2017 6:14:34 PM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
    Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19ACFDF1, 0x3C2A58ED)
    Error: MANUALLY_INITIATED_CRASH1
    file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
    product: WhoCrashed
    company: Resplendence Software Projects Sp.
    description: Resplendence WhoCrashed Crash Dump Test
    Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.




    Conclusion

    2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
      My Computer
    Quote Quote

  13. Kelltech
    Posts : 16
    Windows 10 Home 1709 build 16299 64-bit
    Thread Starter
       New #20

    zbook said:
    1) Please post the DISM log using a one drive or drop box share link.

    2) Insert the Windows 10 iso into any USB port
    3) open administrative command prompt and copy and paste:
    4) DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:E:\Windows /LimitAccess
    The very first command gave me this

    Error: 0x800f081f
    The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077 DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
      My Computer
    Quote Quote

 

  Related Discussions
Random freezing
in Drivers and Hardware

hi.my windows 10 have this wierd bugg it just random freeze and need force restart after restarting my pc i get this ''unidentified network'' problem thats easy fix but my windows still keep freezing i updated drivers.updated windows. i scaned for...
freezing and random reboots
in BSOD Crashes and Debugging

hi I have had a problem since the creators update. the computer started random reboot for awhile then stopped . I had had bought a new game rome 2 and it was crashing and now I know it is not just the game but my computer is freezing just...
Random freezing
in Performance & Maintenance

I installed Windows 10 recently and it kept freezing for a second or so. Even before I installed windows 10 I still get random freezes, I tried changing the power options and it didn't work. It happens when I'm browsing,idling mostly what I do....
Hello, I'm going to post two different scenarios that happens when my computer needs a hard restart My computer freezes completely (literally no movement on the screen or anything, it's not slow it's frozen). And an extremely loud buzzing...
I have a new PC that I built and i'll include the parts at the end. I'm running Windows 10 Pro Insider Preview. Eval copy. Build 10565. This machine randomly freezes on me(No BSOD) and I haven't been able to figure out the cause. It does not matter...
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 08:26.
Find Us




Windows 10 Forums