Seldom, but annoying (R4 after long sleep will not power on, requires pulling all power sources)

Hey guys, (view sig below for specs)
1 out every 6-8 sleep resumes, usually after about 6-8 of the computer being in sleep, my M17xR4 will not resume from sleep, I can't even force shut down, I have to pull the power cord and pop out the battery (its done this without any USB connections BTW, I made sure), It then powers up again without any issues.

It could just be a bug in windows 8, I would not be surprised; or the 13.1 drivers, but I highly doubt it, as it requires me to pull all power sources just to power down the machine. (last option would be complete clean system install)

Any suggestions?

 

Have you tried disabling PowerPlay in CCC? In the past, having it enabled (which it is by default) would cause my R2 to hang when attempt to go into S3.

 

Is it definitely freezing from sleep or hibernate? Check your power plan and disable hibernate maybe?

Is there any feedback from laptop when it is black? Any response from keyboard, maybe even try outputting to hdmi or something?

Sounds like a bad graphics driver issue. Could try the latest beta ATI CCC drivers. 13.2? or even try the ones from dell for troubleshooting.

 

Hibernate is never enabled, its sleep, I don't have power play enabled and I use high performance power plan, so by default hibernate is off. 13.2 beta does not allow some of my windows 8 tiles to function, but it also happened with 13.2, that is why i rolled back to 13.1

...I'm still leaning toward OS being the issue. Thanks guys for the input.

 

It is probably that. At least it does not happen all the time. Did it work fine on Win 7?

 

Yes it worked fine on Windows 7, never had that issue. The OS seems to cause the hang, but its very difficult to tell since it seems to be an isolated issue. Until the issue gets aggressively worse, I will not be reinstalling Win 8.

 

I had this happen with my R3. Gradually got worse until it always locked up in sleep mode (and that was a 120hz model as well with no iGPU). Other people had seen the same and I tried all the fixes I saw to no avail. Then I had a HD failure; fresh install of windows (7) and didn't happen again, so the OS is in the mix somewhere

 

I figured as much, thanks for the input, that helped confirm my findings.