Windows 10 Creators update breaks SIV

[Jacmac]

EasyTune SIV abruptly stopped working when the Windows 10 Creators update came out. I have a GA z170 Gaming 7 motherboard with Windows 10. It has been working great for months with SIV controlling my water pump speed. Then the creators update came out and now the pump runs at max rpm. I tried upgrading Easytune and SIV, but I get "SIV EasyTune engine is re-starting. Please wait" forever. I have to end task to kill it. Can anyone give advice on this? My ears are ringing from the pump drone.

I would just add that the system event log shows Error 7034 The EasyTune Engine Service terminated unexpectedly.

Code: [Select]

Application: EasyTuneEngineService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at Gigabyte.ComputerSystemHardware.BIOS.BdrAid.SearchKeyword(UInt64, UInt64, System.String, UInt64 ByRef)
   at Gigabyte.ComputerSystemHardware.BIOS.BdrAid.RetrieveBaseOffset4ReverseDirection(Int64, UInt64, UInt64, UInt64 ByRef)
   at Gigabyte.ComputerSystemHardware.BIOS.BdrAid..ctor(Boolean)
   at Gigabyte.ComputerSystemHardware.BIOS.EasyFunctionHeader.RetrieveSmiPort(Int32 ByRef)
   at Gigabyte.ComputerSystemHardware.BIOS.EasyHealthHeader..ctor(Boolean)
   at Gigabyte.ComputerSystemHardware.BIOS.EasyTableComWrapper.UpdateFile()
   at Gigabyte.EasyTune.EasyFunctions.EasyTableControl.UpdateSmiDataFile()
   at EasyTuneEngineService.EasyTuneEngineService.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()


Code: [Select]

Faulting application name: EasyTuneEngineService.exe, version: 8.0.6.6, time stamp: 0x58d87175
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x01e32d15
Faulting process id: 0x25f8
Faulting application start time: 0x01d2b9703817f183
Faulting application path: C:\Program Files (x86)\GIGABYTE\EasyTuneEngineService\EasyTuneEngineService.exe
Faulting module path: unknown
Report Id: c91618e8-2688-4143-b8cd-36b4a4bc9e07
Faulting package full name:
Faulting package-relative application ID:

[shadowsports]

Can you revert?  Settings > Update & Security > Recovery > Go Back To an earlier build...

Or Advanced Start Up > Troubleshoot > Advanced Options > Go Back To Previous Build

Nothing magical about this update from what I've read.

You should also open a ticket with Gigabyte Support...  But ATM, you are the only user I've seen mention this issue. 

[Jacmac]

Can you revert?  Settings > Update & Security > Recovery > Go Back To an earlier build...

Or Advanced Start Up > Troubleshoot > Advanced Options > Go Back To Previous Build

Nothing magical about this update from what I've read.

You should also open a ticket with Gigabyte Support...  But ATM, you are the only user I've seen mention this issue.

Going back to the previous build works. I've seen someone else mention the same problem with this motherboard, Windows 10 Creators update, and SIV, although I don't think it was crashing the same way as mine is. There was some recommendation to install .Net 4.5, but that is already included with Windows 10, so .Net is not the problem. I'll get an external PWM controller so I don't have to worry about this in the future.

By the way, the F21 BIOS and the Windows 10 Creators update weren't compatible either. When the BIOS was upgraded, I was not longer able to boot Windows at all.

[shadowsports]

Glad you could roll back and regain function. 

I think we are looking at 30-90 days (from 4/11) before the creators update is actually pushed to machines via windows update.  Its optional (manual) for now unless you are 'insider"

Sounds like it should be avoided for now until more vendors can test their software with it.   



 

[fusifusionworld]

Not sure if anybody is still following this post...
I found that on my machine the issue is somehow related to Microsoft Hyper V, after hours of troubleshooting I reinstalled Windows (twice as once I installed the killer network software which basically killed any network connection I had) then once I was up and running I performed an acronis backup which I normally restore to a virtual machine, when I enabled Hyper V SIV would no longer launch, disabled hyper V and restarted and all working again!

Hopefully this will help somebody else!

(I only use Hyper V at home to test backup restores so not a real problem for me)

[shadowsports]

A .tib file can be restored to a host disk whether physical or virtual.  Hyper V behaves differently depending on the host OS, server vs. plain windows.  This also affects software and hardware interaction, so apps that have specific hardware access requirements could have problems running on a machine with hyper visor enabled.  Again, the behavior varies depending on the host OS.  The version of App Center and SIV could also be a factor. 

In any event, SIV ran just fine for me from the moment I upgraded to "Creators Update".  I think for most, if they weren't an early adopter, SIV ran normally without any issues.

[NeoMouse]

Not sure if anybody is still following this post...
I found that on my machine the issue is somehow related to Microsoft Hyper V, after hours of troubleshooting I reinstalled Windows (twice as once I installed the killer network software which basically killed any network connection I had) then once I was up and running I performed an acronis backup which I normally restore to a virtual machine, when I enabled Hyper V SIV would no longer launch, disabled hyper V and restarted and all working again!

Hopefully this will help somebody else!

(I only use Hyper V at home to test backup restores so not a real problem for me)

Disabling Hyper-V prevented the SystemAccessViolation in EasyTuneEngineService.exe and I could start SIV. Thanks!

To disable Hyper-V (from elevated powershell prompt):
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

To (re)enable Hyper-V:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

edit: the -All switch is probably unnecessary but I haven't experimented

[shadowsports]

PowerShell is great.  I wish I started using it earlier.  It makes managing Exchange so much easier... Waiting to see how it will integrate with 0365 once MS moves away from 2016.