We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Blue Screen of Death on Win10
Good morning.
Apologies for the very vague question. We are running Dropbox on 2 Win10 PCs. One runs absolutely fine but, on the other, it will run for maybe 30 seconds and then cause the PC to crash with a Blue Screen of Death.
Could you provide any advice on how I can go about determining what the conflict is that causes this to occur please?
If it's any help, Dropbox will not launch automatically on that PC - it must always be executed manually even though it's setup to launch on Computer start in the Dropbox settings.
Without Dropbox running the PC runs perfectly.
There are a great deal of applications installed on that PC so I'm reluctant to wipe & reinstall everything if there's a solution out there that doesn't require doing so.
This PC also experiences the issue of the browser not refreshing as described in this post here: https://www.dropboxforum.com/t5/Missing-files-folders/Webpage-folder-not-refresh/m-p/322934#M15542. Chrome auto updates so that shouldn't be the issue. I'll follow the other suggestions in that post to see if I can resolve that issue. It seems strange, and probably just coincidence, that this one PC suffers from these two problems but it may be useful for you to know.
Thank you in advance for any assistance.
Jason.
Hey everyone, we have a little update to share with you all!
We've been in contact with Symantec and they've let us know that there is an update which should resolve the BSoD. This would be version 15.1 MP1 (Maintenance Patch 1) for the Endpoint Protection Client.
ScubaStephen and gojanpaolo, along with anyone else who may be running an older version of Symantec, please try updating to see if this does the trick for you.
If you still get the BSoD with the updated version of Symantec, then please reach out to them directly for their support for resolution.
Keep us posted with your results!
- Rich
Super User II
FadedPoppy wrote:
Could you provide any advice on how I can go about determining what the conflict is that causes this to occur please?
There will be an stopcode and probably the faulting file listed on the blue screen. Get those and do a Google search for them. I believe Windows 10 also includes a QR code on a blue screen. Scan that with your phone and it should take you to a page with information about the error.
Hi Rich,
Thank you for the information. I've been experiencing this for many months and forgot that I did as you said way back when and wasn't able to make any headway. The Stop Code is: CRITICAL_PROCESS_DIED. There is no additional hexadecimal code. When I scan the QR Code I'm taking to a troubleshooting page but I recall this wasn't much help. I had previously uninstalled & reinstalled Dropbox and the problem occurred again.
Thank you again if you had any other guidance on what I can do short of uninstalling/reinstalling Dropbox. Are there any known conflicts with other applications? Both our PCs have pretty much the same setup but the problematic PC also has Visual Studio.
Thank you,
Jason.
- Rich
Have you checked the Application and System event logs in Windows' Event Viewer?
Office 360, Outlook, and Excel try to restore access to files in use last time. If those files are also in the dropbox folder there MIGHT be a drain on resources that cause <youknowwhat> while Dropbox tries to sync the same files. Try letting dropbox start after the others are done.
I don't think this is the case in my situation because, try as I might, I cannot get Dropbox to start upon PC boot. As such I have to launch it manually and invariably this is done some time after the PC has booted so I would expect any such syncing to have completed before I attempted to do this.
I don't know if the inability of Dropbox to auto launch is related to the BSoD. Is Dropbox auto launching for any other users that are experiencing BSoD?
Jason.
My issue is definitely related to Dropbox opening upon start. As soon as dropbox starts up, I get the BSoD. Once I disabled dropbox from starting upon startup, my computer stopped crashing. I even tried uninstalling and reinstalling dropbox and that hasn't helped. I also tried manually starting dopbox after the start sequence and got the BSoD immediately.
I'd love to know if there is a solution in the works. I rely on dropbox working for my workflow and not having it synced on my work computer is a big inconvenience. Thanks!
We have 3 computers in my office running dropbox with symantec. We have a corporate IT department. 2 of the computers kept crashing getting the BSOD. 1 computer has yet to crash. The 2 computers that were having trouble crashed within a minute of start up when it started to sync. We found a corupt file in dropbox that was the reason for crashing. When we tried to open the file it says it was corupt. To solve we had drop box shut off and deleted the file out of drop box then restarted the computer and dropbox would sync. Now we are having problems with the file reappearing again not staying deleted. We deleted old devices that might be causing an issue but the file keeps showing up after we delete. When that file shows up it tends to cause a BSOD on those 2 computers.
- Daphne
Dropbox Staff
Hey wildman83, thanks for reaching out to us here!
We recently had an update about BSoD with those using Symantec on their devices, when you have a moment, please check out this post here.
For the issue with the reappearing file, can you check the file history of the files to see which device it was added back from?
Let me know what you find!
@wildman83
How did you find the corupt file?
I have this issue since November with no resolution.
Thank you
PatrikOne of the guys got lucky and noticed that it was trying to resync some files. We went looked at those and noticed they were corupt. Once we got rid of those we could get dropbox to work some. We are still having issues now on one computer again that just started today with it today in getting the BSOD. Its a different error this time, not the kernal error from before.
