I think folks have to be grown up about the Insider Program.
There Are Fast, Slow and Preview rings, and the ability to stop altogether or take a timeout, and if you have started to understand how the update process works, various ways to delay or prevent installations of new builds. So much is under control of the user.
You are under no obligation to send feedback, although it can help you to report your problem, and send system information at the instance your problem occurs, together with a screenshot of what your see.
However user feedback only reports the outward signs of a problem, and the reporting is subjective, and often imprecise because the observers are not in full knowledge of the underlying systems and problems.
Just by running the Previews on your devices, Windows Error Reporting is sending telemetry back to Microsoft, and in the case of problems "under the hood" - equivalent to auto engine misfires - the presence of known bugs and the way their presence is shown, on systems that are made up of different components shows the developers how to write bulletproof code.
There was a Sysinternals utility called NotMyFault, which could be called to crash the system at will - thus presenting a BSOD and crashdump on demand.
No doubt some of the bugs in Preview builds are there in order to create snapshots of processes that are not always behaving as expected, and the WER telemetry will allow observation of these processes at their point of failure.
The Insider's program is not for everyone--it is not a consumer-release update channel! Inside the the Insider's, the "fast channel" is not for everyone, all the time--but there's a "slow channel" if you are adverse to petty and annoying bugs. Microsoft has spelled this out since day 1 and I am surprised to see folks still confused about it.
From 10/1/2014 I was on the fast channel until the 1607 consumer, retail release. I'm taking a much-needed break from the whirlwind...! For awhile. I'll get back on the Fastlane when something more interesting develops...
Seriously, though, if you are not into bugs--and sometimes annoying, frustrating, hair-pulling bugs--then drop down to the slow channel. And if that is still too risque and wild for you, drop out of the Insider's program altogether. Stick with 1607 and the regular 1607 retail cumulative updates until such time as you feel you might want to start beta testing again. If you feel like an "unpaid bug tester" for Microsoft then it is clearly time for you to get out of the Insiders program altogether, imo, because you are mistaking this beta-testing program with Microsoft's regular consumer-level retail releases. A lot of people seem to think that being in the Insider's is what you have to do to run Windows10! The two are *not* related.
^^ Very well put!! The key thing is not everyone is cut out for beta testing an OS. It can be trying and nerve wrenching.
Picture a conversation between Sergio Marchionne and Mario Andretti:
"Hey Mario, why don't you come on over and check out our latest Ferrari Spider build. It's totally new and has a bunch of the latest features that folks will go mad for!
One thing though, we realize that the windows won't roll up and we're not sure if the wheels will fall off or not, but, why don't you try it out for a couple weeks and tell us what you think"?
"Ah..., naw! Tell you what; you get those issues remedied and I'd be glad to take it for a spin"
(I'm sure you get the point!)
Edwin, I don't get your point, or rather I don't agree with it: Windows 10 Insider builds have some minor bugs but nothing that can be compared for a car losing its wheels.