Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

PC is freezing and/or forcefully rebooting when I use the i7. Possibly


  • Please log in to reply

#1
axl2468

axl2468

    Member

  • Member
  • PipPip
  • 67 posts

edit: Drat, I forgot to finish typing my title lol

 

Hello,

 

I currently have a Sandy Bridge system and I currently have two processors: an i3 2100, and an i7 2600.

 

Whenever I use the i3, the PC is fine. However, when I use the i7 (at first it boots properly), the two things could happen to the PC:

 

1. The PC suddenly reboots back to the BIOs splash screen.

2. The PC freezes, forcing me to reboot the system (sometimes the USB ports can also stop working).

 

I checked the memory, but it wasn't a problem as I tested it with other sticks of RAM that I had (that I was sure had no problems).

 

I also checked if it was the GPU's fault, but the problem persists even when I used the integrated graphics instead.

 

I don't think it was the PSU, as I'm using a good quality model and brand. Also, problem persists when I use another PSU.

 

I don't think it was the motherboard, since I can the PC just fine with the i3.

 

However, I did notice that when I used memtest86 on my RAM sticks while having the i7, there would be errors (one test had 1 error at the 7th test and 10th test, both at pass 3; the other had 20 errors in the 7th test, at pass 1).

When I used memtest86 after replacing the i7 with the i3, I found no errors.

 

Is it possible that there my i7 has a faulty component (I think likely the memory controller)?

 

Anyways, here are my current system specs:

Attached Files


Edited by RKinner, 04 July 2020 - 09:45 AM.

  • 0

Advertisements


#2
RKinner

RKinner

    Malware Expert

  • Expert
  • 22,923 posts
  • MVP

You do have some hard drive errors:

 

C6
                                            Attribute name    Uncorrectable Sector Count
                                            Real value    4
                                            Current    200
                                            Worst    200
                                            Threshold    0
                                            Raw Value    0000000004
                                            Status    Good
                                        C7
                                            Attribute name    UltraDMA CRC Error Count
                                            Real value    552,265
                                            Current    200
                                            Worst    1
                                            Threshold    0
                                            Raw Value    0000086D49
                                            Status    Good
                                        C8
                                            Attribute name    Write Error Rate / Multi-Zone Error Rate
                                            Real value    2
                                            Current    200
                                            Worst    200
                                            Threshold    0
                                            Raw Value    0000000002
                                            Status    Good

Probably need to run a disk check:

 

Open an elevated command prompt

http://www.howtogeek...-in-windows-10/

Type:

chkdsk /r c:

 

then tell it Y and reboot.  Will take a few hours to complete.

 

Then

Open an elevated command prompt:

http://www.howtogeek...-in-windows-10/

(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.


After you finish SFC, regardless of the result:



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

 

Are you sure when you switch CPUs that you are replacing the thermal paste correctly?  Could it be overheating?

 


  • 0

#3
axl2468

axl2468

    Member

  • Topic Starter
  • Member
  • PipPip
  • 67 posts

Yeah, I think those hard drive errors were caused by the continuous freezing and rebooting of the PC when I still had the i7 on the motherboard. In fact, Windows automatically did disk repair after one of the forced reboots.

 

Anyways, I did what you asked:

 

For sfc /scannow, Windows Resource Protection did not find any integrity violations.

 

First output:

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 05/07/2020 10:31:18 am
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 03/07/2020 11:40:08 am
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/07/2020 11:09:12 am
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/07/2020 10:47:05 am
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/07/2020 10:18:06 am
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/07/2020 9:58:16 am
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/07/2020 2:45:01 am
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/07/2020 1:35:41 am
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/07/2020 1:10:21 am
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: 01/07/2020 8:50:28 am
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: 01/07/2020 12:38:28 am
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: 30/06/2020 1:08:40 pm
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: 30/06/2020 12:46:28 pm
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: 30/06/2020 12:21:36 pm
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: 30/06/2020 11:27:58 am
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: 29/06/2020 12:19:28 am
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: 28/06/2020 12:44:29 pm
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: 28/06/2020 3:10:22 am
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: 27/06/2020 2:40:48 am
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: 27/06/2020 2:15:25 am
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: 26/06/2020 5:33:37 am
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: 05/07/2020 1:36:24 am
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server microsoft.windowscommunicationsapps_16005.12827.20400.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 05/07/2020 1:36:23 am
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server Microsoft.WindowsFeedbackHub_1.1907.3152.0_x64__8wekyb3d8bbwe!App.AppXsdjy3vfbpyyren487rr1k4k8g5t1k844.mca did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 05/07/2020 1:36:23 am
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 05/07/2020 1:36:23 am
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server NcsiUwpApp_1000.19041.1.0_neutral_neutral_8wekyb3d8bbwe!App.AppXw175g9nmx2zykh9fyt6xjc0xf8vmj1w6.mca did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 05/07/2020 1:36:23 am
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1_neutral_neutral_cw5n1h2txyewy!App.AppXx4zfy1ffv3wctgdz2vypnybzjkh27jhw.mca did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 05/07/2020 1:36:23 am
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server Microsoft.MicrosoftOfficeHub_18.2005.1191.0_x64__8wekyb3d8bbwe!Microsoft.MicrosoftOfficeHub.AppXt4mh7c9swwc5cmd5jgmtmwcfmvkddpn1.mca did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 04/07/2020 9:25:09 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 9:25:06 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 9:25:04 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 9:25:01 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 9:24:59 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 9:24:56 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 9:24:54 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 9:24:51 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 9:24:48 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 6:53:10 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 6:53:08 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 6:53:05 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 6:53:02 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
Log: 'System' Date/Time: 04/07/2020 6:52:59 am
Type: Error Category: 0
Event: 7 Source: disk
The device, \Device\Harddisk0\DR0, has a bad block.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 05/07/2020 2:10:42 am
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-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: 05/07/2020 2:08:45 am
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: 05/07/2020 2:08:45 am
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: 05/07/2020 2:08:45 am
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: 05/07/2020 1:40:59 am
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-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: 05/07/2020 1:40:08 am
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: 05/07/2020 1:40:08 am
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: 05/07/2020 1:40:08 am
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: 05/07/2020 1:33:21 am
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-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: 04/07/2020 12:58:49 pm
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.1_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: 04/07/2020 12:58:48 pm
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.1_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: 04/07/2020 12:58:36 pm
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.1_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: 04/07/2020 12:58:17 pm
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.1_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: 04/07/2020 11:45:16 am
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-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: 04/07/2020 11:45:02 am
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-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: 04/07/2020 11:43:23 am
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.1_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: 04/07/2020 11:38:28 am
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.1_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: 04/07/2020 10:30:07 am
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-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: 04/07/2020 2:07:37 am
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 DESKTOP-FK5518F\Axl SID (S-1-5-21-149550382-1744679906-194812198-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: 04/07/2020 1:43:17 am
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name r7---sn-2aqu-hoaek.googlevideo.com timed out after none of the configured DNS servers responded.
 
Second output:
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 05/07/2020 10:35:20 am
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 05/07/2020 2:03:23 am
Type: Error Category: 0
Event: 264 Source: Microsoft-Windows-Defrag
The storage optimizer couldn't complete retrim on System Reserved because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
 
Log: 'Application' Date/Time: 04/07/2020 12:31:27 pm
Type: Error Category: 0
Event: 264 Source: Microsoft-Windows-Defrag
The storage optimizer couldn't complete retrim on System Reserved because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
 
Log: 'Application' Date/Time: 04/07/2020 9:45:32 am
Type: Error Category: 0
Event: 264 Source: Microsoft-Windows-Defrag
The storage optimizer couldn't complete retrim on System Reserved because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
 
Log: 'Application' Date/Time: 04/07/2020 9:20:33 am
Type: Error Category: 0
Event: 264 Source: Microsoft-Windows-Defrag
The storage optimizer couldn't complete retrim on System Reserved because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
 
Log: 'Application' Date/Time: 04/07/2020 9:15:07 am
Type: Error Category: 0
Event: 264 Source: Microsoft-Windows-Defrag
The storage optimizer couldn't complete retrim on System Reserved because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
 
Log: 'Application' Date/Time: 04/07/2020 8:29:55 am
Type: Error Category: 0
Event: 264 Source: Microsoft-Windows-Defrag
The storage optimizer couldn't complete retrim on System Reserved because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
 
Log: 'Application' Date/Time: 04/07/2020 8:15:34 am
Type: Error Category: 0
Event: 264 Source: Microsoft-Windows-Defrag
The storage optimizer couldn't complete retrim on System Reserved because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
 
Log: 'Application' Date/Time: 04/07/2020 7:06:34 am
Type: Error Category: 0
Event: 264 Source: Microsoft-Windows-Defrag
The storage optimizer couldn't complete retrim on System Reserved because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
 
Log: 'Application' Date/Time: 04/07/2020 6:39:46 am
Type: Error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW.  hr = 0x80070006, The handle is invalid. . 
 
Operation:
   Executing Asynchronous Operation
 
Context:
   Current State: DoSnapshotSet
 
Log: 'Application' Date/Time: 03/07/2020 11:41:05 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x1870 Faulting application start time: 0x01d6512ed0171709 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: ee657c4d-b756-4997-9f7b-5b08d486e980 Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 11:10:42 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x2124 Faulting application start time: 0x01d6512a97234ec5 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: 947b5c9a-ea96-4cf5-aa61-02cf8ceb25fe Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 11:10:35 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x22ec Faulting application start time: 0x01d6512a92fe2554 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: e4803113-3b7a-449b-acd7-eacf44d10c0d Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 11:10:30 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x2054 Faulting application start time: 0x01d6512a901b1653 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: 279f80da-7e7e-435a-b22f-66f10241a4e8 Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 11:10:22 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x219c Faulting application start time: 0x01d6512a8b303905 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: c0730eb5-d460-4c16-9365-0f058c33130d Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 11:10:16 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x1c2c Faulting application start time: 0x01d6512a87cd81b4 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: 8e0acd0b-7bb2-480e-b493-985d8d8c914e Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 11:10:04 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x19dc Faulting application start time: 0x01d6512a7e0ebdf3 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: 2a85fbdb-d3dd-4a4e-b523-0c3b3a3535f3 Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 10:49:13 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x1b70 Faulting application start time: 0x01d651279680897f Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: afe7558b-2e9d-4872-a952-1572e061865c Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 10:49:06 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0xdb8 Faulting application start time: 0x01d651279251d3f4 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: 562ecd21-ff21-40c9-9a47-407ec9a919e3 Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 10:48:59 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x20a8 Faulting application start time: 0x01d651278e0b7c99 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: 31230957-8084-4846-98de-934afb204610 Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
Log: 'Application' Date/Time: 03/07/2020 10:48:49 am
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchApp.exe, version: 10.0.19041.153, time stamp: 0x0ba6e048 Faulting module name: ConstraintIndex.Search.dll, version: 10.0.19041.153, time stamp: 0x4f1e28d8 Exception code: 0xc0000005 Fault offset: 0x00000000000b4f91 Faulting process id: 0x1b30 Faulting application start time: 0x01d6512788a0aa53 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe Faulting module path: C:\Windows\System32\ConstraintIndex.Search.dll Report Id: 7be9d9c4-e526-4317-bb23-f4474ad7d901 Faulting package full name: Microsoft.Windows.Search_1.14.0.19041_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 05/07/2020 2:25:18 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (8080,D,2) {EFE35FC5-C1A3-4149-B5A8-6737E8C45A49}: 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: 05/07/2020 2:25:18 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (8080,D,2) {EFE35FC5-C1A3-4149-B5A8-6737E8C45A49}: 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: 05/07/2020 2:25:18 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (8080,D,12) {EFE35FC5-C1A3-4149-B5A8-6737E8C45A49}: 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: 05/07/2020 2:25:18 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (8080,D,50) {EFE35FC5-C1A3-4149-B5A8-6737E8C45A49}: 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: 05/07/2020 2:25:18 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (8080,R,98) {EFE35FC5-C1A3-4149-B5A8-6737E8C45A49}: 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: 05/07/2020 2:24:07 am
Type: Warning Category: 1
Event: 642 Source: ESENT
MicrosoftEdge (5732,D,12) C:\Users\Axl\AppData\Local\Packages\microsoft.microsoftedge_8wekyb3d8bbwe\AC\MicrosoftEdge\User\Default\DataStore\Data\nouser1\120712-0049\: 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: 05/07/2020 2:24:07 am
Type: Warning Category: 1
Event: 642 Source: ESENT
MicrosoftEdge (5732,R,98) C:\Users\Axl\AppData\Local\Packages\microsoft.microsoftedge_8wekyb3d8bbwe\AC\MicrosoftEdge\User\Default\DataStore\Data\nouser1\120712-0049\: 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: 05/07/2020 2:06:33 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Catalog Database (3216,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: 05/07/2020 2:06:33 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Catalog Database (3216,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: 05/07/2020 1:42:06 am
Type: Warning Category: 1
Event: 642 Source: ESENT
MicrosoftEdge (1140,D,12) C:\Users\Axl\AppData\Local\Packages\microsoft.microsoftedge_8wekyb3d8bbwe\AC\MicrosoftEdge\User\Default\DataStore\Data\nouser1\120712-0049\: 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: 05/07/2020 1:42:06 am
Type: Warning Category: 1
Event: 642 Source: ESENT
MicrosoftEdge (1140,R,98) C:\Users\Axl\AppData\Local\Packages\microsoft.microsoftedge_8wekyb3d8bbwe\AC\MicrosoftEdge\User\Default\DataStore\Data\nouser1\120712-0049\: 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: 05/07/2020 1:38:03 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Catalog Database (2076,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: 05/07/2020 1:38:03 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Catalog Database (2076,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: 04/07/2020 7:52:38 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (9760,D,2) {37799F73-6C17-4BC2-A8D6-AB7A163A5E7D}: 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: 04/07/2020 7:52:38 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (9760,D,2) {37799F73-6C17-4BC2-A8D6-AB7A163A5E7D}: 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: 04/07/2020 7:52:38 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (9760,D,12) {37799F73-6C17-4BC2-A8D6-AB7A163A5E7D}: 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: 04/07/2020 7:52:38 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (9760,D,50) {37799F73-6C17-4BC2-A8D6-AB7A163A5E7D}: 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: 04/07/2020 7:52:38 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (9760,R,98) {37799F73-6C17-4BC2-A8D6-AB7A163A5E7D}: 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: 04/07/2020 7:49:13 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (5096,D,2) {A6382B64-D4B3-4DCE-BD56-CB7BAB489E78}: 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: 04/07/2020 7:49:13 am
Type: Warning Category: 1
Event: 642 Source: ESENT
Video.UI (5096,D,2) {A6382B64-D4B3-4DCE-BD56-CB7BAB489E78}: 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).
 
Also, no I don't think it was caused by overheating. The temperatures for the i3 and i7 were very similar (I added new thermal paste for both processors). Also, I checked the CPU temperatures, they would idle around 30-40 Celsius (and around 40-50 when Wallpaper Engine is on).

Edited by axl2468, 04 July 2020 - 08:41 PM.

  • 0

#4
RKinner

RKinner

    Malware Expert

  • Expert
  • 22,923 posts
  • MVP

The i7 requires 95 w vs the i3's 65 w.  Presumably your PSA has enough extra power that the 30 additional watts won't drag it down.

 

I checked with your motherboard maker and the i7 2600 is supported:

 

https://www.ecs.com....55-LL-Intel-RR-

 

I'm wondering if the BIOS needs to be reset to the default or otherwise modified in order to compensate for the difference in CPUs?  I'd go through each page of the BIOS and note how it was set before trying to reset it to default.

 

Doubtful that the i7 could cause bad sectors on a drive. 

 

Have you had an SSD in this system at some time?  One of the errors talks about retrim which is something you do to an SSD and not a standard hard drive.


  • 0

#5
axl2468

axl2468

    Member

  • Topic Starter
  • Member
  • PipPip
  • 67 posts
Nope, I've never used an SSD.

Anyways, I'll try your suggestion. I'll post in this thread again if the problem persists.

Edited by axl2468, 04 July 2020 - 11:39 PM.

  • 0

#6
axl2468

axl2468

    Member

  • Topic Starter
  • Member
  • PipPip
  • 67 posts
Same thing happens, unfortunately.

Any idea on what I can still do? Or is the processor really faulty?
  • 0

#7
RKinner

RKinner

    Malware Expert

  • Expert
  • 22,923 posts
  • MVP

Does it still fail the memtest?

 

Seems to be with such major differences in processors that Windows might need to be setup differently so you might want to get the bootable version of Win 10 on USB:

 

https://www.microsof...nload/windows10

 

Click on Download Tool Now and follow the instructions to create a bootable USB.  Then boot off it and use it to repair or reinstall windows.


  • 0

#8
axl2468

axl2468

    Member

  • Topic Starter
  • Member
  • PipPip
  • 67 posts

Hmm, I've never tried memtest with the BIOS settings set to default. I'll try that first.

 

Also, would it be possible to try to use a USB bootable OS without needing to reinstall Windows? Maybe with Linux, perhaps?


  • 0

#9
RKinner

RKinner

    Malware Expert

  • Expert
  • 22,923 posts
  • MVP

Should be able to run from USB:

 

https://www.pcmag.co...rom-a-usb-drive

 

You could also try Hiren's:

 

https://www.hirensbo...rg/usb-booting/

 

Get the .iso from:

https://www.hirensbo...HBCD_PE_x64.iso


  • 0

#10
axl2468

axl2468

    Member

  • Topic Starter
  • Member
  • PipPip
  • 67 posts

Ah, I see.

I'll try to boot Windows from a USB once I'm done with the memtest.

 

EDIT TO ADD:

Memtest finished, no errors.

 

Also,

Apparently my USB drive doesn't have enough space for a bootable Windows 10. I have no other higher capacity drives, so it appears the only option that I have is a Linux (I'll choose Ubuntu).


Edited by axl2468, Today, 01:49 AM.

  • 0

#11
axl2468

axl2468

    Member

  • Topic Starter
  • Member
  • PipPip
  • 67 posts

EDIT: Drat. PC rebooted itself again (while using Ubuntu on a USB) after I thought that the system was working fine.

 

I guess my i7 really is faulty?


Edited by axl2468, Today, 03:25 AM.

  • 0

#12
RKinner

RKinner

    Malware Expert

  • Expert
  • 22,923 posts
  • MVP

I'd try Hiren's before I gave up.  Or maybe get another SATA drive and try installing on it.  That way you won't lose your first installation.  Doesn't have to be as big.  All you need is 20 GB or so.  In a pinch you could shrink one of the partitions on your current drive and create a new partition and dual boot.


  • 0

#13
axl2468

axl2468

    Member

  • Topic Starter
  • Member
  • PipPip
  • 67 posts

Using Hiren's right now. Nothing bad is happening yet, but I want to test longer just to be sure.

 

Would just leaving it to play Youtube videos (with autoplay on) be a good way to test it, or is there a better way?


  • 0






Similar Topics

2 user(s) are reading this topic

1 members, 1 guests, 0 anonymous users


    axl2468

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP