Please give me a hammer!

[ryanbatc]

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:

[Guest Kosta]

I feel you Ryan, I really do. I have no real advice for you though... something IS wrong. I'd type on GPU, DX and GPU drivers.But seriously - when such things start happening, I usually do one thing: format c. Start from scratch.

[virtualstuff]

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:

It can be frustrating to say the least but BSOD are most of the times 99% hardware related (faulty hardware or bios settings (OC etc...))...Do you have more info, for example in the real world at server level or a simple desktop you always start with the output of log files..Happy to have a look ;-).Cheers,

[Guest jahman]

I would start with a repair of Windows (easy to do) and of course no OC at all.Then check start-up logs.Then memtest.Updating hardware drivers/BIOS from your MB vendor can also help.Ideally a low-wattage standard video card to avoid straining a marginal PSU.Then it gets messy: Isolating PSU/MB/CPU errors from each other is via component switch and re-try.Best done with the assistance of your local PC repair shop with the necessary parts (unless you have a sceond PC you can cannibalize.)Cheers,- jahman.

[ryanbatc]

Do you have more info, for example in the real world at server level or a simple desktop you always start with the output of log files..Happy to have a look ;-).

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.

I would start with a repair of Window (easy to do) and of course no OC at all.Then check start-up logs.Then memtest.Ideally a low-wattage standard video card to avoid straining a marginal PSU.Then it gets messy: Isolating PSU/MB/CPU errors from each other is via comonent switch and re-try.Best done with the assistance of your local PC repair shop with the necessary parts (unless you have a sceond PC you can cannibalize.)

I've done most of those things actually. I logged my initial bios settings when I started to build, then OCed.I've memtested my ram, stress tested my PC with stock settings for 12+ hrs, updated all my drivers, there are no exclamation points in my Device manager.I don't have a local PC shop (I can't think of one in Duluth) nor do I have the money (or time - brand new baby!) to buy different parts and try them. I mean how would something faulty on say the mobo create ntdll.dll errors in Windows?

[dazz]

Try Blue Screen Viewer. Maybe there's some clue in the crash dumpsYou did pass memtest already didn't you?

[ryanbatc]

Yeah I ran multiple passes on separate and together sticks for a few hrs.

[cmeeks]

All I'm saying is that Sandy Bridge has been very finicky with memory. That would be my first guess. Don't really know where I would go after that. Perhaps mobo?

[alainneedle1]

If it was me the first thing I'll do is to take the mem. stick out and reinstall them, after that try SuperPi at 32M and if you pass the test chances are (not 100%) that your mem is OK, second I'll try OCCT for 2 hours, third thing would be Memtest. with at least 5 pass (I think you did that already. If after all of that everything is OK I'll be looking at the PSU, I know it's a pain in the butt to try another one but what you need to do is to eliminate one thing at the time.EDIT: read my other post below.

[dazz]

Yeah I ran multiple passes on separate and together sticks for a few hrs.

so it only crashes in FSX? also at your former higher overclock?

[alainneedle1]

Your system may be very stable since you passed all test with flying colors BUT may not be with FSX, I had a similar problem once, my system was very stable with OCCT passed memtest and all kind of test but unstable with FSX, after raising my core voltage one or two notch FSX was stable.Remember that FSX as a mind of his own, raise the core voltage one notch and fly, if you get BSOD again raise it another notch.Also make sure your rams are set to at the rated voltage, if it's 1.65V keep them there or one notch over and don't worry on paper they can go higher then 1.65v but try the core voltage first.

[Chaos81]

Your system may be very stable since you passed all test with flying colors BUT may not be with FSX, I had a similar problem once, my system was very stable with OCCT passed memtest and all kind of test but unstable with FSX, after raising my core voltage one or two notch FSX was stable.

Yeah, I wouldn't be surprised if he's experiencing the same thing you did. If I remember correctly [H]ard|OCP had a similar issue when they received their SB chips. I believe they said their system would run Prim95 just fine, but gaming would cause a BSOD. Can't remember if they had a solution for it, though.

[ryanbatc]

Yeah I have oddball memory... 1866mhz - while most people recommend 1600. Definitely could be a factor.I think I'm going to have to pull the thing out from under my desk, and test on my bar downstairs where I can access the components with ease. The way my desk is setup there's no way I can easily access the RAM, and swap sticks, much less do anything else with the parts. But I'd still want to run FSX for testing because that's where all my errors occur.I think what I'd like to do is reset everything, reset CMOS, reinstall everything. Even though it would be a major PITA, I think it could help. After I get everything installed I could run memtest, OCCT/P95 on a very stock system and go from there.Ugh

Yeah, I wouldn't be surprised if he's experiencing the same thing you did. If I remember correctly [H]ard|OCP had a similar issue when they received their SB chips. I believe they said their system would run Prim95 just fine, but gaming would cause a BSOD. Can't remember if they had a solution for it, though.

With this though - I can run Portal2 and Half life 2 just fine... in fact I've been playing through HL2 - and I'll play it for a few hours at a time. I've never had a CTD or error or anything while playing that.I've found the article FWIWhttp://www.hardocp.com/article/2011/01/03/intel_sandy_bridge_2600k_2500k_processors_review/2Interesting because this is what I'm noticing with FSX. But I can run 3dMark11 demo fine.

[Guest jahman]

No PC repair in Duluth? You gotta be kidding...After disconnecting and reconnecting all tour cables, CPU, RAM sticks, Video card etc., definitely the cheapest alternative (especially if you include the cost of your time and particularly if it means not tending to the needs of your baby, and I admit at first I thought you were referring to your gaming PC! :Big Grin: ), is to head for a repair store (or call the guy to your home and tell him what he needs to bring along).Me, I built my PC and it wouldn't boot. Since I had no other hardware-compatible PC to try the components with, I headed for a PC repairer. First thing he did was remove the Video card and replace it with a regular card. Bingo! The PC booted, I knew the video card was faulty, I returned it, got a new one, installed it and have been simming since. End of styory.Cheers,- jahman.

[alainneedle1]

Ryan, with all due respect you have to get something in your head FSX is like no other game, I was able to play all my games including Crysis 2 without problems, PC stable as hell but with FSX I was getting BSOD, raise the core voltage one notch or two, it WILL NOT hurt anything and you may get your problem fixed.This is the best thing to do before reinstalling everything or "######ing" about having to disconect all your hardware.