This HP Community is for Customer to Customer Product Support. First Time Here? Check Out Videos on How to Search, Register, Post and More.

Re: Windows 8 - No video after initial Startup Screen (923 Views)
Reply
Student
TrainzGuy
Posts: 3
Registered: ‎01-01-2010
Message 1 of 4 (996 Views)

Windows 8 - No video after initial Startup Screen

Just when an operating system finally arrives to truly take advantage of the TouchSmart interface (Iq770), it installs fine, but then CRASHES.  THe fluid interface shows up after the first boot, then disappears to a blank screen with a cursor which DOES respond to the mouse input.

 

Has any else tried the WIndows 8 Customer Release and have similar or same problems?  Everything else (including the touch response) seemed to check out fine on the initial boot...just that the video disappears after the system crashes.

 

Thanks!

Please use plain text.
Student
egumpert
Posts: 2
Registered: ‎04-08-2012
Message 2 of 4 (936 Views)

Re: Windows 8 - No video after initial Startup Screen

I'm having the same problem when try to boot a Presario CQ60 running windows 8. When I press the power button I see the COMPAQ screen with instructions to enter the startup screen. Then the screen goes black and there is no audio. This will continue untill I hold down the power button untill it forces down. Then if I immediately repower It will boot properly. The same symptom also occures if I attempt to reboot from a fully functional system. 

Please use plain text.
Tutor
boxerm
Posts: 42
Registered: ‎07-06-2009
Message 3 of 4 (930 Views)

Re: Windows 8 - No video after initial Startup Screen

make sure your system is able to run Windows 8....a good read

 

http://www.zdnet.com/blog/bott/does-your-pc-have-what-it-takes-to-run-windows-8s-hyper-v/4254

Please use plain text.
Student
egumpert
Posts: 2
Registered: ‎04-08-2012
Message 4 of 4 (923 Views)

Re: Windows 8 - No video after initial Startup Screen

Thanks for the info. The laptop is capable. Anyhow, after windows update ran today the problem seems to have been fixed. 

Please use plain text.