[sukucoy]

I have this weird issue on my scarlett solo 3rd gen where everytime I do a full reboot (either restart or boot up after shutdown) my focusrite USB audio just doesn't work. It work just fine if I just put my PC to sleep.

 

I use the scarlett solo for my mic and headset output. When the issue occur I can't switch between audio outputs and my mic won't work, i'll attach a screenshot of my sound window

there's no volume bar on the rightside and I can't click on it. 

 

so far I've tried:

1. Disabling windows auto update,

2. Trying different USB ports,

3. Re-installing USB drivers,

4. Re-installing Focusrite USB Audio drivers.

 

re-installing focusrite USB Audio drivers fixed it temporarily. But after I restart or shutdown the PC it broke down again (I've re-installed the driver 10 times at this point already).

 

it's annoying so if anyone can give me some inputs that would be much appreciated

[Advertisements]

When it is not working:

 

Search for

device manager

hit Enter

find your focusrite driver.  Might be under Sound, Video & Game Controllers or under USB Controllers.

 

Right click on the device and select Properties.

 

Under the General tab does it say it is working properly?

Look under the Events tab

Are there any events?  If it has any events from around the time of the last reboot click on one then select the text in the Information section and copy (ctrl + c) then move to a reply and paste (ctrl + v)

repeat for any other events between the last reboot and now.

Look under the Resources tab.  Does it report any conflicts?

Look under the Driver tab.  What is the date and version number of the driver?

If it has a Power Management tab, uncheck Allow the computer to turn off this device to save power.  OK

 

 

1. Please download the Event Viewer Tool by Vino Rosso
http://images.malwar...om/vino/VEW.exe
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:

* System
4. Under 'Select type to list', select:
* Error
* Warning


Then use the 'Number of events' as follows:


1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.


Please post the Output log in your next reply then repeat but select Application.  (Each time you run VEW it overwrites the log so copy the first one to a Reply or rename it before running it a second time.)

Note:  May not work if your computer does not use English.  Will not work if you forget to right click and Run as Administrator.

 

 

[RKinner]

When it is not working:

 

Search for

device manager

hit Enter

find your focusrite driver.  Might be under Sound, Video & Game Controllers or under USB Controllers.

 

Right click on the device and select Properties.

 

Under the General tab does it say it is working properly?

Look under the Events tab

Are there any events?  If it has any events from around the time of the last reboot click on one then select the text in the Information section and copy (ctrl + c) then move to a reply and paste (ctrl + v)

repeat for any other events between the last reboot and now.

Look under the Resources tab.  Does it report any conflicts?

Look under the Driver tab.  What is the date and version number of the driver?

If it has a Power Management tab, uncheck Allow the computer to turn off this device to save power.  OK

 

 

1. Please download the Event Viewer Tool by Vino Rosso
http://images.malwar...om/vino/VEW.exe
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:

* System
4. Under 'Select type to list', select:
* Error
* Warning


Then use the 'Number of events' as follows:


1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.


Please post the Output log in your next reply then repeat but select Application.  (Each time you run VEW it overwrites the log so copy the first one to a Reply or rename it before running it a second time.)

Note:  May not work if your computer does not use English.  Will not work if you forget to right click and Run as Administrator.

 

 

[sukucoy]

Under the General tab does it say it is working properly?

Look under the Events tab

Are there any events?  If it has any events from around the time of the last reboot click on one then select the text in the Information section and copy (ctrl + c) then move to a reply and paste (ctrl + v)

repeat for any other events between the last reboot and now.

Look under the Resources tab.  Does it report any conflicts?

Look under the Driver tab.  What is the date and version number of the driver?

If it has a Power Management tab, uncheck Allow the computer to turn off this device to save power.  OK

 

it said device is working properly and there are no new events recorded

driver date is 6/2/2020

driver version is 4.65.5.658

 

it's a long one but I've only been using this focusrite USB audio since 9/1/2021

 

VEW Result on system:

 

Vino's Event Viewer v01c run on Windows 7 in English

Report run at 26/01/2021 23:26:49

 

Note: All dates below are in the format dd/mm/yyyy

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'System' Log - Critical Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'System' Date/Time: 25/01/2021 09:13:43

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 24/01/2021 11:20:28

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 24/01/2021 11:04:06

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 09/01/2021 11:44:16

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 03/01/2021 05:51:48

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 31/12/2020 03:31:08

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 14/12/2020 11:16:31

Type: Critical Category: 64

Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode

The device Apple Mobile Device USB Device (location 000c.0000.0003.004.000.000.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

 

Log: 'System' Date/Time: 14/12/2020 11:16:31

Type: Critical Category: 64

Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode

The device Apple iPhone (location 000c.0000.0003.004.000.000.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

 

Log: 'System' Date/Time: 14/12/2020 11:16:31

Type: Critical Category: 64

Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode

A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

 

Log: 'System' Date/Time: 13/12/2020 23:52:05

Type: Critical Category: 64

Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode

The device Apple Mobile Device USB Device (location 000c.0000.0003.004.000.000.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

 

Log: 'System' Date/Time: 13/12/2020 23:52:05

Type: Critical Category: 64

Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode

The device Apple iPhone (location 000c.0000.0003.004.000.000.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

 

Log: 'System' Date/Time: 13/12/2020 23:52:05

Type: Critical Category: 64

Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode

A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

 

Log: 'System' Date/Time: 13/12/2020 23:48:47

Type: Critical Category: 64

Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode

The device Apple Mobile Device USB Device (location 000c.0000.0003.004.000.000.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

 

Log: 'System' Date/Time: 13/12/2020 23:48:47

Type: Critical Category: 64

Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode

The device MTP USB Device (location 000c.0000.0003.004.000.000.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

 

Log: 'System' Date/Time: 13/12/2020 23:48:47

Type: Critical Category: 64

Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode

A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

 

Log: 'System' Date/Time: 28/11/2020 09:09:10

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 21/11/2020 12:32:39

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 21/11/2020 06:53:52

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 19/11/2020 04:26:04

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Log: 'System' Date/Time: 15/11/2020 12:47:35

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'System' Log - Error Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'System' Date/Time: 25/01/2021 09:13:49

Type: Error Category: 0

Event: 6008 Source: EventLog

The previous system shutdown at 16:10:56 on ?25/?01/?2021 was unexpected.

 

Log: 'System' Date/Time: 24/01/2021 11:34:04

Type: Error Category: 0

Event: 10005 Source: Microsoft-Windows-DistributedCOM

DCOM got error "1115" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}

 

Log: 'System' Date/Time: 24/01/2021 11:20:32

Type: Error Category: 0

Event: 6008 Source: EventLog

The previous system shutdown at 18:19:11 on ?24/?01/?2021 was unexpected.

 

Log: 'System' Date/Time: 24/01/2021 11:04:11

Type: Error Category: 0

Event: 6008 Source: EventLog

The previous system shutdown at 17:31:00 on ?24/?01/?2021 was unexpected.

 

Log: 'System' Date/Time: 23/01/2021 17:50:35

Type: Error Category: 0

Event: 10010 Source: Microsoft-Windows-DistributedCOM

The server microsoft.windowscommunicationsapps_16005.13426.20368.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.

 

Log: 'System' Date/Time: 23/01/2021 17:50:35

Type: Error Category: 0

Event: 10010 Source: Microsoft-Windows-DistributedCOM

The server Microsoft.MicrosoftOfficeHub_18.2008.12711.0_x64__8wekyb3d8bbwe!Microsoft.MicrosoftOfficeHub.AppXt4mh7c9swwc5cmd5jgmtmwcfmvkddpn1.mca did not register with DCOM within the required timeout.

 

Log: 'System' Date/Time: 22/01/2021 07:02:11

Type: Error Category: 0

Event: 36871 Source: Schannel

A fatal error occurred while creating a TLS client credential. The internal error state is 10013.

 

Log: 'System' Date/Time: 22/01/2021 07:01:57

Type: Error Category: 0

Event: 36871 Source: Schannel

A fatal error occurred while creating a TLS client credential. The internal error state is 10013.

 

Log: 'System' Date/Time: 17/01/2021 12:26:23

Type: Error Category: 0

Event: 10005 Source: Microsoft-Windows-DistributedCOM

DCOM got error "1115" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}

 

Log: 'System' Date/Time: 17/01/2021 12:08:30

Type: Error Category: 0

Event: 98 Source: Microsoft-Windows-Ntfs

Volume E: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

 

Log: 'System' Date/Time: 17/01/2021 12:03:41

Type: Error Category: 0

Event: 98 Source: Microsoft-Windows-Ntfs

Volume E: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

 

Log: 'System' Date/Time: 17/01/2021 11:53:47

Type: Error Category: 0

Event: 98 Source: Microsoft-Windows-Ntfs

Volume E: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

 

Log: 'System' Date/Time: 14/01/2021 22:34:49

Type: Error Category: 0

Event: 98 Source: Microsoft-Windows-Ntfs

Volume E: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

 

Log: 'System' Date/Time: 13/01/2021 07:36:38

Type: Error Category: 0

Event: 98 Source: Microsoft-Windows-Ntfs

Volume E: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

 

Log: 'System' Date/Time: 13/01/2021 07:35:28

Type: Error Category: 0

Event: 10005 Source: Microsoft-Windows-DistributedCOM

DCOM got error "1115" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}

 

Log: 'System' Date/Time: 13/01/2021 07:33:47

Type: Error Category: 0

Event: 98 Source: Microsoft-Windows-Ntfs

Volume E: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

 

Log: 'System' Date/Time: 10/01/2021 23:38:10

Type: Error Category: 0

Event: 36871 Source: Schannel

A fatal error occurred while creating a TLS client credential. The internal error state is 10013.

 

Log: 'System' Date/Time: 09/01/2021 18:01:43

Type: Error Category: 0

Event: 98 Source: Microsoft-Windows-Ntfs

Volume E: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

 

Log: 'System' Date/Time: 09/01/2021 15:13:48

Type: Error Category: 0

Event: 7031 Source: Service Control Manager

The NVIDIA LocalSystem Container service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 6000 milliseconds: Restart the service.

 

Log: 'System' Date/Time: 09/01/2021 15:13:48

Type: Error Category: 0

Event: 7023 Source: Service Control Manager

The NVIDIA LocalSystem Container service terminated with the following error:  A generic command executable returned a result that indicates failure.

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'System' Log - Warning Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'System' Date/Time: 26/01/2021 16:25:01

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  Windows.SecurityCenter.WscDataProtection  and APPID  Unavailable  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:25:01

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  Windows.SecurityCenter.WscBrokerManager  and APPID  Unavailable  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:25:01

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  Windows.SecurityCenter.SecurityAppBroker  and APPID  Unavailable  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:23:31

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:23:18

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:23:18

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:23:14

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:23:13

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.610_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:22:59

Type: Warning Category: 0

Event: 17 Source: Microsoft-Windows-WHEA-Logger

A corrected hardware error has occurred.  Component: PCI Express Endpoint Error Source: Advanced Error Reporting (PCI Express)  Primary Bus:Device:Function: 0xA:0x0:0x2 Secondary Bus:Device:Function: 0x0:0x0:0x0 Primary Device Name:PCI\VEN_10DE&DEV_1AEC&SUBSYS_132410DE&REV_A1 Secondary Device Name:

 

Log: 'System' Date/Time: 26/01/2021 16:22:59

Type: Warning Category: 0

Event: 17 Source: Microsoft-Windows-WHEA-Logger

A corrected hardware error has occurred.  Component: PCI Express Endpoint Error Source: Advanced Error Reporting (PCI Express)  Primary Bus:Device:Function: 0x1:0x0:0x0 Secondary Bus:Device:Function: 0x0:0x0:0x0 Primary Device Name:PCI\VEN_1CC1&DEV_8201&SUBSYS_82011CC1&REV_03 Secondary Device Name:

 

Log: 'System' Date/Time: 26/01/2021 16:22:59

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  {7022A3B3-D004-4F52-AF11-E9E987FEE25F}  and APPID  {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:22:59

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  {7022A3B3-D004-4F52-AF11-E9E987FEE25F}  and APPID  {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:22:59

Type: Warning Category: 0

Event: 17 Source: Microsoft-Windows-WHEA-Logger

A corrected hardware error has occurred.  Component: PCI Express Endpoint Error Source: Advanced Error Reporting (PCI Express)  Primary Bus:Device:Function: 0xA:0x0:0x1 Secondary Bus:Device:Function: 0x0:0x0:0x0 Primary Device Name:PCI\VEN_10DE&DEV_1AEB&SUBSYS_132410DE&REV_A1 Secondary Device Name:

 

Log: 'System' Date/Time: 26/01/2021 16:22:59

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  {7022A3B3-D004-4F52-AF11-E9E987FEE25F}  and APPID  {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 16:14:38

Type: Warning Category: 0

Event: 17 Source: Microsoft-Windows-WHEA-Logger

A corrected hardware error has occurred.  Component: PCI Express Root Port Error Source: Advanced Error Reporting (PCI Express)  Primary Bus:Device:Function: 0x0:0x1:0x1 Secondary Bus:Device:Function: 0x0:0x0:0x0 Primary Device Name:PCI\VEN_1022&DEV_1483&SUBSYS_14531022&REV_00 Secondary Device Name:

 

Log: 'System' Date/Time: 26/01/2021 11:50:55

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.610_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 11:50:29

Type: Warning Category: 1014

Event: 1014 Source: Microsoft-Windows-DNS-Client

Name resolution for the name user.drivermax.com timed out after none of the configured DNS servers responded.

 

Log: 'System' Date/Time: 26/01/2021 11:50:21

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.610_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 11:50:18

Type: Warning Category: 0

Event: 10016 Source: Microsoft-Windows-DistributedCOM

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user SOL\REKA SID (S-1-5-21-3015468460-4228945627-1467974525-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.610_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

 

Log: 'System' Date/Time: 26/01/2021 07:51:29

Type: Warning Category: 0

Event: 17 Source: Microsoft-Windows-WHEA-Logger

A corrected hardware error has occurred.  Component: PCI Express Root Port Error Source: Advanced Error Reporting (PCI Express)  Primary Bus:Device:Function: 0x0:0x1:0x1 Secondary Bus:Device:Function: 0x0:0x0:0x0 Primary Device Name:PCI\VEN_1022&DEV_1483&SUBSYS_14531022&REV_00 Secondary Device Name:

 

 

VEW result on application:

 

Vino's Event Viewer v01c run on Windows 7 in English

Report run at 26/01/2021 23:28:45

 

Note: All dates below are in the format dd/mm/yyyy

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'Application' Log - Critical Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'Application' Log - Error Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'Application' Date/Time: 26/01/2021 11:50:21

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 26/01/2021 11:50:21

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

Log: 'Application' Date/Time: 26/01/2021 11:50:18

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 26/01/2021 11:50:18

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

Log: 'Application' Date/Time: 26/01/2021 06:07:27

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 26/01/2021 06:07:27

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

Log: 'Application' Date/Time: 26/01/2021 06:07:25

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 26/01/2021 06:07:25

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

Log: 'Application' Date/Time: 25/01/2021 10:57:18

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 25/01/2021 10:57:18

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

Log: 'Application' Date/Time: 25/01/2021 10:57:15

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 25/01/2021 10:57:15

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

Log: 'Application' Date/Time: 25/01/2021 09:29:30

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 25/01/2021 09:29:30

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

Log: 'Application' Date/Time: 25/01/2021 09:29:28

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 25/01/2021 09:29:28

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

Log: 'Application' Date/Time: 25/01/2021 09:20:53

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 25/01/2021 09:20:53

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

Log: 'Application' Date/Time: 25/01/2021 09:20:51

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=55, authorId=311, vendorId=0, vendorType=0

 

Log: 'Application' Date/Time: 25/01/2021 09:20:51

Type: Error Category: 2

Event: 2002 Source: Microsoft-Windows-EapHost

Skipping: Eap method DLL path validation failed. Error: typeId=254, authorId=311, vendorId=14122, vendorType=1

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'Application' Log - Warning Type

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Log: 'Application' Date/Time: 26/01/2021 16:22:59

Type: Warning Category: 1

Event: 642 Source: ESENT

Catalog Database (4588,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 26/01/2021 16:22:59

Type: Warning Category: 1

Event: 642 Source: ESENT

Catalog Database (4588,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 26/01/2021 07:57:09

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (13900,D,22) {22F718DB-257D-4539-8F1E-227082D12C10}: The database format feature version 9120 (0x23a0) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 18:29:36

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (13900,D,2) {22F718DB-257D-4539-8F1E-227082D12C10}: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 18:29:36

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (13900,D,2) {22F718DB-257D-4539-8F1E-227082D12C10}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 18:29:36

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (13900,D,12) {22F718DB-257D-4539-8F1E-227082D12C10}: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 18:29:36

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (13900,D,50) {22F718DB-257D-4539-8F1E-227082D12C10}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 18:29:36

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (13900,R,98) {22F718DB-257D-4539-8F1E-227082D12C10}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 12:57:54

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (5140,D,2) {8F80258E-4D40-47FA-8919-A2AA88BFDC81}: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 12:57:54

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (5140,D,2) {8F80258E-4D40-47FA-8919-A2AA88BFDC81}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 12:57:54

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (5140,D,12) {8F80258E-4D40-47FA-8919-A2AA88BFDC81}: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 12:57:54

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (5140,D,50) {8F80258E-4D40-47FA-8919-A2AA88BFDC81}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 12:57:54

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (5140,R,98) {8F80258E-4D40-47FA-8919-A2AA88BFDC81}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 10:14:42

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (14772,D,2) {5720332A-2503-4971-B51C-ABB845BA973F}: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 10:14:42

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (14772,D,2) {5720332A-2503-4971-B51C-ABB845BA973F}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 10:14:42

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (14772,D,12) {5720332A-2503-4971-B51C-ABB845BA973F}: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 10:14:42

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (14772,D,50) {5720332A-2503-4971-B51C-ABB845BA973F}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 10:14:42

Type: Warning Category: 1

Event: 642 Source: ESENT

Video.UI (14772,R,98) {5720332A-2503-4971-B51C-ABB845BA973F}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 09:44:37

Type: Warning Category: 1

Event: 642 Source: ESENT

Catalog Database (4076,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Log: 'Application' Date/Time: 25/01/2021 09:44:37

Type: Warning Category: 1

Event: 642 Source: ESENT

Catalog Database (4076,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

 

Edited by sukucoy, 26 January 2021 - 10:57 AM.

[RKinner]

Lots of errors. Some might be important for your problem.  I see a lot of unexpected shutdowns.  Is it crashing or are you having power problems?

 

Log: 'System' Date/Time: 25/01/2021 09:13:43

Type: Critical Category: 63

Event: 41 Source: Microsoft-Windows-Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Windows does not do well  with unexpected shutdowns.  Always try to shut your PC down properly.

 

 

Log: 'System' Date/Time: 17/01/2021 12:08:30

Type: Error Category: 0

Event: 98 Source: Microsoft-Windows-Ntfs

Volume E: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk.

 

 

 

I don't know what the E: drive is it but it needs to have chkdsk run

 

Open an Elevated Command Prompt:
Win 7: Start, All Programs, Accessories then right click on Command Prompt and Run as Administrator
Win 8: http://www.eightforu...indows-8-a.html
win 10: http://www.howtogeek...-in-windows-10/

type:

chkdsk  /f  e:

 

Log: 'System' Date/Time: 26/01/2021 16:22:59

Type: Warning Category: 0

Event: 17 Source: Microsoft-Windows-WHEA-Logger

A corrected hardware error has occurred.  Component: PCI Express Endpoint Error Source: Advanced Error Reporting (PCI Express)  Primary Bus:Device:Function: 0xA:0x0:0x2 Secondary Bus:Device:Function: 0x0:0x0:0x0 Primary Device Name:PCI\VEN_10DE&DEV_1AEC&SUBSYS_132410DE&REV_A1 Secondary Device Name:

 

 

 

This may be caused by the USB controller driver.  Check with your PC maker's support page to see if there is a new driver.  This error probably happens after a restart so it may be an important part of your problem.

What make and Model number PC is this and what version of Windows?  (I'm guessing Win 10 version 2004 based on some of the errors I see)

 

Assuming it is Win 10 it would not hurt to run DISM & SFC:

 

Open an elevated command prompt:

http://www.howtogeek...-in-windows-10/
http://www.eightforu...indows-8-a.html

(If you open an elevated Command Prompt properly it will say Administrator: Command Prompt in the margin at the top of the window)


Once you have an elevated command prompt:

Type:

 DISM  /Online  /Cleanup-Image  /RestoreHealth

 

 (I use two spaces so you can be sure to see where one space goes.)
Hit Enter.  This will take a while (10-20 minutes) to complete.  Once the prompt returns:

Reboot.  Open an elevated Command Prompt again and type (with an Enter after the line):

sfc  /scannow

 

This will also take a few minutes.  

When it finishes it will say one of the following:

Windows did not find any integrity violations (a good thing)
Windows Resource Protection found corrupt files and repaired them (a good thing)
Windows Resource Protection found corrupt files but was unable to fix some (or all) of them (not a good thing)

If you get the last result then type:

findstr  /c:"[SR]"  \windows\logs\cbs\cbs.log  >  %UserProfile%\desktop\junk.txt

 

Hit Enter.  Then type::

notepad  %UserProfile%\desktop\junk.txt

 

Hit Enter.

 Copy the text from notepad and paste it into a reply.


 

 

 

 

 

 

 

[sukucoy]

 

 

I see a lot of unexpected shutdowns.  Is it crashing or are you having power problems?

 

 

there were blackouts and I think I've only did a hard restart once since the focusrite issue.

 

I rarely do a shutdown, but when I do usually its a normal shutdown/restart. most of the time i just put it to sleep.

 

 

 

I don't know what the E: drive is it but it needs to have chkdsk run

 

 

E: drive was an external HDD

 

 

This may be caused by the USB controller driver.  Check with your PC maker's support page to see if there is a new driver.  This error probably happens after a restart so it may be an important part of your problem.

What make and Model number PC is this and what version of Windows?  (I'm guessing Win 10 version 2004 based on some of the errors I see)

 

Assuming it is Win 10 it would not hurt to run DISM & SFC:

Yes, Im running on a win10 version 2004.

 

I ran DISM & SFC twice

 

SFC right after DISM Without reboot: Windows Resource Protection found corrupt files and repaired them

2nd SFC after reboot: Windows did not find any integrity violations

[RKinner]

What make and Model number PC is this?  Also give me the service tag if it has one.

[sukucoy]

What make and Model number PC is this?  Also give me the service tag if it has one.

 

I assume this is the answer of the question? I'm not sure.

[RKinner]

Make sure you have the latest BIOS and Chipset  & Audio drivers.  They are available near the bottom of:

https://www.galax.co...otherboard.html

 

Let's also do a dxdiag:

 

Search for:

dxdiag

hit Enter

 

It will start automatically.

When it finishes, Save All Information as dxdiag.txt to your desktop (or somewhere you can find it)  Then attach it to a reply.

[sukucoy]

I updated BIOS and reinstalled Chipset & Audio drivers just to make sure its up to date.

 

as for dxdiag:

 DxDiag.txt   60.92KB   252 downloads

 

oh and I screenshot some description on the troubleshooter window when the focusrite USB audio stopped working

 

everything stays plugged in

Edited by sukucoy, 26 January 2021 - 09:10 PM.

[RKinner]

DxDiag says:

Description: LC24RG50 (2- NVIDIA High Definition Audio)
 Default Sound Playback: No
 Default Voice Playback: Yes

and

Description: Speakers (10- Focusrite Usb Audio)
 Default Sound Playback: No
 Default Voice Playback: No

 

and

 

          Description: Speakers (Realtek High Definition Audio)
 Default Sound Playback: Yes
 Default Voice Playback: No

 

I don't have multiple sound devices so I can't play with the options but I wonder if it would help to make the Focusrite the Default?  Perhaps Windows is getting confused?

If you search for

control panel

and hit Enter then View by: Large Icons then click on Sound then select Focusrite

there is a Set Default button at the bottom to set the default.  It's greyed out on mine since I only have the one but should be a possibility on yours.

 

Also there may be something in Settings:

 

Search for

settings

hit Enter

Select System then Sound

Under Output try selecting Focusrite where it says Choose your Output Device.

 

You can also click on Manage Sound Devices and it should show you the three devices.  You can click on the nonFocusrite devices and you will see an option to Disable the device.  Perhaps if you disable the others Windows will keep working with Focusrite.

 

 

At the bottom of DxDiag is a list of errors.  You have more than I normally see but most don't tell me much.  I do see:

 

Windows Error Reporting:
+++ WER0 +++:
Fault bucket LKD_0x144_INVALID_TRANSFER_EVENT_PTR_ED_0_DUPLICATE_USBXHCI!TelemetryData_CreateReport_VEN_1022_DEV_43D5_REV_01, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: fa0247a2-0be3-437e-9ddf-5f6f1e98af12

which refers to
 

AMD 400 Series Chipset USB 3.1 XHCI Controller

 

Sometimes you can fix this by going into Device Manager and and right clicking on each device under USB Controller and uninstall then reboot.  Windows will detect and reinstall all of the USB devices and that may help.  (Do not allow it to remove any drivers if it asks)

 

Also:

 

+++ WER5 +++:
Fault bucket 2169670832464090866, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: AfterFX.exe
P2: 17.1.1.34
P3: 10.0.19041.2.0.0

 

 

 

AfterFX.exe is part of Adobe After Effects.  Look and see if there is a newer version that doesn't have the memory leak.  Probably not part of your problem but I really hate software that is so poorly written that it has a memory leak.

[sukucoy]

I don't have multiple sound devices so I can't play with the options but I wonder if it would help to make the Focusrite the Default?  Perhaps Windows is getting confused?

i usually switch between realtek HD (speakers) and focusrite audio (headset). The other was just enabled because i did a BIOS update and havent disabled it when i ran dxdiag

 

here's a dxdiag run with focusrite as the default

 DxDiag focusrite default.txt   59.16KB   257 downloads

 

which refers to

 

AMD 400 Series Chipset USB 3.1 XHCI Controller

 

Sometimes you can fix this by going into Device Manager and and right clicking on each device under USB Controller and uninstall then reboot.  Windows will detect and reinstall all of the USB devices and that may help.  (Do not allow it to remove any drivers if it asks) 

 

 

 

i'll do this in the meantime

[sukucoy]

UPDATE: A FRIEND CAME THRU WITH A FIX AND NOW IT FIXED

 

looks like there was something in the focusrite registry, so he suggested to uninstall and wipe out everything about focusrite on the registry before installing it again.

 

so far i've tried 3 reboots and it still working just fine

[RKinner]

OK thanks for the update.