webForumDet fria alternativet

Någon som vågar debugga

2 svar · 221 visningar · startad av mayday

maydayMedlem sedan aug. 20003 473 inlägg
#1

Altså kan ej förstå vad som e fel

nån som kan hjälpa till

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {ff00f980, ff, 1, 804e383c}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ff00f980, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e383c, address which referenced memory

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

WRITE_ADDRESS: ff00f980

CURRENT_IRQL: ff

FAULTING_IP:
nt!KeUpdateSystemTime+ff
804e383c 8903 mov [ebx],eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 0040c1f7 to 804e383c

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:
f5322d64 0040c1f7 badb0d00 00a30040 f3434d98 nt!KeUpdateSystemTime+0xff
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012daa4 00000000 00000000 00000000 00000000 0x40c1f7

STACK_COMMAND: dds @$csp ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
804e30e4-804e30e7 4 bytes - nt!KiServiceTable+3c4
[ 8f 60 66 80:b0 c0 69 f7 ]
4 errors : !nt (804e30e4-804e30e7)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

legisMedlem sedan juli 20044 453 inlägg
#2

Vild gissning. korrupt minne eller korrupt processor. Vissa Intel-processorer har en bugg som kan orsaka liknande problem.

maydayMedlem sedan aug. 20003 473 inlägg
#3

testat både minne o cpu
samt kör amd 3200+

131 ms totalt · 3 externa anrop · v20260731065814-full.beb2e261
0 ms — hämta forumlista (cache)
0 ms — hämta statistik (cache)
128 ms — hämta tråd, inlägg och bilagor (db)