We really need more information.

@Ramhound Such as? I didn't want to overdo it.

@gronostaj Updated. Thanks!

_SB indicates the South Bridge so its likely a device that is connected to it. Do ALL devices have Windows 8.1 drivers installed?

@Ramhound 8.1 came installed on the machine, so I would hope so.

I2C3 seems to be connected to ACPI which means this likely a ACPI driver problem. Its specicially tied to Tegra I2C Controller Driver which is odd to say the least on a x86 tablet. Make sure you have all OEM drivers current.

@Ramhound I'll work on that from Lenovo's website. On a side note, I came across this page (via the Lonovo forum), offering an update to bios v.1.07. Lenovo's website doesn't list any available bios updates. I'm assuming it's not a good idea to download + open some random zip file on the internet though.

If you have Hyper-V installed that basically disables your ability to use connected standby.

@Ramhound I'm not running Win8 Pro here. But if there's another way to disable connected standby (at least for the meantime), I'd love to hear it. Thanks again!

One of three ways. Get rid of the ACPI drivers, disable Secure Boot, or modify the registry

@Ramhound Thanks. I did that. But I'm still looking for a real solution...

@GiantDuck - Those are real solutions. Outside of a firmware update to resolve the actual problem from Lenovo.

@Ramhound I see. Thanks for your help. If you want to post that as an answer I'll come back to accept it.

@GiantDuck - If you confirm there are zero firmware updates, zero driver updates, and one of those solutions actually work I will post an answer.

@Ramhound All updates from Lenovo's website are either the same (or even older) than what's installed. I suppose there's a 1 in 1,000,000,000,000,000 chance that contacting them would produce something, but I may try that. The problem has, at the moment, subsided because I disabled connected standby.

@GiantDuck - I will write an answer at some point today if thats the case.

@Ramhound Well, that kinda broke when I see from powercfg /A that no other standby state (S1, S2, or S3) is available. Any ideas?

@GiantDuck - Its an either or situation. This appears to be a firmware issue that devices like the Surface Pro also had to fix.

@Ramhound Oh. Any ideas why I can find I2C1, I2C2, and I2C4-I2C7 in device manager, but I2C3 is missing?

I will be honest. I am not even sure the reason your x86 hardware has that device because my research indicates its connected to Tegra hardware.

@Ramhound Thanks for your help. I think I'll have to go for the 1 in 1,000,000,000,000,000 chance.