Bios corruption problem?

[WohthaN]

Hi all,
today, using beryl as always for some months on my dell inspiron 9400 equipped with a 7900gs, i occurred in a strange problem:
while switching the desktop, firefox's window got corrupted (showing strange colored boxes instead of the content), and few time later the system crashed.
After the shut down, you can see in the photos what i have:
strong graphic corruption, at the bios bootsplash, in the bios, on grub, on the shell.
As espected, even if the system is booting "without problems", x isn't starting anymore, and the nvidia kernel module is having problems as you can see in the "dmesg" file attacched.
It is with 9746 driver and 2.6.20. Any idea on how to fix it? Should i call Dell to change the board or it is fixable? Help!

[WohthaN]

And here the log of the nvidia tool!

[netllama]

This looks like a hardware problem. I'd suggest contacting Dell for assistance.

[WohthaN]

I'll surely do. Just for information, i had the same kind of problem on 2 different acer aspire 1524 with a 5700, that had burn 5 cards in less than 2 years. Every time sostituited in warranty, but i mean.. i changed that "old" laptop with this one fearing of that problem... and now here it is with a strongly different hardware! I think, maybe there's a bug somewhere? Or beryl stress the board too much?!? I forgot to say that some days before the crack i had some sporadic video corruption while playing some videos in kaffeine, maybe there is some kind of relation between aiglx and application using xv or gl? Thank you for helping!

[1neo1]

Look like video card have overheat and damage GPU or bad driver.

[WohthaN]

Little update, if this can provide somehow an help:

Galileo:~# nvclock -s
Xlib: extension "NV-CONTROL" missing on display "localhost:10.0".
Card: Unknown Nvidia card
Card number: 1
Memory clock: -1073741.875 MHz
GPU clock: 200.475 MHz

Galileo:~# lspci | grep nVidia
01:00.0 VGA compatible controller: nVidia Corporation GeForce Go 7900 GS (rev a1)

Is there any sense in this?
I never tryed nvclock before the problem so i can't say if this is normal...