• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

2500k "clock interrupt on secondary cpu" BSOD

Vdroop has been around forever. It used to be pencil mods etc. to fix it. These days, I don't worry about it - if it's stable it's stable, doesn't matter on the exact value.
 
the bios will ALWAYS read higher than windows due to it wont run any of the energy saving features.
maybe this is your issue?

I disabled all the energy saving functions now and anyway the cpu-v has always been ok @ idle, Both bios and hardware monitor report the same volts at idle, only under load do I get the issue of V-droop, I do wonder how much V-droop I would get if I disabled LLC though, One guy on tweaktown had something like 0.08v V-droop on exactly the same board, So I guess I should count myself lucky :D
 
do gigabyte have an overclocking app that you can run in windows?
i find that using the ASRock tuneup util gives me the best info for mobo/cpu temps aswell as all the voltages. i dont use it for anything other than a reference with realtemp and cpu-z.
 
do gigabyte have an overclocking app that you can run in windows?
i find that using the ASRock tuneup util gives me the best info for mobo/cpu temps aswell as all the voltages. i dont use it for anything other than a reference with realtemp and cpu-z.

Yes, I had it installed and that gave the same volt readings as bios and H/M, not sure why I uninstalled it though? Might re-install it just to check.
 
Guy`s, starting to think my M/B is borked as the same BSOD has reared it`s head once again and whilst browsing, The stupid thing is I can run prime stable for 6hrs+ with this O/C (4.2ghz @ 1.27v) and no BSOD`S, yet when just browsing I seem to get this same BSOD, though it has happened twice only over the past few days.

I thought I had solved the issue because intially I was running my cpu volts too low @ 1.26, but because I had a V-droop of 0.02, it was actually 1.24, So I managed to get the V-droop down to about 0.01v and increased the Volts to 1.27, with the V-droop that meant 1.26v. Now the only thing I can think of, is that on both of these times I have had the relevant power saving features enabled when it has BSOD`D, now surely the m/b should`nt crap out using these features should it!?

If it were the cpu, then surely it would fail prime or crash in games, though saying that it did lock up in football manager the other night but then again I played Anno 1404 with no probs :confused::confused:

I also thought it could be my corsair 650tx and under load I noticed it drop from 12.024v to 11.075v (12v rail), though this doesnt really add up as to why it gives this BSOD when just web browsing, I am at my wits end trying to figure this out, does anyone now of a solution to confirm it is the m/b or other hardware.
 
Last edited:
have you tried running at stock settings?
if that works then its probs not the MB is borked, just that some settings aint correct.

Yeah I have thought about going back to stock, but my argument against was that it has been stable in prime (running prime now & no issues) for 6hrs + and the BSOD is so random and has only happened whilst having the power saving features enabled, though will give it a try.

In relation to the freezing I was having the other day, I found a thread where A guy had set his Corsair ram @ 1.5v and was having the same issues as I was, So he upped his volts to 1.61v and all has been well since.
http://www.sevenforums.com/crashes-debugging/145396-w7-random-lockups.html

Just in case anyone is having the same issues, mine seems ok now on that front, just these BSOD`s.....Will try stock settings with the power features enabled and disabled.

Will post some bios screens up of my current settings to see if I have messed anything up (high probabilty)
 
Last edited:
Yeah I have thought about going back to stock, but my argument against was that it has been stable in prime (running prime now & no issues) for 6hrs + and the BSOD is so random and has only happened whilst having the power saving features enabled, though will give it a try.

In relation to the freezing I was having the other day, I found a thread where A guy had set his Corsair ram @ 1.5v and was having the same issues as I was, So he upped his volts to 1.61v and all has been well since.
http://www.sevenforums.com/crashes-debugging/145396-w7-random-lockups.html

Just in case anyone is having the same issues, mine seems ok now on that front, just these BSOD`s.....Will try stock settings with the power features enabled and disabled.

prime really isnt proof its 100% stable. its good as a guide, but i have had mine pass over 24hours of prime testing and fail on a video encode or something.
EDIT : if it was me, then as its universally agreed that 1.35v is 'safe' then i would bump it up to that, and do the tasks that are causing the BSOD. if that then stops them, lower it a notch and try again, until you get to the point where the BSODs come back. once you have this sorted and have stopped them in normal use, then prime it.
 
Last edited:
prime really isnt proof its 100% stable. its good as a guide, but i have had mine pass over 24hours of prime testing and fail on a video encode or something.
EDIT : if it was me, then as its universally agreed that 1.35v is 'safe' then i would bump it up to that, and do the tasks that are causing the BSOD. if that then stops them, lower it a notch and try again, until you get to the point where the BSODs come back. once you have this sorted and have stopped them in normal use, then prime it.

Normally I would, Though seeing as when It happens I am just browsing and I am using the power saving features I know that at that point the system is undervolting and it does not use the max volts that I am setting manually for that overclock.
 
Using it properly? Correct number of threads and amount of memory? What GFLOPS was it averaging?

Tbh, I probably did not run it properly, though my thoughts behind using it were that I would prob not use that much of my system in the same enviroment that that would use it, So did not really regard it as a real-time everyday scenario.
 
Well I think I may have found my problem, Last night whilst running IBT, I noticed that both easy tune 6 and hardware monitor were showing my cpu v at 1.24v and then up to 1.28v, I knew this was not right as I have my voltage hard set at 1.31v with a V-droop of 0.01v, so under load it should be showing 1.30v, easy tune normally shows this as 1.29.8v.

This is not a constant V-droop of 0.07, this is a intermittent fault and to me also tells me why I was getting fault code 0x101 = add more vcore bsod`s whilst just web browsing, I am pretty sure that the M/B is faulty, As I have checked the ram via Memtest and Occt (a 6hr run), Also run IBT for 20 passes( with an avg of 58 Gflops, using max ram available and 4 threads).
The only things I have not ruled out are the PSU and M/B. The PSU does drop from 12.073 to 12.027 and has gone as low as 11.978 under load, which is still well with-in margins, So I am thinking it is the M/B. I am open to suggestion if anyone thinks any different as to what it could be..:confused::confused:
 
I can't help much, but I can say what I've been saying a lot recently on the use of IBT. The peak power of your SB chip is 32 times the clock speed, so at 4.2 the max would be 4.2*32 = 134.4 GFLOPS. You need to use more memory, so that it reaches 80% or more of the peak. I.e. close more progs and keep running ad increasing the memory (use custom if it helps) until youre seeing 0.8*134.4 = 108 GFLOPS or more. If you're seeing 58 GFLOPS it's not stressing the CPU.
 
Back
Top Bottom