Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
May I ask how you are mounting that 50mm for the VRM area? Sounds interesting.
Anyone tried out the MSATA function on the board? Opinions?
Yes and it works well. SATA 2 speeds only though. I have a 60GB OCK Nocti drive running as a cache for a 1TB mechanical drive using RST and its excellent.
Off topic but I heard those Noctis run QUITE hot. Something to consider when in a SFF. Simon what is your take on that matter?
Yeah, the USB3.0 cable could be just a hair shorter, but honest, it's not all that bad once you get it sort twisted in the right direction. It tucks right out of the way. However, the SATA port right by the PCIe16 slot is awfully close and with the cables I'm using (not the stock ones) they have to be pushed out of the way for the GPU to seat properly. But no biggie. The curse of SFF I guess.so far, the most frustrating thing about this box is the internal usb 3.0 header cables...i don't have my video card yet but it seems like it's going to be in the way of the pcie slot. i've managed to get the cables bent under the drive cage but this was a really poor design choice by shuttle. it wouldn't be so bad if the cable was just a bit shorter.

That is not by any means stable, and you really need to push it more to see temps. Since the cooling on a Shuttle is hardly amazing, that thing will reach the envelope and throttle / shut down, gauranteed, at those volts and with the shuttle cooling.
No luck with my RAM, unfortunately. Even after updating the BIOS.
I fail to see how the shuttle cooling can run a Sandy at 5.0 at 1.48v at anything acceptable under prime, when it doesn't even do that most of the time with a $35 dedicated cooler.
Water cooling.
I was thinking that but you shoulda said that, I didn't see anything about it. lol.
I really cant recall if it was only once I selected XMP profile in the bios that it worked for me - maybe the Auto did not... The selection was only available after I modded the bios.
I think Shuttle are getting closer though... should not be too long before they get it sorted properly - I hope.
Would be happy to share but before I do I want to do a couple of things...
1. Speak to shuttle about a few quirks with the 201 bios (non modded)... i have problems running some DOS applications and get lockups in the bios from time to time. I can't instal windows XP for example and this is a worry because if it locks while flashing then we are in trouble.
2. Let me create a cleaned up version. I have unlocked about 150 extra functions (most will not do anything) but there are actually only a few we need.
With regards temps...
another slight worry is that the reported CPU temps and power use in windows (i use real temp, but the values seem much the same in other applications) seem very low. my idle CPU temps are 16-25c and Prime95 at 5GHz is only just in the 70's with the fans not on full. I would say the CPU feels cool and the air comming out the back does not feel hotter than the temps would suggest, but it is a concern. With regards power, real temp only reports 97-102w running Prime95 at 5GHz and I know i was seeing 110w at 4.8GHz with the previous bios... so again something is odd.
The temp queries are probably a symptom of the IB changes, but again I want to speak to Shuttle.
The VRM area seems fine. I will get a temp probe in there in the next day or two. I currently have a 50mm fan on the VRM heatsink but as I say the area feels no hotter than before.
Finally... did a bit more playing and was able to boot to windows at 5.4GHz with all the voltages (except ram related) to the max, but could not run SuperPi. I can, however run Super-Pi at 5.3GHz - this is comparable to speed I can achieve with the CPU in a desktop P67 board.... so its basically the CPU's limit.
I can't stop my i7 2700k from clock rate limiting... I tried boosting the current
limit box (in modded bios) but it didn't seem to help and the other two power
limit adjustments (right under the multiplier setting) seem to be hard-limited
so they can't be increased. It runs at 4.6GHz with Prime95 for a short time
then backs down to 4.2 or so (all voltages default). I have the Asetek cooler
and all stock voltages with all temps <70C so I don't think it is hitting a
thermal wall. I didn't see the Thermal adjusts present in the previous bios
using AMIBCP 4.50.0.23, just some current limit adjusts.
My experience with modding the 201 bios so far :
The RAM presets work for G.skill Ares 32Gb 1866, all 32G runs 1866 with
stock voltage (1.5)
Manually configuring RAM was a near disaster... next click up was 2133 which
I thought I would experiment with, box did not boot, and CMOS clear
(button on chassis rear) did not reset mem timing to BIOS defaults!To get it
going I took out all but one stick, luckily it booted and I then cleared out the
RAM myself to defaults. It is a big problem if hardware CMOS clear does
not reset the BIOS to all defaults; one bad config and you could lock out the
box for good and need to send for a new BIOS chip.
I get intermittent freeze-ups while in the BIOS and flaky behavior with DOS,
which I use to flash the bios, my Seagate Seatools DOS disk wouldn't recognize
keyboard with new BIOS.
Linux 3.3 (or 2.8) does not show the correct clock frequency any more, it
pegs at 3.3GHz for the i7 2700k I have, to see the right clock frequency it
is necessary to use "turbostat". This did not happen on previous bios. The
clock frequency is correctly shown in Win7 though.
I can't stop my i7 2700k from clock rate limiting... I tried boosting the current
limit box (in modded bios) but it didn't seem to help and the other two power
limit adjustments (right under the multiplier setting) seem to be hard-limited
so they can't be increased. It runs at 4.6GHz with Prime95 for a short time
then backs down to 4.2 or so (all voltages default). I have the Asetek cooler
and all stock voltages with all temps <70C so I don't think it is hitting a
thermal wall. I didn't see the Thermal adjusts present in the previous bios
using AMIBCP 4.50.0.23, just some current limit adjusts.
You sure you raised the MAX TDP from 95w to 120+w?
With my modded 104 I run Prime95 with all 4 cores at 4.6ghz for hours on end.
I get the same lockups in bios and some DOS applications dont run - you can't install windows XP for example. I have informed Shuttle of this.
I will check which setting it is you change... the 201 is all different there is no setting for limits.... Here you go... in the CPU Configuration there is a setting called IA Core Current Max(1/8 Amps)... in one of the Bios mod files I renamed and can't remember what to DOH but it starts IA - I have set this to 1250 and that seems to do the trick.
I think the lockups in bios and dos might be USB related, but await Shuttle's response.
Because i'm messing with the bioses all the time I have a spare chip so I can always recover although the 201 is the first file that sucessfully flashes to a spare chip, but at least i'm safe now. Worth getting one, mine was about £8 in the UK
Oh finally, I find that if the Ram gets messed up taking the power out for a minute or two causes a hard reset on next boot and it seems to sort itself out... so I do cmos clear then take the mains lead out for a minute or two before booting back up. I expect removing the cmos battery would do the same.
I have a 2700k also with 16gig of G.SKILL Ripjaws X 1600 memory and asetek cooler. I put the multiplier on 45 and it will start prime at 4.5 but slows to 3.9 then 3.8. Stock bios and memory won't run faster then 1333.
No dice on upping IA current limit in Bios 201 to 1250 with my 2700k... some governor appears to be kicking in and limiting it to 4.2 to 4.4 on Prime95 and 3.6 to 3.8 on Linpack, power draw is kept somewhere in the regime of 95W by the governor. Not that such a stress load is that important for typical usage, but it makes it impossible to do reliable stability testing at the max overclock multiplier (I'm currently using 46 at stock voltage).
I'm really busy for the new couple of days but will try and take another look on Saturday and see if i'm missing passing something on. It is possible that its the 2700K over the 2600K but i'm not convinced.
I think the problem is related to the Power 1 and Power 2 limit values, in the new BIOS I believe these are the long term and short term power limits. The new 201 bios limits Power 1 to a range of 380 to 760 (1/8 watt) -> 47.5W to 95W which I theorize is long-term power limit, and Power 2 to a range of 475 to 950 (1/8 watt) -> 60W to 120W which I guess is short-term power limit. I haven't found a way to override the limits above 95W/120W through AMIBCP interface.