Upgraded to Windows 10, but ran into problems with the sleep mode. Help!!!

Hi,
I recently upgraded to windows 10 on my laptop, which is a HP Pavillion. It runs pretty smoothly, except for the fact that every time I close my laptop lid, it goes into sleep mode, but when I try to turn it back on from sleep mode, the laptop screen will not light up, so I need to restart my computer each time it goes into sleep mode. Is there anyone who can help me resolve this issue? I am at my wits end trying to solve this.

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_perf/windows-10-build-10130-sleep-issues/1a82fd6e-bafb-4051-a872-cd9a30da31ce?auth=1

I've tried searching for answers, but there doesn't seem to be any solution to this.

This is my exact problem!!! Been talking to online support but no fix yet!I have the exact same laptop too.

Does the power button light stay on while you are hibernating/sleep as well?
Mine doesn't hibernate or sleep properly. Needs a restart for it to come back on and my shutdown doesn't work properly. My power button light stays on after its meant to be shut down.

They told me to check for any troubleshooting fixes for power but no luck.
They haven't come across this problem either from what the woman I was talking to was saying.

Edit: after being passed onto different microsoft answer techs I've been told something could be wrong with the installation of windows or this feature of windows 10 hasn't been updated yet. But how have other people not had problems if its a feature?!
He said either revert back to my old windows or wait for an update and not use the sleep/hibernate function.
Very helpful

Hi Tinkerbell, my laptop is able to hibernate properly, but I've heard other people also face the problem where it can't hibernate properly. And according to the link I posted earlier, they said to either reinstall windows 10 together with a fresh iso file, or alternatively, to switch the setting to 'do nothing' when you close the lid.

The advice probably wasn't helpful because there's only so much you can do without any logs or record of what happened, and why.
Is there anything in the Event Viewer under System?

My best guess is something is blocking a power transition, most likely a 3rd party device driver. Without any logs, it's impossible to say.
An xperf trace of shutdown might find a culprit as well.

This is part of my event log. I'm not sure if this helps

Error 4/8/2015 5:31:16 AM Microsoft-Windows-DistributedCOM 10010 None The server App.AppX8h0bdkbb5frkt9s09fvshhbvqnntmvm1.mca did not register with DCOM within the required timeout.

Error 4/8/2015 5:31:15 AM Microsoft-Windows-DistributedCOM 10010 None The server Windows.Networking.BackgroundTransfer.Internal.BackgroundTransferTask.ClassId.1 did not register with DCOM within the required timeout.

Error 4/8/2015 5:31:15 AM Microsoft-Windows-DistributedCOM 10010 None The server Windows.Networking.BackgroundTransfer.Internal.BackgroundTransferTask.ClassId.1 did not register with DCOM within the required timeout.

Error 4/8/2015 5:31:14 AM Microsoft-Windows-DistributedCOM 10010 None The server CortanaUI did not register with DCOM within the required timeout.

Error 4/8/2015 5:31:14 AM Service Control Manager 7031 None The Sync Host_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

No, I don't think they're the problem. DCOM and service control manager issues are unrelated to pnp ones.