EggXpert

ok getting frequent BSOD is either one of three things. its either a heat problem, a memory problem, or a power problem.

first check the heat. download a program like SpeedFan and monitor the temps. if there high then buy a new CPU / GPU cooler. for a temporary fix take the side panel off of your comp and put a desktop fan or something pointing in there.

if it is not the heat, next check memory. run a Memtest86 , or switch memory with a friend or swap it with something if you can. if its faulty ram either RMA your current memory or just buy new ones.

if its not the memory or heat, its almost definitely the power. first make sure everything in your computer is properly connected to the power supply. also, if your plugged into a power strip it may not be letting your comp get full power, switch to a direct wall outlet. you can also buy a PSU tester here at newegg or im sure a place like bestbuy would have them also. you plug the connectors from the PSU into it and it reads the voltages . if you can find a friend or somewhere you can get a PSU with higher wattage that would be great so you can swap and see if its fixed. if you find it is power, you will have to buy one with a higher wattage. single rail PSUs are the most efficient and reliable.  most truly high end systems would only need a 700W power supply. 700W is more then enough for sli 8800GTs and 4g ram, 3.2ghz CPU, all of it. For an average system 550W is more then enough if its from a decent maker. some good PSU brands include OCZ, Antec and Corsair. if you check and find that the problem is not one of these, your most likely going to need a new MOBO, CPU, or HD. but 99% of the times BSOD/random freezes and shut downs occur its because of power, heat, or memory.

Edit: it can also be caused by bad drivers or an unstable CPU/GPU/RAM overclock. if you check your power, heat, and memory and your still getting problems make sure your video/chipset/audio drivers are up to date and lower your overclocks if you have them pushed to the limit. you can also run a stability test(Ntune has one for instance) and leave it running alone for atleast 30 minutes. if your computer hangs, freezes, restarts or shuts down then it is infact one of you components are either overclocked to an unstabe level or there damaged.

 

This is the first time I've seen a train of thought that long, in a long long time.

haha thank you. i hope it helps some people

kevin217:

keep this bumbed so its handy for people who need it. 

Would placing a sticky on it so it stays on top be better?  (think I'll space it out a bit too, cause that one huge paragraph is like huge )

yea if you can make it a sticky that would be great.

I recently built my first computer Phenom x4 9850BE, 2x2 Corsair dominator ram, 500gb HD, ATI hd3870 crossfired. I have had a lot of computer lock ups, randomly. I had my Bios settings set for 1066, and for my mobo the native was 800. I was so dumb, took me few weeks to find the problem :-/ hehe. Just set the volts up to 2.1 and fsb to 400. Was getting very frustrating trying to play Age of conan, and locking up every 30 minutes to an hour.

i play age of conan too lol. anyway is it fixed now?

Looks good but memtest should probably link to here. Just my opinion though as this is the most up to date version and the people will be directed to the latest version in the future.  Also HWMonitor usually works better for me as my board is hard to get readings of of and it still doesn't give correct voltage readings except for how far over or under they are, but it would tell me if my voltages were real low on a rail as the value would be negative instead of postive, just would not know which rail most boards I'm sure it would do well though.  If  they have Nvidia chipset then Ntune could be used and on newer AMD chipsets the the AOD utility could be used also and these provide lots of info to the user if they work/install correctly.  Also they can check manufacturer or the board as they usually provide a utility that will monitor the boards health from bios also.    

Also you may want to tell  people to diasable automatic restart so that they can read the complete BSOD message by right clicking my computer/  then selecting properties/ advanced/ startup and recovery and uncheck automatic restart.  And then google the 0X000000 number they get to see if it comes up memory related or with any helpful info.  Although my machine BSOD on an overclock the other day and is set to restart but don't think it did.  As I said though it was an overclock so???

Is a good idea for a sticky though. 

Nice write-up on the issue. Also one other thing that can create a BSOD is drivers from a NIC, Chipset, Video card, sound card ect.. Just uninstall Redownlaoding and install. and you are done.

 

 

 

natesuniverse

 

They will not need the whole 0X00000D hex number here is a shot way of doing it

 

In Google

 

0X0D

 

http://www.google.com/search?q=BSOD+0X0D&btnG=Search&hl=en&sa=2

 

 Personally I run into less heat, PSU, and driver issues.  Many BSODs I encounter are from failing hard drives.

To be thorough,

Heat
Bad Memory
Bad Driver
Power issues
Failing HD

PS:  Never thought about that little google trick applying to Stop errors. I'll definitly be using that

"natesuniverse

They will not need the whole 0X00000D hex number here is a shot way of doing it In Google 0X0D

http://www.google.com/search?q=BSOD+0X0D&btnG=Search&hl=en&sa=2"

 

Not sure I get it, as you get two totally different search results from 0x000000D and 0x0D.  If I type in a long version it sometimes takes me to what I need to know sometimes.  Sometimes not but letting me know something the BSOD is related to.  Like oh, thats a certain error ralating to this part of the system.  But hey, I'll give it a try next time.

Don't get 'em much lately unless running Winamp AVS which is most likely broken/old AVS code.  Is fairly CPU intensive though.  Really cool though with the newer monitors and fast CPUs.

natesuniverse:

"natesuniverse

They will not need the whole 0X00000D hex number here is a shot way of doing it In Google 0X0D

http://www.google.com/search?q=BSOD+0X0D&btnG=Search&hl=en&sa=2"

 

Not sure I get it, as you get two totally different search results from 0x000000D and 0x0D.  If I type in a long version it sometimes takes me to what I need to know sometimes.  Sometimes not but letting me know something the BSOD is related to.  Like oh, thats a certain error ralating to this part of the system.  But hey, I'll give it a try next time.

Don't get 'em much lately unless running Winamp AVS which is most likely broken/old AVS code.  Is fairly CPU intensive though.  Really cool though with the newer monitors and fast CPUs.

 

Here is a example

 0X0000000D1 or 0XD1   <--- the fist part that is needed do not put the parameters in after this hex.          

DRIVER_IRQI_NOT_LESS_OR_EQUAL  <---------------------------------- The second part that is also needed. This is causing the error to occur.

**** WXYZ.sys - Address F73120AE base at C00000000 DateStamp 36b072A3 < ---- The third section, 'driver information,' may contain vital info. If an actual driver file is associated with the blue screen, it will be listed here. or the person could put WXYZ.sys as well which is fine with me others might want the address base but not really necessary.

 

With out all three parts there really is nothing that we could go on. So it would look like this well at least I hope that some one would put it like this. I used WXYX.sys because I forgot the Nvidia one its nv****.sys cant remember the whole thing.

0X0000000D1 or 0XD1: DRIVER_IRQI_NOT_LESS_OR_EQUAL: WXYZ.sys <-- this will not work to the full extent because the driver wxyz.sys does not exist.

But if you run 0XD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL it does come up.

EDIT

Please make your own thread at this point do not hijack other threads. Thanks.