My computer have decided not to work. I have had big problems with random BSODs and I thought previously that it had to do with temperature. I then started to suspect that it was my HDD. It is old and have been along for a long time so I went out and bought a new one. Installed windows and the regular software stuff but no luck. BSOD returned. :sad: I then suspected my Soundblaster X-Fi (which I already have a hate relationship with since before) but that seemed ok. Now I have ripped out my SATA controller card and so far (fingers crossed) the computer haven't BSOD. :sideways:
So now I am donw to the options that I buy a new SATA controller card for about 40-50 Euros or a buy a new motherboard instead for roughly twice that price and get the SATA connections directly on the board.
Anyways, I will not be around on the servers until I get this mess sorted.
Good luck with the repairs Mats or ....
get a spinky new PC :)
GL and fingers crossed!
BTW, are you sure it's not the GraphicsCard?
My old 1 gave me loads of BSOD's.
Quote from: DuVeL;236748GL and fingers crossed!
BTW, are you sure it's not the GraphicsCard?
My old 1 gave me loads of BSOD's.
I have running on the same rig for almost 2 years now with the exact same setup. :g:
Now I have installed a new SATA controller card that is PCI instead of PCI-e and all the HDDs are up and running and still no BSODs. I noticed that the old controller card was loose in the socket so it could easily be moved. I think this is the reason for the problem.
Hopefully I will be back soon. Now I "only" have to install all the software again ...
Quote from: Dr Sadako;236772Now I have installed a new SATA controller card that is PCI instead of PCI-e and all the HDDs are up and running and still no BSODs. I noticed that the old controller card was loose in the socket so it could easily be moved. I think this is the reason for the problem.
Hopefully I will be back soon. Now I "only" have to install all the software again ...
How long interludes did you have between the BSoDs? Are they related to use, i.e. what happens if you just leave the PC running? And finally, did you use BSoD software to track the meaning of the crash?
Quote from: delanvital;236774did you use BSoD software
Yes. he's running Windows :roflmao:
Quote from: delanvital;236774How long interludes did you have between the BSoDs? Are they related to use, i.e. what happens if you just leave the PC running? And finally, did you use BSoD software to track the meaning of the crash?
It was random crashes. It could be while I was playing a game, browsing the internet, not using the computer, being in the BIOS, during windows startup. Then I could have days without any BSODs. Random in one word.
Quote from: BlueBall;236775Yes. he's running Windows :roflmao:
So whe have all BSODs:narnar:
Quote from: Dr Sadako;236783It was random crashes. It could be while I was playing a game, browsing the internet, not using the computer, being in the BIOS, during windows startup. Then I could have days without any BSODs. Random in one word.
I had something similar, BSoD at random with my old computer. Would strike at random, but around 30% of the time I booted into CS:S it would have a fit. (I suuspected my ram but could never proove it). There's nothing more annoying than thinking you've tracked down a problem but not being sure when you've fixed it.
Good Luck.
Quote from: BlueBall;236775Yes. he's running Windows :roflmao:
:roflmao:
I was thinking along the lines of enabling memory.dmp and then using fx. dumpchk to get the stop code. Then run the stop code by for example MSDN to check for a possible explanation. That is at least a hint to reaching a diagnose. Has helped me in the past to track down bad ram, which can be a real PITA (due to being random :rolleyes:)
Edit: One place to check codes is here fx
http://msdn.microsoft.com/en-us/library/ms789516.aspx
I had BSOD's on my old system which appeared at random, but i discovered (after re-install of windows, using different hdds cables etc etc), it was my RAM after running a RAM checker, I suggest you defo should look into this, i will try and find it again.
Edit : you could try 'memtest' http://hcidesign.com/memtest/download.html - although this was not the one i used IIRC
For mem testing http://www.memtest.org/ (http://www.memtest.org/) - memtest86+
A note for Asus motherboard users.
(for newer mobos with AI overclocking, like Asus P5K)
It seems that the AI overclocking function is ON by default. I displays as [Optimal] in BIOS settings. So it tryes to figure out itself some overclocked settings which doesn't crash immediately. However this doesn't mean it doesn't hang up in longer heavy use. This can still cause random BSODs with different error codes which doesn't point to any particular direction (like OC BSODs in general). You should check it to [standard] for non overclocked setup or if using OC I would recommend doing it manually.
So the BSODs have returned and are more evil than ever. I never manage to get into windows even.
I have had a look around on various forums and there seems to be an issue with having 4x1Gb internal memory and also Quad cores. There might be a solution to play around with voltages and such but the more I read the less inspired I become.
I am considering just taking out the mobo and replacing it with a new one that actually is Quad core ready from the start. So any suggestions on a mobo that should support this
Quad Q6600
4x1 Gb PC-6400
8800 GTX
5 sata drives
1 ide slot
Soundblaster X-fi Fatality
I have no interest in overclocking (unless it is idiot simple setup, no fuss, and working)
Doc "BSOD" Sadako
Quote from: Dr Sadako;237643So any suggestions on a mobo that should support this
Quad Q6600
4x1 Gb PC-6400
8800 GTX
5 sata drives
1 ide slot
Soundblaster X-fi Fatality
I have no interest in overclocking (unless it is idiot simple setup, no fuss, and working)
Doc "BSOD" Sadako
Any of the Gigabyte DQ6 series. I have the P35 DQ6 but I believe the X48 DQ6 is now available:
X48 (DDR2 version): http://uk.giga-byte.com/Products/Motherboard/Products_Overview.aspx?ProductID=2763
X48T (DDR3 version): http://uk.giga-byte.com/Products/Motherboard/Products_Overview.aspx?ProductID=2765
Any Gigabyte mboards that have T are DDR3
I'm using a Q6600 with 4GB of ram (2x2GB)
I've put it in a one of these (https://www.overclockers.co.uk/showproduct.php?prodid=MB-127-GI)
It lets you overclock easily. (Idiot simple, 3 steps...1, Run windows based overclocker set the scroll bars to the numbers you want, 2 Test it's stable using a program called Orthos and leaving for 20mins or more (if it crashes don't clock that high), 3 set the settings in your motherboard (if the settings stop the computer booting etc it will load the settings from the second bios automatically). I'd never overcocked before it really was that simple and now I'm on 3.33GHz.
The board has 8(i think)xSATA, supports DDR3 and 2, the DDR3 are 2 of the 6 slots so you've room for your 4 chips. It has an IDE slot.
Easy overclocking is failed overclocking! -.-
A lot of boards out there got issues running 4x1Gig sticks @ 6400.. you tried underclocking your ram a bit ?
Quote from: kregoron;237669Easy overclocking is failed overclocking! -.-
A lot of boards out there got issues running 4x1Gig sticks @ 6400.. you tried underclocking your ram a bit ?
To begin with I have no clue at clocking at all. I haven't touched the features in the bios setting and just run it at "auto". Now all of a sudden it has started to show issues.
I bought all components except the Q6600 (had an E6600 before) about 2 years ago. The Q6600 was added in January. I have run the system without any BSODs during that time and all of a sudden I get loads of them.
I could try underclocking them but to be honest I have no clue to where to start.
I was thinking of doing somehting much easier. Removing all memory capsules and adding them one by one.
Quote from: Dr Sadako;237671I was thinking of doing somehting much easier. Removing all memory capsules and adding them one by one.
I would be tempted to try them one at a time rather than adding them one by one.
Quote from: BlueBall;237672I would be tempted to try them one at a time rather than adding them one by one.
I agree with BB, try em one at a time, run memtest a bit, then try the next and memtest it... if that shows no errors, you could try installing a pair and memtesting em in pairs.. just to entirely eliminate the possiblity of a failing module..
When hardware grow old, (happens a lot faster tehn you chaps ;) ) components start to fail and they start having these weird ideas.. especially these days with high performance HW that runs at so high frequencies / temps.. 2 years is actaully often the average lifespan for loads of HW these days.. sadly.. :(
OK. I have removed all memory sticks now and only run on one. I manage to get into windows without BSOD and running a memtest now.
I got a bios startup message saying that seomthing about overvoltage (overclocking) didn't work. The memory shows up as PC5300 even though it is PC6400.
I will go through the memory stick one by one as suggested and see how it goes.
Could someone please explain this to me. On the memory i have it says it is 4-4-4-12. When I run Everest this is reported
5-5-5-12 @ 400MHz
4-4-4-13 @ 270MHz
In my bios setting I can enter the following
DRAM
-CAS Latency
-RAS Precharge
-RAS to CAS Delay
-RAS Activate to Precharge Delay
-Write Recovery Time
I suspect that my values are 4-4-4-12 but what should the last one be. Also why does Everest display other figures than what the standard should be? Should I go in manually and set this? It is on Auto now so I don't know the actual setting for the above.
Quote from: Dr Sadako;237706OK. I have removed all memory sticks now and only run on one. I manage to get into windows without BSOD and running a memtest now.
I got a bios startup message saying that seomthing about overvoltage (overclocking) didn't work. The memory shows up as PC5300 even though it is PC6400.
I will go through the memory stick one by one as suggested and see how it goes.
many of the faster memory sticks will not run faster unless they are given more than the 1.8V that the motherboard expects to give a memory stick. You may well have to give it 2.1V or even 2.2V (add 0.3 or 0.4V in BIOS) to make it run stable.
Quote from: BlueBall;237723many of the faster memory sticks will not run faster unless they are given more than the 1.8V that the motherboard expects to give a memory stick. You may well have to give it 2.1V or even 2.2V (add 0.3 or 0.4V in BIOS) to make it run stable.
According to Corsairs webpage they should be run at 2.1V. I have it in [Auto] atm but can of course set 2.1V if I want.
Quote from: Dr Sadako;237729According to Corsairs webpage they should be run at 2.1V. I have it in [Auto] atm but can of course set 2.1V if I want.
Try 2.1V (add 0.3V if the BIOS only gives you the option to add a voltage as opposed to picking the voltage you want) and leave all the other timings at auto (for now); that should prove stability.
I'll talk you through setting other timings if we get it running stable at the slower (auto) timings.
Quote from: BlueBall;237733Try 2.1V (add 0.3V if the BIOS only gives you the option to add a voltage as opposed to picking the voltage you want) and leave all the other timings at auto (for now); that should prove stability.
I'll talk you through setting other timings if we get it running stable at the slower (auto) timings.
Ok Thanks.
I have gone through all memory modules one by one and now running 2x1Gb test. Not a BSOD in sight so far. Will update the bios to 2.1V when I reboot and add more memory.
4x1Gb at 2.1V no BSOD so far.
Quote from: Dr Sadako;2377544x1Gb at 2.1V no BSOD so far.
Good news :)
Leave it like that for a few days just to be certain :)
Some more information for you
(http://www.lugnagatan.net/mats/temp/mem1.jpg)
(http://www.lugnagatan.net/mats/temp/mem2.jpg)
(http://www.lugnagatan.net/mats/temp/mem3.jpg)
If it helps. :)
A tricky problem nicely diagnosed :D good going you two! :D