Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

What To Do When Windows Vista Crashes: Page 2 of 10

  • Boot Repair For Vista
  • There's a little-known restoration process, which you can use to get your system back up to snuff without going through a complete reinstall. It's controlled via a command-line tool called Bootrec, and it's more powerful than ever in terms of repairing nettlesome startup issues.

  • Vista's Reliability Monitor
  • The third leg of our story discusses a neat tool that's hiding just beneath the surface of Vista. It's called the Reliability Monitor and it keeps a tally of all your Windows crashes, application failures, and hardware problems.

    How To Break Vista

    I got interested in the subject of crash-recovery after I recently re-read Fred Langa's popular piece, XP's Little-Known Rebuild Command. For the purposes of our crash-recovery discussion, there have been some big changes since the XP days. Mostly, they involve the way Vista handles booting up. The OS no longer uses a boot.ini file. That's been replaced with a sophisticated file-like structure called Boot Configuration Data. (More about that later.)

    The upshot is that standard Vista installations are less likely to fail to boot than were standalone Windows 95/95/XP setups. Paradoxically, dual-boot configurations seem more prone to problems, but that'll be the subject of a second article.

    Vista also is more resistant to damage to key files. Indeed, my original plan was to retrace Langa's XP path for my Vista article and induce a crash by damaging the crucial "hal.dll" file. Thanks to Vista's improved protections, even though I had admin privileges, I couldn't touch it. (On the other hand, my hal.dll test exposed the achingly slow way search runs in Vista. I found the hal.dll file manually by going to directly C:/Windows/System32, while search was still lumbering along.)