Re: Troubleshooting an XP BSOD
Borgholio <[email protected]>
| Newsgroups | gmane.mail.spam.spamcop.geeks |
|---|---|
| Organization | SpamCop |
| Message-ID | <[email protected]> |
Frog Prince wrote: > "Borgholio" <[email protected]> wrote in message > news:[email protected]... > | Porpoise wrote: > | > > | > "Borgholio" <[email protected]> wrote in message > | > news:[email protected]... > | > > | >> Porpoise wrote: > | >> > | >>> > | >>> > | >>> It's the invasion of the ......................................... > | >>> COMPUTER SNATCHERS!!!!!............ > | >> > | >> > | >> Sure feels like it. :) I'm thinking it's some program that's > | >> rebooting the system. I have Spybod S&D running at 4 am, and AVG > | >> auto-updates at about the same time. It could be that either of them > | >> is rebooting the system after it updates itself. I've changed the AVG > | >> update time to keep a better eye on it. As for the error codes in > | >> event log, I'm thinking it's just re-logging crashes that happened > | >> some time back, as the error codes are always identical. > | > > | > > | > The error codes could be identical if it's the same error each time. I > | > had problems previously with some software clashing with my TV tuner, > | > taking the system resources to 90+% and causing the TV software to crash > | > (but leaving the sound going in the background!). It took me a little > | > while to discover it was F-secure causing the problem (fssm32.exe). > | > Since converting to ZoneLabs the problem has not recurred. > | > | I'm thinking it's something automatic happening at around 4am....it always > | reboots around that time. > > Change the system clock to reflect 4AM in your time say 10 AM and watch what > happens. > > No need...just spontaneously rebooted on me. I'm changing audio drivers AGAIN....