For example, this sketch will print a large amount of data:
void setup() {
Serial.begin(115200);
}
void loop() {
Serial.println("hello");
}
According to the person who wrote the bug report I linked in my previous reply, if they run a sketch that outputs that volume of data that with Serial Monitor open, it will cause a BSoD within a matter of minutes.
If you upload that sketch to your board and then leave Arduino IDE running with Serial Monitor open (first making sure you don't have any unsaved work that would be lost through a crash), does it cause a BSoD?
Conversely, I would not consider this sketch to print a large amount of data
void setup() {
Serial.begin(9600);
}
void loop() {
Serial.println("hello");
delay(1000);
}
(note the delay was increased to 1000 ms)
That is somewhere in the middle.
Did you have Serial Monitor open in Arduino IDE during that test?
I provided detailed instructions here:
https://github.com/arduino/arduino-ide/issues/2592#issuecomment-2574854418
My approach to writing instructions is to add a step for every single action that needs to be performed, no matter how trivial (because I have found that something I think is obvious may not be to someone else). So even though it looks like a lot of steps, I think you'll find that it is quite simple to accomplish.
Although we haven't received many reports of the BSoD problem. We have received a ton of reports about a different problem with using the recent drivers with specific batches of the "CH340" chips. I use the exact same instructions when supporting all those users (many of whom weren't terribly computer savvy) and nobody has had any problems. So I think you will be fine.
Nice!
I think so. We never received any reports like this before the latest version of the CH340 driver was released. Likewise, people are reporting that the problem only occurs when using the Arduino Serial Monitor; not when using alternative serial terminal applications. So it seems to be a software bug (either with the CH340 driver or with the the "go-serial" Go module used by Serial Monitor), not a problem with the hardware.
Cross that bridge when you come to it.
This will take a couple of minutes as Windows must first automatically reinstall the driver.
