Crashing problem - minidumps attached

Status
Not open for further replies.

dudeman

Posts: 18   +0
Hi there - I have been having so many problems with my computer, every time I send an error report it says its something different!


please can someone help me!

thanks!
 

Attachments

  • minidumps.zip
    89.8 KB · Views: 5
Hi dudeman,

The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
 
wow that was quick! thanks for that.

the ram module is 184 pin and the other slots are larger. can i run my ram on only one stick? thought two sticks had to be in.

one stick is probalay faulty - its it likely to be the CPU temp? how do i check this? in my device manager there are two processors installed but i only have one - could this be a problem?

also how do i change the ram speed

sorry im a noob - shall i just put new ram in and hope for the best?!!
 
Hello and welcome to Techspot.

Your latest minidump is from 7/10/05. does this mean that your computer has not crashed since then?

Your minidumps are crashing with various culprits, including your antivirus programme, and msn messenger.

Go HERE and follow the instructions for testing your ram.

Regards Howard :wave: :wave:
 
sorry these are more recent.

i use panda antivirus - is this know to cause this? could it be my video card as i have read on these forums so many times?!


why would MSN cause crash surely that isnt badly written!?
 
Hi,

Open a new thread for new problem. The symbol is not resolved, You had better attach the minidumps to the new posts.
 
Hi Dudeman,

One minidump has 3874 memory errors. Probablly the paging space is corrupted. Remove the current paging space and allocate a new paging space.
 
Right guys i took out one 512 stick and the system was fine - stable i could run programs like itunes without it crashing as it did previously.

i watched dvd today for about 40 mins and i got BSOD again :( said the file was ntfs.sys that caused the problem.

im not sure how to change pageing space - please help you guys have been real helpful so far!


attached is lastest minidump


btw i had to moce graphic acceleration up to full for DVD full screen cos i took it down as i thought i might have been the problem a while back!
 
The latest dump has one bit memory corruption at module ntfs. It is faulty memory. Failed memory hardware includes memory modules, Level 2 (L2) SRAM cache of CPU, or video adapter RAM.

Suggestion
1. De-install Panda Firewall and install sygate firewall
2. Check your your ram is incompatible with the m/b
3. Install Prime 95 to stress test the CPU
http://www.mersenne.org/freesoft.htm
Mini103105-01.dmp BugCheck 10000050, {aa3da8c0, 0, f839fa9b, 0}
Probably caused by : memory_corruption
STACK_TEXT:
ba3da9a0 f839fd83 ba3da9bc 817e7e00 8235e648 Ntfs!NtfsCommonCleanup+0x1bf2
ba3dab18 804e13d9 8218d020 817e7e00 8234e278 Ntfs!NtfsFsdCleanup+0xcf
ba3dab28 f8422bbf 81899558 817e7e00 ba3dab94 nt!IopfCallDriver+0x31
ba3dab38 804e13d9 8235e590 817e7e00 81ee80d8 sr!SrCleanup+0xb3
ba3dab48 baeb1742 818997c0 817e7fd8 81ee80d8 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
ba3dab94 baeb330f 81ee8020 817e7e00 81899558 pavdrv51+0x3742
ba3dabec 804e13d9 81ee8020 817e7e00 817e7e00 pavdrv51+0x530f
ba3dac64 804e13d9 8172a610 8172a730 817e7e00 nt!IopfCallDriver+0x31
ba3dac74 8057c627 81696a60 823ebca0 00000001 nt!IopfCallDriver+0x31
ba3daca4 8056e943 81a25560 8172a610 00120089 nt!IopCloseFile+0x26b
ba3dacd4 8056ea96 81a25560 01696a60 823ebca0 nt!ObpDecrementHandleCount+0x11b
ba3dacfc 8056e9bc e2369c60 81696a78 00000334 nt!ObpCloseHandleTableEntry+0x14d
ba3dad44 8056ea06 00000334 00000001 00000000 nt!ObpCloseHandle+0x87
ba3dad58 804dd99f 00000334 00e7f29c 7c90eb94 nt!NtClose+0x1d
ba3dad58 7c90eb94 00000334 00e7f29c 7c90eb94 nt!KiFastCallEntry+0xfc
00e7f29c 00000000 00000000 00000000 00000000 0x7c90eb94

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
f839faa0 - Ntfs!NtfsCommonCleanup+1bf7
[ ff:ef ]
1 error : !Ntfs (f839faa0)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption

Mini100305-01.dmp BugCheck 93, {82e, 0, 0, 0}
Probably caused by : nvcap.sys ( nvcap+5599 )
 
thnaks for your reply.

how can i check this out? i havent been able to do a mem test yet (i dont have a floppy) and the bootable cdrom thing didnt work.

specs

P4 3.4 ghz 3400mhz
L2 Cache 1024
RAM 512 (normally 1024)
mobo 775Dual-800 pro (Asrock i think)
200 gig HDD

why is it only crashing now on DVD playback where before it could be at anytime?? maybe both ram modules are bust - the other one having more errors than this one?

whats with the ntfs.sys messages? what is this system file?


thanks
 
right i ran prime95 for 20 hours no faults found - what does this mean?


still no crashes, but havent tried DVD yet. Computer has been on over 24 hours and hasnt crashed - normally would have 100s of times. sinbce removeing one stick of RAM its been ok (expect when playijng DVDs)
 
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...
 
Status
Not open for further replies.
Back