HP Pavilion P6620f has no display after manual shutdown.

Zuckerton

Honorable
Apr 28, 2013
37
0
10,530
So my Grandma gave me her HP Pavilion P6620f to fix. She said it would freeze and then go through a cycle of shutting down and turning back on.

She gave it to a guy to fix before me who said there were bad chips near the video portion of the board, so he put in a GPU. He said the PSU that was in there wasn't the one that was supposed to be, so he replaced it as well. He also put in a new Hard Drive and wrote Windows 7 back on, setting it up with the restore Discs that came with the Computer when it was originally purchased.

I got it out here and it turned on just fine. I left it on overnight and it didn't malfunction. Left in on while I was at work and it worked fine when I got back. I woke up today and the screen was Display was blank. After 32 hours, it had finally froze.

I held in the Power button to shut it down, but when I pressed it again, the PC would boot, but there's nothing on the display. I manually shut it down again and back on, same thing. I did this 3 times, then unplugged everything for a little while. Plugged them all back in and I got the splash screen for the motherboard, then it went to a black screen with a blinking line. I shut it down manually, turned it back on and now I'm back to no Display.

Any ideas on what could be causing this?

*Update" I disconnected the PSU from the motherboard, reconnected it and the PC turned on normally. After about a minute, it went to the BSOD mentioning a faulty driver trying to corrupt the system. "Stop: 0x000000C4 (0x0000000000000091, 0x0000000000000002, 0xFFFFF88002F1FFC0," there were other codes there, but they didn't fit in the picture, I think it was just 0x0's the rest of the way.

I turned it off, turned it back on and back to no display. I removed the PSU again, and it turned on just fine. Then when I went to pull up Firefox, the PC restarted. It then went through the whole boot sequence, but when it got to the "Welcome" screen, it froze and this long beep started. I turned it off, turned it back on and it froze at the splash screen. Shut it down, turned it back on to boot into safemode, it ran fine for a few minutes, restarted and I got the blinking line again.
 
Solution
This sounds like the motherboard may be bad. If the visual behavior is doing the same with onboard graphics and a custom GPU, the only culrpit left is the motherboard. Unfortunately the only way to test this theory out would be to hook all that stuff up to another board and test them out. I see that model was released in 2010, so through that time, it might have suffered through multiple outages and things. I doubt its under warranty, but the next action I would take is finding a board to replace/test with. Either that or you can call it a loss, but depending on the rest of its specs, it might have some potential.
This sounds like the motherboard may be bad. If the visual behavior is doing the same with onboard graphics and a custom GPU, the only culrpit left is the motherboard. Unfortunately the only way to test this theory out would be to hook all that stuff up to another board and test them out. I see that model was released in 2010, so through that time, it might have suffered through multiple outages and things. I doubt its under warranty, but the next action I would take is finding a board to replace/test with. Either that or you can call it a loss, but depending on the rest of its specs, it might have some potential.
 
Solution


That's my first thought (actually, first was the hard drive, but they told me it was already replace). I found ONE person selling the motherboard. I bought it this morning, then he messaged me saying that he put down the wrong model of the motherboard. He had it labeled as "N-Alvorix-RS880-uATX", but it's actually H-RS880-uATX (Aloe). They appear to be compatible, so we'll see. Thanks for the input.
 


It appears to. My Grandma just likes to replace everything with the exact same thing that was removed. If all else fails, I'll just build her a computer.
 


If it's the motherboard, I certainly will. If it's not, I'll be back, haha.
 
I got in the new motherboard and hard drive today (turns out the motherboard in this was the original one either, it was actually the same one I ordered, so there's a plus), replaced it all (took about an hour), then I went to put in her System Restore discs and got:

"the system recovery does not support this computer"

Not sure why. I installed a 1TB hard drive that is the exact make and model of the one I took out, I installed a motherboard that is the exact make and model of the one I took out.

Back when I was testing to see if it was the hard drive, I installed a 300GB (instead of the 1TB in there before), and the system recovery worked fine, so I don't think the Hard Drive swap would cause anything.

And the motherboard, again, is the exact same model, so it shouldn't have an affect on it either. I think it might have a different BIOS installed, but I can't seem to find the BIOS for it. FoxConn doesn't seem to have the motherboard listed in their products.
 


So I the PC works (then again it worked for three days before messing up last time), issue is that the recovery discs don't work for it anymore. They worked with the last motherboard (as I used them with the Hard Drive I replaced), but not with this one.

The Motherboard that was originally in here was the BIOS version 6.02 and the new Motherboard has the BIOS version 6.08. That's the only difference I see between the two (as said, they are both H-Alvorix-RS880-uATX).

Would the "upgraded" BIOS be the reason it doesn't work? I used "Free Commander" to delete the Recovery files that tells the computer that copies were already made and was able to make new ones, but they don't work for the PC either. My guess is because it used the Recovery Partition on the Hard Drive that was written to it using the other motherboard, but that's just a guess.

If all else fails, I'll just install the OS and install all the programs separately, then make a recovery disc out of the system at that point, if it's possible to do that.
 


I contacted them and they said they no longer support it, so they don't have them. I contacted the guy who I bought the motherboard off of and he said he still has the disks and that he'll send copies to see if they'll work.

Otherwise, I'm looking into Slipstreaming to see if I can use that to write the OS to a disk with all the updates, drivers and a few programs.

I read that it supports adding updates and drivers, but I have yet to see someone mention programs. If it allows programs to be added and they can be auto-installed, that should work.
 


Indeed, I'll keep this updated in case someone else runs into this issue.
 
Motherboard was the issue. I ended up putting her Old Motherboard back in, using the System Restore Discs that came with it originally to restore it back to Factory Settings, then put the new motherboard back in and used Macrium Reflect to create a Disk Image of the Hard Drive.

I sent it back to my Grandma and she called me last week saying the computer was froze.

I ran "Repartition Bad Drive" on the new hard drive I bought her. RBD scans the drive and every time it finds a bad sector, it creates a new partition that removes the bad sectors. By the time RBD was done scanning the drive, it had 18 Partitions.

I threw her old HDD back in and ran the program on it and it came back with 0 bad sectors. So I used the Macrium Reflect discs that I created to put the image of the "new" HDD back onto her old HDD (as RBD erases it when scanning) and sent it back to her.

Hopefully, the PC doesn't have to come back again.