Windows 8.1 Suspend Issues

Windows keeps firing back up again shortly after suspending, or a few hours later. I realise it's a common issue, so I'll just rattle off what I've tried. I have scoured the 'net but not found any solution.

1. Checked Event Viewer, but it shows source unknown, or something to that effect.

2. I've disabled the feature that allows Windows updates to wake up for install.

3. I've disabled Kaspersky's feature that is similar to the above.

4. I've tried the powercfg command under CMD and it seems only the mouse and keyboard can wake up the computer, regarding hardware, which they do, normally, as they have done for a long time. Neither mouse nor keyboard has shown signs of issue, but I disabled the mouse, just in-case.

5. I've tried unplugging my wireless adapter (LAN disabled via BIOS) during suspend, to no avail.

List updated:

6. I've tried suspending and hibernating but the same issue arises.

7. I've tried hibernating and suspending with all USB devices removed to no avail.

Probably tried other things but that's all I can remember. A friend of mine has the same issue with a computer of his running Windows 8.1 ¬_¬ It's especially annoying because my SSD has some sort of weird issue with this computer, meaning I have to suspend unless I want to keep opening up the computer on almost every restart. -_- I don't think these issues are linked, 'though I accept the possibility.

Would greatly appreciate an assist.

PS

This feature USED to work for a few months without any problems. This is quite a recent problem as of perhaps a week ago. Could this be due to a crappy Windows 8.1 update?

Try sfc/scannow in admin command prompt.

What sort of issue with the SSD do you mean? I assume you have installed windows on the SSD, so this issue could be relevant to the problem.

IW849 said:

Windows keeps firing back up again shortly after suspending, or a few hours later.

Click to expand...

When you say "suspending", is it: Sleep or Hibernate? Just to make sure we are on the same level.

See the difference here:
Sleep and hibernation: frequently asked questions

cipals15 said:

IW849 said:

Windows keeps firing back up again shortly after suspending, or a few hours later.

Click to expand...

When you say "suspending", is it: Sleep or Hibernate? Just to make sure we are on the same level.

See the difference here:
Sleep and hibernation: frequently asked questions

Click to expand...

Sleep, 'though I tested hibernation to the same result. Also tested without any USBs and still the same. :|

Sleep and suspend seem very similar to me so I've gotten used to referring to sleep as suspend, sorry.

axe0 said:

Try sfc/scannow in admin command prompt.

What sort of issue with the SSD do you mean? I assume you have installed windows on the SSD, so this issue could be relevant to the problem.

Click to expand...

And what do you expect that to do? it does nothing but wastes the OP time.

It is normal for a unit to get woken up from Standby. Especially if you have not made sure that devices cannot wake it. Same as some malware scanners will wake the system if they are set to scan after the computer has been idle for a period.

Didn't read the part "meaning I have to suspend unless I want to keep opening up the computer on almost every restart" correctly, sorry.

A common issue for my age in my country unfortunately.

I'm seeing a couple of replies that are showing my post wasn't properly read. Please read through it and note the link if you're curious about the SSD issue, and/or think they are linked. Thank you!