• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I have been reading quite a few posts about XP random reboots and.....

J

Joyride

Golden Member
Many people suggest turning off the auto reboot function so you can see the BSOD information

I am a total noob when it comes to that kinda stuff.

What do I do with the information the BSOD gives me? Are there some settings I can change according to the BSOD?

Help me understand my BSOD more and get it toned down or eliminated.

Thank you


This was locked here because it was in the wrong forum
 
Random reboots are almost never the fault of the OS.
In my experience ( in order of likelyhood) it is

1) Bad RAM
2) Power supply issues (not enough juice, or just a bad power supply)
3) Incompatible software.
4) Virus
 
I have the same prob , I have an athalon 1.3 and 2-256m strips of generic ram and a 300w power supply. Sometimes if I open that one extra program, the system reboots. I'm running ME. So how do I narrow it down?
 


<< Random reboots are almost never the fault of the OS.
In my experience ( in order of likelyhood) it is

1) Bad RAM
2) Power supply issues (not enough juice, or just a bad power supply)
3) Incompatible software.
4) Virus >>



It's got to be #3 here.

1.My crucial ram is only 6 months old (doubt its bad).
2.Just put in a 350w power supply since December
4.Running Norton Antivirus and scan and update once a week
 
1) Bad RAM
2) Power supply issues (not enough juice, or just a bad power supply)
3) Incompatible software.
4) Virus >>

Actually, #1 would be bad 3rd party drivers. And answering the original question, the blue screen info has a lot of techinical jargon in it, but it's basically the OS throwing it's hands up and saying 'I can't fix this' while trying to point out what it can't fix. Often the bsod will list the driver that causes it, which often times is the driver that did actually cause it (confusing eh?). You want to look for something like 'module xyz.sys caused an XXX to occur'. Go look and see if you can determine what xyz.sys is from (most .sys files are store in the windows\system32\drivers folder). Right cliking on it and hitting properties will often give you a clue to which manufactuer the driver is from. If you can get that far you may be in the home stretch, see if there are any updates from them over what your running and install them. (repeat as necceisary!)

Bill
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top