After updating to .393 (from .379) I had two BSODs yesterday, though I also installed some Windows Updates too and am unsure if it was that or CloudDrive that triggered them. No drives were attached at the time of either crash. I'll upload the memory dump from the second BSOD in a bit - unfortunately it overwrote the dump of the first BSOD. The second one was a CLOCK_WATCHDOG_TIMEOUT - I didn't note what the first one was, though IIRC it was different.
*edit* The first BSOD was defiantly Windows Update related, and not CloudDrive, as I can reproduce it. The second one though I'm still not sure of.
Question
thnz
After updating to .393 (from .379) I had two BSODs yesterday, though I also installed some Windows Updates too and am unsure if it was that or CloudDrive that triggered them. No drives were attached at the time of either crash. I'll upload the memory dump from the second BSOD in a bit - unfortunately it overwrote the dump of the first BSOD. The second one was a CLOCK_WATCHDOG_TIMEOUT - I didn't note what the first one was, though IIRC it was different.
*edit* The first BSOD was defiantly Windows Update related, and not CloudDrive, as I can reproduce it. The second one though I'm still not sure of.
Edited by thnzLink to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.