Bug: HASS Agent crashing when try add GPU Load or Temperature sensors

[BenjyP1235]

Describe the bug
My HASS Agent crashes whenever I try to add either the GPU Load or GPU Temperature sensors, weirdly it is fine with the CPU Load & Clock sensors so I assume it has something to do with GPU drivers, I have an AMD RX 7900 XTX.

To Reproduce
Steps to reproduce the behaviour:
Click add sensor and select either GPU sensor then when hit "Store & Activate Sensors"

Expected behavior
The sensor to be added and the agent to remain open

Misc info (please complete the following information):

• Windows build (ideally screenshot/info of winver.exe output):
  
• Windows' UI language: English (UK)
• HASS.Agent version: 2022.14.0

Please check what's applicable (multiple answers possible):

• Installed via installer
• Installed manually
• Problem occurs in HASS.Agent
• Problem occurs in Satellite Service

Logs
Nothing in logs, just quits as if the process were killed and then starts normally on the next boot.

[naxey]

This is a duplicate of my problem #386
For reference, I'm using an RX480

[BenjyP1235]

This is a duplicate of my problem #386 For reference, I'm using an RX480

Just saw your issue update specifying which sensors made it crash, mine works fine with lastactive and lastboot or any combination discluding the GPU monitoring, assuming its AMD driver conflicts then.

[mrmees]

Having the same problem as you. 6800XT can't add GPU load or temperature without crashing the app. Nothing shown in HASS agent logs, but the following are in the Event Viewer:

Application: HASS.Agent.exe CoreCLR Version: 6.0.2623.60508 .NET Version: 6.0.26 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFFD6CF3C89 (00007FFFD6B20000) with exit code c0000005.

Faulting application name: HASS.Agent.exe, version: 2022.14.0.0, time stamp: 0x63558578 Faulting module name: coreclr.dll, version: 6.0.2623.60508, time stamp: 0x656f6ab2 Exception code: 0xc0000005 Fault offset: 0x00000000001d3c89 Faulting process id: 0x1f24 Faulting application start time: 0x01da56ac2b7ad6b0 Faulting application path: C:\Users\matth\AppData\Roaming\LAB02 Research\HASS.Agent\HASS.Agent.exe Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.26\coreclr.dll Report Id: 266d03dc-afcd-46f2-9df4-73b02a63a2c9 Faulting package full name: Faulting package-relative application ID:

Both OpenHardwareManager and Libre are able to display the information without issue.

[Maxklos]

Got the same problems with Windows 10 Pro 22H2 , same agent version. for me it was just GPU-Temp & Load. I have a AMD R9 480

[Frusciantism]

same problem, with windows 11 and nvidia gtx 1080

[stnokott]

Same issue on my end.

Nothing in the logs, even with extended logging activated.

Expand for Event Viewer details

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
	<System>
		<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
		<EventID>1000</EventID>
		<Version>0</Version>
		<Level>2</Level>
		<Task>100</Task>
		<Opcode>0</Opcode>
		<Keywords>0x8000000000000000</Keywords>
		<TimeCreated SystemTime="2024-02-19T08:46:43.5226074Z" />
		<EventRecordID>921</EventRecordID>
		<Correlation />
		<Execution ProcessID="12896" ThreadID="27284" />
		<Channel>Application</Channel>
		<Computer>REDACTED</Computer>
		<Security UserID="REDACTED" />
	</System>
	<EventData>
		<Data Name="AppName">HASS.Agent.exe</Data>
		<Data Name="AppVersion">2022.14.0.0</Data>
		<Data Name="AppTimeStamp">63558578</Data>
		<Data Name="ModuleName">coreclr.dll</Data>
		<Data Name="ModuleVersion">6.0.322.12309</Data>
		<Data Name="ModuleTimeStamp">6216cac2</Data>
		<Data Name="ExceptionCode">c0000005</Data>
		<Data Name="FaultingOffset">00000000001cd70f</Data>
		<Data Name="ProcessId">0x36c0</Data>
		<Data Name="ProcessCreationTime">0x1da63101e4f8e34</Data>
		<Data Name="AppPath">C:\Users\REDACTED\AppData\Roaming\LAB02 Research\HASS.Agent\HASS.Agent.exe</Data>
		<Data Name="ModulePath">C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.3\coreclr.dll</Data>
		<Data Name="IntegratorReportId">9e551b18-4f77-4983-b0d4-f30b42d539b3</Data>
		<Data Name="PackageFullName">
		</Data>
		<Data Name="PackageRelativeAppId">
		</Data>
	</EventData>
</Event>

[aalencia]

I can confirm this is still an issue as well.

[JLSBeth]

This is also happening to me with both GPU sensors.