BSOD when resuming from sleep after upgrading from 2 GB to 4 GB RAM

[gv1031]

Hello, I have just tried to install upgraded RAM on my computer and have found that I consistently get BSOD on resume from standby (sleep) mode. I have run the WinDbg software to find that the problem has to do with a certain driver but due to my inexperience, I cannot understand the debug log. If someone could please assist me that would be great.

 

[koolkat77]

McAfee
We have seen McAfee cause BSOD's on several systems and recommend uninstalling it with the McAfee Removal Tool and replace with Microsoft Security Essentials. How to uninstall McAfee products using the consumer Removal Tool (MCPR)

Uninstallers (removal tools) for common antivirus software. Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free

   Information

• :warn: Do not start the free trial of MalwareBytes, unselect that option when prompted.
  
  
  
  
  
• :tip: Update and make full scans with both separately.

Start up

Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.
Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7

Disk Check

For errors on your Hard drive(s): How to Run Disk Check in Windows 7

This tutorial http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html may help you:

To Disable Selective Suspend:

1. open the control panel
2. go to power options (you may have to set view to small icons)
3. click change plan settings
4. in the window that opens:
5. click change plan settings
6. click change advanced power settings, expand usb and ensure usb selective suspend is disabled.

Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

   Tip

Do this test overnight.

 

[gv1031]

One more thing to note

One more thing to note is that, as soon as I installed my old RAM back in, this BSOD problem went away.

I will try running memtest on the new RAM, in addition to uninstalling Mcaffee and trying the clean boot to see if it helps.

I ran anti-malware software you suggested and it did not find anything.

Is there anyway to see the dump file and see what driver is causing the problem?

 

[gv1031]

Another thing to add, the problem disappeared when I tested each RAM module by itself. The problem only appears when I put the two modules together. Could this have to do with 32 bit vs. 64 bit?

 

[Arc]

Have you tested each RAM module in all the available DIMM slots and got the same result?

 

[gv1031]

Yes I tested both modules by themselves in both slots and the blue screens disappeared.

There's only an issue when they're put in together.

 

[Arc]

The RAM modules are a 2x2 GB kit, right?

I think you should send it to Dell for servicing. As it is out of warranty, they will charge for it; but that is the best option for you there.

 

[gv1031]

I Don't think sending it to dell will help as this is not a problem with my computer. The original Ram modules work fine, just installing the new ram together causes problems.

 

[Arc]

I Don't think sending it to dell will help as this is not a problem with my computer. The original Ram modules work fine, just installing the new ram together causes problems.

Is it?

If you want to increase the RAM, Either match the FSB of the existing one while purchasing or get a whole new 2x2 GB kit. Everything will be nice.

Mismatch RAM will do the problem that you are having, for sure. I interpreted it as a motherboard issue, as I overlooked that pare somehow.