The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Had the y410p for about a year, now can't go past Lenovo logo screen

    Discussion in 'Lenovo' started by nisbahmumtaz, Aug 18, 2014.

  1. nisbahmumtaz

    nisbahmumtaz Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    A day ago, I tried to open up my computer, and when it opened up to the Lenovo screen, it automatically closed, and booted back up to the Lenovo screen, and closed again. Then it repeats ad infinitum.
    I can still access BIOS screen, but I really don't think that would do any good.

    A few days back before the error occured, my computer did suffer from a few hardware related shutdowns, but I just scuffed it off. The error is called WHEA or something.

    So, my current verdict is hardware failure. But I'm really not sure what's the problem. I hope to god that it's not a hard drive failure, because the last time I backed up was, stupidly, a year ago.

    The only modification I made with it was first-day downgrade to Win7, and an extra RAM addition. But it worked fine for about a year, so I really don't think my tinkering did anything significant to the failure.

    Maybe this is why it was discontinued...

    EDIT: So I tested the laptop with Hiren's Boot CD, and tried to log in from there. As soon as I tried to normally boot through the CD, I got a BSOD, with the main error titled as BAD POOL HEADER. Not being sure what that was, I tried booting into the TinyXP on the CD. It worked, but it doesn't really access my hard drive, so I'm still not sure what components are giving me the problem. I'll run memtest and chkdisk first, and see what comes next.