Josh8315 Suspended 26780 Posts user info edit post |
what causes it? how do you fix it when it seems to be happening once a day or so? 11/10/2005 7:15:47 PM |
qntmfred retired 40812 Posts user info edit post |
depends on which flavor of blue you're getting 11/10/2005 7:35:32 PM |
Shaggy All American 17820 Posts user info edit post |
probably a hardware issue.
Check your ram. 11/10/2005 7:43:51 PM |
eraser All American 6733 Posts user info edit post |
^ Yep.
Overheating is a very common reason for the BSOD.
Find out which module is causing the BSOD. If the computer is resetting before you can read it then:
Control Panel System CP Advanced tab Startup and Recovery settings button Deselect the 'Automatically Restart on failure' option 11/10/2005 8:04:47 PM |
Charybdisjim All American 5486 Posts user info edit post |
you could also run a memory test program of some sort. it should tell you which module is bad if one is bad at all. if it crashes during the program, try it with only one stick of ram in at a time. if you only have one module of ram... then you probably have a bad module.
http://oca.microsoft.com/en/windiag.asp
there's one from microsoft, never used it, but if you google "memory test" you'll find a couple free ones.
[Edited on November 10, 2005 at 8:17 PM. Reason : ] 11/10/2005 8:16:57 PM |
Josh8315 Suspended 26780 Posts user info edit post |
^^ill do that. so i should write down that code and then google it or call my dell people?
overheating is plausible. the case has good cooling, but theres some dust, and it stays on 24 7.
thnx.
^will do.
[Edited on November 10, 2005 at 8:18 PM. Reason : -] 11/10/2005 8:18:11 PM |
eraser All American 6733 Posts user info edit post |
The BSOD will usually identify which module caused the fault.
The difficulty of solving the problem will depend on what it says. Sometimes you will get specific driver name or DLL associated with a certian driver and updating the driver or removing a certian device will fix it. (Disabling Hyperthreading on some machines solves mystery crashes too.)
Sometimes it is much more complicated but let us know what you find out - the only way to know is to make a note of what is causing it to fuck up.
In this example, the second line is key - it tells the nature of the error.
[Edited on November 10, 2005 at 8:28 PM. Reason : visual aid] 11/10/2005 8:25:40 PM |
jahosephat All American 3130 Posts user info edit post |
I had the same problem a lot with my IBM...but it was happening multiple times a day 11/11/2005 12:28:22 AM |
Petschska All American 1182 Posts user info edit post |
yeah let us know the error that is in all caps. I was having BSODs the past couple days, but I think I fixed it now. Stupid nForce drivers. 11/11/2005 8:57:51 AM |