El Crash:: Windows Video Driver Infinite Loop

[robotbob]

After a information devoid crash in linux, I tried windows again.

 

[Apologies in advance for the non -linear thought of this post]

 

El and the whole OS locked, then it died, windows gave me a blue screen

message from the bowels of the kernel that:

 

NV_DSP is in a infinite loop. (Nvidia Video Driver).

 

Now without profile info or any meaningful error message, I'm stuck

"something in el is causing my video driver in both linux and windows to 'infinite loop'.

 

Oh, I should note I was not fighting this time. I had killed the training monster ~2 seconds prior.

So determining a cause, to the effect is proving painful.

 

[stream of thought]

What should I do? turn things off in make.conf and compile again? I mean from an enduser pov.

Maybe profile info to find out what routine is infinite looping. Or is it a single error forcing the driver

into a loop...

[/]

 

Ideas?

[Entropy]

Sistem specs?

Are you sure you are using the most up to date driver? Tried the poor man option?

[robotbob]

On the machine I am testing on:

 

CPU: P4 1.6 GHZ

RAM: 512 MB

VID CARD: Nvidia GeForce FX 5500 (256mb)

Driver Version: 6.14.11.6375 (windows)

Driver Date: 10/4/2007

 

Windows OS: Win XP Home Version 2002 Service Pack 2

 

---

 

Suse 10.2 Updated kernel, latest driver for nvidia, updated everything possible.

 

 

* Tried Poor man option, everything off.

* Windows Binary, Windows NoCluster Binary.

 

Did a cvs, and compile in Suse, yesterday. With those options unset\set.

 

========================================

 

However just now in windows, with a debugger running, I turned -everything on- (not music)

and I cannot get it to crash. Just prior the crash was certain.

 

So perhaps something that is disable by those options isn't completely disabled?

I have yet to go as far as digging through the code.

 

Ill keep playing as normal and seeing if I can catch what is happening in more detail.

[Entropy]

Try disabling the vertex buffer objects thing, it is known to cause some issues.

[robotbob]

I did. If I could uncheck It, I did so.

 

I'll try to get it to crash reliably , or at least try, later today.

At first I was willing to write it off as -windows sucks- but I experience

the same event in my Linux distro.

 

Hopefully I can get some real crash info, instead of this vague stuff I'm posting now.

I know from experience its annoying to receive ambiguous bug reports from users, its impossible

to resolve.

 

After my morning work, I'll try again.

[NotaBot(tm).]

Great. You're actually TRYING to get the game to crash! I can't even get in! Ah, the subtle balance of rEaL life!

[bluap]

After a information devoid crash in linux, I tried windows again.

How recent is your CVS build, i.e. when did you last cvs update then compile?

Did you compile from CVS for both Linux and windows?

When you get the problem, have you changed window resolution or toggled full screen?

AFAIK, the only random crash bug that is definately still in the CVS version is the resolution change bug. It would be very useful to get others opinions of that assertion.

edit: cvs builds with standard options only of course.

Edited December 8, 2007 by bluap

[robotbob]

How recent is your CVS build, i.e. when did you last cvs update then compile?

 

I cvs\compiled with the standard options after this last change

"Fixed buffer size for video_modes[], would write past bounds. Can't see were the array is used there after mind"

 

Did you compile from CVS for both Linux and windows?

 

Only in Linux, I am set up to do it in windows, but haven't. Since I get the same error in linux

(event of totally freezing KDE, so its tough to call it an error)

 

When you get the problem, have you changed window resolution or toggled full screen?

 

No. I made no resolution changes prior to the crash. Although I have tried playing the game full screen

with the same effect.

 

 

AFAIK, the only random crash bug that is definately still in the CVS version is the resolution change bug. It would be very useful to get others opinions of that assertion.

edit: cvs builds with standard options only of course.

 

After thinking about the pattern prior to the crash (I don't mean EL crashes I mean EL crashes the entire

OS &\OR GUI when this happens)

 

1) Game and OS GUI freezes for ~20, If I am lucky, I come back, resync'd

2) If I am not lucky, The GUI remains frozen and in Windows the Entire OS bombs out.

 

It becomes a made rush to reboot to see if I am now in the underworld. This has happened only

one time sitting in a storage. It makes ad training\mixing with toads\pking a nice game of roulette.

[bluap]

This sounds very unusual. It makes me wonder if you have a problem with your graphics card, the hardware. May be some faulty memory. Do other graphic intensive games work OK. Are your OS stable normally when not playing EL. Obviously Linux crashing. or locking is almost unheard of in normal use, I can't comment on windows as I don't use it When your Linux desktop freezes, can you switch virtual terminals or remotely login from another computer? If so, can you attach a debugger to see where the client is, or run strace to see if the client is actually still running, or kill it and recover your desktop?

[Entropy]

Yes, maybe you have something missconfigured in the hardware. Do you have an overclocked system? Do you hav an IRQ assigned to the video card?

[robotbob]

So far hour of the invasion, no crash. I've change nothing from yesterday

 

I test the ram with a tool I have for work.

I have no misconfigured IRQs.

 

No Overclocked or altered video card settings.

 

In linux I cannot switch desktops, nor connect\kill anything. Total freeze I have never experienced

that ever in the 10+ years I've used linux.

 

Yeah I would suspect the same, a hardware fault. If someone called me with this problem.

I'm diligent about testing. but I will go back and re-examine ram\hdd\vid card.

 

And no, nothing else, games, apps, anything ever has caused this problem, in this Machines XP or Linux install.

 

I crash in nothing else, only EL. So I assumed it was the single app and not the system.

[robotbob]

2+ million exp no crash, I have no idea why the change.

 

I must have tired my gremlin out.

 

Anyway, problem resolved.

[bluap]

2+ million exp no crash, I have no idea why the change.

I must have tired my gremlin out.

Anyway, problem resolved.

Good news