goneout said:
i got errors when I use xp.
it ramdomly restart or i get a blue screen
i have a minidump file can anyone fix this.
please reply..... need to fix this before it becomes worst .......
Hi goneout,
5 of your minidumps have memory corruption. Probably it is overheat within the CPU or m/b. If your PC is not overheat, it is faulty ram.
AGE_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: e1340c84, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bfdba85c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: e1340c84
FAULTING_IP:
nv4_bfdb0000+a85c
bfdba85c ?? ???
MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from 00000000 to bfdba85c
TRAP_FRAME: f844d1f4 -- (.trap fffffffff844d1f4)
ErrCode = 00000000
eax=e1ae54b8 ebx=00001500 ecx=0000005e edx=0000000e esi=e1340c70 edi=00000240
eip=bfdba85c esp=f844d268 ebp=f844d274 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
nv4_bfdb0000+0xa85c:
bfdba85c ?? ???
Resetting default scope
STACK_TEXT:
f844d264 00000000 00000180 e1ae5010 f844d290 nv4_bfdb0000+0xa85c
CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
806b5fa9-806b5faa 2 bytes - hal!KeGetCurrentIrql+a85
[ 00 00:40 38 ]
806b5fad-806b5fae 2 bytes - hal!KeGetCurrentIrql+a89 (+0x04)
[ 00 00:02 10 ]
806b5fb0-806b5fb6 7 bytes - hal!KeGetCurrentIrql+a8c (+0x03)
[ 00 00 00 00 00 00 00:62 50 70 73 df ff 02 ]
806b5fb8-806b5fb9 2 bytes - hal!KeGetCurrentIrql+a94 (+0x08)
[ 00 00:d4 03 ]
806b5fbb-806b5fbc 2 bytes - hal!KeGetCurrentIrql+a97 (+0x03)
[ 00 00:20 79 ]
806b5fbf-806b5fc0 2 bytes - hal!KeGetCurrentIrql+a9b (+0x04)
[ 00 00:30 79 ]
806b5fc3-806b5fc4 2 bytes - hal!KeGetCurrentIrql+a9f (+0x04)
[ 00 00:40 38 ]
806b5fc6-806b5fc8 3 bytes - hal!KeGetCurrentIrql+aa2 (+0x03)
[ 00 00 00:08 06 68 ]
806b5fca-806b5fd0 7 bytes - hal!KeGetCurrentIrql+aa6 (+0x04)
[ 00 00 00 00 00 00 00:62 50 f0 89 df ff 40 ]
806b5fd2-806b5fd7 6 bytes - hal!KeGetCurrentIrql+aae (+0x08)
[ 00 00 00 00 00 00:c4 03 40 10 4d 80 ]
806b5fdb-806b5fdf 5 bytes - hal!KeGetCurrentIrql+ab7 (+0x09)
[ 00 00 00 00 00:10 eb a8 01 01 ]
806b5fe2-806b5fe7 6 bytes - hal!KeGetCurrentIrql+abe (+0x07)
[ 00 00 00 00 00 00:a7 73 04 80 e2 1f ]
806b5feb - hal!KeGetCurrentIrql+ac7 (+0x09)
[ 00:f0 ]
806b5fee-806b5ffa 13 bytes - hal!KeGetCurrentIrql+aca (+0x03)
[ 00 00 00 00 00 00 00 00:30 cd fa 0f 10 73 2c 99 ]
806b5ffc-806b5ffe 3 bytes - hal!KeGetCurrentIrql+ad8 (+0x0e)
[ 00 00 00:02 08 12 ]
63 errors : !hal (806b5fa9-806b5ffe)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .trap fffffffff844d1f4 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE