|I was running on my Latitude D630 that I've had for a couple of years just fine until...|
a few weeks ago I allowed WinBLOWs (XP Pro, SP3) to do an update. (I have my system set so that it notifies, but doesn't automatically update because when I'm running some heavy scientific program I can't afford for it to slow down... I update later.) Anyway, after I allowed the update, BSOD. It started with the NMI parity error, system halt, but quickly progressed to the nv4_disp error. The screen, which has always been flawless, started to display crap as well... After putting up with this and trying to debug it for a couple of weeks, I ended up going back about 3 weeks to a known good restore point (not just known good to windows, but also to a time when I knew it was running correctly). I backed out all of the updates after that and... been running perfectly for days now. I don't think this is a hardware problem (at least not for me). It strongly appears to be some incompetent moron at MS that has released bad code that corrupts something. All of my programs were working fine, then the only change was allowing the MS Win-XP updates, then nothing worked at all (for more that a little bit of time), then backed out the updates, now everything works fine. The only difference is the Win-XP updates. I'm ready to jump the MS ship and go to linux.