Viz Vista by Ed Tittel

In writing about my trials and tribulations with Windows Vista on my production PC over the summer, I summarized my situation in a blog entitled "Time for a new motherboard?" on September 20. By the beginning of October things with the system had quieted down enough, thanks to switching to a single-vendor security solution (PC Tools Spyware Doctor with Antivirus, plus the PC Tools Firewall, and their ThreatFire behavioral malware blocker) and making some other software and configurations changes, that I thought I had the hiccups behing me. I was down to random problems once a week, and went three whole weeks without a single BSOD.

I've been using Spyware Doctor to handle spyware on my machine for over two years now, with great success in handling spyware. In the past three months, I have switched to PC Tools Spyware Doctor with AntiVirus thanks to issues documented in my story "Best-of-Breed Apps Aren't Always Best for Vista" --namely, incompatibilities between AVG AntiVirus 8.0 and Spyware Doctor 6.0 that kept causing blue screens on my primary production machine.

In the past couple of months, I 've been grappling with graphics stability issues. Mostly, this has meant driver restarts where you get a message that reads something like "Display driver stopped responding and has recovered." Occasionally, this has involved a BSOD that mentions the Nvidia driver files nvlddmkm.dll or nvlddmkm.sys. When it happens, it seldom occurs more than twice a week. I keep checking the Nvidia driver download page, grabbing new drivers as they become available (including occasional betas), and hoping for the best.

The second Tuesday of every month is also known as "Patch Tuesday," because that's the day when Microsoft normally releases its security updates, along with other patches and fixes for its various Windows operating systems, applications, and so forth. Yesterday was the second Tuesday in September, and Windows Update proffered 10 items, most of which are described in the Security Bulletin for that month.Here, I'm going to focus in on one non-security update entitled "Update for Windows Vista (KB955302)".

OK, so I'm finally starting to relax a little bit. After six weeks of intermittent crashes and daily blue-screens, I've now gone four days on my production Vista machine without a major hiccup. I've still had a few minor problems, as I'll soon report, but it now seems somewhat safe to say that the system is reasonably stable and appears inclined to stay that way. I have one word to comment on this state of affairs: "Hooray!"

My production Vista machine is still acting screwy. When I leave it running all night, as I usually do, to let it run automatic updates for Windows itself, anti-virus and anti-spyware software, and to conduct all kinds of automated housekeeping tasks (disk defrag, file system cleanup, and so forth), this PC hangs every night. Alas, I get no entries in the Windows event logs to tell me what's causing the problem and I still haven't been able to pinpoint a definite cause. But when I leave the machine alone for two hours or more, then sit back down to get back to work, the GUI essentially quits responding to user input, and I have to resort to extreme measures to get things working properly again.

In digging further into my BSOD from Thursday, August 7, using the Windows Debugger I observed that the ultimate cause was a module named pctsSvc.exe (see attached screenshot below). A quick process lookup informs me that this is part of PC Tools Spyware Doctor runtime environment. Additional research on Windows crashes related to this module indicates that a remove/reinstall maneuver often addresses the problem (see this PC Tools forum thread for more info).

If you're been followiing my travails with my primary production system lately, you already know that I've been struggling to fix mysterious hangs and occasional bluescreens since the third week of July. On Wednesday, one of the two drives in my system drive mirror crashed. I not only replaced both of those drives, I also went ahead, bit the bullet, and did a clean reinstall of Vista Ultimate on that machine. The PC kept running properly through the night for the first time since my troubles began, so I got up the next morning to find a system that still responded to my attempts to log in (previously, leaving the machine alone for more than 2-3 hours would cause the GUI to freeze, and the Explorer interface to become inaccessible).

If you've been reading my blogs lately, you'll know I've been battling mightily with some vexing and puzzling stability problems on my primary production PC. In the past two weeks, I've tried nearly everything I can think of to bring this problem under control. My failure to find a convincing resolution is forcing me to plan for the unthinkable last ditch for Vista system repair: back everything up, blow away the system drive, then reinstall Vista and all my applications. Ouch!

OK, I have to start this blog with a confession: I’m an inveterate system tinkerer, and am always looking for something better for my system (if not for something rated as the best of its kind). For example, this approach has led me to skip using a good all-around security suite in favor of picking the best elements of each kind by itself (anti-virus, anti-spyware, firewall, anti-spam, rootkit detector, intrusion detection/prevention, system file and state monitoring, and so forth).