BSODs some thoughts.

[Roger]

Started getting BSODs (Blue Screens Of Death) a couple of days ago when loading or sometimes after loading FsX. Occasionally I got them whilst booting up with the inevitable bios message "Overclocking hasn't worked...".<?xml:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" /><o></o>
So to work.<o></o>
For reference here are my system specs<o></o>
SYSTEM :
OS:Vista Home premium 32 bit (labotomised).
DX versionx9c and Dx10.
Processor:Q6600 (SLACR) processor overclocked to 3.3 gHz with Zalman cpu fan.
Motherboard:Asus Maximus Extreme.
RAM:4096 mb DDR3 1.6 gHz.
Video Card:GF8800GTX core clock overclocked to 612 mHz. Memory clock to 1000 mHz.
Monitor/Resolution: SyncMaster 920N LCD. 1280 x 1024 (32 bit 60Hz)
Sound: SoundMax Blackhawk (AMD).
<o></o>
1. Removed overclocking (I have had my 6600 at 3.3 gig for over a year without problems). Still BSOD running FsX<o></o>
<o></o>
2. Removed 2 recently added software programs. Still BSOD running FsX<o></o>
<o></o>
3. Spend a day changing my video and audio card drivers to various other versions. Still BSOD running FsX<o></o>
<o></o>
4. Build a new FsX Cfg. Still BSOD running FsX<o></o>
<o></o>
5. Removed several recently added FsX addons. Still BSOD running FsX<o></o>
<o></o>
6. Considered reinstall of <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-comffice:smarttags" /><st1lace w:st="on">Vista</st1lace> and FsX. Thought better of it and retired to a darkened room with bottle of drinkin' whisky.<o></o>
<o></o>
7. Got the BSOD long enough to read some detail "Page fault found in non paged area" Googled it. Problem likely to be in memory (ram) or other hardware fault in anything in my pc.

8. More time in darkened room considering the cost of replacing the Asus Maximus Extreme mobo.

9. Flashed latest bios (dead easy on the Maximus with a pen drive). Seemed to help a little.

10. More Googling..."Check all boards are seated correctly, especially ram".

11. Did it.

Story ends here. Just lifting all pcie and ram boards out then reseating them did the job.

Phew!! (these are all for me..go and get your own)
<o></o>

 

[kilo delta]

Set the bios settings to default and run memtest in order to seek out any issues with the Ram. Are you running 4 sticks of 1gb or 2x 2gb

modules?

Edit.......oops just seen that you've sorted out the problem

 

[Roger]

Set the bios settings to default and run memtest in order to seek out any issues with the Ram. Are you running 4 sticks of 1gb or 2x 2gb modules?

Yes, 2 x 2gb but as I said in the last few lines, a new bios and a reseating all the boards sorted the problem

Cheers

 

[kilo delta]

NP, Rog, glad you got it sorted.........hope you enjoyed your whiskey (malt?? ) anyhow! :ernae:

 

[Roger]

NP, Rog, glad you got it sorted.........hope you enjoyed your whiskey (malt?? ) anyhow! :ernae:

Naw...saved the malt for special occasions (like my b'day:mixedsmi This is just the local supermarket's budget/paintstripper:isadizzy:

 

[Nick C]

Odly, I got that overclocking message on bootup yesterday Roger, I may just check the seating of mine too as I haven't overclocked this machine!

 

[ibl19108]

Usually, BSoDs are a hardware related problem. Something not installed properly or something come loose or maybe a piece of hardware starting to fail. As I said, usually.

 

[Roger]

Usually, BSoDs are a hardware related problem. Something not installed properly or something come loose or maybe a piece of hardware starting to fail. As I said, usually.

Ha yes, that's the reason for penning this missive. It's sometimes something so basic as dirty contacts

 

[gigabyte]

Ha yes, that's the reason for penning this missive. It's sometimes something so basic as dirty contacts

Roger, I take care of about 80 computers at work (plus all the problems for the home systems of our users... I know goes with being a geek...lol I can't tell you how often I have had BSOD problems and eventually traced the issue back to one connection or another. Something we often never think of with computers, while there are few mechanical moving parts there is heat and that causes expansion and contraction when shut down and the system cools. This will eventually cause a bad connection somewhere and very often with memory modules, one of the first things I do now when I get a BSOD (that does not happen right after installing something) is yank the RAM, I bet this has saved me over 100 hours of trouble shooting the past year or so. It is often the simple things that we overlook in the beginning that are to blame... I can't complain a good many times I have grabbed a "problem child" computer, took it off to my "Bat Cave" fixed the problem and spent the next 2-3 hours undisturbed working on my pet project of the week...lol If they only knew

 

[CodyValkyrie]

Having built computers for over 10 years and getting my A+ cert, I have come across all sorts of nutzo things when it comes to what causes faults. I actually saw a computer post once, run up the hard drive and act completely normal (with the exception of NO visuals on the screen) because the voltage switch on the back was set incorrectly. Guess a cat or something got behind there.... Anyways, there is no end to the crazy stuff a computer will do... or won't.

 

[gera]

I open my PC at least twice a year, re-seat all boards including Ram and "clean" everything with a PC vacuum cleaner and have noticed better performance and longer life. We do this to 163 PC´s in the office as part of their maintenance and the techs agree its a good practice to avoid premature deaths and other PC ilness........heat and dust are mean.

 

[harleyman]

Glad to see you fixed her Roger.......And not sharring and shots too,...Boy Oh Boy....