Windows has recovered from an unexpected shutdown

Hi all - having a serious problem with Bluescreen. Seems Windows after falling asleep, reboots and then posts this message upon login:

Windows has recovered from an unexpected shutdown.
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Ive zipped the XML and MiniDump files to this post that may contain additional information about the crashing. Unfortunately, I dont know how to read these files, or get much from them.

Thanks for any help you can provide! :)

Code:

On Tue 2009-12-22 17:30:21 your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x1000007E (0xC0000005, 0x90E61700, 0x807B5770, 0x807B5350)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\122209-55692-01.dmp
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 195.62 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 195.62

The driver at fault is the graphic driver. Is it fully updated from nVidia's website?
Welcome to NVIDIA - World Leader in Visual Computing Technologies

EDIT

But seeing the version in the little report, you are up-to-date... maybe someone with more expertise can help you out.

Silly me... that was the BSOD I had the other day... Here is the right one.

Code:

On Sun 2009-12-27 20:53:42 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF8A0044B4970, 0x2, 0x1, 0xFFFFF80002E9814C)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\122709-20763-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

Sorry but I'm using a software called "WhoCrashed" to analyze minidumps. And, I had to put them in the minidump folder where mine was also sitting.

Anyway, the error is in a standard Microsoft module - ntoskrnl.exe. A driver is at fault... but which one... Try to update every driver possible : Chipset, graphic card, sound card, printer, webcams, scanners, LAN (Ethernet card), etc.

EDIT

@wishmaster, that's was a little mistake on my side. You might want to read the new one above.