(emphasis mine)JrPickle wrote:This hasn't been solved? ! I have been having random computer freezes after putting my laptop into sleep over the past month.
If the developers can't reproduce it in a reliable manner[1],
- => they can't know what's going on,
- => they can't begin troubleshooting whatever might cause it,
- => they can't begin addressing it,
- => no fix.
- => they can't begin addressing it,
- => they can't begin troubleshooting whatever might cause it,
How do you know for example that this is not an interaction with some other piece of software? And what software might that be? Have you had this appear on a freshly installed Win10 installation for example? And when I sat freshly installed, that includes the OEM drivers/software that comes with the bundles of each OEM. They have been causing problems for example, more problems than you can imagine...
[1]: Yesterday I was testing a newly released test build. It crashed VBoxSVC on exit. Reliably, reproducibly and consistently, under really specific conditions. I keep copies of the previous test builds and I narrowed down the crash between r127414 and r127496, 82 builds in between, which made it easy to narrow and hone in on the mistake. Within 1/2 hour the developers knew about it, reproduced it, and fixed the crash. Within 1 hour there was a new test build, with the error taken care of...