Comp keeps totally locking up on me

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

ok, first i had a stick of ram that was 512 it wasnt the one meant for it, my manufacturer gave me this stick because the memory that came with the computer was bad...recently i have switched out that stick with a new one, this memory IS compatible with my proccessor and my mother board but it for some reason will constantly lock up with me. I have done the whole trial and error thing to see if it is the memory stick...i have currently been through 4 sticks now and they all give me the same result... a blue screen with the error messages 0x0000008E and 0xc0000005 and 0xBFA3F4BB and 0xEBB52A50 and 0x00000000 there are other messages also NAVENG.Sys - address EBB52A50 base at EBB52A50 Datestamp 00000000 and another saysNv4_disp.dll - address BFA3F4BB base at BF9B7000 datestamp 3f725d4c i have resarched all of these in google; most give me memory related results but the last 4 error messages that i mentioned give me no results, i hope that i copied them right...im sure that it isnt the memory now because 4 consecutive memory sticks couldnt all be bad... thanks in advance for any and all of your help.

i also reinstalled Windows Xp onto my system and yet it still seemed to freeze on me......
 
no i dont believe it is the ram because this is the fourth stick that i have been through i doubt that 4 consecutive memory sticks can be bad
 
It could be a hardware problem. And you are probably right about the memory.
However, memory is a funny thing. Some motherboards/manufacturers have to
have it just right. Did you try a stick of the exact same brand of the
original?

Won't your manufacturer fix the problem? You say they sent you a new chip, so
you must be under warrantee still (??)

I been through some rebooting/blue screen of death problems with adding a 512
MB pc2700 stick to my current Samsung (Patriot). But I didn't crash all that
much - maybe a few times a week. Sometimes more. But less too. And I left
my computer on all day, so not that much as I say..

I didn't even think it was the added memory, because it was so intermittent.
People told me (here in Usenet) that the stick should work fine. The Samsung
is a PC2700 with only a 133 (or 166??) MHz bus rating. The Patriot was what
just about all of the Pc2700 sticks are, a 333 MHz bus rating. I was told the
faster would just slow down to the slower BUS speed.. And it did. But after
over a month of intermittent crashes, I removed the extra stick maybe almost 2
weeks ago. I am back to running 512 MBs RAM, but have had no crashes since.

I am pretty sure there is nothing wrong with the Patriot stick. It is just
incompatible with my eMachines T3265 3200+ computer.. I am going to not go
for any sale now when I buy a new 512 stick - it will be the exact same brand
& bus rating as the original.

Anyone want to buy a PC2700 512 stick 333 MHz BUS rating ? I don't think
they'll take it back now after about 2 1/2 months & a rebate. It has a
lifetime warrantee, though I don't know if it is transferable. I guess I'll
give them a call & see if there is anything they can do.

....D.
---------------------------------
 
Most lockups can be a direct result of not having the updated drivers for you stuff. In this case note the NAVENG.sys a device driver. The event log in your administrative tools found in the control panel is your best place to start. Look at the system and applications logs for red Xs that appeared at the time of your lockup . Double clicking these will bring up a details window. This will more than likely look like some alian language but if you look closely you will often get a module name that you can recognize. Go to every manufacturers site of your hardware\software and get their XP updates. An excellent program to assist you is Everest Home Edition. It's free for standalone home users and will assist you getting a list of everything that makes up your system and often gives links to the drivers as well. 99% of the time lockups are caused by driver conflicts or a call by the OS for a higher function that the driver hasn't got enabled and so they loop and freeze. There are other things that can cause lockups like not having the proper configuration for your wheel mouse and if it's an Athlon processor some motherboard\chipsets will lockup when calling for the AGP and there is a reg fix for both. Let us know how you make out.
 
I had a computer freezing problem and was told it was the memory chip. Turns
out it wasn't actually the chip but somewhere in the slot it sits in. After
inserting a new chip the computer might run for a day or two before freezing.
As I have a laptop there doesn't seem to be much I can do beyond avoiding
that slot (which reduces me to the only other slot and 512MB max). I bought a
MemTest-86 bootable CD-Rom memory diagnostic program from BradyTech Inc;
haven't tried to boot up with it yet though (with a chip in the slot that has
the bad spot in it somewhere) partly because I would probably have to run the
thing days and then all I would get is conformation of what I already know. I
wish there was a way to ignore/bypass whatever is bad in the slot (like can
be done on hard drives) but I don't think that is possible. Anyone know
differently?? So I am posting this mostly just in case someone else's problem
is the same, yet the possibility of a bad slot rather than the chip in it
never occured to them. I suppose it could be repaired in a PC but I am told
it can not be done in a notebook.
--
Thank you, Raymond


NitricNoobie said:
ok, first i had a stick of ram that was 512 it wasnt the one meant for it, my manufacturer gave me this stick because the memory that came with the computer was bad...recently i have switched out that stick with a new one, this memory IS compatible with my proccessor and my mother board but it for some reason will constantly lock up with me. I have done the whole trial and error thing to see if it is the memory stick...i have currently been through 4 sticks now and they all give me the same result... a blue screen with the error messages 0x0000008E and 0xc0000005 and 0xBFA3F4BB and 0xEBB52A50 and 0x00000000 there are other messages also NAVENG.Sys - address EBB52A50 base at EBB52A50 Datestamp 00000000 and another saysNv4_disp.dll - address BFA3F4BB base at BF9B7000 datestamp 3f725d4c i have resarched all of these in google; most give me memory related results but the last 4 error messages that i mentioned give me no results, i hope that i copied them right...im sure that it isnt
the memory now because 4 consecutive memory sticks couldnt all be bad... thanks in advance for any and all of your help.
 
Back
Top