Gå til innhold
Trenger du hjelp med PCen? Still spørsmål her! ×

Hjelp til tolkning av krasjdump?


Anbefalte innlegg

Hei

Bygde nettopp en ny pc som ser ut til å bli grei, men fikk plutselig problemer med at den slo seg av hver gang Win XP pro startet. Analyserte "krasjdumpen" med Win debugg og fikk dette svaret som jeg limer inn til slutt.

Ærlig talt skjønner jeg veldig lite av det, så hvis noen kan se det med et lite blikk hadde det vært flott.

 

Mvh Jom-Jom

 

Could not read faulting driver name

Probably caused by : EIO.sys ( EIO+1b6e )

 

Followup: MachineOwner

---------

 

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

 

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: a8270fee, memory referenced.

Arg2: 00000000, value 0 = read operation, 1 = write operation.

Arg3: 8052b8d0, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 00000000, (reserved)

 

Debugging Details:

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

 

 

Could not read faulting driver name

 

READ_ADDRESS: a8270fee

 

FAULTING_IP:

nt!READ_REGISTER_UCHAR+4

8052b8d0 8a02 mov al,byte ptr [edx]

 

MM_INTERNAL_CODE: 0

 

CUSTOMER_CRASH_COUNT: 12

 

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

 

BUGCHECK_STR: 0x50

 

PROCESS_NAME: ATKKBService.ex

 

LAST_CONTROL_TRANSFER: from b6b93b6e to 8052b8d0

 

STACK_TEXT:

b5da5bc4 b6b93b6e a8270fee b5da5bfc b6b93f49 nt!READ_REGISTER_UCHAR+0x4

WARNING: Stack unwind information not available. Following frames may be wrong.

b5da5bd0 b6b93f49 8a178888 00000004 00000001 EIO+0x1b6e

b5da5bfc b6b9325a 8a178888 830020ec 00000004 EIO+0x1f49

b5da5c40 804ef18f 8a2f1650 00000001 806e6410 EIO+0x125a

b5da5c50 8057f982 8a2ecd60 897eaef8 8a2eccf0 nt!IopfCallDriver+0x31

b5da5c64 805807f7 8a1787d0 8a2eccf0 897eaef8 nt!IopSynchronousServiceTail+0x70

b5da5d00 80579274 000000a8 00000000 00000000 nt!IopXxxControlFile+0x5c5

b5da5d34 8054161c 000000a8 00000000 00000000 nt!NtDeviceIoControlFile+0x2a

b5da5d34 7c90e4f4 000000a8 00000000 00000000 nt!KiFastCallEntry+0xfc

0087f3b8 00000000 00000000 00000000 00000000 0x7c90e4f4

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

EIO+1b6e

b6b93b6e ?? ???

 

SYMBOL_STACK_INDEX: 1

 

SYMBOL_NAME: EIO+1b6e

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: EIO

 

IMAGE_NAME: EIO.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 448fa23c

 

FAILURE_BUCKET_ID: 0x50_EIO+1b6e

 

BUCKET_ID: 0x50_EIO+1b6e

 

Followup: MachineOwner

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!

Start en konto

Logg inn

Har du allerede en konto? Logg inn her.

Logg inn nå
×
×
  • Opprett ny...