search

Rem0o / FanControl.Releases

This is the release repository for Fan Control, a highly customizable fan controlling software for Windows.
Other
14.04k stars 442 forks source link

Crashing with AccessViolationException #2709

Open arielmoraes opened 1 month ago

arielmoraes commented 1 month ago

FanControl is randomly crashing when not being used with the following event:

Application: FanControl.exe
CoreCLR Version: 8.0.824.36612
.NET Version: 8.0.8
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
   at ADLXWrapper.Bindings.ADLXPINVOKE.delete_ADLXHelper(System.Runtime.InteropServices.HandleRef)
   at ADLXWrapper.Bindings.ADLXPINVOKE.delete_ADLXHelper(System.Runtime.InteropServices.HandleRef)
   at ADLXWrapper.Bindings.ADLXHelper.Dispose(Boolean)
   at ADLXWrapper.Bindings.ADLXHelper.Finalize()

No log.txt was found.

My Windows PC is giving me some random BSODs so don't know if that's somewhat related.

Rem0o commented 3 weeks ago

Are you on V201 and on the latest version of Adrenaline?

sam8457 commented 1 day ago

I get the same issue on V205. For me it crashes after trying to launch, for both .NET versions and for both the installer version and the portable version. The errors I get in windows event viewer are:

Application: FanControl.exe
CoreCLR Version: 8.0.824.36612
.NET Version: 8.0.8
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFE62082BD3

Faulting application name: FanControl.exe, version: 205.0.0.0, time stamp: 0x66960000
Faulting module name: atiadlxx.dll, version: 32.0.12011.1036, time stamp: 0x66f4eb58
Exception code: 0xc0000005
Fault offset: 0x0000000000062bd3
Faulting process id: 0x0x3DA4
Faulting application start time: 0x0x1DB1919A765B676
Faulting application path: C:\Users\username\Downloads\FanControl_205_net_8_0\FanControl.exe
Faulting module path: C:\Windows\SYSTEM32\atiadlxx.dll
Report Id: f83cd520-4ca3-45ee-8d27-c5e1f083c094
Faulting package full name: 
Faulting package-relative application ID: 

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FanControl.exe
P2: 205.0.0.0
P3: 66960000
P4: atiadlxx.dll
P5: 32.0.12011.1036
P6: 66f4eb58
P7: c0000005
P8: 0000000000062bd3
P9: 
P10: 

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FanControl.exe_162ebf6fa054d0d431a761353eef3230e891ad1_5ce258ab_c5d225f4-69bd-4599-9588-4dcb258e98c8

Analysis symbol: 
Rechecking for solution: 0
Report Id: f83cd520-4ca3-45ee-8d27-c5e1f083c094
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Fault bucket 2294529679421172255, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FanControl.exe
P2: 205.0.0.0
P3: 66960000
P4: atiadlxx.dll
P5: 32.0.12011.1036
P6: 66f4eb58
P7: c0000005
P8: 0000000000062bd3
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.df682859-5f50-4298-a81a-e67a0f7f7b32.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FanControl.exe_162ebf6fa054d0d431a761353eef3230e891ad1_5ce258ab_c5d225f4-69bd-4599-9588-4dcb258e98c8

Analysis symbol: 
Rechecking for solution: 0
Report Id: f83cd520-4ca3-45ee-8d27-c5e1f083c094
Report Status: 268435456
Hashed bucket: 0c88abca275d81406fd7ce96247d6a1f
Cab Guid: 0

Also no log.txt file is created on my end. Using an MSI B550 Gaming Plus motherboard if it matters.