Corrupted error reports are rare....arghhhh

Status
Not open for further replies.

dudeman

Posts: 18   +0
right, i had some problems with my comp a while ago, but have been away travelling - forgot about problems but since comming back i have started to get annoyed again!

everything pointed to RAM so i got some new ram (all compatible) using now and i dont seem to have crashes due to ram (after sending error report) i am now encountering device driver crashes.

this all seem related to video/graphics card to me but i cannot ressolve. i have downloaded latest drivers and reinstalled graphics card but to no avail - except i get a totally new error message entitled 'Corrupted error report'


an anyone help me on this? is it likely i have a duff graphics card?! if so man that is unlucky RAM and graphics?! almost unbelievable......


could the problem be a corrupt installation of windows?!

thanks guys
 
Hi Dudeman,

Your minidump is inaccessible which is the symptom of faulty ram or PSU. Attach the more minidumps here.
 
Surley my new ram is faulty as well?

I dont have a floppy to run a memtest


thanks for looking heres some more mini dumps
 

Attachments

  • dudeminidump.zip
    85.4 KB · Views: 7
Hi,

One of your minidumps has 3 bytes memory corruption. What do you think?


Mini011106-02.dmp
BugCheck 1000000A, {9090ffff, 1c, 1, 804e781a}
Probably caused by : memory_corruption

Followup: memory_corruption
---------
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: 9090ffff, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e781a, address which referenced memory

Debugging Details:
------------------
WRITE_ADDRESS: 9090ffff
CURRENT_IRQL: 1c

FAULTING_IP:
nt!KiSwapThread+65
804e781a a3ffff9090 mov [9090ffff],eax

CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e1c1e to 804e781a

STACK_TEXT:
b9e52cac 804e1c1e 00000000 c0000022 86650198 nt!KiSwapThread+0x65
b9e52cd4 8051baa4 00000001 00000006 86323101 nt!KeWaitForSingleObject+0x1c2
b9e52d4c 804dd99f 00000eac 00000eb4 00000000 nt!NtSignalAndWaitForSingleObject+0x168
b9e52d4c 7c90eb94 00000eac 00000eb4 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
03cbfef0 00000000 00000000 00000000 00000000 0x7c90eb94


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
!chkimg -lo 50 -db !nt
3 errors : !nt (804e7818-804e78f8)
804e7810 00 c6 81 c8 04 00 00 00 *f9 ad a3 ff ff 90 90 90 ...................

804e78d0 90 90 90 90 8b ff 55 8b *fc 51 51 56 8b f1 57 8b ......U..QQV..W....

804e78f0 e8 3b ff ff ff 8b 4e 28 *3b 4e 18 8b 46 2c 1b 46 .;....N(;N..F,.F

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
 
Status
Not open for further replies.
Back