Windows 10: Random Freezing

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?

 

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

 

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.

 

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

 

HD Tune:
















CCleaner and Disk Clean:









System:

 

Drivers Page: A Trusted Brand for Gaming Laptops | Sager Notebooks

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.

 

The very first command gave me this *Sad

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

 

The webpage for the drivers displayed the latest available drivers with dates of February 2017.
There was no BIOS listed on this webpage.
The current BIOS: BIOS Version/Date American Megatrends Inc. 1.05.15RLS1, 7/5/2017 SMBIOS Version 3.0
Please open the website for the BIOS source to check to see if it is the most recent version and post a URL or hyperlink into the thread.
For Ccleaner uncheck memory dumps and windows logs.
For the WDC drive run:
Software and Firmware Downloads | WD Support

Please post images of the test results into the thread.

 

From what I can tell, there is no BIOS update if it's not on the Sager drivers page. At least that's all I can find out.

Here's the WD test:

 

Was the BIOS installed before the computer was purchased or is there a website source to check for updates? The BIOS has a date of July 2017. See if there is customer support information for BIOS updates.

Run HD Sentinel (free or trial edition) on the WDC drive and post images of the results into the thread.
Overview and SMART tabs.
Hard Disk Sentinel - HDD health and temperature monitoring

 

Today I am wondering at what point does it become more efficient to just wipe and install the OS again? And would that solve the issues? Unbelievable that this is corrupt after only at most 90 days of use. *Banghead

Results of chkdsk from last night:

C Drive - https://www.dropbox.com/s/wfrhqcqdt4...drive.txt?dl=0
Secondary drive - https://www.dropbox.com/s/vkxskiwtr8...drive.txt?dl=0
Wininit - https://www.dropbox.com/s/9lmqihof17...ninit.txt?dl=0

 

There were 2 reports on drive C: approximately 12 hours apart. What happened?

 

If it brand new mate, reinstall and fully update but dont install any programs and if still the same take it back. Shouldnt have to faff around with a brand new laptop.

 

Windows had made corrections to the file drive system.

A new computer should be for the most part problem free.

If it's easy to return then do that.

If you need some study results you can perform some tests.

 

I couldn't tell you, I didn't run chkdsk at 11am, ran them late last night back to back on each drive.

Totally agreed. Except I'm 99.999% certain it's the OS, not the hardware. Friggin crap windows *Mad