Installed more RAM, Blue screens with random errors.

[Joshyy]

So I bought 8GB of RAM today, Taking my computer up to 16GB, Installed it, all went
well loaded up, windows 7 detected it fine, it seems to be happening randomly, can anyone tell me if it's a hardware or software issue.

 

[Joshyy]

2 more BSOD's since starting the thread, added to this post.

 

[Arc]

As it happened after installing additional RAM, first of all you should check the RAM modules.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Update your ATI/AMD display driver.
You can get it from the link in our forum, http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.

During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.

Uninstall all ASUS junks.

Start Menu\Programs\ASUS\AI Suite
Start Menu\Programs\ASUS\Cool & Quiet  
Start Menu\Programs\ASUS\PC Probe II 
Start Menu\Programs\ASUS\TurboV EVO

Free up the startup. A lot of programs are set to auto start, all are not needed other than the antivirus.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Do some Disc checks, too.

1. Update your SSD's Firmware
2. Reseat the sata and power.
   
   
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.

 

[Joshyy]

Hi Arc, Thanks for the reply, I think I've found the problem, I went to take out 3 sticks of RAM for Memtest and I found the 4th stick wasn't seated correctly, how it booted I don't know, I've reseated it now and hopefully that fixes the issues, if I still get BSOD's I'll run memtest on each stick.

Thanks!
Josh

 

[Arc]

Good to know

 

[bassfisher6522]

Hopefully that should fix if for you? An unproperly seated RAM stick will difintely cause BSOD's.

 

[Joshyy]

Just got another BSOD with an error about Clock speeds on the second processor

I can't help but think this means it's a processor issue not a RAM issue, My CPU is not overclocked and is at 1.40V

 

[Joshyy]

Removed the RAM and the errors stopped instantly. Contacting the business I bought it from to get a replacement, hope the new sticks work.

 

[Pauly]

Just so we dont gloss over it have you bought the same RAM now as was originally installed mixing and matching RAM can cause problems even if its similar specs

 

[Joshyy]

The memory I bought was

G.Skill RipjawsX 8GB (2x4GB) DDR3 PC3-12800 1600MHz Dual Channel Kit | F3-12800CL9D-8GBXL

The memory I've currently got installed is identical, apart from the fact the new stuff says 'Intel XMP' on the sticker. It's identical.

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 101[/COLOR], {31, 0, fffff880009ec180, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

Follow it: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html