-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amd fan error #30
Comments
That is a known bug in the AMD driver. I will implement a workaround. Could you also try it without 1070's? |
I already fixed the fan bug. The next version won't have this issue. |
Nice work =)) And if i rename phymem_vista_win7_win8 to phymem, win7 crash. If dont rename, Excavator dont load phymem (turn-driver-signature-enforcement-off activated). Simple phymem.sys crash system too. |
That's very helpful to know. Excavator is supposed to load phymem_vista_win7_win8.sys automatically on Windows 7, and the driver is properly signed for that. It might be the case that Microsoft changed driver signing requirements for Windows 7. I will look into this. As for 1070's, it would be great if could physically take out 1070's and try excavator only with RX 480's. (Some motherboards allow practically the same thing with dip switches.) If it is too much trouble, you could just wait for the next version, which should be available shortly. |
Any info about when the next version will be released? |
I can also confirm using windows MSI 7950 ... no matter what i try with MSI afterburner to control my fan speed.. Excavator continuously down-clocks my fan speed to almost zero. Is there anyway to control the fan speed again? After a few test run using the "start-admin.bat" i was supppppppper impressed with the hash speeds. |
This bug has been fixed. Please use Version 1.2.11a. |
My rig: 2x480, 2x1070. Mine only 1070s on Excavator.
If do NOT disable AMD support(-na), amd fans reset to 0% and dont changes to other value.
P.S. And phymem.sys, phymem_vista_win7_win8.sys crashing system on Win-7x64, so this issue dont fixed.
The text was updated successfully, but these errors were encountered: