Search results

I guess one can be lucky sometimes. What's normal for VR VOUT, measure VRM output or sense feedback? Seems to increase with load suggesting VRM output but jumps around by a few 10's of mV. Might have to mod it to be sure. Heaven bench run with default settings. If IIRC current averaging was...

Thanks for your reply. Shame it's like that as making connections to the board isn't fun for me these days.

Would it be possible to add this? Voltage is not always the same as reported via nvidia api For instance my GTX 1660 Super uses a uP9512R with byte of register 0x2D reporting 10mV units according to datasheet. Thanks.

The description on the left shows LLC/Ring ratio, on the right in summary it is shown as Uncore, giving max and status while again the left describes uncore as not supporting ratios. I would have thought the summary would show LLC instead of Uncore for clarity. I'm probably nitpicking. Don't...

Intels Uncore can be a little confusing, being everything off core. Any thoughts to making this less so in HWiNFO?

Your welcome, thank you for clearing up the confusion.

Martin, v4.49-2355 seems to be using CPUID flag bit 29 for RDSEED but from doc's out there say bit 18 while bit 29 is SHA. Are the doc's wrong or HWinfo32?

Looks like HWMonitor got the same doc's as you. :rolleyes: Might as well mark this as solved. If I'm supposed to do that idk how. :huh: Rgds

Well if it's not then XTU is wrong. Offset is given in steps of 0.9765625mV which is 1/1024V. Remember I didn't say I was sure, I said "I think". Unfortunately that's the best I can offer you.

I see you have now fixed this in build 2063 Build 2060 11-Dec-2013 Build 2063 21-Dec-2013 I think there's still a small problem with both positive and negative numbers in that each bit should be 1/1024th of a Volt, not 1mV (1/1000). The two screenshots should be -80mV I believe...

Hi Martin. When using a negative offset, for example -100mV for Cores HWInfo32 shows 1.945V. I suspect you are treating the offset as an unsigned number instead of signed. Rgds...

Parsec was very kind and did some testing. C-States were OS disabled, including C1, EIST disabled in the BIOS and multi's software set as 1st core = x8, second core = x14, third core = x20 and 4th core = x26. As you can see, at least for the Desktop SKU, the processor runs at one...

That should be easy to check, well if one has an 1150 that is. :( If EIST is disabled in the BIOS, which generally does not disable EIST but presents zero performance states to the OS instead, then the cores can be software programmed with different ratio's and then checked by loading all cores...

Hi Martin, hope all is good. Hope you do not mind a few questions/thoughts to your statements, I do not have a Haswell system yet so hopefully they don't appear too stupid. First of all Haswell 328897 CPU datasheet sec 4.2.1 suggest vcore operates much the same as previously, that is one...

RE: CPU Core temperature measuring via DTS - Facts & Fictions I'm curious as to how you came to some of these measurements. Isn't Tjmax read from MSR 0x1A2 actually TjTarget where TjTarget is the minimum temperature expected for DTS=0? Wouldn't this mean for example that your plus or minus...

No Vpro. With i5-2500k & P67 things are fairly sparse, no AMT, no MEBx, no Txt etc... [attachment=291]

Not so fortunate with this board. [attachment=290] But nice to hear it might be available for other boards. Sounds like things might get a bit messy with IvyBridge and ME 8.x requirements although not too sure what that's all about.

Okay my bad, seems I was using 391 for some strange reason instead of 393, my apologies, all okay. :blush: Would it be possible/useful to show the ME Firmware version?

Hi Martin, where is this to be found? P67 MEI 8.x

I see you added the color scheme to the features box, looks nice. :) I was wondering if it went just a little further... Grayed - Unsupported features Black - Supported with no enable/disable function. Green - Supported and enabled. Bold Green - Supported, enabled and locked. Red -...