Explorer is continuously active?
Explorer is continuously active?
I've noticed this program explorer.exe version 10.0.26100.7019 has stopped communicating with Windows and has been closed. It seems to occur infrequently, mostly only when other applications like Discord, Steam, or the game itself are running. There have been only a handful of such instances recently—possibly just three since the issue began last month. In the event viewer it appears very unusual, causing the task bar to freeze and stop functioning normally. When I click anywhere on the taskbar, a loading icon appears briefly before resolving itself. Sometimes this happens once every day, other times multiple times per minute. Despite cleaning my SSD and reinstalling Windows, the problem persists. I've run scans and performed repairs without success. Updated graphics drivers and chipset changes haven't resolved it. Could you assist me with a solution?
This:
"when it happens the task bar at the bottom will freeze the clock"
Try installing a new, fresh CMOS battery by following the procedure provided in the applicable Motherboard's User Guide/Manual.
If the system's date and time is faltering then there can be synchronization errors.
= = = =
Also:
Update your post to include full system hardware specs and OS information.
Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?
Disk drive(s): make, model, capacity, how full?
List of all connected peripherals.
Wired or wireless network?
Noted:
"no label the type is called Microsoft recovery partition 621MB of 69.2 another Microsoft recovery partition 445MB used of 84.5MB"
Open the Disk Management window and expand so everything is visible and clear.
Capture the screen and share it here via imgur (www.imgur.com > green "New post" icon).
Also execute "dism" and "sfc /scannow" to locate and repair damaged files.
Source for Windows 11?
For the source, I don't really recall having it on a USB for a while; it seems to have come from Windows. I also want to mention that it wasn't just the clock that froze—it was the entire task bar, and the scan didn't detect any integrity issues. My RAM came up clean during the scan as well.
Uncertain about the situation.
The Disk Management interface (imgur) seems to clash with the partition details from your initial message (highlighted in Post #5). The warning "no label the type..." suggests a specific issue.
Regarding the source USB, it’s crucial since outdated, damaged, fake, or pirated OS versions can cause problems—sometimes they seem functional at first but later fail. A fresh Windows installation on another USB drive might be necessary.
The problem isn’t limited to just the desktop clock; it involves timing and synchronization across devices. If network equipment can’t agree on time or date, complications arise.
Check if you ran "dism" and "sfc /scannow" to detect and repair corrupted files—what were the outcomes?
If not, what other scans were performed?
Sorry for the delayed reply. The sfc and dism were clean. I adjusted my monitor resolution, but it took two days before it worked again. It started working within five minutes after my computer was turned on. I don't know why this happened, but it seems to be a problem.
What video and monitor setup details are in use? Which configurations function correctly and which cause issues? What are the specific monitor models? Do these displays require separate drivers? I believe there may be some compatibility problems or configuration errors.
The monitor is an MSI g27C4 with updated drivers. It runs at 1920x1080 at 144hz, but after lowering the resolution to 1760x990 it stopped working. This is the second monitor in use. The main display is a Dell AW2723DF at 240hz with 2560x1440 resolution. People often advise against mixing HZ monitors, though I've set this up for nearly five years without issues—things seem to change over time.
the clock on the display failing to update suggests the graphics driver isn't responding. Windows didn't recognize that the graphics driver was unresponsive.
the drive error means the system restarted without a proper shutdown, leaving the file partition with an incorrect status. chkdsk needs to be executed at the next boot.
I recommend removing any GPU overclock drivers, lowering the refresh rate on all monitors, and rechecking. You might find a utility to determine the optimal refresh rate for your screens, considering resolution, refresh settings, and card capacity to avoid overheating. Exceeding these limits can cause the graphics card to miss signals and stall in refreshing.