superka

I don't have any info on this other than to say that I am not experiencing these issues, and that I haven't experienced any blue screens related to those settings. That user isn't suggesting a rollback, they're suggesting that you edit the advanced settings to force your drive to convert to the newer hierarchical format.
I should also note that I do not work for Covecube--so aside from a lot of technical experience with the product, I'm probably not the person to consult about new issues. I think we might need to wait on Christopher here. My understanding, though, was that those errors were fixed with release .1314. It presumes that existing data is fine as-is, and begins using a hierarchical structure for any NEW data that you add to the drive. That should solve the problem. So make sure that you're on .1314 or later for sure.
Relevant changelog:
.1314 * [Issue #28415] Created a new chunk organization for Google Drive called Hierarchical Pure. - All new drives will be Hierarchical Pure. - Flat upgraded drives will be Hierarchical, which is now a hybrid Flat / Hierarchical mode. - Upgrading from Flat -> Hierarchical is very fast and involves no file moves. * Tweaked Web UI object synchronization throttling rules. .1312 * Added the drive status bar to the Web UI. .1310 * Tuned statistics reporting intervals to enable additional statistics in the StableBit Cloud. .1307 * Added detailed logging to the Google Drive migration process that is enabled by default. * Redesigned the Google Drive migration process to be quicker in most cases: - For drives that have not run into the 500,000 files per folder limit, the upgrade will be nearly instantaneous. - Is able to resume from where the old migration left off.  

Awesome, glad to hear it! 
For all of this: 
https://stablebit.com/Support/CloudDrive/Manual?Section=I/O Performance
The reason that my suggestion worked is that it's less threads grabbing much more data. That means a bit more latency (since it's waiting on more data, at once), but there is less overhead (HTTP, REST or other API calls, basically).  And the Prefetch Time Window is the ... window for the trigger to occur. You want smaller here, so that it only prefetches on larger, sequential reads. 
For the upload threshold, this stops uploads from happening if data is still being written.  This means that uploads should happen less often, but should get whole chunks of data, rather than uploading the same chunk (or parts of the same chunk) again and again, wasting API calls, basically.  So, this is an optimization, and should be fine at it's default.