Re: More Vista Woes

Martin Brown wrote:
Ho hum. The last whizzo 1/10/08 Vista update did for my only Vista PC - a Toshiba portable. It totally destroyed itself beyond repair.

The update finished and upon reboot it generated a genuine BSOD sysnurdle error message screen which persisted for all of 200ms before the machine spontaneously switched itself off with a loud click (not enough time to read it and barely enough time even to recognise what it was). Blink and you would have missed it entirely.

After that nothing worked - the repair functions basic and advanced diagnostics could see the previous known good configurations but were unable to finalise them even given several hours trying. It got stuck in some kind of verification loop. The first serious attempt to boot after that failed whilst it was checking modules with about 3300/68990 displayed on the screen when it went click and switched off. Then it got even worse and stuck at 667/68990 but now it did not instantly switch off so it was possible to write down the error message for all the good that does:

!! 0xc0000034 !! 667/68990 (qwave.dll)

The display appeared to be refreshing this text at glacial speed.

Hardware testing with Vista not loaded shows nothing wrong.

I finally lost patience this morning and trashed the whole thing back into working with the master install disk. Thank heavens for backups.

Their lame slogan "Working just got more fun" really grated.

I wonder how long it will last this time...

Regards,
Martin Brown
** Posted from http://www.teranews.com **

Don't use Vista!
I've got a new quad core machine and used my old copy of XP.
Why would *anyone* want Vista?

--
Dirk

http://www.transcendence.me.uk/ - Transcendence UK
http://www.theconsensus.org/ - A UK political party
http://www.onetribe.me.uk/wordpress/?cat=5 - Our podcasts on weird stuff
.

Relevant Pages

  • Re: More Vista Woes
    ... Martin Brown wrote: ... The update finished and upon reboot it generated a genuine BSOD sysnurdle error message screen which persisted for all of 200ms before the machine spontaneously switched itself off with a loud click. ... After that nothing worked - the repair functions basic and advanced diagnostics could see the previous known good configurations but were unable to finalise them even given several hours trying. ... Buy garbage, get garbage, expect garbage results like what you have. ...
    (sci.electronics.design)
  • Re: More Vista Woes
    ... It totally destroyed itself beyond repair. ... even worse and stuck at 667/68990 but now it did not instantly switch ... off so it was possible to write down the error message for all the good ... Hardware testing with Vista not loaded shows nothing wrong. ...
    (sci.electronics.design)
  • Re: Scripting Error/Runtime Error
    ... So now the IE repair procedures you tried will be appropriate. ... That article does not apply to IE7. ... Reference error message: The operation completed successfully." ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Internal Error Occurred : The request is not supported
    ... Finally concluded that the configuration could not be salvaged - no repair ... an entire clean install of Windows XP MCE, only minor hassle was the time it ... > Attempting to start each manually resulted in the error message "Error 1068 ... > the conclusion that only a clean install of Windows XP will resolve this. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Office Outlook(2003)
    ... The error message indicates there’s an apparent problem with the faxing software, ... You should open the Help menu in Outlook 2003 and select the Detect And Repair option. ... If neither of these suggestions works, a final remedy is to replace the Fxsext32.dll file with a new copy from the Windows installation CD-ROM. ... You can accomplish this task with help from the System File Checker utility. ...
    (microsoft.public.office.misc)