Windows stops booting when new RAM is installed


Recommended Posts

Currently have 1x 4 GB chip.

Trying to install a second 4 GB chip.

Without the new RAM, it boots fine but with the new RAM (in different slots), Windows reboots when it says "Starting Windows" (the animation doesn't even appear).

It also reboots before Startup Repair or Safe mode get properly started.

PC boots fine if I take out the RAM.

The RAM is 100% compatible with the PC.

Any ideas?

EDIT: Tried taking out the older chip and only put the new one in. Same problems. Faulty RAM?

w/o further info, it's hard to diagnose. are the two sticks identical in specs? some motherboards require that the RAM be placed in certain slots. are they installed correctly? can you run the single, new stick w/o the old stick installed?

I actually had the similar behavior, and the fix was to actually uncheck 'automatic' from the RAM timing and set manually to the rated specs of the RAM. Took me FOREVER to figure that one out...

Also, if you remove your original RAM and use only the new RAM does it still boot? It seems you've only confirmed that it still boots correctly if you remove the new RAM.

w/o further info, it's hard to diagnose. are the two sticks identical in specs? some motherboards require that the RAM be placed in certain slots. are they installed correctly? can you run the single, new stick w/o the old stick installed?

As I said, the RAM is 100% compatible with the PC.

Only using the new chip causes the same problems.

I don't really see a need to even guess. Just take it back to where you bought it say it wouldn't boot when it was in. They should replace it without argument.

I bought it originally from Ebuyer. It didn't work (random BSODs after a few hours) so I RMA'd it to Corsair. This new chip is the RMA replacement chip and now the PC won't even boot :/

I bought it originally from Ebuyer. It didn't work (random BSODs after a few hours) so I RMA'd it to Corsair. This new chip is the RMA replacement chip and now the PC won't even boot :/

Okie doke, continue looking through the bios for the memory timing options then. :rofl:

Although there is still the outside chance that you're just unlucky and got 2 bad sticks in a row.

As I said, the RAM is 100% compatible with the PC.

Only using the new chip causes the same problems.

but you didnt answer my questions.

1. are the sticks identical in specs?

2. some motherboards require that the RAM be placed in certain slots. are they installed correctly?

3. can you run the single, new stick w/o the old stick installed?

Okie doke, continue looking through the bios for the memory timing options then. :rofl:

<snip>

Within Advanced, I see:

  • CPU Configuration
  • Chipset
  • Onboard Devices Configuration
  • USB Configuration
  • PCIPnP
  • Intel VT-d Configuration

but you didnt answer my questions.

1. are the sticks identical in specs?

2. some motherboards require that the RAM be placed in certain slots. are they installed correctly?

3. can you run the single, new stick w/o the old stick installed?

1. Yes. As I said, I know the RAM is fully compatible with the PC.

2. I've tried various slots.

3. Read my original post edit. The edit was made literally 10 seconds after I first made the topic.

Name both modules you are using.

And as said above - ensure RAM timing is set to auto.

If you don't know how to use it, then it should looks like this.

<image snipped>

As I've said, I see nothing like that in the BIOS. It's a very basic motherboard.

I see no way to adjust RAM timings and even if I could, I would never have touched them.

As others have asked, lets try this.

What is the make/model of the memory, what is the make/model of the system or motherboard?

Help us, help you...

It's a custom built PC. The motherboard information is in my signature, the Asus P7H55-M SI.

Both RAM chips are 4 GB DDR3-1333.

I've found out the hard way that mobo's are extremely sensitive on RAM. If you're using different brands, that could be causing problems. If you're using a brand and model not even listed by the moobo manufacturer that could be your cuplrit too. I built an i3 HTPC and had stability problems. A fellow Neowinian pointed out the list of compatible RAM with my mobo and I bought it and haven't had a single problem since. From now on when I build, I'm going to the mobo site and making sure I buy RAM listed as approved. That's the biggest lesson I've learned in years.

does this help you at all? i pulled this information about the BIOS from the motherboard's manual

post-34502-0-63999300-1343137523.jpg

The only BIOS screen I can find related to RAM is this one, and it's all set to Auto:

post-645-0-23761000-1343137709.jpg

I will try resetting the BIOS defaults in 30 minutes when I get home, although I can't see it helping unfortunately.

2. Set bios defaults

3. Memtest x86

I'm surprised this hadn't been suggested earlier. This is the first thing I do in case of a similar event.

Should memtest86+ return any errors, the customer service will replace the memory without blinking.

I've found out the hard way that mobo's are extremely sensitive on RAM. If you're using different brands, that could be causing problems. If you're using a brand and model not even listed by the moobo manufacturer that could be your cuplrit too.

Actually, I haven't found that to be the case at all. I have two pairs of memory installed, each with a different size, different brand, different speed rating and different timings - the RAM works perfectly in dual-channel and my system is 100% stable (Prime95; Intel Burnt Test). However, when I first installed the RAM my computer wouldn't boot because I had the timings set to manual. It corrected itself though as my motherboard has automatic memory configuration.

Have you got another computer you can test the memory in? If you reset the BIOS and use just the new chip it should theoretically work; if not it would seem it's either faulty or incompatible with your motherboard.

The RAM is 100% compatible with the PC.

How did you determine this? Is the manufacturer specifically listed in the motherboard's manual and/or website or are you referring to the speed rating? Although all RAM should be compatible with all motherboards with the same memory rating the reality is that there are sometimes incompatibilities, which is why motherboard manufacturers usually list specifically compatible memory.

I recommend resetting the bios with the jumper and not using restore default settings within bios, it is not the same thing, It happened to me many times and the only way it worked was with hard reset.

I took the battery out for 30 seconds, which reset the BIOS. Same issues occured.

I'm surprised this hadn't been suggested earlier. This is the first thing I do in case of a similar event.

Should memtest86+ return any errors, the customer service will replace the memory without blinking.

This is... different somehow mate. I just don't feel that is the issue.

Actually, I haven't found that to be the case at all. I have two pairs of memory installed, each with a different size, different brand, different speed rating and different timings - the RAM works perfectly in dual-channel and my system is 100% stable (Prime95; Intel Burnt Test). However, when I first installed the RAM my computer wouldn't boot because I had the timings set to manual. It corrected itself though as my motherboard has automatic memory configuration.

Have you got another computer you can test the memory in? If you reset the BIOS and use just the new chip it should theoretically work; if not it would seem it's either faulty or incompatible with your motherboard.

Unfortunately, I have no other PC to try it in.

How did you determine this? Is the manufacturer specifically listed in the motherboard's manual and/or website or are you referring to the speed rating? Although all RAM should be compatible with all motherboards with the same memory rating the reality is that there are sometimes incompatibilities, which is why motherboard manufacturers usually list specifically compatible memory.

It's Corsair CMV4GX3M1A1333C9.

The other chip (that works perfectly) is "PNY 4GB DIMM DDR3 PC3-10660 1333 MHz 240 PIN".

So they should both be compatible with the motherboard and with each other I presumed :s

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

    • No registered users viewing this page.
  • Posts

    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      83
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!