CCleaner 7 (latest release) upon launching crashes SSD-LED which terminates with 'something went wrong... exiting...'

[krzemien77]

As per the subject line - CCleaner 7 (latest release) upon launching crashes SSD-LED which terminates with 'something went wrong... exiting...'

It can be reproduced on my both PCs (Windows 11, Windows 10, x64 both, latest updated versions) every time I launch CCleaner 7.

[Shuttleman58]

Re: #17, #20 with similar issues. Also noting that CCleaner v7 has numerous issues of its own reported but may offer clue to earlier and similar issues. It seems that anything that clears Windows temp files also causes problems with SSD as I have noted this with CCleaner v6 and other maintenance apps.

[krzemien77]

Yup, understood and agreed.

The difference being though: crash occurs upon CCleaner 7 launch exactly, not upon running some cleaning and such tasks (which I never do, I only use CCleaner 7 these days to check for obsolete / updated software and drivers only - and I launch these tasks manually).

NB I also spotted SSD-LED crashing on its own when PC is left unattended for - say - an hour - assume it's related to CCleaner 7 launching some background task that does that.

[krzemien77]

Having played with Process Monitor a bit just now (and am truly far from knowing exactly what I'm doing ;-)), that's what happens ad infinitum when SSD works in background:

(...)
13:31:18.1851707	SSD-LED.exe	24764	RegQueryKey	HKLM	SUCCESS	Query: HandleTags, HandleTags: 0x0
13:31:18.1851782	SSD-LED.exe	24764	RegOpenKey	HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib	SUCCESS	Desired Access: Read
13:31:18.1851872	SSD-LED.exe	24764	RegCloseKey	HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib	SUCCESS	
13:31:18.1851989	SSD-LED.exe	24764	RegQueryValue	HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\Disable Performance Counters	NAME NOT FOUND	Length: 20
(...)

The moment CCleaner is launched, it introduces this:

(...)
13:31:18.4023595	SSD-LED.exe	24764	IRP_MJ_CREATE	C:\	SUCCESS	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
13:31:18.4024040	SSD-LED.exe	24764	IRP_MJ_QUERY_VOLUME_INFORMATION	C:\	SUCCESS	Type: QuerySizeInformationVolume, TotalAllocationUnits: 488,022,783, AvailableAllocationUnits: 373,575,590, SectorsPerAllocationUnit: 8, BytesPerSector: 512
13:31:18.4024145	SSD-LED.exe	24764	IRP_MJ_CLEANUP	C:\	SUCCESS	
13:31:18.4024268	SSD-LED.exe	24764	IRP_MJ_CLOSE	C:\	SUCCESS	
**13:31:18.4024430	SSD-LED.exe	24764	IRP_MJ_CREATE	\Device\HarddiskVolume4\	SUCCESS	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
13:31:18.4024608	SSD-LED.exe	24764	IRP_MJ_QUERY_VOLUME_INFORMATION	\Device\HarddiskVolume4\	SUCCESS	Type: QuerySizeInformationVolume, TotalAllocationUnits: 284,927, AvailableAllocationUnits: 47,478, SectorsPerAllocationUnit: 8, BytesPerSector: 512
13:31:18.4024678	SSD-LED.exe	24764	IRP_MJ_CLEANUP	\Device\HarddiskVolume4\	SUCCESS	
13:31:18.4024756	SSD-LED.exe	24764	IRP_MJ_CLOSE	\Device\HarddiskVolume4\	SUCCESS**	
13:31:18.4024862	SSD-LED.exe	24764	IRP_MJ_CREATE	E:\	SUCCESS	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
13:31:18.4025001	SSD-LED.exe	24764	IRP_MJ_QUERY_VOLUME_INFORMATION	E:\	SUCCESS	Type: QuerySizeInformationVolume, TotalAllocationUnits: 244,190,207, AvailableAllocationUnits: 119,886,312, SectorsPerAllocationUnit: 8, BytesPerSector: 512
13:31:18.4025105	SSD-LED.exe	24764	IRP_MJ_CLEANUP	E:\	SUCCESS	
13:31:18.4025189	SSD-LED.exe	24764	IRP_MJ_CLOSE	E:\	SUCCESS	
13:31:18.4025295	SSD-LED.exe	24764	IRP_MJ_CREATE	D:\	SUCCESS	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
13:31:18.4025459	SSD-LED.exe	24764	IRP_MJ_QUERY_VOLUME_INFORMATION	D:\	SUCCESS	Type: QuerySizeInformationVolume, TotalAllocationUnits: 488,378,111, AvailableAllocationUnits: 318,203,377, SectorsPerAllocationUnit: 8, BytesPerSector: 512
13:31:18.4025559	SSD-LED.exe	24764	IRP_MJ_CLEANUP	D:\	SUCCESS	
13:31:18.4025674	SSD-LED.exe	24764	IRP_MJ_CLOSE	D:\	SUCCESS	
(...)

and other various .NET-related stuff that follows, eventually ending with:

13:31:30.9765148 SSD-LED.exe 24764 Process Create C:\WINDOWS\system32\WerFault.exe SUCCESS PID: 17640, Command line: C:\WINDOWS\system32\WerFault.exe -u -p 24764 -s 2244

when I click 'OK' button in 'something wrong... exiting...' message.

So to my uneducated eye it would appear that CCleaner triggers disk search / discovery, which it in turn seems posing problems for SSD-LED.
And myself either, as having used 'List-Device-Name-and-Path.ps1' script just now to firmly assess which HarddiskVolume# is which, I don't see this HarddiskVolume4 at all, as seen above...?

PS D:\Downloads> powershell -nop -ep bypass .\List-Device-Name-and-Path.ps1

DevicePath              DriveLetter
----------              -----------
\Device\HarddiskVolume3 C:
\Device\HarddiskVolume5 E:
\Device\HarddiskVolume6 D:
\Device\CdRom0          K:

Would my Virtual CD (VirtualCloneCD) be the suspect to blame for it?

[Shuttleman58]

Nice work. It makes sense that if another program is doing disk searches or discovery that could be the trigger. I think I'll watch if an app does disk indexing if it also triggers the failure.

Maybe now, with multiple reports of this error the developer(s) will take a look.

[krzemien77]

...so played a bit further with VirtualCloneCD and can confirm it's not related to it.

Having re-looked into Process Monitor, have found this just after disc rediscovery section:

(...)
14:11:10.4274872	SSD-LED.exe	4676	FASTIO_WRITE	C:\Users\[redacted]\AppData\Local\Apps\2.0\Data\59N8AY8G.EGV\T5VDVX4R.EQL\ssd-..tion_0000000000000000_0001.0000_3226fa789aed507b\Data\1.0.7.5\SSDLED20260114_001.log	SUCCESS	Offset: 13,936, Length: 434
(...)

Which lead me to SSD-LED log files, where one can find this course of events:

2026-01-14 13:29:13.987 +00:00 [INF] Starting SSD-LED v1.0.7.5
2026-01-14 13:29:14.710 +00:00 [INF] Found the following Physical Disks: ["1 E:","2 D:","0 C:","_Total"]
2026-01-14 13:29:14.718 +00:00 [INF] Loading settings:
2026-01-14 13:29:14.718 +00:00 [INF] -----------------
2026-01-14 13:29:14.722 +00:00 [INF] max KBS: 800
2026-01-14 13:29:14.722 +00:00 [INF] RefreshInterval: 100
2026-01-14 13:29:14.722 +00:00 [INF] SingleDrive monitoring: True
2026-01-14 13:29:14.722 +00:00 [INF] Successfully parsed single drive monitoring instance 0 C:
2026-01-14 13:29:14.723 +00:00 [INF] Selected single drive: 0 C: which is index 2 of the drive list
2026-01-14 13:29:14.728 +00:00 [INF] ColorDefault: Color [A=255, R=0, G=0, B=0]
2026-01-14 13:29:14.728 +00:00 [INF] ColorRead: Color [A=255, R=0, G=255, B=0]
2026-01-14 13:29:14.728 +00:00 [INF] ColorWrite: Color [A=255, R=255, G=0, B=0]
2026-01-14 13:29:14.728 +00:00 [INF] -----------------
**2026-01-14 13:29:23.924 +00:00 [ERR] PhysicalDisk->0 C: could not captured - Exception here: System.InvalidOperationException: Instance '0 C:' does not exist in the specified Category.
   at System.Diagnostics.CounterDefinitionSample.GetInstanceValue(String instanceName)
   at System.Diagnostics.PerformanceCounter.NextSample()
   at System.Diagnostics.PerformanceCounter.NextValue()
   at SSD_LED.SSDLED.SSDActivityPerfCount()
2026-01-14 13:29:24.028 +00:00 [ERR] PhysicalDisk->0 C: could not captured - Exception here: System.InvalidOperationException: Instance '0 C:' does not exist in the specified Category.
   at System.Diagnostics.CounterDefinitionSample.GetInstanceValue(String instanceName)
   at System.Diagnostics.PerformanceCounter.NextSample()
   at System.Diagnostics.PerformanceCounter.NextValue()
   at SSD_LED.SSDLED.SSDActivityPerfCount()
2026-01-14 13:29:24.143 +00:00 [ERR] PhysicalDisk->0 C: could not captured - Exception here: System.InvalidOperationException: Instance '0 C:' does not exist in the specified Category.
   at System.Diagnostics.CounterDefinitionSample.GetInstanceValue(String instanceName)
   at System.Diagnostics.PerformanceCounter.NextSample()
   at System.Diagnostics.PerformanceCounter.NextValue()
   at SSD_LED.SSDLED.SSDActivityPerfCount()**
2026-01-14 13:29:32.023 +00:00 [INF] Too many errors in sequence -> Exiting...

(I do monitor traffic on disk C: only so the above is right)

So, what exactly takes place here then - triggered (in this case) by CCleaner 7 launch?

[Shuttleman58]

It does not appear that the admins are responding to issues here any longer. Is SSD-LED dying/dead?