RAM problem?

warez · 10-09-2006, 08:29 AM

Hi there,i have some weird problem with my system but i'm not too sure whether is Ram problem or Ram slot problem or m/b problem.My problem is i'm using some software but it come out "Access Violation" error and then say "Check Your Memory!" so i try to test my RAM by using Memtest86+ but what i get is Pass without any error,so now i have no idea what cause the problem,please help.

My system is.
P3 Tualatin 1.13GHz
M/B Asus TUSL2-C
Ram 128-128-256

Bios setting for RAM is default and didn't do any overclock.

*Bofinn* · 10-09-2006, 10:18 AM

what software are you running to cause this error?

Try removing the two 128MB sticks and see if the error goes away.

warez · 10-09-2006, 10:50 AM

That's japanese software.
I have try remove the two 128 sticks and only plug the 256 on slot 1,2 and 3 but the errors still there.

h20-ski · 10-09-2006, 11:23 AM

How many passes did Memtest run before you quit? Anything less than 32 is not testing all of your ram.

warez · 10-09-2006, 11:37 AM

I just let it run 2 pass,but the 256 RAM is just new so it should not having problem right?
Anyway what's the diffrent between Memtest86 and Memtest86+?

h20-ski · 10-09-2006, 11:49 AM

I myself have not ever received a bad stick of ram, but I have had my ram go bad more than once.
Memtest 86+ is where the creator of Memtest 86 left off. Memtest 86 was built by one person. After he quit the project he made the source code open source. So 86+ is the version that you would want to run.

warez · 10-09-2006, 11:56 AM

Ok,will take some times to test my ram then.So you recommend me test by using the latest memtest86+ right.Anyway i'm using the program quite long time and it have no problem with it,but then the problem suddenly come out and i have try plug the new 256 ram slot by slot to test it but the result is 3 slot also giving me the problem but that's new ram so i feel weird and i have no idea why it like that and the error come out like "Access Violation" "Check Your Memory!" "ntdll.dll" "This Means Memory Leaks" and something like address error.

Now i really not sure whether is Ram problem or slot itself or even m/b itself.
Want to know how long should i run the ram test?

h20-ski · 10-09-2006, 03:19 PM

Wait which version are you using, the Windows version or the bootable version from here. I would suggest using the one from the link.

warez · 10-09-2006, 03:26 PM

I'm currently using memtest86+ bootable version,that's same as your suggestion,so how long should i test?

Updated with the error log,take a look.

Quote:

Exception: EAccessViolation TFinderClient. Check your memory! Access violation at address 7C918522 in module 'ntdll.dll'. Read of address 02C166A0
Exception: EAccessViolation Critical Error! Report hurry! Code=2. Access violation at address 7C918522 in module 'ntdll.dll'. Read of address 02C166A0

*Bofinn* · 10-09-2006, 03:49 PM

I would test with all your modules installed. I usually test for a couple of hours. But as stated above - next time I'll do 32 passes...

GWillakers · 10-09-2006, 05:09 PM

Your error log looks more like a programming error.. then a hardware error...

The program is trying to access a piece of memory it doesn't own...
the hardware doen't let it and throws an exception...

Program is bad... not the memory

Memory errors are sporadic in nature...

This software that constantly gives you the error... how old is it.
Did it run under Windows 3.1? ie is it 16-bit?

h20-ski · 10-09-2006, 06:22 PM

As far as I know Memtest does not use any .dll files. That is why I was asking if you where using the Windows version. And it should work as I have used it in a 233 P2 machine.

warez · 10-10-2006, 02:10 AM

@GWillakers

That program not too old and i have google around with the error log but the result is only few people having such problem and from their readme file it say "If an Access Violation happens, check that your PC's memory and other hardware does not have problems."I'm not too sure whether this is 16-bit but i'm running it with WinXP Pro with SP2,anyway this program only works with "Windows 2000 SP4 and above Windows XP" take from their readme file.

@h20-ski

No,i'm not using windows version but bootable version.

warez · 10-11-2006, 04:00 AM

Any idea guys?

h20-ski · 10-11-2006, 11:41 AM

Warez, I find it interesting that the readme say that it needs 2000 or Xp to run, as Memtest is OS dependent. And if you are running XP your system is 32bit.

I have looked on the Memtest forum to find that that crash may be caused by the BIOS not mapping the memory correctly and then Memtest goes to test it, but it can not read/write to that area because the BIOS has it locked. They said one way to try and fix the error is to temporarily disable all non-essential options as that may not use the memory that causes the failure.

10-09-2006, 08:29 AM	#1
warez Registered User Join Date: Oct 2006 Posts: 9	RAM problem? Hi there,i have some weird problem with my system but i'm not too sure whether is Ram problem or Ram slot problem or m/b problem.My problem is i'm using some software but it come out "Access Violation" error and then say "Check Your Memory!" so i try to test my RAM by using Memtest86+ but what i get is Pass without any error,so now i have no idea what cause the problem,please help. My system is. P3 Tualatin 1.13GHz M/B Asus TUSL2-C Ram 128-128-256 Bios setting for RAM is default and didn't do any overclock.
(Offline)

10-09-2006, 10:18 AM	#2
Bofinn I'm gettin' dizzy! Join Date: Jan 2004 Location: Chicagoland Posts: 11,035	what software are you running to cause this error? Try removing the two 128MB sticks and see if the error goes away. __________________ ---------- JimBo ----------- When in doubt, smack it!
(Offline)

10-09-2006, 10:50 AM	#3
warez Registered User Join Date: Oct 2006 Posts: 9	That's japanese software. I have try remove the two 128 sticks and only plug the 256 on slot 1,2 and 3 but the errors still there.
(Offline)

10-09-2006, 11:23 AM	#4
h20-ski Forget Wakeboarding Join Date: May 2004 Location: Texas Posts: 2,460	How many passes did Memtest run before you quit? Anything less than 32 is not testing all of your ram. __________________
(Offline)

10-09-2006, 11:37 AM	#5
warez Registered User Join Date: Oct 2006 Posts: 9	I just let it run 2 pass,but the 256 RAM is just new so it should not having problem right? Anyway what's the diffrent between Memtest86 and Memtest86+?
(Offline)

10-09-2006, 11:49 AM	#6
h20-ski Forget Wakeboarding Join Date: May 2004 Location: Texas Posts: 2,460	I myself have not ever received a bad stick of ram, but I have had my ram go bad more than once. Memtest 86+ is where the creator of Memtest 86 left off. Memtest 86 was built by one person. After he quit the project he made the source code open source. So 86+ is the version that you would want to run. __________________
(Offline)

10-09-2006, 11:56 AM	#7
warez Registered User Join Date: Oct 2006 Posts: 9	Ok,will take some times to test my ram then.So you recommend me test by using the latest memtest86+ right.Anyway i'm using the program quite long time and it have no problem with it,but then the problem suddenly come out and i have try plug the new 256 ram slot by slot to test it but the result is 3 slot also giving me the problem but that's new ram so i feel weird and i have no idea why it like that and the error come out like "Access Violation" "Check Your Memory!" "ntdll.dll" "This Means Memory Leaks" and something like address error. Now i really not sure whether is Ram problem or slot itself or even m/b itself. Want to know how long should i run the ram test? Last edited by warez : 10-09-2006 at 12:14 PM.
(Offline)

10-09-2006, 03:19 PM	#8
h20-ski Forget Wakeboarding Join Date: May 2004 Location: Texas Posts: 2,460	Wait which version are you using, the Windows version or the bootable version from here. I would suggest using the one from the link. __________________
(Offline)

10-09-2006, 03:49 PM	#10
Bofinn I'm gettin' dizzy! Join Date: Jan 2004 Location: Chicagoland Posts: 11,035	I would test with all your modules installed. I usually test for a couple of hours. But as stated above - next time I'll do 32 passes... __________________ ---------- JimBo ----------- When in doubt, smack it!
(Offline)

10-09-2006, 05:09 PM	#11
GWillakers Registered User Join Date: Sep 2006 Posts: 176	Your error log looks more like a programming error.. then a hardware error... The program is trying to access a piece of memory it doesn't own... the hardware doen't let it and throws an exception... Program is bad... not the memory Memory errors are sporadic in nature... This software that constantly gives you the error... how old is it. Did it run under Windows 3.1? ie is it 16-bit? __________________ SuperMicro P4DC6+ Dual Pentium XEON 1.7GHz {I was thinking bandwidth, PCI-X, SCSI etc, Turned out to be louder than my electric razor. Taught me to pay attention to heat and noise. Intel D875PBZ-204 - P4/2.53GHz/512K/533Mhz Rock solid system - the type where Intel makes you a believer ASUS A8N-VM CSM AMD 3500+ Venice {Heard all the trash talk on the Net. Wanted first hand experience before challenging AMD fanboys. What I found was, my AMD 3500+ was cooler and a bit faster than my 2.53GHz P4, but the Intel system was much more dependable. Intel D975XBX-305 E6600 SL9S8 2.4GHz/4MBL2/1067FSB/default Voltage Antec P180 case/Antec Phantom 500 PSU/AC cooler 7 Pro. Crucial DDR2 667 ECC 2x512MB SPD 5-5-5-15 /74GB Raptor / 2x WD 500GB in Intel Matrix Raid / 1TB Seagate / PNY GeForce 7600 GS / Vista Ultimate SP1 installed on 128K striped drive Last edited by GWillakers : 10-09-2006 at 05:26 PM.
(Offline)

10-09-2006, 06:22 PM	#12
h20-ski Forget Wakeboarding Join Date: May 2004 Location: Texas Posts: 2,460	As far as I know Memtest does not use any .dll files. That is why I was asking if you where using the Windows version. And it should work as I have used it in a 233 P2 machine. __________________
(Offline)

10-10-2006, 02:10 AM	#13
warez Registered User Join Date: Oct 2006 Posts: 9	@GWillakers That program not too old and i have google around with the error log but the result is only few people having such problem and from their readme file it say "If an Access Violation happens, check that your PC's memory and other hardware does not have problems."I'm not too sure whether this is 16-bit but i'm running it with WinXP Pro with SP2,anyway this program only works with "Windows 2000 SP4 and above Windows XP" take from their readme file. @h20-ski No,i'm not using windows version but bootable version.
(Offline)

10-11-2006, 04:00 AM	#14
warez Registered User Join Date: Oct 2006 Posts: 9	Any idea guys?
(Offline)

10-11-2006, 11:41 AM	#15
h20-ski Forget Wakeboarding Join Date: May 2004 Location: Texas Posts: 2,460	Warez, I find it interesting that the readme say that it needs 2000 or Xp to run, as Memtest is OS dependent. And if you are running XP your system is 32bit. I have looked on the Memtest forum to find that that crash may be caused by the BIOS not mapping the memory correctly and then Memtest goes to test it, but it can not read/write to that area because the BIOS has it locked. They said one way to try and fix the error is to temporarily disable all non-essential options as that may not use the memory that causes the failure. __________________
(Offline)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode