I did a fresh install. I have been wondering if it's a memory leak, though. How would I find that out and what do you mean by "keep the memory dumps"?

Just took an hour flight from Portland to Yakima with real weather and most everything at 100%. And 13 Saitek USB devices.Core0=46, core1=46, core2=57, core3=47.At least it is consistant!Rick S.

I did a fresh install. I have been wondering if it's a memory leak, though. How would I find that out and what do you mean by "keep the memory dumps"?

Start -> Right click on "Computer" -> Advanced System settings -> Startup & recovery, and set "Write debugging information" to "Small memory dump" It might be configured to save complete memory dumps, usually in %SystemRoot%/Windows. If that's the case you will have some .dmp files in your windows partition although for what I know you need to install the windows debugging tools and symbols (and it's a pretty big download) to open those.If it's set to save mini-dumps as shown above, you can use Blue Screen Viewer

Alright, I made the changes above and installed Blue Screen View. It appears it's able to view the dump files that are already in the minidump folder. From the attached screenshot, I can see that hal.dll and ntoskrnl.exe are causing issues, but what do I do from there? I will do some googling in the meantime.Also I ran memtest just two days ago. 10 full passes on each individual stick with 0 errors. Ran prime95 blend for 8 hours yesterday (I know, complete overkill). Hard drive issue, maybe? Maybe graphics card?

While all I have played with is OC and CPU voltage, I'll go ahead and say it's about the same. Same 4.8GHz at 1.37 to 1.38v. However, I am able to OC my memory now! And just like my Gigabyte, it seems the BSOD while internet browsing persists. Had it happen for the first time this morning. I'm going to play with VCCIO and PLL and see if that does anything to fix it.

Did you try my settings with LLC set to high and offset volts set around .06? There are a lot of posts about volts dropping too low on low loads and causing BSOD'S. Cant say I've had that problem.Do you get BSOD's if browsing with Prime95 running?

Did you try my settings with LLC set to high and offset volts set around .06? There are a lot of posts about volts dropping too low on low loads and causing BSOD'S. Cant say I've had that problem.

If I don't figure something out soon, I might eventually try that route. The thing is that my Gigabyte board suffered from idle BSOD and the voltage was always 1.38v. I have no problems with prime95 whatsoever. I ran it for 8hrs just yesterday and did some browsing in there too. That's a good way to see if that's at, but if this is like my Gigabyte board, this error happens about once a week. So trying to browse while prime95'ing isn't going to single it out.

Just in case anyone is interested I just spoke with an intel tech rep this morning. Told me that 10 to 15 C spread between cores @ 3.4GHz was within specification. Added that 72.6C was the limit and that oh yeah, they do not condone OC'ing.Thanked him for his trouble.Rick S.

oh yeah, they do not condone OC'ing.

Yet they release unlocked K processors

Yet they release unlocked K processors

I did memtion that to him but got no respone.Let me ask you a question. All of my high temps appear to be on core#2.I have used Spirits BIOS settings, but had to come off the 5G ver and set it back to 4.8 with a few drops in the vcore. I saw76 (mostly low 70's) in Prime95 on #2 and mid 60's on the rest. I think I will try lowering the vcore till I get a BS and raise it one click.I tried FSX and it runs perect but I noticed my G-13 shows Coer#2 running in the 90+% most of the time. I do see core#1 get way up from time to time but not near that high and the others way down low. Is that normal? If not, how do you adjust it? BTW my high temps in FSX are 53, 52, 63 & 51.ThanksRick S.

Sorry, I accidentally hit the post button. I was responding here, but then decided to create a dedicated thread here.

Just tried overclocking my machine for the first time.At standard clock speed and idle the temps are 34 32 34 32 CRunning OCCT at max stock speed the temps were 52 57 54 56 CRunning Intel burn at max stock speed temps 48 51 49 51 CRunning OCCT at 4.6 and 1.35V the temps were around 73 CRunning Intel Burn Test the temps approach 90 after just a few minutes and I cut off the test. I did not notice huge differences in temperatures between cores.I think my Nh-D14 may not be seated correctly or I used too much paste. I used a pea size rather than rice size and did not smooth it out or anything, just rotated the fan back and forth very slightly and then installed. Man, I really hope this is just a thermal paste issue.Mark.

Don't use Intel Burn Test. The latest version takes advantage of AVX which inadvertently causes temps to skyrocket! If you're staying under 75C with OCCT and prime95 then you're doing just fine.

Good to know, thanks I will drop the burn test.