So now dGPU users should expect crappy drivers from AMD and NVidia if they are running the "legacy" OS, W7 on their latest GPUS? Is this some kind of lame joke?
I mean a driver that doesnt randomly crash under the first or second most used Windows OS, W7.
Can you provide a proof that this is the case (with the current driver)? Even the newegg issue, I'm not convinced it's a graphics driver issue until a second user confirms.
Can you provide a proof that this is the case (with the current driver)? Even the newegg issue, I'm not convinced it's a graphics driver issue until a second user confirms.
Windows 7 doesn't work on tablets/2in1. What do you think businesses install there? Do you think they reinstall Surface Books with Windows 7?
Its no different on the Mac side, what to use latest office? Yosemite is the minimum.
o365 alone makes a lot of companies move if they didn't already.
I'm surprised no one here has yet talked about the issues people are facing with their new Skylake-S builds (might not be limited to S, but those are the ones people are checking in with so far).
I, and many others who've recently built 6700K/6600K (and non K as well) systems have been experiencing this strange complete system freeze when idle. When it happens, the only resolution is to hard power off the machine, resetting does not work. It can happen anywhere from a few minutes after leaving the computer, to several days. There's a long thread [0] over at Tom's that I've been participating in over the last couple months, but no one's been able to get to the bottom of it. This post in particular [1] sums it up pretty well.
I'm having the issue as well, it freezes for me about once per week on average, sometimes it goes longer, other times it'll freeze two days in a row. I've RMA'ed the motherboard, changed PSU, changed RAM, tried default 2133MHz for RAM, latest BIOS (even beta ones), pretty much everything you could think of. Nothing makes any difference whatsoever.
It's seemingly affecting builds using all manufacturers of motherboards, as well as all RAM manufacturers, so all signs are pointing to either a chipset problem or Skylake uArch problem. Some have even replaced their CPU's only to have the problem show up again.
In addition to these freezes, the guys over at the Prime95 forums are tracking a bug with AVX that causes the workers to fail with a hardware error [2]. They have instructions on how to reproduce if you want to try. I've been able to repro the hardware error myself.
The Prime95 issue and freezing issue are probably unrelated, but who knows, they very well could be. In any case, there seem to be some real unsettling issues with this new platform. Hopefully they can be resolved by BIOS/microcode updates, but so far that hasn't been the case.
What really irks me is that no one is stepping up to confirm anything, not Intel and not the mobo manufacturers. Probably because they are afraid of financial repercussions, but it's highly annoying when your early adopters spend so much money on your gear and then have to troubleshoot very serious and very annoying problems on their own.
[0] http://www.tomshardware.com/forum/id-2830772/skylake-build-randomly-freezing-crashing.html
[1] http://www.tomshardware.com/forum/i...ndomly-freezing-crashing/page-6.html#17247740
[2] http://mersenneforum.org/showthread.php?t=20714
1st one was resolved by upping the ram voltage slightly, I have a feeling the 2nd has the same problem. Thy are both running ram above 2133MHz. There have been quite a few issues with XMP. People usually find stability by either manually setting the ram speed or upping the voltage slightly.
The 3rd one could be an error with Prime95. Older versions have a bug that fails tests when it shouldn't when using FMA3 or AVX.
I'm surprised no one here has yet talked about the issues people are facing with their new Skylake-S builds (might not be limited to S, but those are the ones people are checking in with so far).
I, and many others who've recently built 6700K/6600K (and non K as well) systems have been experiencing this strange complete system freeze when idle. When it happens, the only resolution is to hard power off the machine, resetting does not work. It can happen anywhere from a few minutes after leaving the computer, to several days. There's a long thread [0] over at Tom's that I've been participating in over the last couple months, but no one's been able to get to the bottom of it. This post in particular [1] sums it up pretty well.
I'm having the issue as well, it freezes for me about once per week on average, sometimes it goes longer, other times it'll freeze two days in a row. I've RMA'ed the motherboard, changed PSU, changed RAM, tried default 2133MHz for RAM, latest BIOS (even beta ones), pretty much everything you could think of. Nothing makes any difference whatsoever.
It's seemingly affecting builds using all manufacturers of motherboards, as well as all RAM manufacturers, so all signs are pointing to either a chipset problem or Skylake uArch problem. Some have even replaced their CPU's only to have the problem show up again.
In addition to these freezes, the guys over at the Prime95 forums are tracking a bug with AVX that causes the workers to fail with a hardware error [2]. They have instructions on how to reproduce if you want to try. I've been able to repro the hardware error myself.
The Prime95 issue and freezing issue are probably unrelated, but who knows, they very well could be. In any case, there seem to be some real unsettling issues with this new platform. Hopefully they can be resolved by BIOS/microcode updates, but so far that hasn't been the case.
What really irks me is that no one is stepping up to confirm anything, not Intel and not the mobo manufacturers. Probably because they are afraid of financial repercussions, but it's highly annoying when your early adopters spend so much money on your gear and then have to troubleshoot very serious and very annoying problems on their own.
[0] http://www.tomshardware.com/forum/id-2830772/skylake-build-randomly-freezing-crashing.html
[1] http://www.tomshardware.com/forum/i...ndomly-freezing-crashing/page-6.html#17247740
[2] http://mersenneforum.org/showthread.php?t=20714
Do you let it go to sleep? Or leave it running when you don't use it? I have a friend who built a carbon copy of my system and he never sees it either because he lets it go to sleep.I've had a 6600K and an i3-6100 so far, both OCed, never have seen this.
The prime95 one happens with the newest version as well, just takes longer to happen.
And I think you're discounting the freezing problem much too quickly. You have to read the full thread (I know it's long), but essentially, we've all tried 2133MHz, no XMP. The problem is not RAM, at least not the speed.
I'll take a look at all my drivers, thanks for the latencyMon suggestion.Have people tried upping the voltage?
Are we saying that Prime95 is no longer a reliable stress testing tool when using FMA/AVX?
I also had freezing issues for a while. It turned out to be the latest drivers for my WiFi was causing it. I reverted to the "latest" version that Asus have on their website, ironically labelled Beta. It's been perfectly stable ever since.
I've had other stability issues but they were related to Windows 10. For some reason the drivers it automatically installs aren't great. Same thing happened with the November update. I've had to revert to the previous build. I have a feeling that was driver related too. I'm waiting on a bios that doesn't switch back from M.2 to Sata Express with a 950 plugged in before I do a fresh install.
I'd suggest re-installing all your drivers if you are using windows 10. Then using LatencyMon to see if any drivers are causing hiccups and find alternate versions for them.
Ha! At my company, Win 7 is the new Enterprise IT. I think the lease cycle in 1H 2014 finally brought all PC's up to Win 7. I know my PC at the start of 2014 was still running XP Pro even though it had Win 7 sticker on the PC. At the rate these guys move, I don't see Win 10 being the Enterprise IT until 2017 maybe even 2018.
I have mine set for High Performance, it's always performing some task. I just lock the terminal and shut off the screens when it's unattended.Do you let it go to sleep? Or leave it running when you don't use it? I have a friend who built a carbon copy of my system and he never sees it either because he lets it go to sleep.
I'm not claiming it affects everyone, but there is a significant number chiming in that seems to make it a real issue.
What I forgot to note is that our systems are completely stable during normal use, at least for most people, there are a couple outliers who claim theirs freeze when in use as well. Gaming is no problem, overnight memtest using hci is no problem, even prime 95 (excluding the specific avx test above) torture test is fine.
We're hardly a huge company, probably 500 desktops or so, but in my environment we're the same. We're a Dell shop, and every new network attached computer comes with Windows 7. We're pretty quick on upgrading Office, but OSes are another matter. There still no time line on upgrading to Win10.
Users will soon be able to overclock Intel's Skylake-based Xeon processors on a selection of ASRock motherboards, sources have revealed to TechSpot. Intel normally prevents Xeons from being overclocked, but ASRock has managed to overcome these restrictions through software tricks in their motherboard's BIOS.
This feature is currently being tested internally at ASRock, and will be released to the public in due course. In their testing, the company has managed to push a Xeon E3-1220v5 from 3.0 GHz to 4.5 GHz, a significant clock speed increase of 50% that transforms a basic workstation CPU into a decent performer. The ability to overclock Skylake Xeon processors has big implications for system builders. The Xeon E3-1220v5, for example, is very similar to a Skylake Core i5 part, with a similar array of four cores and four threads, but with a lower base and turbo clock speed, and no integrated graphics. Due to a lesser feature set, the E3-1220v5 costs only $220, less than the Core i5-6600 ($230) and the unlocked i5-6600K ($280).
This means that, theoretically, a user wanting to build a gaming PC could purchase the cheapest Xeon CPU (the E3-1220v5) and overclock it with ease on an ASRock motherboard to the level of a high-end Core i5 CPU. If a user opts for a Xeon with hyper-threading, the cheapest of which is the $275 E3-1230v5, they could build a Core i7-6700K-equivalent system and save over $100.
The two ASRock motherboards that will support Xeon overclocking are the Fatal1ty E3V5 Performance Gaming/OC and the E3V5 WS, both of which use Intel's C232 chipset. These motherboards support consumer-friendly features like DDR4 memory (both ECC and non-ECC), dual PCIe slots, and a healthy collection of USB 3.0 and SATA 6 Gbps ports.
I'll take a look at all my drivers, thanks for the latencyMon suggestion.
I'm regards to voltage, yes many have tried upping it and for some it seems to reduce the frequency of the freezes but no one has been able to get rid of them completely with voltage increases. So yeah it does seem to have something to do with the imc.
I have not, but wouldn't it be strange that voltages would need to be bumped to get stable operation at stock speeds?Just to be thorough, you seem to know what you are doing, but have you also tried a VCCIO voltage boost? maybe alongside a ram voltage boost?
http://techreport.com/news/25138/new-haswell-microcode-to-block-overclocking-on-non-z87-mobos
Intel will make a mandatory microcode update to block overclocking on non Z170 mobos, don't count on this lasting much longer, as history has shown.