Sign in with
Sign up | Sign in
Your question

Intermitten blue screen after memory installation

Tags:
  • Blue Screen
  • Windows Vista
  • Computers
  • Memory
Last response: in Windows Vista
Share
February 21, 2014 3:06:25 PM

I have a Dell 530s with Vista Home. I never, repeat never had a BSOD with my machine until I upgraded my memory from 2GB to 4GB. I have had almost zero problems with my machine since day one. Here's the problem. I upgraded the memory from 2 to 4 GB. The computer ran fine until I started getting memory dump BSOD's. This was occurring after using the computer for about an hour. I've checked and rechecked the memory cards from Crucial and they are the correct cards. I uninstalled the 2 slots as the BSOD was driving me crazy. I kept the cards out of my computer for a few months then reinstalled them. Everything worked fine until today and again I have the same problem. Memory dump with the BSOD. I plan to upgrade to windows 7, so I really need the extra memory. I've run every test, including memory and scannow. I've downloaded every upgrade that is available for my Dell. All the latest from MS for Vista are also installed. I checked the device manager and everything is clean. I have never gotten the BSOD using my factory installed 2 GB of RAM. When I installed the extra 2 GB of RAM, the computer ran fine for a while, then the same problem, the BSOD returned, so I removed the new 2GB of RAM, again. I could let the box run for the next five years and not get a BSOD with 2GB of RAM, but if I install the extra 2GB I will get a BSOD. Yes, I am very mad.
Dell 530s MS Vista Home Premium 32 bit
Intel Core2 Duo CPU E4500@ 2.20GHz
2.0 GB RAM ATI Radeon HD 2400

More about : intermitten blue screen memory installation

a b } Memory
February 23, 2014 9:56:37 PM

Couple of things. Windows 32 bit OS doesn't recognise 4gb of RAM, its an older OS, and therefore limited by age. Also, unfortunately, there are differences in RAM, even if they look to be the same, they sometimes will not play nice with each other. You seem to be trying to use 2 differents sets of sticks, and their internal timings will be different. This can cause your bsod's. Ideal situation would be to return the new memory, swap it out for 2x4gb, use that in slots 2,4 (counting from the cpu-out) and tossing the old memory. Just make sure to look up the memory requirements for the board you have, so you don't exceed the limits. Do this only when you upgrade to win7 and make sure you get the 64 bit version not the 32 bit version, and you should have no more headaches over this.
m
0
l
February 24, 2014 2:09:50 AM

Umm, nope. I went to Microsoft.com and my MB and chip will only allow for 32 bit, NOT 64 bit. I am very techie, having a background in electronics and mechanical engineering. Karadjgne, I've done everything you posted. I swapped the old memory chips for the new ones, using the same slots. I didn't get the BSOD, but I was back to 2GB. I swapped the old memory cards into the new slots and the new ones into the old slots. The box beeped like it was on fire. Something else is causing the problem to make the memory dump occur. I have Nirsoft blue screen recorder. Next time this happens I will post the results. The chips are fine we ran them through another 530 without a problem. I noticed one thing as to when the event occurs. I have X amount of windows opened. (Firefox only, never use IE) When the event occurs, it's when I open another window using "open in a new tab" with Firefox and/or I am viewing a video. I thought that it may be Flash, as Adobe issued a security warning. I uninstalled Flash and got a crash with Firefox, so I did a system restore, then reinstalled Flash without any problems. I do not understand how I can use 3GB (3 slots) and never have a problem, (except a very long boot time) but as soon as the 4th slot is filled, I will (sometimes) get a memory dump and a BSOD. I've read everything about this, including changing the voltage, NOT a good idea, since my chip is not O/C. I've also experimented without any results by changing the swap file size. Some outside source is causing the event and it's really driving me nuts.

m
0
l
!