[SOLVED] iWork 10 Flagship i15 T freeze in Android and Win10

[Azzi]

Hi everybody,

I have a big problem with my iWork 10 Flagship, it is in fact unusable. When booting Windows 10 it crashes almost instant, sometimes it just freezes, sometimes it displays an error dump and I have to shut it down by holding the power button.

At first I thought the Windows 10 installation was corrupted, so I did a clean install of Windows 10 Pro 64 Bit (deleted all Windows partitions and installation worked just fine). But the problem is still the same. I can’t even install drivers, because it crashes right after booting.

When I choose Android it is the same, it boots Android and then freezes. I always have to kill it by holding the power button.

Strange thing is, that the Windows installation works fine, but as soon as I start one of the OS it crashes.

Booting from a Live Stick results in a crash too.

 

Does anyone have an idea, what I can do?

 

Edit: For the first time the error dump completely showed. The error message is CLOCK_WATCHDOG_TIMEOUT under Windows 10

[Dudelbit]

Did it work when you received it?

If yes, what was the last thing you did when it started to crash?

[Azzi]

No, it did not work.

I disabled everything regarding Intel Trusted Execution Engine, Trusted Computing Module, TPM and the Intel C-State. After that I was able to do a clean Windows 10 installation (before I wasn’t even able to start the setub anymore).

Now I am setting up Windows and until now it works without any crashes. The only thing, that does not work is the touchscreen (it worked for a short time, after I installed the driver, so I think there was another driver which is blocking it) and the windows key on the screen. But these are problems I can work on, now that the system is stable.

If anybody has a hint for me, what to do regarding the windows key, you are very welcome. I will start reenabling the settings in the BIOS to find out, which one is the real “killer”.

 

Edit: Touchscreen is working after updating the display drivers.

Edit 2: I downloaded the driver package from the HowTo Thread and copied the TouchSetting.gt into Windows/inf, because the calibration did not work. The TouchSetting.gt file was not included in the driver package I used to setup the tablet. Now the touchscreen works precisely and the Windows key works too.

[Azzi]

So I figured it out. I have to disable every Option under Advanced->PPM Configuration (EIST, CPU C State Report, S0ix) to keep the tablet running. TPM etc. had nothing to do with it. Maybe this helps if anybody else has similar issues. That would have saved me several hours of frustration.

[Ai Lleenixz]

http://4pda.ru/forum/lofiversion/index.php?t725568-100.html

cube iwork10 ultimate root side here

tutorial here https://www.youtube.com/watch?v=ErFaHbk7efw

[Hans Sprungfeld]

That solution doesn’t make any sense. Why are you then the only having this problem? Why do other people not need to deactivate these options? Also, you are deactivating with this all the energy saving mechanisms of the CPU => fail.

[Azzi]

@Hans Sprungfeld: sorry, but unless you don’t have any helpful adivce, just keep your fingers still. I know, that I am the only one with the problem (wo wrote about it on this thing called internet). Any normal person would have sent the tablet back, because it is broken. I don’t know, if it is a faulty CPU or BIOS, but if I activate any energy saving mechanism it crashes.

The second I tried to do a clean Windows install, I was commited to getting the tablet to work, because otherwise I would not have been able to reset it to factory setting. And now it works flawless with a clean Windows 10 and full “hard drive” capacity, because I don’t need Android at all.

The time I would need to restore the tablet to factory settings (including Dual Boot etc.) is more valuable to me, than the money I spent on the tablet. This workaround works for me, because if I don’t use the tablet, I just shut it down.

I just documented this solution for anyone, who is confrontet with the same problem. If there is and will be no one else: congratulations. But if there is just one person whos time I can save by this post, I’m glad about it.

So as I said: as long as you have no real advice, just don’t post anything. Thank you!

[Hans Sprungfeld]

Azzi wrote:

@hans Sprungfeld: sorry, but unless you don’t have any helpful adivce, just keep your fingers still. I know, that I am the only one with the problem (wo wrote about it on this thing called internet). Any normal person would have sent the tablet back, because it is broken. I don’t know, if it is a faulty CPU or BIOS, but if I activate any energy saving mechanism it crashes. The second I tried to do a clean Windows install, I was commited to getting the tablet to work, because otherwise I would not have been able to reset it to factory setting. And now it works flawless with a clean Windows 10 and full “hard drive” capacity, because I don’t need Android at all. The time I would need to restore the tablet to factory settings (including Dual Boot etc.) is more valuable to me, than the money I spent on the tablet. This workaround works for me, because if I don’t use the tablet, I just shut it down. I just documented this solution for anyone, who is confrontet with the same problem. If there is and will be no one else: congratulations. But if there is just one person whos time I can save by this post, I’m glad about it. So as I said: as long as you have no real advice, just don’t post anything. Thank you!

lulz : DDD The problem most likely is related to your microcode / faulty CPU btw, which just can be fixed by a new bios or a new CPU/tablet. It’s a hardware bug with Skylake CPUs so the new Atoms most likely have this issue too:

https://communities.intel.com/thread/97358

http://forum.asrock.com/forum_posts.asp?TID=1712&PN=6&title=new-asrock-z170-pro4-randomly-freezing

[Author]

Posts