March 7, 2007
Hardware Failures and Windows Vista
I've had an interesting experience with Windows Vista. At first, the OS was shutting down some of the applications, apparently at random. Vista has a memory access protection system (called DEP) and in case of a very unusual memory access a program is terminated, as it is considered as a possible attack to the system integrity. I was quite puzzled at first. Then I started getting abrupt system restarts and/or blue screens. Many of them. I could even boot and the system was gone.
Having had a few troubles with drivers, I though one of them was the culprit. For example, almost on every boot Vista re-installs the audio driver with the default Microsoft one (which doesn't work for my hardware) and it did replace the video driver and one of the motherboard drivers with a different version. So I tried to reinstall and discovered many interesting features. Booting with the setup DVD, you can revert back the system to a known state (although Vista missed some of its own driver re-installations). If you have a system backup, you can restore it directly. However, having a corrupted system file is not contemplated. I wanted to do a system reinstall (as I was getting errors in one core DLL) and had a hard time, as you cannot update/reinstall a system unless you boot it. I could boot only in safe mode, but you cannot reinstall/update from it (you can also do a clean install). Odd.
While doing more experiments I found a very handy memory check procedure. Well, the first time I run it it missed the error, but later executions helped me track the problem. What I find very odd, though, is that the memory test, which is executed at boot time in "DOS mode", gives you only a generic message that everything is OK or there is an error. In fact, it tells you the memory error report will be displayed as you boot the operating system as log into your account. However, with the system crashing on login, I could not get to see the report. I think this is a very naive approach: in case of system errors a low level / DOS or file based complete reporting would do better. Also, when I finally got to see the error report, it says only that there was a memory error, with no extra details.
Overall, even if I got quite upset during the process (my fault was not to fully trust Vista!) I have to say the OS is more robust and has a number of failure protection and restoration mechanism not seen before. On the other hand, they seem to over-trust themselves, as low level error messages after login, no way to update corrupted system libraries, and no way to update the OS until after a correct boot and login can prevent you from using the system in case of a bad crash. Like the one I had.
6 Comments
Hardware Failures and Windows Vista
I had similar problems with XP that also turned out to be becasue of faulty memory. It started with XP bluscreening once or twice a week and I assumed, as you, that it was because of faulty drivers. But after some time I had BSODs more or less every day and I decided to track down what it was. What finally showed me the problem was memtest86, you burn it as a bootable CD and it runs totally selfcontained in a DOS like environment. It can be found and downloaded for free here: http://www.memtest86.com/ I think MS have a similar utility that is burned as a bootable CD so I'm not sure what you used.Comment by PeterS on March 7, 11:17
Hardware Failures and Windows Vista
Mark and Peter, I used the internal memory test of Vista. I activated it from the Admin Console once and from the install disk another time. I didn't know about the TAB... However, the reported information is very limited and displayed after you login. This seems odd to me. In case of an error it should stop and show some details...Comment by Marco Cantù [http://www.marcocantu.com] on March 7, 17:57
Hardware Failures and Windows Vista
I've been trying out Vista in a WMWare virtual machine, running on an XP Pro host. It works pretty well, and is easy to play around with, since you can just make copies of the VM. I did notice that the fan is pretty much going flat out all the time, audio is poor, even with the latest driver (seems a pretty common complaint), and for some reason the VM doesn't recognise the native resolution of my screen. I'm not sure if this latter is a Vista or VMWare problem (or a bit of both). The VM is setup to use 1G of RAM (I have 2G of physical memory), and 20G of disk space. Performance is pretty good. I haven't heard the same said of Vista on VirtualPC :-)Comment by Jim Cooper [http://www.tabdee.ltd.uk] on March 7, 17:59
Hardware Failures and Windows Vista
I also had problems on a Windows XP install crashing with random stop codes. The culprit turned out to be a faulty Kingston module (actually two, because the module the seller replaced for me was also faulty!), which only Windows Memory Diagnostic, from Microsoft, reported correctly as being defective. The modules were good according to Memtest86. I never used the built-in diagnostic tool from Windows Vista, though, but the ones above do give you a thorough report as they are running.Comment by Romulo A. Ceccon on March 7, 22:25
Hardware Failures and Windows Vista
MemTest86+ is memory test when you are diagnosing memory faults. Try leaving it running 24 hours and it will sniff out any faults you have and if that doesn't find it you can always do a more thorough scan by changing the options on it.Comment by Alex Gregory [http://www.delphifusion.com] on April 29, 20:16
Post Your Comment
Click here for posting your feedback to this blog.
There are currently 0 pending (unapproved) messages.

Hardware Failures and Windows Vista
Comment by Mark Robinson [http://www.dundeemedia.com] on March 7, 11:05