Will Asus Dead Pixil Policy cover this???

I have had my asus laptop for about 1-1.5 years now and, recently, and out of nowhere, a strip of miscolored pixels are at the bottom of my screen. They change different colors, but do not follow anything on the screen; they're just broken. It is a strip about the height of this line "|" (giv or a take a pixel) and have a width of the entire screen. It is at the very bottom. It is very annoying, so im wondering if Asus can fix this for me or will i have to pay for a fix/new laptop
Thank you

Also, i forgot to mention I have a broken control panel that wont open, so if anyone can give me some advice on that itd be great!

 

Dead pixel policy is 30 days from date of purchase.

If you're in warranty, they'll cover it so long as it didn't happen through user "action".

 

As I recall, Zero Bright Dot guarantee is limited to 30 days from purchase. But what you're experiencing is not a dead or stuck pixels issue, it sounds like something's wrong with either your graphics driver or the graphics chip or its line to the screen. Try reinstalling the driver, and if that doesn't work you could back up your data and try a full reinstall of the system. If that still doesn't fix it you're dealing with a hardware failure, and I suspect that is the case really, and you should be covered by the standard two year warranty (provided it's not a result of misuse) to call up Asus and make an RMA claim.

 

Thank you all very much, ill try all this out!

 

Try "UDPixel" and let it run for 24hrs.............if your pixel is dead i.e black then there's no hope but if it's green, blue, red or white then it's a "stuck" pixel and the above mentioned UDPixel may work for you.

 

If you bring up the run command and type control do you get an error? If you do please post it and we can help.
OR
If you want to it won't hurt to run system file checker
How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

Since files may be replaced I would recommend doing an image of your machine prior to running this program if you use the /scannow option
Or you can use /verifyonly if you do not wish to image first.

 

I type control and a window pops up then dissapears; ill try those fixes, thank you

 

I'm pretty confident they would cover it.