Blue screen memory dump that happens only during gaming

This topic is locked from further discussion.

Avatar image for StSk8ter29
StSk8ter29

1804

Forum Posts

0

Wiki Points

0

Followers

Reviews: 15

User Lists: 0

#1 StSk8ter29
Member since 2003 • 1804 Posts

I keep getting the blue memory dump screen randomly when I'm playing my games and I have absolutely no idea why. It only happens during gaming and at random intervals. Here's what I've done to attempt to fix it, all resulting in failure:

-I replaced my old graphics card with a new one because the VRAM was bad (which I thought was the problem, but no)

-I purchased a new power supply unit at 600w which is 50w over what my graphics card requires

-I ran Windows' Memory Diagnostic Tool which found no errors in my physical memory sticks.

-My drivers for the nvidiagraphics card are completely updated; so are the drivers for my onboard audio.

-My cpu has a new heat sink with a fresh layer of artic silver

-I increased the voltage on my memory in an attempt to stabilize

-I tried using only one of my two memory sticks in case of a conflict

-There are no yellow exclamation marks in the hardware tab

-I tried downgrading to Windows XP SP3 from Windows 7

-I've attempted to lower graphics settings on my games to keep them from crashing

-Internal temperatures for both the CPU and the GPU are exactly where they should be under load

Nothing of the above has helped at all, and it's really annoying because I can't play any of my games. The only thing that works consistantly is the internet. Anybody have any idea what I an do that might help?

My setup: Windows 7 Home, 2.3ghz duel core athlon, Geforce GTX275 800+mb VRAM, 4 gigs of RAM, 600w Thermaltake PSU.

Avatar image for freesafety13
freesafety13

823

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#2 freesafety13
Member since 2008 • 823 Posts
Download Prime95 and Realtemp. Run Prime95 with small fft's and watch your temps. If Prime95 will run for at least 4 hours straight without error then your hardware is stable. If not you will need to start narrowing down if its cpu or ram related. To test the ram, download memtest x86 and make a bootable cd. Boot into memtest and let it run for at least 4 hours, again checking for errors. If you get any try 1 stick at a time. If both those come back clean, then you have a driver issue. Something is either creating a driver conflict or you have a driver trying to access protected memory on your ram.
Avatar image for GTR12
GTR12

13490

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#3 GTR12
Member since 2006 • 13490 Posts

Your mobo could be bad.

Avatar image for belboz
belboz

1548

Forum Posts

0

Wiki Points

0

Followers

Reviews: 1

User Lists: 0

#4 belboz
Member since 2003 • 1548 Posts

You have done a good job on your diagnostics.

I have two things to suggest:

  • If you over clock, don't.
  • Update BIOS

Also, what is the STOP code you get? You can probably find it in the event viewer.

Avatar image for StSk8ter29
StSk8ter29

1804

Forum Posts

0

Wiki Points

0

Followers

Reviews: 15

User Lists: 0

#5 StSk8ter29
Member since 2003 • 1804 Posts

Event ID: 18

Source: WHEA-Logger

Reported by component: Processor Core

"A fatal hardware error has occurred"

Avatar image for Lach0121
Lach0121

11782

Forum Posts

0

Wiki Points

0

Followers

Reviews: 17

User Lists: 0

#6 Lach0121
Member since 2007 • 11782 Posts

Event ID: 18

Source: WHEA-Logger

Reported by component: Processor Core

"A fatal hardware error has occurred"

StSk8ter29

oh that sounds like you have a dying cpu, but I am not sure on that.

Avatar image for xbxjetraider
xbxjetraider

1522

Forum Posts

0

Wiki Points

0

Followers

Reviews: 53

User Lists: 0

#7 xbxjetraider
Member since 2004 • 1522 Posts

One of your RAM modules might be bad. Try testing the RAM chips individually.

Avatar image for belboz
belboz

1548

Forum Posts

0

Wiki Points

0

Followers

Reviews: 1

User Lists: 0

#8 belboz
Member since 2003 • 1548 Posts

Check this and search for Ether6123 post. See if it applies to you.

If not, google "event id 18 whea-logger" (without quotes) for other hints. One link points out that upping the RAM volatage to 1.9 solved it (but you already did that, I guess, as you stated that you increased RAM voltage)

Avatar image for venjhammet
venjhammet

127

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#9 venjhammet
Member since 2009 • 127 Posts

I think you're motherboard is having a problem. You should definitely change that