MrGreen

Ok, I did that. But this will only make me read the next crash dump, right?EDIT: What I don't get though is, if one of the sticks are faulty shouldn't the memtest I did last night have come up with errors? Or does the healthy stick somehow "cover" for the bad one?

The folder is empty, dunno why.

Hmm, I just had a BSOD 0x000007A error while watching a video in VLC. I've tried searching for info about the BSOD code but I'm not finding much usuable info. An hour before I updated windows (quite a big update as I hadn't done it in about 3 months).Anyone know what causes that kind of BSOD?

Weird thing is, I just did a clean reinstall of FSX and so far (SP2 installed but nothing else) I'm able to start the sim, run a flight etc without any errors. If the memory was faulty you'd think the stresstests I did would've picked it up. I'll run an overnight blendtest tonight, my corsairs failed that with even a slight OC so if these are faulty hopefully it shows. If nothing shows up and FSX gets unstable I'll do a memtest on each stick.That should be enough, right?

Hi. This topic might be better put in the CTD section but as it also has to do with hardware i thought i'd post it here. If moderators want to move it, by all means :)I bought some new Ram from g.skill (8GB 2133 /9-11-10-28) after having low-on-memory issues with my earlier 4GB mushkin 1600CL6 and feeling a bit "ripped off" by the Corsair 2000Mhz CL9 only running 1866 and not 2133 which i had hoped.Right after the switch I had problems starting another game but that was easily fixed by reinstalling the client for it. After starting FSX I got a APPCRASH fatal error when opening the free flight section. The 3D screen of the default plane immediately freezes when opening that screen."Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61355.0 Application Timestamp: 4643ee0a Fault Module Name: d3d9.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4b926eb5 Exception Code: c0000005 Exception Offset: 000013cb OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1053Additional information about the problem: LCID: 1053 FSX was working fine before, unless my memory blacked out and I did some switch inbetween my last working flight and the RAM switch; which i seriously doubt.I have since done 3 stresstests:Intel burntest on maximum ram - completed 5 (default number) passes successfullyOvernight (7h or so) Memtest 4.0a completed without errorsPrime95 blendtest completed 3h without errors or warnings.Can it really be the memory that is faulty or has my fsx install been corrupted somehow? I have windows 7 update on manual download and install.Is it possible to fix this error without having to reinstall FSX/reformat the computer? (i heard the d3d9.dll error is tricky to cure without a full reformat)Any advice is appreciated!

I'm not! I get to T/D and it doesn't descend! Unless of course i set the altitude bug to the desired altitude at the next watpoint. You guys are acting like I have to be making mistakes, I'm not!

I think you just answered your own question there lol. To make vnav descend on the calculated vertical path you need to have a lower altitude set in the MCP altitude window.

About the RAM limiting your OC, I think it's worth testing just to be sure, but it's not so likely in SB as in previous generations where RAM often was the limiting factor.Offset is used to enable C1E & SpeedStep, the power saving modes that slow down the CPU and lower the Vcore when it's idleWith LLC at Ultra High you should have no Vdroop, the lower Vcore you see is probably C1E kicking in. it will adjust Vcore as a function of CPU load. The higher the load, the higher the Vcore

Thanks Dario. The dropping vcore happens while stresstesting at full load, with manual vcore, and its steady at idle. I thought this was because of vdroop? Anyway, I tried OC:ing my RAM to the speeds and timings I wrote earlier, but I recieved an error in memtest at the second pass. VDIMM = 1.65How can I solve this? Thanks in advance

The only boards that have ever failed for myself or my family are Gigabyte boards, I wont touch them because of this.

I just read an article on a swedish website where they had a graph with RMA statistics from a french website (lol). According to this graph Gigabyte motherboards actually have the lowest percentage of RMA's. http://www.sweclockers.com/nyhet/13859-fransk-datorsajt-publicerar-rma-statistik-for-april-manad Link is in swedish but the graphs are pretty easy to understand, lower is better.A link to the original website is at the bottom of the page. Moderkort = MotherboardGrafikkort = Graphics card. Google translated link to the original website.

You could run them at 1866MHz, or loosen the timings, or try pumping your Vdimm a little bit and see if that helps. Is your RAM rated at 1.5V?

I have the exact same RAM as Cmeeks so I was thinking of trying to run them at the same speed and timing as he is: 2133 (9-11-10-28-1T). Stock settings are 2000 (9-10-9-27-2T). Rated at 1.65. EDIT: One more question, right now I have my vcore at a manual 1.405v but I see a lot of guys on here using offset. What is the reason for this? Could it be more stable in regards to my idle bsod (I saw Cmeeks had a similar problem and upped his offset to + 0.04)? When I tried using offset it seemed to go higher than manual even at a low +0.025 (LLC Ultra high). With + 0.025 it went over 1.410 and with + 0.04 sometimes went up to 1.425 and temps seemed higher than with manual, I'm guessing because with vdroop my vcore sometimes goes down to 1.38 in IBT.

Lol. I couldn't resist trying the tips you gave before so I went into my bios, raised multi to 48, VCCIO to 1.18-something (two notches up from standard), Vcore to 1.405, PLL Overvoltage: Enabled and have just completed 5 runs of IBT on max. With temps never reaching 80c, but close. But how do I stresstest the CPU for these random startup/idle bsod's? Last time I had run Prime95 for eleven hours and IBT, and also Hyperpi 32M, all those were successful, but my comp still crashed on startup 2 days after. EDIT: If my RAM are the culprit, does that mean I won't be able to run them at rated or 2133mhz-speeds? Kinda sucks running OC-ram at 1333/1600mhz.

Don't worry, it's extremely unlikely that it's degrading already.Try upping your Vccio (max 1.2V)or downclocking your RAM to rule out memory being the limiting factor at those speeds But I would settle for 4.7GHz at that Vcore TBH. Not worth the hassle for just another 100MHz

2% decrease in performance or so, right? I think I'll stay with 4.7Ghz for now. With HT on 1.370 was rock stable, with HT off I can probably decrease the volt a little if I wanted to get the lowest possible heat. Btw, any reason for me to turn on HT again, now that I'm at 4.7?

Agreed. For FSX, HT disabled.And at those clocks, CPU PLL Overvoltage, Enabled

I was able to reach 4.8 at 1.400v 11h prime95 blend stable, IBT stable. No crashes while running applications, playing games etc. PLL Overvolt was disabled though, didn't see your reply before now Dario.After about 1-2 days, this morning, I start up my computer and let it do its post and when I come back it just shuts down. Believing it is a power outage I flip the lights in the room, but they work. I check the orange light on my surge protector: it's lit. I turn on my computer again but when windows is booting up I get a bluescreen 124. What the h*ll? I increase the voltage to 1.410v but i can't get past the windows logo. Trying Offset Vcore gets me as far as the desktop but I bsod after a couple of seconds. Not before I decrease my OC to 4.7Ghz can I stably get into windows. So, has my CPU actually decayed after 2 days of running 1.4v never exceeding 80c?

Yeah, I'll try that. Sorry about the jibberish at the end, don't know how that happened :) So it is confirmed that HT does not provide anything to FSX performance? EDIT: One other question, if I can boot into windows without PLL Overvolt but I bsod while doing stresstesting/idling, should I enable it or is it only for hitting the multiplier wall, i.e not being able to boot past windows icon?

Hey. I guess this is an update to my previous "2600k Max safe temp" thread I posted earlier. I settled for 4.7ghz for a while, but I just couldn't resist going for 4.8. Maybe it was because everyone else seems to be running that setting, or maybe because it's an even number ;) So anyway, with HT on, the temps were always a bit high for the vcore (1.415)I needed to run 4.8, but then I reseated the heatsink to make it blow in air from the side and push it out the side fan rather then down-up which I had previously run. The temperature decreased by a little bit and I seemed to be able to run prime95 without having my core temps reach 80c so I was quite satisfied. Now I've run into another problem though, I pass prime95 and IBT, but I get both the "vcore-bsod's" like 101 and 124 and also a more exotic one called MACHINE_CHECK_EXCEPTION 0x0000009c. All of these BSOD's I get while the CPU is idle or I'm surfing etc. How come I pass really stressfull tests like intel burn test and prime95 but I crash when idle? If I don't reach 80c in prime95, could I just up the vcore by +0.05/0.1v or should I abandon the 4.8ghz goal and just run 4.7ghz where I'm stable at about 0.3v lower? sasasdasdasdasd asaaaaTh sadaasdasasdasdasassadassadasdasasdassssssad

Yeah, I might try disabling HT. I've run Real temp in the background while playing FSX and another game that can be quite stressing on CPU when you unlock the fps (Global Agenda) and temps never go above 65, Prime95 also doesn't give me as high temps as the damned IBT :P Anyway HT on or off how much will a 4.7-4.8/4.9Ghz scale in fps?

Your temps and voltage seem about right for 4.8 compared to other users. Personally I'd back off to 4.5GHz. 80C is pushing it, and so is 1.4+ for 24/7 use. Stressing your hardware like that just isn't worth the extremely minute performance gain (feel free to chime in, Word Not Allowed ). Your CPU isn't going to make 5.0 without causing smoke, if that's what you're ultimately shooting for.

I pulled it back to 4.7Ghz now at 1.375v and I have a feeling that I can lower that vcore a little bit more, temps lower than never beyond 79 at the hottest core and mostly below 76c. I always had 4.8ghz as my goal but 4.7 isn't too bad :) Just a question, if I disabled HT how much vcore could I lose on a 4.8ghz OC?

Thanks for the link ironmaiden... When a lot of people post their temps it sometimes feels like those are the CPU temps (tcase) rather than core temps, so to clarify my CPU (not core) temp never went above 69c but I've always heard that core temp is the one you use, not the cpu temp. Anyway, I'd still like some guidance on what to do with my OC :) I guess I could turn HT off, but I'd really like to have it on because of extra performance in some other applications i use (not extremely important however)

Hi. I've been OC'ing my cpu the last few days and was stopped at 4.5ghz and 1.31v before because my thermal paste I used was of sub quality. Now I've recieved some Noctua NT-H1 that comes heatsink and want to go further. At 4.8Ghz I pass Intel Burn Test (linpack) at max memory usage and HT on, but vcore is kinda high (1.415v) and temps sometimes reach 83, 82, 82 (core 1,2,3. core 0 is always a lot cooler). I then lowered the vcore to 1.395v and didn't have any bsod's but i failed at the fourth pass, temps reached 81 on one core a couple of times (realtemp max: 72, 79, 81, 79). I'm wondering what the max safe core temp is for an unrealistic test like IBT? Should i nudge up the vcore to 1.4/1.405 even though i might have temps at 81/82 once or twice? Thanks in advance :) EDIT: The vcore setting at which i failed IBT but didn't bsod was 1.395, not 1.4 Other settings I've changed:DRAM Freq: 1333mhzPLL Overvolt: DisabledLLC: Ultra HighVRM Freq: 350Phase control: ExtremeDuty control: ExtremeDRAM Volt: 1.65 (according to RAM spec)

Sorry to hijack the thread but I have similar questions. Right now I'm following this guide: http://www.clunk.org.uk/forums/overclocking/39184-p67-sandy-bridge-overclocking-guide-beginners.html which I've heard good things about. Right now I'm trying to get my i7 2600k (asus p8p67 deluxe, 8gb 2000mhz cl9, running at 1333mhz same cl while OC:ing) stable at 4ghz before I head upwards. The guide says to use about 1.120 vcore but im still getting bsod 101/124 at 1.145. When looking at the vcore in cpu-z when stresstesting in prime95 i sometimes goes down to 1.04v and doesnt want to stay stable at 1.145 all the time, is this normal? LLC high.Sorry for bad grammar etc, im writing this on my iphone :)

Hi, again. Today I put together my computer and its running pretty smooth atm, there are a couple of questions I'd like to ask though. I'd like to OC this badboy asap as I have less than a week to decide if I want to keep the parts or resend, and if it turns out the CPU/mobo/ssd whatever is quirky/not achieving the kind of OC i'd like etc etc, I'd like to know that now :) So here we go:1. I was a bit overwhelmed by all the settings in the bios and as I have this idea (coming from simforums) that bios should be stable before OS install so that no corrupts/stability issues occur and thus hamper the OS and from there FSX performance, I'd really appreciate it if anyone could give me more precise instructions on what to have on auto, manual, XMP etc in the bios. I know I'm probably being a bit anal here but better safe than sorry, right? For example, should my OC memory be clocked at 1600 or 1866 (XMP) or does it matter at all? Maybe someone has a screenshot or knows a good guide? 2. From reading a number of different threads I came over a guide linked by Word Not Allowed, I think I know what to do when OC'ing my chip, but I ran out of the thermal paste that comes with my NH-D14, NT-H1, and had to use some Arctic Alumina instead. I checked the temps and its currently running at about 30-36c in "idle" (clock seems to be going up and down and so does that temp) and in OCCT:linpack it hit about 50-53 before I got to bored and closed it down after 10 mins. Does these temps seem ok for a 4.8-5Ghz OC, or should I wait for some NT-H1? 3. When installing the chipset drivers there were a lot of drivers that came with the DVD, some are obviously essential but some seemed unnecessary, for example: There were 2 network drivers, Intel and Realtek, Intel Rapid Storage Technology Driver, Bluetooth driver, USB 3.0 Driver, Realtek onboard sound; and a lot of utilities. Would chipset and Realtek do? I have an internal creative soundcard so the onboard sound driver is kind of useless right? A lot of questions, I know. And im probably worrying too much, I just want to have it as optimal as possible ;) Thanks in advance EDIT: I disabled the marvell controller in BIOS as im using the intel sata ports, was that a stupid thing to do?EDIT2: I forgot to ask about TRIM, do I have to enable it somewhere for my intel SSD or is it active by default?

Hello William,Probably not a good idea to write zero's to a SSD drive.Like degragmenting,it might possibly reduce the lifespan of the SSD drive.

Sorry, I should have been more specific, I meant write the mechanical drive with zeroes.

Hi. I'm almost done with my new build for a NGX-computer ;) I have bought and received all parts (i7 2600K, Asus P8p67 Deluxe, Corsair XMS3 2000Mhz, CL9 memory, Intel 320 SSD 160GB), and I'm just about to start building it. There are just a few things I need help with figuring out before I go ahead. 1. Before, I have always used dBan to wipe my harddrive with zeroes because I was recommended that this would provide a much more "clean" install rather than just reformatting the drive with the OS install cd. This time I will however use my SSD for OS and FSX, and my 1TB WD caviar black will be used for storage and other games that I'm not to worried about the loading times ;) Is it still necessary to go through this long-drawn process? 2. Hmmm, damn, I forgot my other question :( But I'll give you another one: I have up to this point been using Firefox as an internet browser. But I just feel like its too big of a resource hog, especially memory wise. I was wondering if you guys had found a more lightweight option that would let me read .pdf documents in the browser, watch youtube without problems and, well thats pretty much what I do on this computer.

1. I don't really follow any guide when I install FSX. Perhaps I should? I just install FSX, run it, reboot, install SP1, run FSX, reboot, install SP2, run FSX, reboot. You can install FSX on any partition of an SSD - shouldn't matter.

Is there any other advantage from partitioning a SSD other than it being more "tidy"?

My motherboard at the time, Gigabyte P67A-UD5, would not run all four sticks at rated speeds. Best it would do was 1600 9-9-9. I sold the sticks before I got my Asus board, so I couldn't tell you if there was any noticeable effect. If you already have four sticks of 1600 CL6, hold off on your RAM purchase and try those first.

Well the situation is like this: I have 8GB (2x4GB) of Corsair Ram and 6GB (3x2GB) of Mushkin RAM. My Corsair RAM can be sent back within a week, but my mushkin ram are over a year old. The Mushkin ram has been wonderful and after reading all the material I can find about this it seems as if the difference is extremely slight and has more to do with stutters than raw fps. 1600Mhz CL6 has lower latency but also a little lower bandwidith or MT/s than 2000Mhz/2133Mhz CL9. If 4GB is enough for FSX and games (I don't work on this computer) I will probably send back the corsair, but I haven't tried them yet so this might change. After reading through probably 5 different threads I still don't know which is best for FSX, frequency/bandwidth or latency. But it seems as if the mushkins are a bit faster (?) when it comes to pure latency, if only the corsairs were 2000@CL7 EDIT: I will test both memory kits in FSXMark11 when I have my OC setup correctly. I have never really switched RAM's without switching motherboard, do I just plug in my other RAM and set them up in BIOS, will my CPU run the OC with different RAM or will I have to redo my OC?

Thanks. Is it really needed to flash the Bios though? This P8P67 Deluxe is of course B3 so it shouldn't be that old? I looked through the thread you posted a bit and found some references of bios versions but nothing that seemed to say "most stable bios", and the thread was 200 pages long. Maybe some asus p8p67 deluxe users here on this forum can help me? :) Also I've been reading about the 8mb issue with Intel 320 SSDs, has anyone heard if there is a fix available yet? And as the intel 320's are Sata2 I don't really need the Sata 6Gbps ports, right? Lastly: After reading the I5-2500K Vs. RAM frequency thread I have become a bit unsure of whether buying the Corsair 2000mhz@cl9 memory instead of sticking with my mushkin 1600mhz cl6 RAM was a good idea. Corey, I saw in that thread that you owned almost identical RAM's as I do (mushkin ridgeback's dunno about the difference but i read they are 1600mhz cl6, as are my mushkin redlines). Why did you upgrade? Was there any noticeable effect? I'm usually flying airliners like the PMDG MD11/NGX so maybe we are doing completely different things and thus your performance is irrelevant for me... Sorry for the 1000 questions here, its late and I'm tired and I kinda want to get started with building my computer, so I want to know if I should go mushkin or corsair ;) Thanks a lot for your answers, keep more of them coming