This image at https://www.bitsight.com/sites/default/files/2024/07/23/Unique%20IPs%20hourly%20avergae.png https://www.bitsight.com/sites/default/files/2024/07/2

This image at https://www.bitsight.com/sites/default/files/2024/07/23/Unique%20IPs%20hourly%20avergae.png https://www.bitsight.com/sites/default/files/2024/07/23/Uniq... makes a compelling argument that something happened concurrently with the third set of weekday peaks. Although considering how similar each peak was for the first two weeks I would say the divergence was earlier than the dotted line where the short sharp peak appeared. Something happened, the nature of that something might be unrelated to the BSOD crash. Could just be another piece of software doing an update at a different frequency that sometimes changes the timing of the crowdstrike update. You'd need a longer term view of data searching for beat patterns to detect that. If the something was a one-off effect, like admins taking sick days to watch the Euro final, I'm not sure how you could positively identify the cause.