[Frank79]

Hallo!

Mein Laptop stürzt seit mehreren Monaten immer wieder zwischendurch ab und zeigt mir vorher noch ´nen BlueScreen. Ich habe im Internet recherchiert und mir über WinDbg das entsprechende Dump-File angeschaut. Nun komme ich nicht weiter. Hat jemand vielleicht mehr Ahnung von der Materie und kann mir zu der Analyse etwas sagen? Das wäre prima!


------------------------------------------------------------------------------------------------------------------


*** ERROR: Module load completed but symbols could not be loaded for vdo_fee-3885.sys
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 805287ae, ef4947ac, 0}



Probably caused by : vdo_fee-3885.sys ( vdo_fee_3885+641 )

Followup: MachineOwner
---------

kd> !analyze -v
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 805287ae, The address that the exception occurred at
Arg3: ef4947ac, Trap Frame
Arg4: 00000000

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




EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.

FAULTING_IP:
nt!wcsstr+4b
805287ae 668b17 mov dx,word ptr [edi]

TRAP_FRAME: ef4947ac -- (.trap 0xffffffffef4947ac)
ErrCode = 00000000
eax=12b31a2a ebx=00006faa ecx=ef5ac5d4 edx=00000076 esi=020dcff8 edi=020de000
eip=805287ae esp=ef494820 ebp=ef494840 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
nt!wcsstr+0x4b:
805287ae 668b17 mov dx,word ptr [edi] ds:0023:020de000=?
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: WINWORD.EXE

LAST_CONTROL_TRANSFER: from ef5ac641 to 805287ae

STACK_TEXT:
ef494824 ef5ac641 020dd0be ef5ac5d4 001392ac nt!wcsstr+0x4b
WARNING: Stack unwind information not available. Following frames may be wrong.
ef494840 8052d571 00000368 00000000 00000000 vdo_fee_3885+0x641
ef494840 7ffe0304 00000368 00000000 00000000 nt!KiSystemService+0xc4
001392f4 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


STACK_COMMAND: kb

FOLLOWUP_IP:
vdo_fee_3885+641
ef5ac641 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: vdo_fee_3885+641

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vdo_fee_3885

IMAGE_NAME: vdo_fee-3885.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4698905b

FAILURE_BUCKET_ID: 0x8E_vdo_fee_3885+641

BUCKET_ID: 0x8E_vdo_fee_3885+641

Followup: MachineOwner
---------

kd> !analyze -v

-----------------------------------------------------------------------------------------------------------

Da steht was von Winword.exe, kann es vielleicht damit zusammen hängen? Danke schon mal vorab für die Mühen, falls sich jemand meiner Nachfrage annimmt.

Gruß, Frank

[Feigling]

PC formatiern und neu installieren. Ob es was bringt da jetzt rum zu pfuschen ist für mich fraglich.

MFG