Ugh... well the problem is I tried raising my vcore and I got more BSOD's with that. Remember my whole 4.5 GHz OCing thread?Imagine that... the power of google at my fingertips. It's duluth though... it's a small city - can never be too sure.On the bright side - I love my Corsair case!

Ugh... well the problem is I tried raising my vcore and I got more BSOD's with that. Remember my whole 4.5 GHz OCing thread?Imagine that... the power of google at my fingertips. It's duluth though... it's a small city - can never be too sure.On the bright side - I love my Corsair case!

So if I understand you correctly....your rig is stable at 4.0GHz after testing it and if you do not change anything else but just raising the core voltage a notch or two and you get more BSOD?

So if I understand you correctly....your rig is stable at 4.0GHz after testing it and if you do not change anything else but just raising the core voltage a notch or two and you get more BSOD?

Yep - it either freezes at the Windows splash screen (in that case I hit restart button), or loads windows, freezes in about 5 seconds, then proceeds with a BSOD.

Yep - it either freezes at the Windows splash screen (in that case I hit restart button), or loads windows, freezes in about 5 seconds, then proceeds with a BSOD.

Now that's a first for me.....my last resort will be to spray some holy water all over the rig...If all your settings are right I guess something is faulty somewhere....I can't help you more since I don't have a SB...PS: what about if you lower the core voltage one notch??

On the bright side - I love my Corsair case!

Haha, me too! Way to look at the bright side. As I said, I'm thinking mobo or ram. I wish I had more advice for you. Perhaps travel into town and get your rig tested? I don't see any other way around it other than weeks of RMA'ing parts one by one.

have you tried Blue Screen Viewer Ryan?

Yep - it either freezes at the Windows splash screen (in that case I hit restart button), or loads windows, freezes in about 5 seconds, then proceeds with a BSOD.

Oh yeah, I had that 3 times today morning when I turned it on. Though mine is working stable once in windows.That thing with boot freezing is known for P67. And it's not only limited to Asus boards.

weird, i am on a ud5 b3 4.7 1.365 and have not had any lock-ups, bsod's or anything weird as of yet. Loving the system. You can get it work Ryan, believe me you can, I had some troubles on my old ud4 b2 and this one initally, that would cause me not to boot with any pll over volt bios, this sounds like not appl to you as you are at 4. I did want to throw it out the window, but I got through it and now all ok. Much more stable for me than my x58, that thing was moody with freezes. What voltage are you on 4, stock auto or what?

So I can bash my PC to bits...I can't take it anymore... 3559 errors/warnings in only 2 months! Just today I got a BSOD (something about 0000006 DX - probably direct x related) while FSX was idle. I jsut started up the program, walked away for a few moments, and came back to a pretty BSOD. Then I run FSX again with the nvidia inspector monitor panel up and it CTD's with NTDLL.dll error - precious!If they made store bought PC's that would run FSX I'd buy one and replace it with this POS. What the heck is wrong with my systems? Is it:1) PSU2) Mobo3) RAM4) DX drivers5) GPU drivers6) other system drivers?Look how many combinations of doom there is!!It's not that hard to hook up the components. Everything has power, everything is connected to the mobo, no lose cables. Temps are very cool down here in the basement. How am I possibly to know what's wrong? I can't spend another 500 bucks getting new parts! ARGHHHHH :Black Eye:

Those errors usually point to windows attempt to automatically run some processes. If, for some reason, some of these processes have been switched off, you'll get errors and blue screen of death.The easy way is to go back to a clean system, which means a new windows installation.tc

Thanks but what are you asking for? I haven't logged this stuff but I had BSOD's even with stock settings, like after I put my computer together and then installed FSX. What drives me bonkers is that none of this is reproduce-able. For instance, I'm flying along right now in FSX with my usual payware planes. Nothing's happening. Maybe something will happen in the next hour, while I fly on FNO/vatsim... or perhaps nothing will happen like last night - 4 hrs straight in FSX, with zero issues.What do regular PC builders do when this stuff happens? Try new motherboards? Seems like a lot of work, considering that would require a fresh install of everything.. ugh.

Well Ryan in the real world we read log files to understand what is happening very convenient :-)For example every error is logged in the repository of a Win O/S hence you can even log even more if you want but only for trouble shooting..In general there are a lot events stored in that database repository :-).The beauty is you can save those log files or view them via start > programs > computer (right click) choose manage (this will open the CM console) or choose start and then run and type compmgmt.msc hit enterbrowser to event viewer and expand that one selected the fist one right click an choose save as (.evtx) Do this for all five of them starting with applications.Then you can share those for trouble shooting...Every BSOD gives a stop error (which is related to the event) next time just write it down on paper very helpful if you know where to look :-) As for memory on SB and P67 mobo make sure it's 1.5 volt...

have you tried Blue Screen Viewer Ryan?

I did download it but ironically have had no BSOD's to view. I also flew on vatsim, with my FPS intensive payware aircraft in FSX for about 4 hrs straight last night. No issues!Argh lol!

PS: what about if you lower the core voltage one notch??

I'll give that a try. I mean if it can't take 1.30v there seems to be an issue with the CPU - or maybe I got a dud :Worried:

Oh yeah, I had that 3 times today morning when I turned it on. Though mine is working stable once in windows.That thing with boot freezing is known for P67. And it's not only limited to Asus boards.

Really? Jeeese that's garbage QA if you ask me... *sigh*Maybe I'll have to have some PC store look at it.

Every BSOD gives a stop error (which is related to the event) next time just write it down on paper very helpful if you know where to look :-) As for memory on SB and P67 mobo make sure it's 1.5 volt...

Thanks Andre, I'll try to rememeber that next time. Though I'm confident it had a lot of 0's and ended in a 6. Something like 000x0000006 DX. My RAM does run at 1.5V - its corsair vengeance 9 10 9 27 1866MHz.

Ryan, you need to make sure your OS is setup to save individual reports for each crash:Start -> Right click on "Computer" -> Advanced System settings -> Startup & recovery, and set "Write debugging information" to "Small memory dump"

Maybe I'm a little late to the game, but I get the feeling Dazz actually knows computer stuff.

Speak of the devil...I was attempting to respond to Dazz's post but system just BSOD (no games running, basically idle with Chrome browser open), "Fatal Error" - usually doesn't mean anything good LOL!

This is what I found in google about that c000021a crash:http://support.micro....com/kb/156669/