Replies

So, I come back to the problem this morning, after a couple of days and very many reboots showing curruption, to find that both chkdsk and chkntfs find the drive to be clean. I am bemused – is this the famed magical selfhealing property of NTFS? If so, would be nice if it told me what is going on! On the other hand, the slow shutdown is still there, and when I attempted to run chkdsk /f at startup (just to be sure), chkdsk still stopped after 5 seconds.

My only course of action is to press on operating normally and watch it like a hawk. Perhaps in the medium term I should contemplate an upgrade to Win 7, as a slicker system with hopefully more reliable system tools. Any views on whether that is a smart move or a foolhardy one, given the potential problems I have at present?

Many thanks DocWatson and JoePerez for your help.

Chris

Chris
Win 10 Pro x64 Group A

Event log – all I could find was errors in Administrative events, 9 each time I booted saying “The file system is corrupt and unusabe. Please run chkdsk utility on the volumeDeviceHarddiskVolume1. I could not see anything for the sheduled chkdsk that I asked for on reboot.

Chris

Chris
Win 10 Pro x64 Group A

Doc Watson – I have not tried System Restore because it seemed to me that if the file system was corrupt that would not help – in any case I am not sure quite when the problem started.

Joe Perez – just tried with /f/r and I had the same result. Not sure how to get at the System Event Log – can you give me a pointer?

Chris

Chris
Win 10 Pro x64 Group A

Hans

Thanks – I will proceed on that basis

Chris

Chris
Win 10 Pro x64 Group A

I think the issue is finally resolved. The PC crashed again today, but on recovery it offered Vista SP1. Having installed that, it immediately offered a version of KB947562 dated 27 May. This is the compatibility patch originally dated 8 April, but reissued in May to incorporate many more issues (according to the article). With that, SP1 installed, and perhaps my problems with bsods may diminish.

So, perhaps I was hasty with HP, in that MS may well have withheld SP1 while they sorted out the problems. However, what did not help is that all the MS and HP articles said SP1 was available nornally through WU. I guess the one thing that stands is the last line of my previous post:

Wouldn’t it save us all a great deal of time if these people would just be open with us!

Hope this might help other HP owners.

Chris

Chris
Win 10 Pro x64 Group A

Joe – thanks for the caveats, which I shall watch carefully if I go that route.

I think I am getting the picture now, although HP is not being open with me and are continuing to maintain that MS have pulled SP1 from Windows Update.

I think there is a problem within the HP setup for my laptop (HP Pavilion dv2535ea) that conflicts with SP1. I think HP is working with Microsoft to fix the problem, because HP have now admitted that HP, not Microsoft, will release the fix that allows SP1 to load. Unfortunately, I do not have a time frame.

I think I am going to give them a bit more time to fix it, since I do not want to go from one sequence of BSODs to another sequence of different BSODs. However, I am still pursuing HP support.

Wouldn’t it save us all a great deal of time if these people would just be open with us!

Chris

Chris
Win 10 Pro x64 Group A

John

Thanks – that’s what I thought. I will have a try at installing that patch manually – it should have come down automatically but I cannot see it on the list I have, but that will have to wait till I get back tomorrow. Meanwhile, HP are still insisting that SP1 has been pulled from Windows Update.

Need I say more?

Chris

Chris
Win 10 Pro x64 Group A

John

Are you getting at the suspension in Feb? I thought that was long since resolved. Microsoft site says it is available through WU, and has not been changed since late April.

Chris

Chris
Win 10 Pro x64 Group A

Bob

Thanks for the routine – I may yet do that, but I am a bit nervous that I have a crook driver that might trip me over when I install.

HP say that MS have withdrawn SP1 because of the problems, but I have not seen anything to that effect, so I suspect a smoke screen. Anyone got any definitive answers?

Chris

Chris
Win 10 Pro x64 Group A

OK – so I flashed the BIOS and I still am not offered Vista SP1. I’m back onto HP support (and their bad english), so I’ll see what happens next.

Still getting the Vista BSODs though!

Chris

Chris
Win 10 Pro x64 Group A

Thanks Fafner. I have installed everything that WU offers other than Silverlight, (or whatever it is called), and that can’t be an issue. I have had an exchange with HP in which, after an initial dumbkopf reply, they recommended a BIOS update. I will do that, hopefully later today, and see whether it gets me any further.

Chris

Chris
Win 10 Pro x64 Group A

Thanks. I have just been on HP Update and got everything it offered (which was only a security patch to itself!). I also looked at the direct driver site, but was somewhat put off by a long list of drivers, starting with one for the problematic Conexant HD Audio that was version 4.19 – while anything up to 4.32 causes problems. Fills me with all sorts of confidence!

I have emailed HP to see what they have to say, and if that does not work I’ll have a look at the BIOS update.

Chris

Chris
Win 10 Pro x64 Group A

Dave

Thanks – I will have another go through HP, but I thought their tool said I was fully patched.

Chris
Win 10 Pro x64 Group A

Rory

Thanks for the heads up – I use Access, but infrequently and in a fairly basic manner, so I may hold off for the moment.

Chris

Chris
Win 10 Pro x64 Group A

Hans and Joe

Thanks for the info – very helpful.

Chris

Chris
Win 10 Pro x64 Group A