Jump to content
HWBOT Community Forums

How to bench Sandy, Ivy, Haswell and Broadwell CPUS if 6.4.x becomes mandatory ...?


bolc

Recommended Posts

Hello,

 

Correct me if I am wrong, but isn't XTU only compatible with the last 3 generations of Intel cpus ? That is :

6.4.x supports Coffee, Kaby and Skylake

6.3.x supports Kaby, Skylake and Broadwell

6.2.x supports Skylake, Broadwell and Haswell

6.1.x supports Broadwell, Haswell and Ivy Bridge

5.2.x supports Haswell, Ivy Bridge and Sandy Bridge?

(older versions of XTU are not allowed for posting scores)

 

Will the upcoming mandatory use of 6.4.1.12 (Upcoming Rule Changes on November 1, 2017) is also limit benching on cpus compatible with Z170/270/370 chipsets?

 

If so, any prospects to make 6.4.x backward compatible with anything from Gen2 onwards?

 

Cheers

Edited by bolc
Link to comment
Share on other sites

I tested 6.4.12 and it worked with M5G and 3770K, Luumi tested 3470 Ivy bridge and it worked as well

 

This is what I was getting yesterday on 6.4.1.12.

The cpu was not recognised, and as could be expected, the bench would not start.

3570 on M5F. With 6.2.x and 6.3.x same issue. 5.2.x and 6.0.x ok, 6.1.x I suppose is ok, will try tonight.

 

https://www.hostingpics.net/viewer.php?id=554362xtubug.png

https://www.hostingpics.net/viewer.php?id=424283xtubug2.png

 

You are both on Windows 10 ?

 

PS: all drivers put for the board, IME / cpu.

PS2: tried at stock or with a different bclk, same story

Edited by bolc
Link to comment
Share on other sites

I checked very fast, used a win10x64 made for 1151

 

 

Thanks for the screenshots.

 

I bet users with Windows 7 (and perhaps windows 8.x) will have issues...

latest ver 6.1.x not working on M5F + 3570

 

so far only latest 5.2.x and 6.0.x working on M5F + 3570 + Win7 Pro 64 bits

Edited by bolc
Link to comment
Share on other sites

Watchdog, yes, required, it comes with XTU (monitoring and recovery). MEI should also be OK when you install it with XTU.

 

watchdog says present but not present at boot

https://www.hostingpics.net/viewer.php?id=554362xtubug.png

 

for IME, when I install XTU, the IME driver version does not change. I installed manually ver 9.x, it stayed the same. I went to 11.05, stayed there

 

 

I also get this driver signature message at the end of XTU installation

489183error.png

 

 

ME firmware revision is 8.1.x in the bios, I had updated it

Edited by bolc
Link to comment
Share on other sites

  • Crew

K I crosschecked

 

fresh install windows 8.1 (latest MSDN version) 32 and 64bit

 

2600K on MVE

 

32bit: 813

64bit: 806

 

3570K on MVE

 

32bit: 813

64bit: 809

 

4790K on OCF

 

32bit: 1112

64bit: 1110

 

Uploaded the 2600K via the bot, works fine :nana:

Edited by Leeghoofd
  • Like 1
Link to comment
Share on other sites

Win7 support will end 2020.

Xp is still used here as well as vista and 7.

I tried win10 pro 32 and got worse scores on xtu than on w7. Plus i find the GUI ugly and the os is heavy.

In companies everybody is on 7...

 

The issue is to fibd out if the new newer xtu version will force to be on win10 or not...

 

From what i see, sandy stops at xtu 5.2 x, ivy at 6.0.x when on win7

Edited by bolc
Link to comment
Share on other sites

K I crosschecked

 

fresh install windows 8.1 (latest MSDN version) 32 and 64bit

 

2600K on MVE

 

32bit: 813

64bit: 806

 

3570K on MVE

 

32bit: 813

64bit: 809

 

4790K on OCF

 

32bit: 1112

64bit: 1110

 

Uploaded the 2600K via the bot, works fine :nana:

 

Thanks mate :-)

 

Curious to see if i screwed up on win7 or if other users have the same issues...

Link to comment
Share on other sites

I don't remember that Important! Windows 8/8.1/10 Allowed on Skylake + Clarification on Engineering Hardware was changed, which clearly states that 8/8.1/10 is allowed for XTU. We're talking XTU here, not all benches.

 

Making a win10 install solely for xtu when most other benches are on win7....

 

Xtu 6.4.1.12 running on all cpu generations on windows 7 needs to be fixed, at least i will strive for that on my pc.

Link to comment
Share on other sites

They won't fix it. Forward >to> W10 + XTU method is NOT to support old OS.

In a way Intel & partners like m$ will try force your upgrade path sooner.

 

Research " zeffy patch " for your Win7 fix. Let me know what you did if it works.

_____________

 

Xtu 6.4.1.12 ... does this support nonK Skylake? If NOT ... selling them off

Link to comment
Share on other sites

  • Crew
Making a win10 install solely for xtu when most other benches are on win7....

 

Welcome to 2016, where each benchmark almost needs a dedicated OS to get best performance...

 

Try latest Win8.1 32bit mate, not sure if Win7 is always the way to go. In my book for XTU 8.1 is way more consistant in output. With 10 I always experience sudden drop in performance forcing me to reinstall to get the efficiency back.

Link to comment
Share on other sites

They won't fix it. Forward >to> W10 + XTU method is NOT to support old OS.

In a way Intel & partners like m$ will try force your upgrade path sooner.

 

Research " zeffy patch " for your Win7 fix. Let me know what you did if it works.

_____________

 

Xtu 6.4.1.12 ... does this support nonK Skylake? If NOT ... selling them off

 

 

XTU not recognizing the cpu all boils down to the digitally signed driver...!!!

 

Pressing F8 at startup, you can disable it and install XTU. Now the cpu is recognizzed on thre latest version of windows. I need to do the digitally aigned driver permanently now ...!

Link to comment
Share on other sites

ok so I found one solution:

Boot Windows 7 64bits into Test Mode and enforce unsigned iocbios2.sys to appear as signed / verified

https://superuser.com/questions/1233615/how-to-force-windows-7-to-disable-driver-signature-enforcement

 

the tool is available here Driver Signature Enforcement Overrider Download does the job nicely to enable the TEST mode, and to indicate which driver to digitally verify !

 

you can also manually do it with the bcdedit.exe command + manually press F8 at each boot...

https://support.hidemyass.com/hc/en-us/articles/202723596-How-to-disable-Driver-Signing-check-on-Windows

 

 

Making a W7 32 bits installation may also solve this...

And W8.1 32 or W10 32 bits seem to work

Edited by bolc
Link to comment
Share on other sites

Question to the moderators:

 

Am I allowed to bench on Win7 64 bits in TEST MODE (in the bottom right of the screen ,TEst Mode Windows 7 with the version is written)

so the IOCBIOS2.SYS driver required for XTU 6.1.x, 6.2.x, 6.3.x and 6.4.x is digitally verified ??

 

Thank you

Edited by bolc
Link to comment
Share on other sites

Should be OK if the result is comparable, which it should be

 

Results are comparable, I benched quickly 3770k at 3.9 and obtained 810ish with basic ram 8-11-8-28-1T.

And obtained around 930 (from the top of my head) at 4.5 with slighlty tightened ram timings

 

The only thing Test Mode does is to allow digital drivers not signed by M$...

https://support.microsoft.com/en-us/help/2509241/how-to-disable-the-test-mode-message-that-is-displayed-in-windows

Edited by bolc
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...