Major bug on Envy 17 3D

Hey guys, I am facing a major bug with my new Envy 17 3D.

Basically every-time the laptop is idle and the display turns off to save power (in my case after 5 minutes) the screen turns off and the laptop restart after crash..

It happens in every power profile. When the screen turns off the laptop crash and restart.

When I have time I will fully investigate what cousin this issue.
I am running the latest ATI Calatyst Control Center 10.12. And the latest Bios F1B if I remember correctly.

I am curious if anyone else is facing the same or similar problem??

 

sorry to hear your issues. I am very interested to know how this develops. Have you called HP Envy tech support yet? In case you are wondering, the phone number is listed on the black slip on the long rectangle paper. Hope they can help

 

Killa Joe, you have the Envy 17 3D?

Can you set your Powe Profile to set your monitor off after like 5 minutes of idle time??

Can you please tell me if your Envy has the same problem and crashes after the monitor shuts off?

Thanks in advance.

 

I had my Envy for 1 day, sent it back the following the day. I kinda wish I kept it for a few days more. Had the warps and some seperation at edges.

I have a dv7 for now and the computer runs great. The monitor goes to sleep when I tell it too. I had no idea the Envy is doing this...kinda weird for a premium laptop. I hope I won't have those issues. I should get mines in Jan 15 if all is well. Until then I am sure someone who has the Envy 3D can comment here. Also, as I mentioned give HP Envy support a call that is something they should be able to fix for you on the spot.

 

I can tell you that mine certainly does not crash after screen wake-up. I have it set to shut off screen after 5 min and it wakes up to a login screen, which I would assume is normal- no crashing on this laptop except for when playing certain games.
Let me know if you want me to try something else.

 

I found what caused the crashed and I fixed it... It took me two hours of research but I found it...

On my power setting I had the turn off screen every 5 minutes.
On my screen saver I had Screen Saver "None". I had "Display Windows Login Screen on resume" checked and I had the time to 5 minutes as well. (This is because I wanted my PC to lock every 5 minutes of inactivity and ask for the windows password on resume)

So both my screen sleep and my screensaver lock was 5 minutes. For some reason Envy 17 cannot handle and generate both at the same time and crashes the whole system.

What I did was set my screensaver lock to 4 minutes for Blank Screen (to lock the system in 4 minutes of inactivity) and then set my Screen to shut off after 5 minutes.

And "voila" hat solved the problem.

I am sure some HP crapware is causing this crash... As all my other PCs with clean Windows 7 installs are handling Screen Sleep and Screensaver lock at the same time with no problem at all.

When I have time to do a format, first I will install an SSD and then I will perform a clean Windows 7 install on it. That will take care this and any other similar problem

 

I think I've cracked it - *NONE* of the previous suggestions helped (driver versions, power setting configuration, etc)... And I had a thought; the only thing I CHANGED since I bought it was to enable the Virtualization settings on the CPU to get VMWare to work.

I went into the BIOS and disabled it, and now the laptop sleeps and wakes PERFECTLY.

Unfortunately, this has borked any 64bit virtualization support within VMWare...

 

just trying a BIOS update as it looks like F16 fixes this issue...
HP Notebook System BIOS Update (Intel Processors) HP ENVY 17-2101ea Notebook PC - HP technical support (United Kingdom - English)

 

Sorry man, this has been a known issue for awhile and was fixed by the BIOS update. I too had the same problem with Intel Virt enabled until they patched it.

 

Yeah - I've seen that its been an old issue and the fix is fairly old too; however I've not seen much in the way of mention about the F16 BIOS update (latest is F18 at time of writing) being the fix. I guess this is just in case anyone else is googling for the problem, it may help them fix it more quickly.