Crashing problem - minidumps attached

Hi,

Do you de-install the Panda Firewall?

thanks again fir your reply


no i havent yet im somewhat hesitant as its a really good program. i have numerous spyware things which i will take off the system if you think they may be a problem?

it seems the only problem im having now is this 'ntfs.sys' error - what does this mean?

for arguments sake lets imagine the RAM problem was infact the module i removed (as the system is running ok now) but when playing a DVD i get the error message relating to ntfs.sys - what could this problem relate to? is it video drivers maybe?

Hi dudeman,

ntfs error is usually caused by bad ram or ntfs filesystem internal system. Run 'chkdsk /r' to perform the health check of your hard disk.

damn just crashed again. very rare now.

was running itunes and msn and loading something else - the system stopped music, hung for a sec (like always) then rebooted. didnt get BSOD.

mini dump attached - probabaly ram - could both sticks be bad (this one haveing less errors then the other?)

cheers guys

Hi dudeman,

Your latest dump is crashed by memory corruption. Instruction address 804e0877 is corrupted. It caused the recursive program check at instruction address 804e077. Each crash writes a stack and consequently the stack is overflow. Hence windows crashes with stack overflow and it trigger kernerl recovery routine crashes with double fault to break recursive program check loop. This is faulty ram. Replace the ram if you do not feel comfortable.

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
17 errors : !nt (804e0800-804e0940)
804e0820 *1f 23 c9 8b 9f 00 03 00 00 8b 8f 04 03 00 00 0f .#.................
804e0840 *10 0f 23 f3 0f 23 f9 e9 *9d 00 00 00 8d 49 00 8b ..#..#.......I..
804e0850 *95 84 00 00 00 8b 9d 88 *10 00 00 8b 4d 7c 8b 95 ............M|..
804e0860 *90 00 00 00 66 89 45 50 *76 89 5d 30 66 89 4d 34 ....f.EPv.]0f.M4
804e0870 *76 89 55 38 eb 3e 90 66 *d7 44 24 02 00 00 55 53 v.U8.>.f.D$...US
804e0880 *46 57 0f a0 bb 30 00 00 00 8e e3 64 8b 1d 00 00 FW...0.....d.......
804e08a0 *10 83 ec 30 8e d8 8e c0 8b ec f7 44 24 70 00 00 ...0.......D$p..
804e08b0 02 00 75 9b fc 8b 5d 60 *9b 7d 68 89 55 0c c7 45 ..u...]`.}h.U..E...
804e0900 *10 00 0b c0 7e 06 e8 ff *ca ff ff 90 0f 20 d7 80 ....~........ .....
804e0920 *10 02 00 00 0f 84 82 01 00 00 55 8b 45 6c 83 e0 ..........U.El.....
804e0940 *ed 7f 00 00 85 c0 7c 2b 80 3d 29 b5 55 80 00 74 ......|+.=).U..t

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

1: kd> r
eax=001d0036 ebx=00000000 ecx=05e2fed8 edx=001ba068 esi=00000000 edi=0000c1cb
eip=804e0877 esp=bad54008 ebp=7c802530 iopl=0 nv up di pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=003b gs=0000 efl=00010046
nt!KiTrap0E:
804e0877 66d7 xlat
1: kd> dc bad54008 l80
bad54008 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54018 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54028 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54038 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54048 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54058 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54068 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54078 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54088 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54098 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad540a8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad540b8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad540c8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad540d8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad540e8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad540f8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54108 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54118 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54128 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54138 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54148 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54158 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54168 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54178 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54188 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad54198 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad541a8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad541b8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad541c8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad541d8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad541e8 00000000 804e0877 00000008 00010046 ....w.N.....F...
bad541f8 00000000 804e0877 00000008 00010046 ....w.N.....F...

brilliant mate cheers for all that. narrowed it down in the end!


so can i ask why its crashing LESS now i have removed half my RAM? could the other module be worse? im running 512 now was 1024 DDR - why was it more unstable with double the ram?

would be good to know as i am gonna have to buy 2 x 512 rather then just one! i know i should do memory test but can atm

Hi dudeman,

Maybe the memory slot is bad. Do you clean the dust inside the computer cae and the motherboard. One of memory stick may be faulty.

Uh, guys.

What program do i use to open the .dmp files?

Hi,

I use windbg to access the minidmp. Open a new thread if you want to report a new problem.

How can i get those programs to open that