Bluescreen dropbox und picasa

[wakeboarder]

Hallo,

ich habe leider ständig Bluescreens. Kann mir jemand sagen woran das liegt?

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\111112-27846-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`0328e670
Debug session time: Sun Nov 11 12:36:11.584 2012 (UTC + 1:00)
System Uptime: 0 days 0:47:46.817
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a00ca33ffe, 0, fffff800030bfc65, 0}

*** WARNING: Unable to verify timestamp for fbfmon.sys
*** ERROR: Module load completed but symbols could not be loaded for fbfmon.sys

Could not read faulting driver name
Probably caused by : fbfmon.sys ( fbfmon+330f )

Followup: MachineOwner
---------
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a00ca33ffe, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030bfc65, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f8100
GetUlongFromAddress: unable to read from fffff800032f81c0
fffff8a00ca33ffe Paged pool

FAULTING_IP:
nt!memmove+255
fffff800`030bfc65 4c8b540af0 mov r10,qword ptr [rdx+rcx-10h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: Dropbox.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff8800cec7e80 -- (.trap 0xfffff8800cec7e80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000ff26 rbx=0000000000000000 rcx=fffff8a00da46bb8
rdx=fffffffffefed456 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030bfc65 rsp=fffff8800cec8018 rbp=fffff8800cec8800
r8=000000000000fcec r9=000000000000075d r10=3b46ff263b468109
r11=fffff8a00da3800c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!memmove+0x255:
fffff800`030bfc65 4c8b540af0 mov r10,qword ptr [rdx+rcx-10h] ds:fffff8a0`0ca33ffe=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003070eec to fffff800030c8fc0
STACK_TEXT:
fffff880`0cec7d18 fffff800`03070eec : 00000000`00000050 fffff8a0`0ca33ffe 00000000`00000000 fffff880`0cec7e80 : nt!KeBugCheckEx
fffff880`0cec7d20 fffff800`030c70ee : 00000000`00000000 fffff8a0`0ca33ffe 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4514f
fffff880`0cec7e80 fffff800`030bfc65 : fffff800`033297ae fffff880`0cec8800 fffff8a0`0ad55180 fffffa80`14139010 : nt!KiPageFault+0x16e
fffff880`0cec8018 fffff800`033297ae : fffff880`0cec8800 fffff8a0`0ad55180 fffffa80`14139010 00000000`00000000 : nt!memmove+0x255
fffff880`0cec8020 fffff800`033d8e52 : 00000000`00000000 fffff8a0`0ad55180 fffff8a0`0ad551b0 00000000`0000fd1a : nt!FsRtlNotifyUpdateBuffer+0x5e
fffff880`0cec8070 fffff880`0163c0b5 : fffffa80`06d35290 fffffa80`0a0666a8 fffff880`0cec8468 fffffa80`079f0056 : nt!FsRtlNotifyFilterReportChange+0x626
fffff880`0cec81a0 fffff880`0169b8f5 : fffffa80`00000000 fffff8a0`1a7b7670 00000000`00000000 fffff880`0cec8468 : Ntfs!NtfsReportDirNotify+0xe5
fffff880`0cec8270 fffff880`016bfb83 : fffff8a0`1a7b7990 fffff880`0cec8800 00000000`0000000a 00000000`00000701 : Ntfs!NtfsSetRenameInfo+0xb59
fffff880`0cec8660 fffff880`01631598 : fffffa80`0ec34d80 fffffa80`0a12db80 fffff880`0cec8801 fffff880`0cec8700 : Ntfs!NtfsCommonSetInformation+0x7e3
fffff880`0cec8740 fffff880`01473bcf : fffffa80`0a12df68 fffffa80`0a12db80 fffffa80`0ec34d80 fffff880`0cec8768 : Ntfs!NtfsFsdSetInformation+0x11c
fffff880`0cec87c0 fffff880`014726df : fffffa80`07c119e0 fffffa80`0a92e580 fffffa80`07c11900 fffffa80`0a12db80 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0cec8850 fffff880`023d030f : fffffa80`0b914900 fffff880`00000002 00000000`00000240 00000000`00000000 : fltmgr!FltpDispatch+0xcf
fffff880`0cec88b0 fffffa80`0b914900 : fffff880`00000002 00000000`00000240 00000000`00000000 fffffa80`1005a740 : fbfmon+0x330f
fffff880`0cec88b8 fffff880`00000002 : 00000000`00000240 00000000`00000000 fffffa80`1005a740 00100002`00000002 : 0xfffffa80`0b914900
fffff880`0cec88c0 00000000`00000240 : 00000000`00000000 fffffa80`1005a740 00100002`00000002 fffff880`0cec88e0 : 0xfffff880`00000002
fffff880`0cec88c8 00000000`00000000 : fffffa80`1005a740 00100002`00000002 fffff880`0cec88e0 fffff880`0cec88e0 : 0x240


STACK_COMMAND: kb

FOLLOWUP_IP:
fbfmon+330f
fffff880`023d030f ?? ???

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: fbfmon+330f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: fbfmon

IMAGE_NAME: fbfmon.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d4190ce

FAILURE_BUCKET_ID: X64_0x50_fbfmon+330f

BUCKET_ID: X64_0x50_fbfmon+330f

Followup: MachineOwner

 

[Inzersdorfer]

fbfmon.sys, Lenovo EE Boot Optimizer.
Boote in den abgesicherten Modus (mittels [F8] vor dem Windows boot) und deinstalliere die Anwendung.