Windows 10 AU and SSD's

DON'T UPDATE YET. There are issues with SSD's and freezing. I don't have an english link, but here is one to PCGH Windows 10: Nach Anniversary-Update vermehrt SSD-Probleme

Basically what happens is my windows drive spikes to 100% usage (even though it isn't writing/reading much) and the whole PC freezes for a couple of seconds. It also seems like Microsoft has NO CLUE why it's happening. Great. If you have this issue and can still go back to the previous Windows 10 build, that should fix it.

EDIT: English link Windows 10 Anniversary Update can cause your PC to freeze, but Microsoft has a workaround

Myself and most people I know are running SSD's and I have to say, I've never come across this issue on the AU - In fact my Windows machine is running better than ever.

I believe this only impacts people who have Windows installed on an SSD and have their Apps set to a HDD in Settings->System->Storage->Save Locations.

I have SSD and HDD in my system and have not had any issues with the AU.

I only have SSDs.

I've actually only noticed it happening with Diablo 3. None of my games are installed on the same SSD as Windows.

All my Windows 10 AU installs are on SSDs, no issues. Using default locations in OS. MS said it seemed to be SSD + Apps on another drive than boot that are having the majority of issues, if the article from other day was accurate.

What do you mean by Apps? As in Microsoft official ones or just regular applications i.e. Steam and games?

No issues here, Win 10 installed on SSD Steam installed on a HDD, also WoW installed on HDD

I had the task bar freeze for about a minute every startup or coming out of sleep. Icons on the desktop worked. After about a minute I could select programs on the task bar or start menu. Also, the update removed the modified WMC, and it killed it's ability to see the SD HDHR tuners. I rolled back and all is fine again. I checked off delay updates, don't know how long that will last.

Hey Microsoft, try testing on more than one PC in future.

I turned off that Game DVR "feature" earlier, didn't have any freezes yet. I played Diablo 3 for about 1.5 hours, I'll probably play a bit more later today and see if it's still happening.

-Strelok- said:

I turned off that Game DVR "feature" earlier, didn't have any freezes yet. I played Diablo 3 for about 1.5 hours, I'll probably play a bit more later today and see if it's still happening.

Click to expand...

Probably has to do with this. The DVR is buffering video constantly when turned on.

rezerekted said:

Hey Microsoft, try testing on more than one PC in future.

Click to expand...

The irony is that all the telemetry and snooping in 10 was promised to resolve stuff like this quicker, or prevent it from reaching the major public releases in the first place.

So in reality it's the same duct-tape development culture that it's always been at MS, but now since "agile" development is a popular buzzword, they've latched onto that as the excuse for why the OS is perpetually buggy and perpetually beta, with the apparent goal no longer being to create the best desktop OS, but a platform for testing new advertising, marketing and mobile features - even though their mobile division is already dead.

DPI said:

The irony is that all the telemetry and snooping in 10 was promised to resolve stuff like this quicker,

Click to expand...

Which it generally does.

or prevent it from reaching the major public releases in the first place.

Click to expand...

Which it does less.

Besides bashing on MS, a favorite pastime of you and rezerekted (who I am starting to think is just a new profile formfiller made when he was first banned from the OS forum 0.o), have you ever thought about the compatibility matrix for something like Windows 10? Have you ever tried supporting even a small piece of it? Because before I moved to my current team, I was an SDET in Windows, and the reality isn't pretty.

We have ~114k employees, 44.4% who are in engineering. For a minute, pretend that 100% of us work on Windows. That would be ~50,000 employees working on Windows. Even if we tried, it wouldn't be physically possible to test all of the hardware combinations (ignoring drivers & other aspects completely, which have a huge impact on the system). Consider, assuming 1 hardware generation/revision per year going back to the start of 2012, including only basic stuff and major manufacturers (estimates followed by (?)) : 3 gpu providers * 4 generations * 2 CPU manufacturers * 4 generations * 10 (?) mobo manufacturers * 4 generations * 10 (?) disk manufacturers (SSD/HD) * 4 generations, alone, is over the number of employees we have, way over how many engineers we have, and way more than the number of engineers we have working on Windows. That's before you start getting into the combinatorics of drivers, programs, upgrade paths, patch levels, and all the rest that we get to deal with. Teams get to deal with that staggering complexity, attempt to find what issues are hitting the most people, and try to help enraged customers all while being bashed by you and those like you.

So in reality it's the same duct-tape development culture that it's always been at MS, but now since "agile" development is a popular buzzword, they've latched onto that as the excuse for why the OS is perpetually buggy and perpetually beta, with the apparent goal no longer being to create the best desktop OS, but a platform for testing new advertising, marketing and mobile features - even though their mobile division is already dead.

Click to expand...

In reality, you are as clueless about the development culture here as you are rude. You constantly make posts ascribing a weird blend of incompetence and malevolence to everybody here. If you think you could do better, why not get a job here and show us how‽



Yes, there are definitely some issues in the anniversary update, a few that I think the team should have caught before release. But I've been in that position, and I've had to deal with the "why wasn't this caught before release" and "how do we fix it" situations. The answer isn't always easy. Sometimes it's as simple as not having the impacted hardware, other times it's a huge hole in the test matrix, sometimes it's as simple as "we found it, but too late to have a fix ready in time to go out with the other fixes". In some cases, it's because there's no way to gather measurements that indicate an issue and it requires a user encountering the problem to help get a repro. Those measurements are the much-maligned "telemetry", and they are quite useful to help find and quash many issues. Even when an issue is found, also consider the tradeoffs that have to be made for when and how it's fixed. For example, how severe is the issue, how many people does it affect, are there workarounds, how long would it take to write a fix, are there implications to other parts of the system that need to be considered, how much time will it take to adequately verify the fix, et cetera?

Do we screw up? Of course we do! Everyone does. Instead of discouraging us from ever wanting to engage with communities like this one (which almost every one of your posts in this subforum does), how about recognizing that we're also people and that this saying is quite true: "we judge others by [our perception of] their actions, but we judge ourselves by our intentions."

rezerekted said:

Hey Microsoft, try testing on more than one PC in future.

Click to expand...

What do you mean? That's what they do - on all of yours. Consumers are the test platform and then the fixed version is released to Enterprise.

In my experience, I have found that the issue is caused by the Microsoft standard AHCI driver. I ran into this on my FX 8300 / 970 chipset setup and a Lenovo laptop that I just redid from scratch. The only other similarity and is that both have an AData SSD installed in them. Basically, on mine, I used the AMD driver and on the Lenovo laptop, I used the Intel RST driver and that seemed to fix the problem. Hope this helps others who are experiencing the issue as well.

http://answers.microsoft.com/en-us/...e/5a60d75d-120a-4502-873c-8bfec65c82d0?page=1

The systems having problems with the SSD hanging the OS seem pretty random, which is odd. But if it's working for you...

pxc said:

http://answers.microsoft.com/en-us/...e/5a60d75d-120a-4502-873c-8bfec65c82d0?page=1

The systems having problems with the SSD hanging the OS seem pretty random, which is odd. But if it's working for you...

Click to expand...

Since I was able to reproduce the issue on two totally different systems with the only similarity being the same SSD manufacturer, I would guess this might be the more common cause of the problem than not. Works for me and I would guess, it stands a good chance as any to work for others with the same issue.

Edit: You will see an error such as a raid0 reset or cannot write to edb.log file. I have no raid 0 setup but that does not matter, that is what the event viewer error points too. Problems may appear to be random but, more often then not, there is a common underlying issue.

So I haven't had this issue crop up anymore, but then again I haven't played as much Diablo 3. I did turn off the Game DVR as I mentioned before. Before that I tried turning off MSI, the fix that microsoft suggests for those with issues with the AHCI driver. That didn't do anything. I might turn it back on and see if anything changes. Either way, I'll keep monitoring it and let you guys know if anything else changes. Right now I think the DVR nonsense is what caused it.