Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD memory errors not consistant


  • Please log in to reply
1 reply to this topic

#1 geno368

geno368

  • Members
  • 255 posts
  • OFFLINE
  •  
  • Local time:10:09 PM

Posted 20 January 2010 - 04:17 PM

I am working on an Inspiron 1525 running Vista Home Premium with 3 GB ram. I can boot and run in safe for a while before it locks up. All my security software is up to date and I have run several good scanners. The system is clean. I ran a system diagnosis and it show the ram memory is running fine. When I do a normal boot, I get the BSOD fairly quickly. Several different error messages appear one of which is the suggesting to reseat the memory, which I have done 3 times with a grounding strap. Here are some more:
"A driver corrupted pool memory used for holding pages destined for disk"
"Memory test fail Dimm B" (which I think would mean Dimm 2 which it is marked.
"error code 123' ( I also have a long stop code)
If all of this shows a bad memory stick, why does the system still recognize the 3 GB?
My guess is that maybe a page file is corrupt or even the OS. Should I just do a system recovery?

BC AdBot (Login to Remove)

 


#2 ThunderZ

ThunderZ

  • Deactivated
  • 4,454 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:09 PM

Posted 20 January 2010 - 04:42 PM

The amount of memory and that it is recognized does not mean it is good. A sector\block of memory can go bad. You will never know it until the OS attempts to write to that area.

My suggestion is to remove the memory from Dimm B (2) and place the memory from Dimm C (3) into it. You will be running on 2 Gigs. See if that eliminates the problem.

Let us know.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users