Driver Power State Failure due ACPI.sys

xNero · Jan 8, 2018

Hi :)

My Cube i7 Book tablet (I use it with the CDK09 keyboard as a laptop) is having issues, so I decided to reinstall Windows 10.

Some quick info on my tablet:
- Windows 10 was pre-installed when I bought it (with license), but due issues I chose to reinstall it with a bootable USB drive.
- Currently, Windows 10 Fall Creators Update is installed, version 1709, build 16299.125.
- CPU: Intel Core M3 6Y30 1,51GHz, Skylake
- Video Card: Intel(R) HD Graphics 515 (Gen9LP HD515)
- Brand: Cube (Chinese brand)

Shortly after I boot the tablet (which is very slow, it takes 30 minutes or more to boot) and log in to my account it shows a Driver_Power_State_Failure error shortly after and then reboots.

Steps I have done:
- I have updated the drivers after the clean installation that had a yellow mark, currently, they do now show any yellow error marks.
- I used Command Prompt for chkdsk /f /r and sfc /scannow but there are no issues found.
- Windows installed all updates shown at the check for updates section.
- I have edited theWindows Page Files for all drivers to custom, where I used 1,5x and 4x the original value.
- I have run Memtest86 from a bootable USB 2 hours and there was no error found.

I now have to run the Systive Collection File App, but the tablet is still booting (for 2 hours now..).
When it has been booted and I have the Systive .zip file I will update this post.
I will also run Driver Verifier, HDD Diagnostics, MalwareBytes and I might run a RAM test again (as I used Memtest86 instead of Memtest86+, if that matters?).

For now I will add the most recent .dump file, I zipped it and uploaded it to OneDrive: https://1drv.ms/u/s!AmEjnLjcfA9aqmzKtByF3ELfKRQ3
All I can get out of the .dump file is that ACPI.sys is causing the error, but I am not skilled enough myself to figure out why that is.

Thanks advance for your help! I really appreciate it!

bwv848 · Jan 8, 2018

Code:

0: kd> !analyze -show 9F 0000000000000003 ffff94828bd2aa00 fffff801eb656c40 ffff94828bffbb40
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffff94828bd2aa00, Physical Device Object of the stack
Arg3: fffff801eb656c40, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff94828bffbb40, The blocked IRP

Code:

0: kd> !irp ffff94828bffbb40
Irp is active with 7 stacks 5 is current (= 0xffff94828bffbd30)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 ffff94828bd2aa00 00000000 00000000-00000000    pending
           \Driver\ACPI
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 ffff94828cfcfe20 00000000 fffff801e8f223c0-ffff94828adfa130 Success Error Cancel pending
           \Driver\SkcController    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-ffff94828adfa130    

            Args: 00000000 00000000 00000000 00000000

Code:

0: kd> lm k vm SkcController
Browse full module list
start             end                 module name
fffff801`a0c10000 fffff801`a0c36000   SkcController T (no symbols)           
    Loaded symbol image file: SkcController.sys
    Image path: \SystemRoot\System32\drivers\SkcController.sys
    Image name: SkcController.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=#ff0000]Mon Nov 09 02:28:58 2015[/COLOR] (56404B3A)
    CheckSum:         0002BDD3
    ImageSize:        00026000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update your Intel Control Logic driver. Sorry I can't find the download link — I couldn't find Cube's support page!?

philc43 · Jan 8, 2018

Hello xNero

The BSOD crash dump file can be examined for the driver which is causing the failure:

Code:

[COLOR=#1e1e1e]0: kd> !irp ffff94828bffbb40[/COLOR]
[COLOR=#1e1e1e]Irp is active with 7 stacks 5 is current (= 0xffff94828bffbd30)[/COLOR]
[COLOR=#1e1e1e] No Mdl: No System Buffer: [/COLOR][COLOR=#1e1e1e]Thread [/COLOR][U][COLOR=#0066cc]00000000[/COLOR][/U][COLOR=#1e1e1e]:  [/COLOR][COLOR=#1e1e1e]Irp stack trace.  [/COLOR]
[COLOR=#1e1e1e]     cmd  flg cl Device   File     Completion-Context[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]            Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]            Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]            Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]            Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e]>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)][/COLOR]
[COLOR=#1e1e1e]            0 e1 ffff94828bd2aa00 00000000 00000000-00000000    pending[/COLOR]
[COLOR=#1e1e1e]          [/COLOR][U][COLOR=#0066cc]\Driver\ACPI[/COLOR][/U]
[COLOR=#1e1e1e]            Args: 00000000 00000001 00000001 00000000[/COLOR]
[COLOR=#1e1e1e] [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)][/COLOR]
[COLOR=#1e1e1e]            0 e1 ffff94828cfcfe20 00000000 fffff801e8f223c0-ffff94828adfa130 Success Error Cancel pending[/COLOR]
[COLOR=#1e1e1e]          [/COLOR][COLOR=#1e1e1e]Unable to load image \SystemRoot\System32\drivers\SkcController.sys, Win32 error 0n2[/COLOR]
[COLOR=#ff0000]*** WARNING: Unable to verify timestamp for SkcController.sys
*** ERROR: Module load completed but symbols could not be loaded for SkcController.sys
[/COLOR][U][COLOR=#0066cc]\Driver\SkcController[/COLOR][/U][COLOR=#1e1e1e]    nt!PopRequestCompletion[/COLOR]
[COLOR=#1e1e1e]            Args: 00000000 00000001 00000001 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-ffff94828adfa130    [/COLOR]

[COLOR=#1e1e1e]            Args: 00000000 00000000 00000000 00000000[/COLOR]

The skccontroller.sys is a driver that you need to try and update. When you have uploaded the Sysnative Collection Files we can look for more information on this driver from your logfiles. The dump file shows the following information on it:

Code:

[COLOR=#1e1e1e]Loaded symbol image file: SkcController.sys[/COLOR]
[COLOR=#1e1e1e]    Image path: \SystemRoot\System32\drivers\SkcController.sys[/COLOR]
[COLOR=#1e1e1e]    Image name: SkcController.sys[/COLOR]
[COLOR=#1e1e1e]    Timestamp:        Sun Nov  8 23:28:58 2015 (56404B3A)[/COLOR]

xNero · Jan 8, 2018

Thank you very much :) I have updated the driver successfully.
I also ran a scan with MalwareBytes and it found 2 threats, which it moved to quarantine (which I think is strange, because it is a newly installed Windows).
The tablet is currently rebooting, although it still takes a long time to reboot, I hope it will no longer show any errors.
Update: Driver_Power_State_Failure occurred when rebooting, I will try to reboot the tablet again.

Oh, yes, Cube is a Chinese brand and doesn't really have any English support.

Here is the outcome of the Systive App:
https://1drv.ms/u/s!AmEjnLjcfA9aqm0PuONRXgNzJvwt

I hope it is useful to you. Please, let me know if you get any more useful information :)
When the tablet is restarted I will check the HDD and try to use the driver verifier after that, when that is still needed.

bwv848 · Jan 8, 2018

xNero said:
When the tablet is restarted I will check the HDD and try to use the driver verifier after that, when that is still needed.

For now I wouldn't bother with Driver Verifier unless the system bugchecks again.

I'm fairly confident that we've found the cause.

xNero · Jan 8, 2018

Unfortunately, the blue screen occurred again

Firstly when the tablet rebooted after updating the driver. Then I rebooted the tablet and it took a long while to load, I logged in and the Driver_Power_State_Failure occurred for the second time.
I guess this means I didn't use the right 'new' driver or there are more issues going on.

xNero · Jan 8, 2018

The error occurs quite often now, making windows very unstable. I cannot log in Windows now without getting the BSOD within 3 minutes. Booting the tablet still takes about 2 hours until I can log in (no kidding).

I will try to boot in Safe Mode, so I can still check the harddisk and run a driver verifier (of course, if these programs work in safe mode).

philc43 · Jan 9, 2018

Are you able to confirm whether the driver date for the updated skccontroller.sys is indeed a newer version? You can use device manager to look for Intel Control Logic (probably in system devices) and check the driver details.

There may well be other drivers causing this so please post a new set of logfiles and we can check.

xNero · Jan 9, 2018

The driver for the Intel(R) Control Logic has currently 9/19/2016 as date and is version 10.44.38.891.
I have uploaded the newest dump files to OneDrive, here is the link: https://1drv.ms/u/s!AmEjnLjcfA9aqm4fSGRroTyWkBc1

Oh and I did post the results of the Systive App. But I can make a new one of that, if that is needed :)

philc43 · Jan 9, 2018

Your new crash dump files are indicating some other drivers are needing updates:

Code:

[COLOR=#1e1e1e]1: kd> !irp ffffc90408661010[/COLOR]
[COLOR=#1e1e1e]Irp is active with 7 stacks 5 is current (= 0xffffc90408661200)[/COLOR]
[COLOR=#1e1e1e] No Mdl: No System Buffer: [/COLOR][COLOR=#1e1e1e]Thread [/COLOR][U][COLOR=#0066cc]00000000[/COLOR][/U][COLOR=#1e1e1e]:  [/COLOR][COLOR=#1e1e1e]Irp stack trace.  [/COLOR]
[COLOR=#1e1e1e]     cmd  flg cl Device   File     Completion-Context[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e]>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)][/COLOR]
[COLOR=#1e1e1e]            0 e1 ffffc90407474c20 00000000 00000000-00000000    pending[/COLOR]
[COLOR=#1e1e1e]	      [/COLOR][COLOR=#1e1e1e] [/COLOR][U][COLOR=#0066cc]\Driver\ACPI[/COLOR][/U]
[COLOR=#1e1e1e]			Args: 00000000 00000001 00000001 00000000[/COLOR]
[COLOR=#1e1e1e] [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)][/COLOR]
[COLOR=#1e1e1e]            0 e1 ffffc90409099e20 00000000 fffff80242d9e5a0-ffffc90408682900 Success Error Cancel pending[/COLOR]
[COLOR=#1e1e1e]	      [/COLOR][COLOR=#1e1e1e]Unable to load image ov5648.sys, Win32 error 0n2[/COLOR]
[COLOR=#ff0000]*** WARNING: Unable to verify timestamp for ov5648.sys
*** ERROR: Module load completed but symbols could not be loaded for ov5648.sys[/COLOR]
[COLOR=#1e1e1e] [/COLOR][U][COLOR=#0066cc]\Driver\ov5648[/COLOR][/U][COLOR=#1e1e1e]	nt!PopRequestCompletion[/COLOR]
[COLOR=#1e1e1e]			Args: 00000000 00000001 00000001 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-ffffc90408682900    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR][COLOR=#1e1e1e]1: kd> !irp ffff82866311b010[/COLOR]
[COLOR=#1e1e1e]Irp is active with 7 stacks 5 is current (= 0xffff82866311b200)[/COLOR]
[COLOR=#1e1e1e] No Mdl: No System Buffer: [/COLOR][COLOR=#1e1e1e]Thread [/COLOR][U][COLOR=#0066cc]00000000[/COLOR][/U][COLOR=#1e1e1e]:  [/COLOR][COLOR=#1e1e1e]Irp stack trace.  [/COLOR]
[COLOR=#1e1e1e]     cmd  flg cl Device   File     Completion-Context[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e]>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)][/COLOR]
[COLOR=#1e1e1e]            0 e1 ffff828662b24c40 00000000 00000000-00000000    pending[/COLOR]
[COLOR=#1e1e1e]	      [/COLOR][COLOR=#1e1e1e] [/COLOR][U][COLOR=#0066cc]\Driver\ACPI[/COLOR][/U]
[COLOR=#1e1e1e]			Args: 00000000 00000001 00000001 00000000[/COLOR]
[COLOR=#1e1e1e] [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)][/COLOR]
[COLOR=#1e1e1e]            0 e1 ffff828662fb4a40 00000000 fffff802df59f5a0-ffff828663f02130 Success Error Cancel pending[/COLOR]
[COLOR=#1e1e1e]	      [/COLOR][COLOR=#1e1e1e]Unable to load image iaLPSS2i_I2C.sys, Win32 error 0n2[/COLOR]
[COLOR=#ff0000]*** WARNING: Unable to verify timestamp for iaLPSS2i_I2C.sys
*** ERROR: Module load completed but symbols could not be loaded for iaLPSS2i_I2C.sys
[/COLOR][COLOR=#1e1e1e] [/COLOR][U][COLOR=#0066cc]\Driver\iaLPSS2i_I2C[/COLOR][/U][COLOR=#1e1e1e]	nt!PopRequestCompletion[/COLOR]
[COLOR=#1e1e1e]			Args: 00000000 00000001 00000001 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-ffff828663f02130    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]

These two drivers are:
ov5648.sys Sun Sep 18 19:44:28 2016 - this is most likely an Omnivision camera driver
iaLPSS2i_I2C.sys Tue Jun 13 21:00:59 2017 - this is Intel(R) Serial IO I2C Controller Driver

See if you can find updated drivers for them.

xNero · Jan 9, 2018

Thank you! I have updated both of them successfully. I will now try to boot in Windows normal mode to check if any BSOD occur.
I'll update once I know more :)

xNero · Jan 9, 2018

The error still occurs, even though the 2 drivers have been updated (I noticed that they already had the newest driver installed, as the newly installed driver has the same timestamp).
Here are the most recent dump files: https://1drv.ms/u/s!AmEjnLjcfA9apXLOVyEBQQ7Rw5ki

philc43 · Jan 9, 2018

Your most recent dump files are showing that there is a USB port implicated in the power state failure. You have various storage drives attached. If possible, please remove them or remove one at a time and see if it makes any difference to getting the BSOD. Please explain what these removable drives are and how you are using them.

xNero · Jan 10, 2018

That's correct, one device I use for extra storage (a micro SD). One USB is the Windows installation I used to boot into safe mode using command prompt. And there is a second USB which I often use to exchange documents to my fully working PC, like the dump files, so I can upload them here.

I let the tablet run overnight without being plugged to the wall charger, so this morning the battery was empty. I disconnected the 2 USB devices and the 1 MicroSD card, plugged in the battery charger and booted the tablet. It booted really quickly this time and worked just fine. I had just enough time to run the Sysnative app to make a new dump file, until after 10 minutes, then the BSOS appeared again.

The tablet is now restarting and as it usually takes about 30 minutes to 2 hours to boot up, I will attach the dump files I made during the boot without the USB devices and MicroSD card when I get into windows again :) will as soon as possible.

xNero · Jan 10, 2018

Apparently, the Sysnative app had no .dump files in the .zip folder. But I found a .dump file in the minidump folder, so I will attach it:
https://1drv.ms/u/s!AmEjnLjcfA9aqm9MPZ4DX4eYL_E2
This dump was made when there were no USB devices or MicroSD cards inserted.
But, the CDK09 keyboard was attached to the tablet (it is no USB keyboard though, it works with pins that attach directly on to the tablet's side).
Also, the tablet is being charged with a USB-C charger.
Could it be that the keyboard self or the USB-C charger is causing the issues?

philc43 · Jan 10, 2018

The dump file still shows the driver power state failure and the failure is related to the USB ports.

Read More:

Code:

[COLOR=#1e1e1e]0: kd> !irp ffffa88d696f9b40[/COLOR]
[COLOR=#1e1e1e]Irp is active with 7 stacks 5 is current (= 0xffffa88d696f9d30)[/COLOR]
[COLOR=#1e1e1e] No Mdl: No System Buffer: [/COLOR][COLOR=#1e1e1e]Thread [/COLOR][U][COLOR=#0066cc]00000000[/COLOR][/U][COLOR=#1e1e1e]:  [/COLOR][COLOR=#1e1e1e]Irp stack trace.  [/COLOR]
[COLOR=#1e1e1e]     cmd  flg cl Device   File     Completion-Context[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-00000000    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]
[COLOR=#1e1e1e]>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)][/COLOR]
[COLOR=#1e1e1e]            0 e1 ffffa88d66697c40 00000000 00000000-00000000    pending[/COLOR]
[COLOR=#1e1e1e]	      [/COLOR][COLOR=#1e1e1e] [/COLOR][U][COLOR=#0066cc]\Driver\ACPI[/COLOR][/U]
[COLOR=#1e1e1e]			Args: 00000000 00000001 00000001 00000000[/COLOR]
[COLOR=#1e1e1e] [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)][/COLOR]
[COLOR=#1e1e1e]            0 e1 ffffa88d69af1c60 00000000 fffff803611ba5a0-ffffa88d6a8d4130 Success Error Cancel pending[/COLOR]
[COLOR=#1e1e1e]	      [/COLOR][COLOR=#1e1e1e] [/COLOR][U][COLOR=#0066cc]\Driver\USBXHCI[/COLOR][/U][COLOR=#1e1e1e]	nt!PopRequestCompletion[/COLOR]
[COLOR=#1e1e1e]			Args: 00000000 00000001 00000001 00000000[/COLOR]
[COLOR=#1e1e1e] [N/A(0), N/A(0)][/COLOR]
[COLOR=#1e1e1e]            0  0 00000000 00000000 00000000-ffffa88d6a8d4130    [/COLOR]

[COLOR=#1e1e1e]			Args: 00000000 00000000 00000000 00000000[/COLOR]

The driver is a windows driver so unlikely to be the problem. I have no experience of the USB-C charger or port so I don't know if it could be a factor. If it works without BSOD when on battery power this could be a good indicator that it is the source of the problem.

xNero · Jan 10, 2018

These are the latest .dump files: https://1drv.ms/u/s!AmEjnLjcfA9aqnAIqjE6XNE7uB0k
The first dump file was made when the keyboard and USB-C charger were both no longer attached (and no USB or MicroSD were inserted).
The tablet ran for 30 minutes, and I was able to run the Sysnative app (first dump file), but it was really really slow.
Then another BSOD occurred (driver power state failure) and a second dump file was made.

MichaelB · Jan 10, 2018

unless you did not start with the intel Skylake Chipset to install,
it will miss / fail on nearly every driver.
Cube i16-L - Google Search

bwv848 · Jan 10, 2018

I do apologize for disappearing for a few days. Nevertheless, I just reviewed the System Event log and found some rather concerning events.

Code:

Event[3374]:
  Log Name: System
  Source: ACPI
  Date: 2018-01-08T15:04:03.963
  Event ID: 13
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NeroCube
  Description: 
: The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.

Code:

Event[3375]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2018-01-08T15:04:02.946
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NeroCube
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [COLOR=#ff0000]0x0000009f[/COLOR] (0x0000000000000003, 0xffff94828bd2aa00, 0xfffff801eb656c40, 0xffff94828bffbb40). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 8305a35b-287f-4814-9a93-513bd7b8968b.

Code:

Event[3376]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2018-01-08T15:04:00.135
  Event ID: 17
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: NeroCube
  Description: 
A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus:Device:Function: 0x0:0x1D:0x0
[COLOR=#ff0000]Vendor ID:Device ID: 0x8086:0x9D18[/COLOR]
Class Code: 0x30400

The details view of this entry contains further information.

As you can see, just before the BSOD is recorded, a WHEA event is written to the Event Log saying that a correct hardware error has occurred. (Note that the Vendor ID is 0x8086, which belongs to Intel; unfortunately I couldn't find any info about the Device ID.) And right after the system automatically reboots from the bugcheck, an embedded controller error is detected and logged.

Given these two events, the BSODs may just be a manifestation of an underlying hardware issue. As the first step of troubleshooting, I would suggest you update your BIOS and chipset drivers if possible.

xNero · Jan 10, 2018

Okay, I have installed the newest Chipset drivers, so I hope that will fix the issue.
The tablet is now rebooting in normal mode, so I guess I will have to wait again for a bit to see if the problem is fixed.
About updating the bios, I've never done that, so I'd need some guidance on that if it turns out it will be necessary!
All I know is that my BIOS is American Megatrends Inc. v5.11.

Driver Power State Failure due ACPI.sys

Member

BSOD Kernel Dump Senior Analyst

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

Member

BSOD Kernel Dump Senior Analyst

Member

Member

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

Member

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

Member

Member

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

Member

Member

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

Member

Sysnative Staff, BSOD Kernel Dump Senior Analyst

BSOD Kernel Dump Senior Analyst

Member