New PC - Occasional blue screen

[Katana1000S]

Its been mentioned already, but I'd download Memtest and run that, if that shows errors you are on the right track, the symptoms you are experiencing are often down to bad memory (that can show fine in the BIOS) for sure all the other stuff is applicable too, but not necessarily the problem, give Memtest a go is my advice.

[NedLynch]

What MajorBoris said.

And reading through all this, what processor do you have?
In one post I read Phenom II x6?
If it is a quadcore right out of the box pressintg that core unlocker should not have been necessary and all four cores should have been detected.

And get yourself a case with proper connections for power and reset and so on, seriously, doesn't have to be anything expensive, my first case was $40.00. Just get rid of that HP thingamadingdong.

And you wrote the psu is new and 680 watts, it would be helpful to know the brand name, especially if you have enough amps on the 12 volt rail to properly support your video card.

I know all the things people wrote here are a lot to sift through, but if you spent all that money on new components it is very well worth it. However I would definitely start with a "normal" connection to the power button and after that cecking the specs of your psu, while making sure, as you certainly have, that all components are properly seated.

After that I would check the bios version and then check on Asus' website if your processor is in the supported list for your mobo and what bios version is the earliest that supports that processor. On the motherboard support cd you should find a utility called AsusUpdate, you can use that to update the bios easily under windows environment as well as verify your current bios version, easy peasy.

Good luck and let us know if you are faring better with your new build.

[5./JG27.Farber]

Ok just had the first BSOD in 3 days...

Damn! I had reseated the ram and "unlocked" the cores... Why they need unlocking is still a f&^*ing mystery to me.

Raggs, found out what my error code where. I'll follow his advice and see if that helps, but alsmost everyone is pointing to a bad stick of ramm... B$%^&teds! Why do they have to display them in the fecking MoBO? Feck!

[5./JG27.Farber]

Bah, another BSOD.

Ill have to work out how to run this memtest then take the ramm back. They will probly want the whole board back then... Then Ill be back to reinstalling OS and wiping my HD again...

[Wolf_Rider]

are you running Sandforce driven SSD's?

[5./JG27.Farber]

No wolf rider.

OK I took one stick of ramm out, PC booted ok. So I put the other stick in on its on and got loads of errors on start up...

So I took the ram back to the shop and they exchanged it. Came home, put the new ramm in with the "good" old one and it BSOD'd before it even booted.

Took it out, booted...

I think my OS might now be corrupt so I guess I will once again have to format the HD

[5./JG27.Farber]

Its working like a charm now. New ram and not one problem since!

Thanks to everyone - especially Raggz who decoded the error codes for me!

Cheers guys!