Okay, a blue screen (likely a crash/reboot loop) coupled with the boot log you provided, and your mention of "painless mesh," points to some likely causes:
1. Memory Issues (Most Likely):
Painless Mesh's memory requirements: Painless Mesh, especially with larger networks, can be memory-intensive. The "ho 8 tail 4 room 4" line, while not definitively diagnostic, could indicate memory management issues.
Heap fragmentation: Repeated allocations and deallocations of memory can lead to fragmentation, where there's free memory, but not in contiguous blocks large enough for the application's needs.
Stack overflow: If your code has deep recursion or allocates large local variables on the stack, it can overflow, causing a crash.
Heap overflow: If your code writes beyond the allocated bounds of a memory block, it can corrupt the heap, leading to unpredictable behavior and crashes.
Insufficient RAM: The ESP devices do not have a lot of ram, and it is easy to use it all.
2. Painless Mesh Configuration Problems:
Incorrect network settings: If your mesh network settings (e.g., SSID, password, port) are incorrect or conflicting, it can lead to instability.
Too many nodes: If you're trying to create a mesh network with too many nodes for your hardware, it can overload the system.
Conflicting libraries: Ensure that you are not using any other libraries that are conflicting with painless mesh.
Incorrect version: Make sure that you are using the correct version of the painless mesh library.
3. Code Issues:
Null pointer dereferences: If your code tries to access memory through a null pointer, it will cause a crash.
Infinite loops: If your code gets stuck in an infinite loop, it can prevent the system from responding and eventually lead to a crash.
Interrupt conflicts: If multiple interrupts are trying to access the same resources, it can lead to conflicts and crashes.
Incorrect data types: Using incorrect data types can cause unexpected behavior and crashes.
Troubleshooting Steps:
Simplify your code:
Start with the most basic Painless Mesh example code.
Remove any unnecessary code, libraries, or features.
This helps isolate the problem.
Check memory usage:
Use the ESP.getFreeHeap() function to monitor the available heap memory.
Add debug print statements to track memory usage at critical points in your code.
Reduce mesh complexity:
If you're using a large mesh network, try reducing the number of nodes.
Simplify your network topology.
Update libraries:
Ensure that you're using the latest version of the Painless Mesh library.
Update your ESP32/ESP8266 board definitions in the Arduino IDE.
Serial debug:
Add extensive serial print statements to your code to track the execution flow and identify where the crash occurs.
If you can get any output before the crash, that will be very valuable.
Check for memory leaks:
Make sure that every time you use malloc() or new, you also use free() or delete when you are done.
Check for large local variables:
If you are creating large arrays or other large variables inside of functions, consider making them global or using dynamic memory allocation.
Verify your board and wiring:
If you are using external hardware, verify that it is wired correctly.
Ensure that your ESP board is functioning correctly.
Example Code:
When asking for help, provide the code that is producing the error. That will greatly increase the ability for others to help you.
You've got some kind of Windows software problem... No matter what the ESP32 does, it cannot crash Windows. I suspect perhaps something along the lines of COM port busy or unavailable.
it is something with the board. make sure you press the rst button while opening the serial monitor and try again! if it still blue screens, I will be happy to help