Repeated kernel crash in 10.04

what is the output of "uname -r"

uname -r:
2.6.32-32-generic

lsmod:
Module Size Used by
snd_hda_codec_realtek 203376 1
binfmt_misc 6587 1
ppdev 5259 0
vboxnetadp 6326 0
vboxnetflt 15280 0
hwmon_vid 2298 0
coretemp 4417 0
snd_hda_intel 22069 2
snd_hda_codec 74201 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 5412 1 snd_hda_codec
snd_pcm_oss 35308 0
snd_mixer_oss 13746 1 snd_pcm_oss
snd_pcm 70694 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 1338 0
snd_seq_oss 26722 0
snd_seq_midi 4557 0
snd_rawmidi 19056 1 snd_seq_midi
snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
snd_seq 47263 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 19098 2 snd_pcm,snd_seq
snd_seq_device 5700 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
vboxdrv 190626 2 vboxnetadp,vboxnetflt
snd 54244 16 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
joydev 8740 0
fbcon 35102 71
tileblit 1999 1 fbcon
font 7557 1 fbcon
bitblit 4707 1 fbcon
softcursor 1189 1 bitblit
serio_raw 3978 0
nvidia 9961216 38
agpgart 31724 1 nvidia
vga16fb 11385 1
vgastate 8961 1 vga16fb
soundcore 6620 1 snd
snd_page_alloc 7076 2 snd_hda_intel,snd_pcm
i2c_nforce2 5199 0
lp 7028 0
parport 32635 2 ppdev,lp
usbhid 36110 0
hid 67096 1 usbhid
floppy 53016 0
forcedeth 49556 0
pata_amd 8766 0
ahci 32360 2

please run "sudo apt-get update"

after that post the output of "apt-cache policy linux-image"

because i cant find 2.6.32-32 in the official ubuntu-repos (using the search from packages.ubuntu.com)

linux-image:
  Installed: (none)
  Candidate: 2.6.32.32.38
  Version table:
     2.6.32.32.38 0
        500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
        500 http://ubuntu.osuosl.org/ubuntu/ lucid-updates/main Packages
     2.6.32.21.22 0
        500 http://ubuntu.osuosl.org/ubuntu/ lucid/main Packages

@Michael Basse
It's easier to check on Launchpad for package versions. You can find 2.6.32-32 at https://launchpad.net/ubuntu/+source/linux, and discover that it's the current (stable) kernel version in Lucid.

Also, there is no reason to think that the linux-image package would be installed. For example, on my system:

ek@Apok:~$ apt-cache policy linux-image linux-image-generic
linux-image:
  Installed: (none)
  Candidate: 2.6.38.10.25
  Version table:
     2.6.38.10.25 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main amd64 Packages
     2.6.38.8.22 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
linux-image-generic:
  Installed: 2.6.38.10.25
  Candidate: 2.6.38.10.25
  Version table:
 *** 2.6.38.10.25 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     2.6.38.8.22 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages

Any ideas on how to address this?

I recommend reporting this as a bug in linux in Ubuntu. Besides leading to an eventual solution to the problem (assuming this is a bug, which is likely, rather than some local malfunction with your hardware or configuration), reporting this as a bug may also lead to workarounds being discovered, or to people who know a workaround for your problem letting you know.

Before reporting it as a bug, you should first read https://help.ubuntu.com/community/ReportingBugs carefully. After searching to see if someone has already reported a bug with kernel messages that look just like yours (but don't sweat it -- it's often quite hard to tell if a kernel bug is the same or not and often best to err on the side of assuming it may be different, and your bug can be marked a duplicate of an existing bug even after it's filed, if your bug has been found to have been reported before), you can initiate the process of reporting your bug with "ubuntu-bug linux". That will make sense after you've read the ReportingBugs wiki page linked to above. If your machine crashes often enough that you're concerned it may crash as you are composing your bug report, then you may instead want to run "apport-cli linux", submit the automatically collected information that way, and save the URL that it produces (e.g., email it to yourself, save it in a file on a USB flash drive). Then you can open the URL on another machine (or on the same machine running another operating system that is functioning more stably) and fill out the bug report.

When reporting this as a bug, please make sure to include the excerpt from kern.log that you posted in your description here, as well as the output of "lsmod" (from post #2). The output of "uname -r" will be automatically included in your bug report. It's a good idea to also include the output of "lspci" and of "sudo lshw" as well. For increased comprehensibility of your bug report, you might want to save the outputs of "lsmod", "lspci" and (especially, as it's long) "sudo lshw" in (separate) text files, and attach the files to the bug report. In your report, please specific more precisely how frequently the crashes occur, as well as what date and time (including time zone information) the last crash occurred, to make it easy for developers to find it in the logs.

Once you've reported the bug, please link it and this question to each other using the "Link existing bug" link at the top of this question page.

It is by no means obligatory for you to file a bug report about this, and even if you choose not to, it's imaginably possible that someone might come along and offer a solution or workaround to your problem. However, besides contributing to the Ubuntu project, reporting this kernel panic as a bug is the best way I can think of to progress toward a fix or workaround for the problem.