Solved BSOD - Most likely RAM issue

[writhziden]

I suspect either the hard drive, graphics card, a fan, or the PSU. Could also be the CD/DVD drive. Let us know which of these you determine, or if there was something I missed.

 

[Dave76]

Is it the motherboard making the beep?

That would indicate a hardware fault.
Is it a repeating beep series?
Could be one beep repeating or long/short combinations, etc., just note the series example: one long two short.

 

[Sabrac]

I don't remember what the beep sounded like now, but it hasn't beeped since I last posted.
I'm still having the "warming up" issue. I had left my computer on for a few days straight without issue, but as soon as I turned it off and let it "cool down", after turning it on, I had issues keeping it on until it "warmed up".
Since I'm only running with 2GB of RAM and running WoW at the same time could it be the RAM just can't keep up?

 

[Dave76]

The 'Cold Boot' issue is usually due to CPU and/or RAM voltage being too low.

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

What are you using to check your CPU temperatures?
Use Core Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and let us know the DRAM voltage, the NB and integrated memory controller voltage, if your CPU has that feature.

 

[Sabrac]

I only posted 1 tab from the SPD since they're both identical.
I use Speedfan to check my temps because a friend recommended it to me and its just what I'm used to.
The Voltages picture is my computer 20 minutes after being turned on this morning.

 

[Dave76]

Check the PSU voltages when the system is cold (with system cold go to BIOS), and again when the system is warmed up. Post both cold and warm voltage settings.
In your BIOS check the output voltages of the PSU. Power > HW Monitor Configuration, VCORE Voltage, 3.3V Voltage, 5V Voltage, 12V Voltage.

Then check the CPU Over Voltage, Memory Over Voltage, (CPU/NB Voltage should be) VDDNB Over Voltage settings, and post them here.
In BIOS, Advanced > Jumper Free Configuration.

 

[Sabrac]

Here's the temps and voltages a few minutes after turning the system on cold.
Everything in the jumper configuration is set to auto except for certain ones for the RAM I set myself.
I set the timing of my RAM and the voltage.
Will post later when it warms up.
Sometimes when the system is cold, it restarts giving me the boot block trying to find a new BIOS.
Could this mean my MB has issues? I've reinstalled the BIOS multiple times.

 

[Sabrac]

Seem to keep getting these ntoskrnl.exe BSODs today.
My RAM is brand new and I've run Memtest a bunch of times. The RAM has no issue.
Psting the minidumps.

 

[Dave76]

Passing memtest86+ doesn't mean that the RAM has no issues, just that it didn't have an issue during the test.
RAM issues can be very elusive and difficult to find.

What are the RAM settings you put in?

Did you get a chance to get the 'warm' voltage settings?

The cause can still be many things, RAM and CPU settings, bad RAM, CPU, motherboard or PSU, to name a few.

 

[Sabrac]

I put in 5-5-5-15 timings and 1.8v in my BIOS settings.
I looked at the newegg site to see what timings and voltages the RAM were after a friend suggested to add them.

Another problem has arisen. Sometimes when I load my computer, in the dark areas(more visible) will be little pink pixels that seem to flicker about on the screen. The screen will then turn on and off(gooing black) every few seconds then after a while will return to normal.
I took a screenshot during the bug and when it fixed itself the pink pixels didn't show.
Gonna try using a new HDMI cable.

And I ran Memtest86+ for 30 minutes and it got some errors then Memtest froze.
Coudl this mean the new RAM went bad too?

 

[Dave76]

Yes, one error on memtest86+ is too many, when memtest86+ freezes it is not a good sign.

Let's look at your RAM and memory controller settings first, sometimes adjusting the settings will make it stable.
These are important, post these voltage settings in your next post so we can proceed.
Check the CPU Over Voltage, Memory Over Voltage, (CPU/NB Voltage should be) VDDNB Over Voltage settings, and post them here.
In BIOS, Advanced > Jumper Free Configuration.

If you are having any problems finding these voltage settings, let me know.

Did you get a chance to get the 'warm' voltage settings?
Speed Fan is showing some strange 5v readings, check it with HWiNFO64, open the 'Sensors' tab.
Let HWiNFO64 run at cold idle and then when it warms up open your game to put some stress on the system, when through post the screen shot.

 

[Sabrac]

Posting cold idle first.

 

[Sabrac]

and here's the jumper configuration.
Somehow when I went back here, the 5-5-5-15 settings for my RAM reset back to auto.

 

[Sabrac]

Not much of a difference warm than the cold here.

 

[Sabrac]

POsting this weird distortion as well.
I can still move my mouse around but it's stuck on the loading wheel.
Then the background went black and it's on screenshot 2.
As soon as I closed these windows, I blue screened.
Now I've been running memtest86+ since I blue screened with no errors.

 

[Sabrac]

Here's the HW64 after running WoW for a while.

 

[Dave76]

Go to your BIOS and get/post the, DRAM frequency and VDDNB Over Voltage, if no voltage number is shown then change it to 'Manual' to get the reading.
Are you selecting 'Exit and Save Changes' after changing BIOS settings?
Confirm your DRAM Voltage is 1.80v.
Your previous BIOS screen shot is showing 'Memory Over Voltage' is on 'Auto'.

Change your 'CPU Over Voltage' to +0.005v.


The various issues you are having may indicate the PSU voltage is not sufficiently stable, we may need to come back to this.

 

[Sabrac]

Managed to change them.
I was exiting out then trying to save instead of just saving before I left the jumper config.
I'm not getting anymore hangs/black outs as of yet, but as with this computer, there's always a new thing that pops up.
Got a few dumps from the past 2 days.
I looked up the LGVirHid.sys and it seems to have to do with my Logitech drivers, but my Logitech drivers are up to date.

 

[Dave76]

Can you confirm what you changed and to what setting (voltage, etc.) amount.

Three of your crashes were:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION  
Usual causes:  System service, Device driver, graphics driver, ?memory
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
IMAGE_NAME:  memory_corruption

These all look like they are caused by memory corruption.
The RAM settings should take care of these.

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003714100
GetUlongFromAddress: unable to read from fffff800037141c0
 fffff6ff30000008 Nonpaged pool
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0xA_nt!MiObtainSystemCacheView+186

Looks like the same cause as above.

Drivers that need updating:

AtiPcie  AtiPcie.sys  Tue May 05 23:00:22 2009

Make sure you have the latest Asus Chipset driver.

GEARAspiWDM GEARAspiWDM.sys Mon May 18 20:17:04 2009

Uninstall iTunes and get the latest version. This driver is known to cause crashes with Win7.

mcdbus   mcdbus.sys   Tue Feb 24 18:34:07 2009

Uninstall MagicISO and install the latest version. This driver is out of date.

If the LGVirHid.sys driver was implicated in a crash somewhere, it is likely the result of the crash and not the cause.

Let us know if you get any more crashes.

 

[Sabrac]

My RAM
Basically I set the 5-5-5-15 as the past screenshot shows and the MemoryOverVoltage is set to 1.8v.
I think the memory corruption dumps were before I had put in the voltage and timing settings, so hopefully those won't resurface.
I assume since I got a new graphics card, that's where the chipset drivers were having an issue.
I also just uninstalled MagicDisc since I don't use it anymore, so that's done with.
And I'm installing the newest iTunes now.