I have a question 2

[Ofir aviel]

hi,

i keep getting this error when i log in on windows 10:

does anyone know how to get rid of this error message?

[Murasaki]

First I'd try running a system file check (Open the command prompt as Administrator, type sfc /scannow and hit Enter)

[Ofir aviel]

5 minutes ago, Murasaki said:

First I'd try running a system file check (Open the command prompt as Administrator, type sfc /scannow and hit Enter)

i ran it, and it showed this:

Quote

C:\Windows\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

but it still shows the error

[Murasaki]

Not sure what else to do then. A lot recommend running the Windows Memory Diagnostic tool or disabling Windows Error Reporting which seems to not really fix this issue.

[GuiltySpark_]

That's Windows telling you your memory is having a problem. 

 

1. Search for "Windows Memory Diagnostic" in your start menu, and run the application.
2. Select "Restart now and check for problems." ...
3. Once restarted, wait for the result message

[Ofir aviel]

1 minute ago, rickeo said:

That's Windows telling you your memory is having a problem. 

 

1. Search for "Windows Memory Diagnostic" in your start menu, and run the application.
2. Select "Restart now and check for problems." ...
3. Once restarted, wait for the result message

It's running now, and I am waiting for it to finish

[Ofir aviel]

2 hours ago, rickeo said:

That's Windows telling you your memory is having a problem. 

 

1. Search for "Windows Memory Diagnostic" in your start menu, and run the application.
2. Select "Restart now and check for problems." ...
3. Once restarted, wait for the result message

it worked!
i am not getting this error anymore