Windows 10: Windows 10 Keeps Crashing

Hi Windows 10 keeps crashing. I thought I had fixed it by removing spotify but now its at it again. Here is sfc /scannow results and also some events that happen around the same time as the crashing that might be causing the problem?



2019-01-06 13:00:07, Info CSI 000052ef [SR] Verify complete
2019-01-06 13:00:07, Info CSI 000052f0 [SR] Verifying 2 components
2019-01-06 13:00:07, Info CSI 000052f1 [SR] Beginning Verify and Repair transaction
2019-01-06 13:00:07, Info CSI 000052f2@2019/1/6:13:00:07.689 Primitive installers committed for repair
2019-01-06 13:00:07, Info CSI 000052f3@2019/1/6:13:00:07.705 Primitive installers committed for repair
2019-01-06 13:00:07, Info CSI 000052f4 [SR] Verify complete
2019-01-06 13:00:07, Info CSI 000052f5 [SR] Repairing 1 components
2019-01-06 13:00:07, Info CSI 000052f6 [SR] Beginning Verify and Repair transaction
2019-01-06 13:00:07, Info CSI 000052f7 Hashes for file member [l:12]'OneDrive.lnk' do not match.
Expected: {l:32 b:9905f2e7a5d33c75361570345fa4441c69ee318f39111cbc9dd9da49dbdf4561}.
Actual: {l:32 b:6484bd797b725d3ec64cbcd6cad9d411835dc0dbcf98c4b501769b40b46af8bc}.
2019-01-06 13:00:07, Info CSI 000052f8 [SR] Cannot repair member file [l:12]'OneDrive.lnk' of Microsoft-Windows-OneDrive-Setup, version 10.0.17134.1, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-01-06 13:00:07, Info CSI 000052f9@2019/1/6:13:00:07.736 Primitive installers committed for repair
2019-01-06 13:00:07, Info CSI 000052fa Hashes for file member [l:12]'OneDrive.lnk' do not match.
Expected: {l:32 b:9905f2e7a5d33c75361570345fa4441c69ee318f39111cbc9dd9da49dbdf4561}.
Actual: {l:32 b:6484bd797b725d3ec64cbcd6cad9d411835dc0dbcf98c4b501769b40b46af8bc}.
2019-01-06 13:00:07, Info CSI 000052fb [SR] Cannot repair member file [l:12]'OneDrive.lnk' of Microsoft-Windows-OneDrive-Setup, version 10.0.17134.1, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-01-06 13:00:07, Info CSI 000052fc [SR] This component was referenced by [l:116]'Microsoft-Windows-OneDrive-Setup-WOW64-Package~31bf3856ad364e35~amd64~~10.0.17134.1.f647690e04ff7e43581b577deaab5f78'
2019-01-06 13:00:07, Info CSI 000052fd Hashes for file member [l:12]'OneDrive.lnk' do not match.
Expected: {l:32 ml:4096 b:9905f2e7a5d33c75361570345fa4441c69ee318f39111cbc9dd9da49dbdf4561}.
Actual: {l:32 b:6484bd797b725d3ec64cbcd6cad9d411835dc0dbcf98c4b501769b40b46af8bc}.
2019-01-06 13:00:07, Info CSI 000052fe [SR] Could not reproject corrupted file \??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\\OneDrive.lnk; source file in store is also corrupted
2019-01-06 13:00:07, Info CSI 000052ff@2019/1/6:13:00:07.798 Primitive installers committed for repair
2019-01-06 13:00:07, Info CSI 00005300 [SR] Repair complete
2019-01-06 13:00:07, Info CSI 00005301 [SR] Committing transaction
2019-01-06 13:00:07, Info CSI 00005302 Creating NT transaction (seq 1)
2019-01-06 13:00:07, Info CSI 00005303 Created NT transaction (seq 1) result 0x00000000, handle @0x17b4
2019-01-06 13:00:07, Info CSI 00005304@2019/1/6:13:00:07.811 Beginning NT transaction commit...
2019-01-06 13:00:07, Info CSI 00005305@2019/1/6:13:00:07.821 CSI perf trace:
CSIPERF:TXCOMMIT;10613
2019-01-06 13:00:07, Info CSI 00005306 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2019-01-06 13:02:08, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2019-01-06 13:02:08, Info CBS TiWorker signaled for shutdown, going to exit.
2019-01-06 13:02:08, Info CBS CbsCoreFinalize: ExecutionEngineFinalize



Event Viewer Events:


Session "Cloud Files Diagnostic Event Listener" failed to start with the following error: 0xC0000022

Bonjour Service - Task Scheduling Error: m->NextScheduledSPRetry 1375


Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Windows Hello for Business post-logon provisioning is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
See https://go.microsoft.com/fwlink/?linkid=832647 for more details.


Intel(R) I211 Gigabit Network Connection
Network link is disconnected.

The description for Event ID 0 from source Disc Soft Lite Bus Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

Many Thanks.

:)

 

Windows 10 keeps crashing

Hi,

There are many possible reasons why the computer will keeps on crashing. One of which is missing or corrupted system files. For us to further isolate the issue, we suggest answering the following questions:

• What exactly are you accessing/doing when the computer crashes?
• Were you still able to login to the computer after it happens?
• Can you send us a screenshot of the error messages or mini dump that you've received?

In the meantime, if you're seeing a blue screen when the computer crashes, we suggest following the steps on this article:
Troubleshoot blue screen errors. Kindly choose the appropriate answer to the category
"When did you get the error?".

We'll wait for your response on this matter.

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.