Graphics glitching and crashing

[Puavo]

Well yeah, i think, my is about 30°C when i play Salem.

I am by no means an expert on the subject, but based on a quick google, the average idle temperature on GPUs seems to vary a lot depending on the manufacturer and model, and it can be anything between 20-70°C. Based on that, I'm assuming 50°C should be nothing to worry about, but the heck if I know!

[ceromaster]

I shan't bet on it, but it looks to me like hardware trouble. Are you sure your RAM is error-free and that your GPU is properly cooled?

RAM is error-free according to the windows diagnostic tool. Also Diablo3 does not overheats the graphic card, its around 50-60*C
The error report contains this:

Code: Select all

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x5b53db20, pid=1488, tid=6876
#
# JRE version: 6.0_27-b07
# Java VM: Java HotSpot(TM) Client VM (20.2-b06 mixed mode, sharing windows-x86 )
# Problematic frame:
# C  [nvoglv32.DLL+0xaddb20]
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---------------  T H R E A D  ---------------

Current thread (0x07474400):  JavaThread "AWT-EventQueue-0" [_thread_in_native, id=6876, stack(0x07790000,0x077e0000)]


loftar: I can send you the full content of the hs_err_pid1488.log file in pm if that would help.

[RonPaulFTW]

How are you checking your GPU temp?

[ceromaster]

How are you checking your GPU temp?

CPUID HWMonitor

[MagicManICT]

Well yeah, i think, my is about 30°C when i play Salem.

I am by no means an expert on the subject, but based on a quick google, the average idle temperature on GPUs seems to vary a lot depending on the manufacturer and model, and it can be anything between 20-70°C. Based on that, I'm assuming 50°C should be nothing to worry about, but the heck if I know!

You're right, and most any PC processor is going to operate safely in this range. (I know some of the AMD processors had to be kept under 60°C or they started having issues, but that was a minority.)
---

No, the card isn't that old, but as far as GPU tech goes, it is getting there, especially as a workstation card. Is it having issues doing anything else? If so, there's the solution. Odds are it's not glitching on just one program if it's hardware. The problem is we're seeing this issue with two different people at the same time. it certainly isn't out of the realm of possibility that both have hardware issues, but the more people you add in, the more the likelihood it's a driver or other software problem.

[dakoo]

So 3 to 4 years old in a work machine that probably runs a lot. And its a quadro. That makes it old school by itself, as its designed to render 3d things, not in real time for gaming. That is a very old line, whereas the gaming stuff has had a few rebirths in that time. This has happened to me on the original planetside, the exact same artifacts on the 3d rendering only, and then again on another game with the next card a few years later. Its like the command to stop drawing a shape isn't working so certain edges shoot off into space.

Mess around all you want, but in the end it will be a hardware issue with the card. Its shot. Maybe just the 3d part. Find another java game with 3d (Minecraft?) Graphics and see what happens. Maybe the errors are just in the instructions set Salem uses,dunno, I'm a hardware guy, not a coder, but its a low level hardware problem... I have seen it. New card, will work great.

[Puavo]

How are you checking your GPU temp?

CPUID HWMonitor

I used GPU Temp (http://www.gputemp.com/).

Is it having issues doing anything else?

Nope. Haven't had any issues whatsoever with anything else except Salem. Then again, I don't think I've tried playing anything else on the computer.

The computer as a whole isn't actually too old - I bought the setup brand new around 7-8 months ago. I don't need any graphics processing power for my work (I do audio stuff), so Nvidia Quadro 600 felt like an alright choice because it was cheap and quiet.

Find another java game with 3d (Minecraft?) Graphics and see what happens.

Yes, that's a good idea. I won't have access to the computer for a couple of days, but once I do, I'll try this.

[ceromaster]

So I deleted everything (game files and java cache), updated to latest nvidia quadro k1000m beta drivers, redownloaded the official client and I still see this:
http://postimg.org/image/3rvzujan3
There are no .salem and Salem directories in the c:\User\<user>\ directory when using the official client, downloading ender's and latikai's won't help.
Also after a couple of seconds the game exits and there are no error messages.

Do you have any other ideas or should I resign and accept the inability to play it from this laptop?

[MagicManICT]

If you really want to use your work computer to play games on and you don't need the graphics card to run CAD or 3D modelling, you might want to look at replacing it. You could probably get a mid range graphics card that's only a year or two old for a swap. (i'm sure there's tons of college students that want something like this willing to do so.)

Getting nVidia to "fix" the drivers so that the quaddro will run games better probably isn't going to happen. That's a bit like using your screwdriver as a chisel and wanting a refund when you break it

[loftar]

Do you have any other ideas or should I resign and accept the inability to play it from this laptop?

Do the crashes you described above (the one which gave you the hs_err_pid*.log error report) still happen even after you upgraded your graphics driver? If they do, then you definitely have some software or hardware trouble outside the client per se, because those errors are produced by the JVM itself crashing, rather than by the client code. Specifically:

Code: Select all

# Problematic frame:
# C  [nvoglv32.DLL+0xaddb20]


That tells you that it is the nVidia driver that crashes.