Recent content by graysky

An update: this is a BIOS bug but there is a work-around. I have been testing several systems (Z77 and H97-based) after I disabled all references to 'xHCI' as it pertains to USB settings[1]. I also enabled wake on keyboard[2]. And finally, I disabled EuP 2013 which affects wattage in power off...

OK, ran out to ~200 hours and as expected, no change in the conclusion. The original post was updated with these results.

I honestly never observed temps going up over time...

@flod - No, too much work since you can get a "bad mount" thus the need for replicates. Someone did this (3 or 5 mounts) per paste and published it. You'll have to google for it. My particular study is less affected by mounting variability I think since any curing effect should be similar as...

Purpose According to the manufacture of AS5, there can be up to 200 hours of break in time required for temps to stabilize. This claim has been tested the results are shared in this thread. Materials, software, and experiment A delidded i7-3770k (over-clocked to 44x100 with fixed vcore) was...

Consider the results I presented invalid. I did not control for the FFT size (thought I did but later realized the defaults define a range). I edited the first post of this thread and will repeat.

I compared Arctic Silver 5 to MX-4 between my new i7-4790K and my NH-14D. In short, I ran mprime (Linux64,Prime95,V28.5,build 2) using large FFTs with 8 threads and logged the temps throughout the run once per second using a shell script. Ambient temp which is very important to consider did...

Under linux, displaying the processor's pstates can be done with programs like i7z, powertop, or turbostat. Can someone recommend a Windows utility that can display processor pstates? % sudo i7z Cpu speed from cpuinfo 3500.00Mhz cpuinfo might be wrong if cpufreq is enabled. To guess...

I just tested it under windows 7 to see if it was a Linux problem, or universal. This machine runs Linux.

Booting into windows 7 and then shutting down from there does not exhibit this behavior. It seems to be something unique to Linux...

This is the only issue stopping me from recommending the board at present. It is fine otherwise, but if you need WOL it is a critical one. Can you post a few links to the posts to which you refer [i.e in the NAS and HTPC forums]? Thanks you.

Odd, I too have this drive. Here is the output of the seagate tools drive detector: Model: ST3000DM001-1CH166, Serial: X1X4C0XX, Firmware: CC29 The error would appear to be in the firmware since smartmontools also reports this as the model: # smartctl --all /dev/sdb smartctl 6.2 2013-07-26...

Update - Latest BIOS 1005 does not fix this problem and 14 emails between myself and the people at Asus who barely speak English have not been fruitful.

If not in the BIOS file, perhaps in the BIOS on the board.

@Blue - Thanks for the confirmation. It is likely something intrinsic in the BIOS then that occurs when it detects bad blocks. Mine is an Asus P8Z77-V Pro... what is your board?