Re: Boot and general operating problems with Home Premium 64

I don't know how the warranty works in the US, but here in Australia you have to have a return code from HP support first which won't happen if they think there is some sort of user fixable problem and they classify reinstallation as user fixable. Since the HDD comes up clean in the BIOS self test, they say there is nothing wrong with the HDD and don't see how the other issues could be hardware based.

<.> wrote in message news:#5YEhw20JHA.5764@xxxxxxxxxxxxxxxxxxxxxxx
Why haven't you returned it? It's HP's problem.

--
.
--
"Stephen @ ZennHAUS" <stephen.huisman@xxxxxxxxxxxx> wrote in message news:e5SZYt20JHA.1096@xxxxxxxxxxxxxxxxxxxxxxx
Hi Guys and Gals

I have an HP Pavillion dv7 Notebook (Model No. FS136UAR to be specific) running Windows Vista Home Premium 64-Bit.

As a little bit of history to the current problem, here is a basic run down of the problems so far.

Got the laptop in first week of February. Up until about Mid April, the laptop would regularly not boot. Post would run as normal and then a black screen message saying Windows could not boot; insert the CD/DVD and repair or run a recovery.

Twice the setup based repair and the HP provided recovery repair did not work and I had to rebuild the laptop. Once I rebuilt it with HP recovery partition and the second time I got a new MS retail CD and installed the system from scratch with drivers downloaded from HP's site.

My initial "diagnosis" was that the hard drive was faulty, but between rebuild 1 and rebuild 2, HP had me run an HDD self test from the BIOS and it passed with flying colours.

So that is the history to this point.

NOW ... running retail VHP64 with O2007, Windows Live, IE8, CS3 and AVG as pretty much the only apps installed. All updates have been installed. However, when the updates were installing, the system kept failing to install a large number of updates. Upon the next boot it would install some more but still some would fail and so on until there were only 4 updates left. A few times it would fail and revert on next boot, but eventually it finally installed all the updates.

Last night (about 10 days since last rebuild) for no apparent reason, every time I double click something (an app, file, explorer) a command prompt is launched. If I right click on an icon, the first and default option is "Open in a command prompt". I can launch apps and open files etc by right clicking and choosing open.

As frustrating as it is, I can get by, but after shutting down my laptop and restarting it at a friends place, it no longer recognizes my mouse (MS compatible 3 button (2+wheel) optical). The mouse has never needed a specific driver, but now it is asking for one. My touch pad is not working either. GRRR!

I have run a virus scan last night and all comes up clean.

This is the first time I have had a system with a 64-bit OS. Is this something I can expect when running 32-bit apps or is this indicative of a deeper hardware issue?

If there is any further detail that might be useful feel free to ask. Also, I am considering putting Windows 7 Ultimate 64 RC on the machine to rebuild it (or is that a bad idea too?)

Cheers

Stephen @ ZennHAUS

.