× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Write down the hex code you get on the BSOD. Then go to
MSDN.microsoft.comand search on it. If no joy there, then just Google
it.

Most likely it is a driver or hardware problem. It is actually hard (but
not impossible) for a normal program to cause a BSOD.

I'd be very hesitant to just reinstall. I've never had to do that with NT4,
Win2K or XP. Reinstalling is sort of like fixing a splinter by chopping
your arm off! Yes, the splinter no longer causes you problems....but arms
are nice to have <g>
Bob
On Jan 28, 2008 1:00 PM, <pctech-request@xxxxxxxxxxxx> wrote:


I had an extremely stable Windows XP system (reboot only on Windows
Patch Tuesday for more than two years).

Went through a strange series of events involving a new PSU and
installing video driver to get a new video camera working (I can give
the details if that will help.) Now, the machine will Blue Screen
almost every day at apparently random moments, often overnight when it's
not being used. Rolled the display driver back, un-installed the
Firewire card, but still BSODs. Several different BSODs, too.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.