F5F Stay Refreshed Hardware Desktop Issues during power-off Malfunctions when shutting down

Issues during power-off Malfunctions when shutting down

Issues during power-off Malfunctions when shutting down

W
WolfyNya
Member
125
03-26-2022, 01:44 AM
#1
I've been experiencing these odd issues when shutting down, though they're not frequent. I ran the command 'sfc scannow' and found no corruption—just a similar result with different numbers.
W
WolfyNya
03-26-2022, 01:44 AM #1

I've been experiencing these odd issues when shutting down, though they're not frequent. I ran the command 'sfc scannow' and found no corruption—just a similar result with different numbers.

X
XknockMC
Member
121
03-31-2022, 05:50 AM
#2
Is the issue caused by explorer.exe? Does the same program consistently trigger the problem, or does it vary? The persistent error during shutdown, especially after a hardware failure, has been ongoing since last year, and no solution has been identified yet.
X
XknockMC
03-31-2022, 05:50 AM #2

Is the issue caused by explorer.exe? Does the same program consistently trigger the problem, or does it vary? The persistent error during shutdown, especially after a hardware failure, has been ongoing since last year, and no solution has been identified yet.

M
Misli
Member
110
03-31-2022, 06:55 AM
#3
It appears explorer.exe is running, but I can't identify the exact program triggering it. The original window often didn't appear.
M
Misli
03-31-2022, 06:55 AM #3

It appears explorer.exe is running, but I can't identify the exact program triggering it. The original window often didn't appear.

M
Mostacheu
Member
63
04-02-2022, 04:50 AM
#4
Refers to a memory read failure at a specific location. Looks like one of Explorer’s scripts has corruption, and when the app ends it thinks it wasn’t closed right, causing this issue. Alternatively, another program might be affecting the memory Explorer uses. I’d run a RAM test using tools like Memtest86 or Windows Memory Diagnostic. If the problem continues, it’s likely a Windows software concern.
M
Mostacheu
04-02-2022, 04:50 AM #4

Refers to a memory read failure at a specific location. Looks like one of Explorer’s scripts has corruption, and when the app ends it thinks it wasn’t closed right, causing this issue. Alternatively, another program might be affecting the memory Explorer uses. I’d run a RAM test using tools like Memtest86 or Windows Memory Diagnostic. If the problem continues, it’s likely a Windows software concern.

V
varsitymendes
Member
64
04-02-2022, 06:57 AM
#5
Ignoring the remark as an error
V
varsitymendes
04-02-2022, 06:57 AM #5

Ignoring the remark as an error

P
ple
Junior Member
13
04-02-2022, 05:50 PM
#6
I've encountered another error, and the Event Viewer displays this message.
P
ple
04-02-2022, 05:50 PM #6

I've encountered another error, and the Event Viewer displays this message.