Windows 10: BSOD when Dropbox begins synching

I'm experiencing an issue where Dropbox is causing a complete system crash on Windows10 64 Bit Pro.

I discovered it was Dropbox causing the issue, through trial and error of disabling different start up programs.

I've tried several different versions of the Dropbox App with the same result.

The issue is temporarily resolved by un-installing the and reinstalling the application, but as soon as the machine is rebooted, the issue comes back.

Dropbox support said the issue, was most likely caused by incorrect permissions when the program was installed, I thought this was unlikely to be the case as i'd installed Dropbox on many computers and never had an issue like this,but I followed the guide anyway, but unfortunately the issue has remained.

I've looked at the crash dumps, every time we get this error:

On Wed 9/16/2015 9:58:09 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091615-13890-01.dmp
This was probably caused by the following module: storahci.sys (0xFFFFF801C48B0698)
Bugcheck code: 0xD1 (0x228, 0x6, 0x0, 0xFFFFF801C48B0698)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\storahci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS AHCI Storport Miniport Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

However on one occasion we also had this:

On Wed 9/16/2015 9:58:09 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: b57nd60a.sys (b57nd60a+0x1EC6C)
Bugcheck code: 0xD1 (0x228, 0x6, 0x0, 0xFFFFF801C48B0698)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\b57nd60a.sys
product: Broadcom NetXtreme Gigabit Ethernet Driver
company: Broadcom Corporation
description: Broadcom NetXtreme Gigabit Ethernet NDIS6.x Unified Driver.
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: b57nd60a.sys (Broadcom NetXtreme Gigabit Ethernet NDIS6.x Unified Driver., Broadcom Corporation).
Google query: Broadcom Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




:)

 

Playing mp3 flies from DropBox

New PC. Logged into my Dropbox and files synched. Windows Media Player will not play - just get "encountered problem" message

 

Blue screen error

Hi Flamerec, when you get a BSOD, it should generate MiniDump File(s) in C:\Windows\Minidump

Please copy them to the cloud (OneDrive, DropBox . . . etc.) and post a link here for us to take a look at

This will give us a better idea of what exactly is causing you BSOD's

 

Hi tomwall43,

Welcome to the 10forums.

I have taken a look at a few crashes.
Because I only see that a Windows driver is blamed there are a few possibilities for now.
1. System file problems (missing files, corruption or other problems). To find these problems, they need to be scanned.
2. A 3rd party driver is 'hiding'. To find them, the drivers needs to be stressed out.

Please do the following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

axe0,

Thanks for the reply.

I actually seem to have fixed the immediate issue by re-downloading all the files from scratch...

However, I ran sfc /scannow anyway and still seem to have some corrupted files, please link below:

Dropbox - CBS.log


Thanks

 

The file xwreg.dll and the source are corrupted.

Please try following command in admin command prompt
Code: DISM /Online /Cleanup-Image /RestoreHealth[/quote] If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial

 

Thanks for this.

Unfortunately, I just get the Source files cannot be found error. I've followed the guide and tried everything on there, but I continue to get the same issue even if I specify the source path.

At present there doesn't appear to be any obvious issues with the machine. So I will probably just leave it for the time being!

Thanks for your help.

 

You're welcome *Smile

Be sure to check the tutorial for the In-place Upgrade in case you need it.