2 Posts

August 30th, 2011 19:00

PS, this laptop is only about a month old.

14 Posts

September 27th, 2011 03:00

Yeah exactly the same here - M18x crossfire ati's. I thought it had something to do with the face recognition software - it does something very similar in low light conditions. So I uninstalled that - nope. I put new SSD drives in mine, so i don't have respawn - but I did a fresh win7 install, same issue. It's not the password screen - IIRC if i booted into windows without a password, the screen stayed in HDMI-in even though the desktop was running. (I need to double check this). I guess it's a nice security feature if you don't know! I am reading a few similar stories on google too (including 1 dude who spent 1 1/2 hours on the phone to dell, for this exact problem). Does anyone from Dell read this???

14 Posts

September 27th, 2011 04:00

And yeah - I tried the customer support thing too. lol

Community Manager

 • 

56.9K Posts

September 27th, 2011 07:00

I read the Forums. Did you both have this issue out of box? Or did you make some driver changes and then the issue arose? What Power Save options are you using when you just close the lid? By the way, I do not use Power Save or hibernate. They have not worked well since Windows 9x. I simply use the laptop, power off. Then power on.

14 Posts

September 27th, 2011 08:00

Okay - from cold boot the password screen don't matter - I get the "starting windows" animation, then white screen - windows boots and runs fine in the background. and off you go...

From standby (balanced plan) - lid closed, I get the full windows desktop flash up for a second - then the white screen again...

HDMI-IN DOES NOT WORK - I am ATI mode, running a WD-LIVETV media player @ 1920x1080@60hz - I get the white screen and no sound - nothing? (I have devoted 2 mins testing this - but it should have worked?)

The OSD does say "HDMI-IN ON" when I switch over.

I flashed the main bios today ver a03 or whatever the latest is.

Vid driver: (Yes I have tried a few using the recommended cclean between installs etc)

I got sick of so many reboots I put SSD's in it!!!

Driver Packaging Version 8.881-110728a-122944C-ATI

Catalyst Version 11.8

Provider ATI Technologies Inc.

2D Driver Version 8.01.01.1178

2D Driver File Path /REGISTRY/MACHINE/SYSTEM/ControlSet001/Control/CLASS/{4D36E968-E325-11CE-BFC1-08002BE10318}/0000

Direct3D Version 7.14.10.0855

OpenGL Version 6.14.10.11005

Catalyst Control Center Version 2011.0524.2352.41027

The video bios reports: BIOS Version 013.010.000.009

Anything else I can give you?

Shane.

14 Posts

September 27th, 2011 08:00

- And to clarify something, NOTHING shows up on top of the white screen - the OSD is only visible on the windows desktop...

14 Posts

September 27th, 2011 08:00

Yeah I realized you do after I said that sorry!

No I had no problem until I started actually using the HDMI-out port (Dirt3 on a 55" samsung rocks!)

I have never bothered even testing the HDMI-IN to see if it works!

The screen is white from either a cold boot - or recovering from a standby situation. Windows is happily running in the background - you can log in etc etc "behind" the white screen...

Gimme 5 - I'll test a few things out... (it's 12:30am here in oz)

14 Posts

October 4th, 2011 12:00

Okay too hard basket huh?

Chris - can you find out WHAT handles the HDMI-IN, I am assuming it is part of the Sandy Bridge chipset?

Which driver is it talking to? - neither the ATI or Intel graphics driver versions make no difference, and the problem is identical booting with either intel or ati graphics...

14 Posts

October 25th, 2011 04:00

Bump....

1 Message

January 16th, 2012 09:00

So I have the same problem with my laptop, it didn't happen out of the box, but after some updates... possibly from windowsupdate i don't remember that far back honestly, I figured out the fn-f8 thing myself pretty quick, so i decided to just live with it, but now I kinda want to use the hdmi-in and want to know what i need to do to get this working.

14 Posts

January 16th, 2012 14:00

Dell diagnosed a faulty rhs sub-board - turned out my motherboard was faulty and was duly replaced...

No Events found!

Top