Windows 10: Audio static, skipping frames on some internet videos

Alrighty! Thanks for the response.
Sorry to ask, what exactly is an Autorun and how would I use it? It seems like it is something that can potentially cause problems/instability, which is why you recommend a disk image/system restore?

I've never done disk imaging, I'll try using Macrium reflect, is it posible to create a disk image onto a USB? Since I only have one Hard drive.

 

Autoruns lets you disable anything that autostarts. The list is divided into sections. Avoid disabling things of MS origin.
It's one of a range of technical tools.. as such exposes more than the typical user sees.
Basic use is quite straightforward.

There are plenty of videos, articles you can find...
SysInternals Pro: Using Autoruns to Deal with Startup Processes and Malware

This is advanced...
Advanced Autoruns Tutorial - How to disable programs that start with Windows - YouTube

Disk imaging is a form of backup. Backups should not be held on your internal disks for obvious reasons (with some particular exceptions).
Images are normally compressed copies of the used parts of your disks or partitions.

Example: I have disks as in 'My computer' below. I use a 2Tb external disk to back up image sets to- a set being the first base image, the rest being differential images- each being the change from the base image.

Here's my write-up on the value of disk imaging.

Everyone who contributes regularly here uses and recommends disk imaging.

If you use it, you can recover from:
- a failed disk drive (restore to a new one)
- ransomware (which encrypts your disk)
- user error
- unrecoverable problems from failed updates to problem programs
- unbootable PC (hardware faults aside)

Images also act as a full backup- you can extract files too.

You can even use images to help you move more easily and quickly to a new PC.
Can be used with Laplink software to transfer your build automatically to another PC

Imaging can even help you sleep at night knowing you have a second chance.

Creating disk images lets you restore Windows and all your imaged disks and partitions to a previous working state from compressed copies you have created and kept updated on external storage media, quickly and probably without technical help.

Many here recommend Macrium Reflect (free) as a good robust solution and more reliable than some others. It’s
- more feature rich
- more flexible
- more reliable
than Windows Backup and Restore system images.

It's well supported with videos, help and a responsive forum.

There are other such programs, free/commercial, some with simpler interfaces, but Macrium R is one of the most robust and reliable.

How long does it take?
SSD+ USB3 - maybe 15 mins for the first system image, less thereafter
HDD + USB2 - maybe 40-50 mins
That’s with little personal data, few programs installed.
- of course, depends how much you have on C:
(You can and should image all your partitions and disks)

Once you've created your first image, keep it updated with e.g. differential imaging- which images just changes from the first image, more quickly, and creates a smaller image file.

You need a backup medium - say- twice as large as the total amount of data you are imaging to keep a reasonable number of differential images. This will vary dependent on the number of images you keep, so is only a rough practical guide.

Some comment that system restore isn't always reliable; if it works and solves the problem, great. But sometimes restores won't work or fail. And of course a restore point only covers a limited number of aspects of the system. That’s where disk imaging comes in.

(There's a tutorial on Macrium in the Tutorials section, and a couple of videos in the user videos section on this forum)
Backup and Restore with Macrium Reflect Backup Restore Tutorials
Windows 10 instructional videos by Ten Forums members




Macrium automatically selects all the partitions comprising Windows if you select that option.

You can of course back up any combination of disks and partitions.

 

So I have experimented a bit with autoruns and haven't found the culprit yet, just being careful not to disable something important since I'm new to the program. I'll still experiment with it.

One of my friends suggested tweaking.com's repair tool, is this a good idea? I just tried its preliminary steps and it already messed up Microsoft office so I had to reinstall it (deleted some office dlls? not sure) I am just scared it will mess something up.

What do you think about doing a reinstall of Windows 10 at this point?


Also I looked through event view and came across some ESENT "Hardware errors". These did not coincide with any computer problems, not sure if they mean anything but worth looking into. There were a few of them a week or so ago scrolling down event viewer.


I'll post them here : (This forum desperately needs spoiler tags!)

1.

Log Name: ApplicationSource: ESENTDate: 11/17/2017 5:07:39 PMEvent ID: 510Task Category: PerformanceLevel: WarningKeywords: ClassicUser: N/AComputer: DESKTOP-UT8IEU7Description:wuaueng.dll (3480,D,0) SUS20ClientDataStore: A request to write to the file "C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log" at offset 507904 (0x000000000007c000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (32 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 141 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="ESENT" /> <EventID Qualifiers="0">510</EventID> <Level>3</Level> <Task>7</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-11-18T01:07:39.959432800Z" /> <EventRecordID>2230</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-UT8IEU7</Computer> <Security /> </System> <EventData> <Data>wuaueng.dll</Data> <Data>3480,D,0</Data> <Data>SUS20ClientDataStore: </Data> <Data>C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log</Data> <Data>507904 (0x000000000007c000)</Data> <Data>4096 (0x00001000)</Data> <Data>32</Data> <Data>0</Data> <Data>141</Data> </EventData></Event>


2.

Log Name: ApplicationSource: ESENTDate: 11/17/2017 5:05:23 PMEvent ID: 508Task Category: PerformanceLevel: WarningKeywords: ClassicUser: N/AComputer: DESKTOP-UT8IEU7Description:wuaueng.dll (3480,D,0) SUS20ClientDataStore: A request to write to the file "C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log" at offset 417792 (0x0000000000066000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (58 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="ESENT" /> <EventID Qualifiers="0">508</EventID> <Level>3</Level> <Task>7</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-11-18T01:05:23.726982700Z" /> <EventRecordID>2227</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-UT8IEU7</Computer> <Security /> </System> <EventData> <Data>wuaueng.dll</Data> <Data>3480,D,0</Data> <Data>SUS20ClientDataStore: </Data> <Data>C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log</Data> <Data>417792 (0x0000000000066000)</Data> <Data>4096 (0x00001000)</Data> <Data>58</Data> </EventData></Event>


3.

Log Name: ApplicationSource: ESENTDate: 11/17/2017 5:04:53 PMEvent ID: 533Task Category: GeneralLevel: WarningKeywords: ClassicUser: N/AComputer: DESKTOP-UT8IEU7Description:wuaueng.dll (3480,D,0) SUS20ClientDataStore: A request to write to the file "C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log" at offset 417792 (0x0000000000066000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="ESENT" /> <EventID Qualifiers="0">533</EventID> <Level>3</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-11-18T01:04:53.962140100Z" /> <EventRecordID>2226</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-UT8IEU7</Computer> <Security /> </System> <EventData> <Data>wuaueng.dll</Data> <Data>3480,D,0</Data> <Data>SUS20ClientDataStore: </Data> <Data>C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log</Data> <Data>417792 (0x0000000000066000)</Data> <Data>4096 (0x00001000)</Data> <Data>36</Data> </EventData></Event>