Hi -
All summer, I've had problems with my win2k pc (w/2 gigs ram, asus m/b) rebooting and/or locking up. I'm hoping one of you may have a suggestion for how to troubleshoot and fix it?
I get everything from IRQL bsods to plain lock-ups, usually when launching a new app, or closing one, or in the middle of a Vegas render, which is frustrating.
It's probably a matter of, I have so many dang programs installed, there's a driver conflict somewhere. Challenge is finding and fixing the bugger. I get at least 2-3 lockups requiring reboot every day. frustrating!
Now I could use verifier.exe to troubleshoot them individually, or in small groups, but it would take forever, eg putting suspect drivers in pool tracking status and seeing which ones have problems... plus the issue of verifier bsodding on reboot and needing to modify the registry to re-enable access etc.. seems like a big headache.
I use a lot of anti-v /anti-spyware programs, so it's probably not a virus/trojan (I use norton, zonealarm, adaware, pestpatrol, webroot and many others), and check the registry windows/run keys and process checkers, and nothing looks out of place.
Any suggestions? I think it's just, I have a lot of stuff running at once, and one driver somewhere corrupts the memory pool over time and causes reboots/hangs, and not sure how to fix it. That's the problem with installing so much a/v related software; something has a conflict and causes problems.
I'd sure appreciate any tips -- thanks all,
Ken
All summer, I've had problems with my win2k pc (w/2 gigs ram, asus m/b) rebooting and/or locking up. I'm hoping one of you may have a suggestion for how to troubleshoot and fix it?
I get everything from IRQL bsods to plain lock-ups, usually when launching a new app, or closing one, or in the middle of a Vegas render, which is frustrating.
It's probably a matter of, I have so many dang programs installed, there's a driver conflict somewhere. Challenge is finding and fixing the bugger. I get at least 2-3 lockups requiring reboot every day. frustrating!
Now I could use verifier.exe to troubleshoot them individually, or in small groups, but it would take forever, eg putting suspect drivers in pool tracking status and seeing which ones have problems... plus the issue of verifier bsodding on reboot and needing to modify the registry to re-enable access etc.. seems like a big headache.
I use a lot of anti-v /anti-spyware programs, so it's probably not a virus/trojan (I use norton, zonealarm, adaware, pestpatrol, webroot and many others), and check the registry windows/run keys and process checkers, and nothing looks out of place.
Any suggestions? I think it's just, I have a lot of stuff running at once, and one driver somewhere corrupts the memory pool over time and causes reboots/hangs, and not sure how to fix it. That's the problem with installing so much a/v related software; something has a conflict and causes problems.
I'd sure appreciate any tips -- thanks all,
Ken