Błąd 0xc0000005. Prosze o pomoc


(Nowy Kuba) #1

Wczoraj przesadziłem z OC karty graficznej co doprowadziło do zawieszenia komputera. Po restarcie pojawił mi się taki komunikat "Aplikacja nie została właściwie zainicjowana (0xc0000005). Kliknij na przycisk OK, aby zakończyć aplikację." Problem w tym że okienko wyskakuje przy wszyskich programach 32-bitowych. Mam viste Home Premium 64-bit. Próbowałem przywrócić system do wcześniejszego stanu ale nie pomogło.

Z góry dziękuję za pomoc.


(Dom@) #2

Podaj odczyt z pliku DMP. Instrukcję, jak to zrobić znajdziesz tu: http://www.hotfix.pl/articles.php?article_id=17


(Nowy Kuba) #3

Microsoft ® Windows Debugger Version 6.10.0003.233 AMD64

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612

Machine Name:

Kernel base = 0xfffff8000221f000 PsLoadedModuleList = 0xfffff800023e4db0

Debug session time: Sun Dec 21 16:23:42.476 2008 (GMT+1)

System Uptime: 0 days 0:00:16.194

Loading Kernel Symbols

...............................................................

.............................

Loading User Symbols

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E4, {1, fffffa8004be2fd8, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+949a )

Followup: MachineOwner


0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

WORKER_INVALID (e4)

A executive worker item was found in memory which must not contain such

items or a work item was queued that is currently active in the system.

Usually this is memory being freed. This is usually caused by

a device driver that has not cleaned up properly before freeing memory.

Arguments:

Arg1: 0000000000000001, Queuing of active worker item

Arg2: fffffa8004be2fd8, Address of worker item

Arg3: 0000000000000000, Queue number

Arg4: 0000000000000000, 0

Debugging Details:


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xE4

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800022c7771 to fffff80002274350

STACK_TEXT:

fffff800033eda28 fffff800022c7771 : 00000000000000e4 0000000000000001 fffffa8004be2fd8 0000000000000000 : nt!KeBugCheckEx

fffff800033eda30 fffff8000227c8b3 : fffff800033edcc8 0000000000000000 fffff800033edad8 0000000000000000 : nt! ?? ::FNODOBFM::`string'+0x949a

fffff800033eda70 fffff8000227d238 : fffff800033edcd0 fffffa8004216502 fffff800033edcc8 fffffa6000000001 : nt!KiTimerListExpire+0x333

fffff800033edca0 fffff8000227da9f : 000000266e1176e7 0000000000000000 fffffa8000000001 fffff80002396a80 : nt!KiTimerExpiration+0x1d8

fffff800033edd10 fffff8000227eb62 : fffff80002393680 fffff80002393680 0000000000000000 fffff80002398b80 : nt!KiRetireDpcList+0x1df

fffff800033edd80 fffff8000244c5c0 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x62

fffff800033eddb0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!zzz_AsmCodeRange_End+0x4

STACK_COMMAND: kb

FOLLOWUP_IP:

nt! ?? ::FNODOBFM::`string'+949a

fffff800`022c7771 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+949a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

FAILURE_BUCKET_ID: X64_0xE4_nt!_??_::FNODOBFM::_string_+949a

BUCKET_ID: X64_0xE4_nt!_??_::FNODOBFM::_string_+949a

Followup: MachineOwner


Mam nadzieje że to to co potrzeba.