Debriefing > Bug Reports & Fixes

GoldenEye: Source is messing up my VRAM and even breaking my GPU.

(1/3) > >>

Yes! I am Invincible!:
OK i was while ago talking about the ''GPU baking'' thing and the bluescreens that happened to my MSI nVidia GeForce 8800 GTS 512 OC, but the problem isn't over. The GPU xploded again but there's a thing that makes me think. The problem isn't overheating. i monitored GPU temp when playing Crysis at max. 60 degrees.
No driver problem, no software problem. here's the deal: I can play Crysis at max without probs as long as i want.
and any other steam game, but GoldenEye: Source and Black Mesa: Source are different. i can play them for a week with daily usage (1-2 hrs a day) and BAOM! Bluescreen comes up saying: HARDWARE MALFUNCTION! NML MEMORY PARITY ERROR CONTACT TO HARDWARE SUPPORT. I checked my RAM. no major problems.

Now i'm starting to suspect the game(s). Maybe the games uses too much VRAM because and it isn't optimized well enough? Somehow this thing has to do between GE:S (or BM:S) and VRAM.
Please help me with this problem. i work on a IT business and even i won't figure WHAT THE FUCK IS GOING ON????!!!  :'(

killermonkey:
I'll say it once and only once: Software cannot cause Blue Screen of Deaths (unless it trips DEP).

YOU CANNOT CAUSE A BLUE SCREEN OF DEATH WITH NORMAL SOFTWARE.

BSOD is caused because Windows has decided that in order to save the computer, and/or prevent further corruption, it HAS TO STOP everything. They are caused 99.9% of the time because of faulty hardware or poorly behaving drivers.

http://en.wikipedia.org/wiki/Blue_Screen_of_Death

If you post the error number (usually something like 0x0000000A) and the extra data numbers (the numbers near the bottom that look like 0x0000000 with four of them across), then we can probably attempt to help you.


--- Code: ---
EXAMPLE:

*** STOP: 0x000000EA (0x882ECA78, 0x885DDA20, 0xBA4EBCBC, 0x00000001)

--- End code ---

It also doesn't hurt to upload the memory dump that windows spits out: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Yes! I am Invincible!:
haha not possible to send Memory dump. The system halts without saving ANYTHING. it's basically not a BSOD, i admit, it IS A FATAL SYSTEM MALFUNCTION NOT A SOFTWARE ERROR!. This is more serious problem than you think. *facepalm*

kraid:
If it were an issue with the mod or even BMS, don't you think there would be more ppl reporting this?
Since you allready had issues with your hardware before, i bet the error is on your end.

Proxie:
Put your video card back in the oven, it's still raw in the middle.

Navigation

[0] Message Index

[#] Next page

Go to full version