Proper RAM Configuration


Recommended Posts

Was wondering if any one can help. Here's the thing, i recently installed 512MB of RAM on my pc and suddenly i started getting blue screens from windows xp (Stop 000000x8e), looked it up and support says that its due to faulty RAM. Since i bought that 512 RAM pretty cheap, i figured it was that. So i went ahead and paid the extra $$ and got some 512 RAM (SDRAM) from crucial...when i installed it yesterday i got two blue screens...one was IRQL_NOT_LESS_OR_EQUAL, i figured that was due to virus scanning Norton error because one of my .dat files from kazaa were missing. but then after i installed a program i got another blue screen and it read STOP 0x0000008e. Now, i really don't think that it is faulty RAM cause i have purchased from crucial b4 and their RAM is tested...could it be that there is some setting in the BIOS that is not right???? I have a PCCHIPS 830ML (I know, that board does sux!!! should have gotten an Asus) and an AMD athlon XP 1800+, i seee some settings for the RAM when i go into the BIOS like:

DRAM Timing Config

SDR/DDR CAS LAtency

RAS active timing

Prechage Time

if anyone has ever dealt with this problem, can u please tell me how you configured your BIOS.....any help at all is greatly appreciated!!!!!!

update-

latest crash shows the following:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

STOP 0x000000D1

afd.sys

anyone please!!!!!

Link to comment
https://www.neowin.net/forum/topic/46516-proper-ram-configuration/
Share on other sites

here is my current settings SHoTTa35, what is in parenthesis means that these are the other possible values.

Graphic win size: 64M (4,8,16,32,64,128,256)

Dram timing Configuration: Normal (fast, ultra, safe)

SDR/DDR CAS Latency: SPD (2T, 3T)

SDR/DDR RAS Active Time: 6T (7T)

SDR/DDR RAS Precharge Time: 4T (3T)

Auto Detect DIMM/PCI CLK: enabled (disabled)

what do you think????!!!

I suspect a software conflict and the bios should work with default settings. Are you running something goofy like MouseWare? If so remove it from control panel. It definitely is a software issue. IF worse comes to worse clean install XP if possible and install only trusted apps.

--Rich

I had the same problem with my system when I originally built it and I found out the problem was I was running my RAM at 133 and it wasn't supporting it (I know, it was cheap RAM). Since I couldn't return it, I just clocked it down to 100 and had no problems since.

got another BSOD. two more actually, one right after the other:

first one:

IRQL_NOT_LESS_OR_EQUAL

STOP 0x0000000A

second one happened right after i rebooted from the first:'

Stop 0x0000008E

this is the third stick of 512 MB SDRAM that i put in, so it can't be the RAM....the one that is there npw is from crucial.

has anyone looked at my bios settings a little earlier in this thread. if anyone is knows what would be a proper setting please help!!!!!

Your BSODs seem to be related to the network, or at least two of them do. Search MSKB (http://support.microsoft.com) with your STOP codes and you will notice that they relate to network drivers/settings.

If you are not connected to the network and you remove your NIC, does it load up fine? I'm asking because of what I just stated above.

If not, reset your BIOS settings and try that.

well, just reinstalled OS with SP1 slipstreamed...after first boot, went to ms update, updated all drivers then rebooted, after login in got another BSOD without installing any software.

PAGE_FAULT_IN_NONPAGED_AREA Stop 0x00000050

Now, i know it just can't be the RAM, cause its the third stick of 512 MB SDRAM that i put in and still get the damn BSOD!!! and if i were to switch to my old 256 MB SDRAM i would not any of these errors.....i must be something in my BIOS, or maybe its SP1 or maybe my power supply is not sending enough power, i have no idea, does any one please have any suggestions?????

pleazeee help getting tired of reinstalling over and over again!!!

If everything works before and after upgrading only the RAM it starts crashing, it is most likely the RAM issue.

Did you get one that supports the appropriate bus speed for your mobo? Or as Mellen states, can it even support 512?

Check the web site for your mobo manufacturer or the manual to verify it supports what you are getting.

yes my motherboard supports upto 1G of RAm, and the ram i got it from crucial, so i followed there recommendations for my particular motherboard (PC CHips MB830LMR)...Dman this MB really sux...i couldn't even find a cotact email for tech support at the pcchips website...guess thats what i get for buying cheap stuff!!!!!

So you are positive it supports the bus speed for the RAM? Have you tried to reset the BIOS settings to default? Are there any BIOS updates as well?

Hmm yeah my roommate had bought a motherboard from a company I never heard of and could never get any updates, support, or anything else on it. Major loss for him since he couldn't use the upgrades he bought :(

It could be that your mobo does support 512 sticks but some sort of fualt in the memory controller couses it to improperly address 512 megabytes of ram in 1 stick and when code is retreived from memory that is improperly addressed the data is a warzone and u simply get a BSOD.

:D i am simply speculating. But this kind of thing, some way or another is a true possibility.

You are using windows XP SP1... i was just thinking about memory controller software, such as emm386 cuasing errors in memory allocation, hmm does windows XP support changing the memory manager system files?

Dont mix SDRAM and DDR-SDRAM chips unless you are 100% sure that your mobo supports that kind of config.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Yes, the Control Pannel issue has been fixed. As I ask when people claim it hasn't, can you name a single thing in Windows 11 that can only be done by opening Control Panel? Your comment about Error 0x80070643 is so asinine that I debated if you were worth a reply, but here I am. The article mentioned a VERY specific issue with the WinRE partition size being too small in Windows 10 and preventing updates from being installed unless you reinstalled or manually fixed it. That issue does not exist on Windows 11, period. To point to random issues with Windows updates on 11 that don't affect everyone and don't involve that issue is being dishonest. Had the article said "Issues with updates, such as..." then I'd agree with you, but it didn't, it simply mentioned that one specific issue, which despite your claim, does not exist on 11 or on newer builds of 10 (so the article is kind of wrong, it did get fixed, just not gracefully). As far as UX/UI comes more down to opinion, but again, you are saying it is "terrible" which has nothing to do with consistency. Windows 11 has a more consistent interface. You are welcome to say it is constantly bad, but I don't see how any objective person can say it isn't more constant than Windows 10's unholy merger of Windows 7 and Windows 8. To be fair, I really like Windows 10's interface, it worked great, but was it consistent, NO, it was one of the least consistent interfaces MS has ever made. I agree with the lack of competition. Linux continues to get better
    • Microsoft isn't happy you're using unsupported Exchange versions, announces final deadline by Usama Jawad Earlier this month, Microsoft announced Exchange Server Subscription Edition (SE), which is the official transition of the product to the Modern Lifecycle Policy, where software is continuously serviced without an end-of-life date, as long as you keep it updated. It also revealed surprising, but brief, Extended Security Updates (ESUs) for Exchange 2016 and 2019. As it winds down support for these products, the company has expressed some displeasure that some customers are using even older and, obviously, unsupported versions of Exchange. In a blog post, the company has noted that it currently offers migration tools that enable the migration of public folders from on-premise Exchange 2013 or older versions to Exchange Online. This is by design, but Microsoft is now changing its tune on the topic. Starting from October 1, 2025, customers leveraging Exchange 2010 or older versions of the software will not be allowed to use Microsoft's tools to migrate their public folders to Exchange Online. Microsoft believes that this deprecation will reduce reliance on legacy systems and enhance "long-term service reliability". Any migrations that are attempted after the aforementioned date will fail, so Microsoft has urged customers to complete their migrations as soon as possible. If customers want to move their data to Exchange Online after October 1, they will first have to upgrade to a newer Exchange version, which is Exchange 2013, but it is important to keep in mind that supported versions are 2016 and 2019. Microsoft has emphasized in a rather stern tone that it does not encourage using unsupported versions of Exchange Server at all, and it has just put out this advisory because it is aware that public folder migrations from legacy systems are currently active, even though they shouldn't be. Needless to say, customers should upgrade to Exchange Server 2016 or 2019 as quickly as possible, but ideally, they should consider moving to Exchange Server SE at this point, considering that the other two versions are running out of support soon, too.
    • A little bit, yeah, if you ask me. Granted, he has the right to be upset with this jerk user that attacked him, but why drop the entire project just because of ONE person? Seems a little exaggerated.
  • Recent Achievements

    • Week One Done
      NeoWeen earned a badge
      Week One Done
    • One Month Later
      BA the Curmudgeon earned a badge
      One Month Later
    • First Post
      Doreen768 earned a badge
      First Post
    • One Month Later
      James_kobe earned a badge
      One Month Later
    • Week One Done
      James_kobe earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      673
    2. 2
      ATLien_0
      256
    3. 3
      Xenon
      165
    4. 4
      neufuse
      145
    5. 5
      +FloatingFatMan
      115
  • Tell a friend

    Love Neowin? Tell a friend!