[Troubleshoot] Ray Sum's Graphics card crashing (Part 7)

Continued from:
http://wai-pc.blogspot.com/2011/10/troubleshoot-ray-sums-graphics-card.html

Wow, it's been just over 2 weeks since last playing around much with the laptop, in which period it has only crashed a few times (only in windows though mind using Google Chrome on facebook, now I can't remember if it was when flash was running or what!)
Anyway, a quick refresh of my mine reminds me that I wrote something small on facebook as a note as self reminder (did on 6th March 2011):
http://www.facebook.com/note.php?note_id=10150118312031624

Blue screen of death notes

http://www.carrona.org/bsodindx.html#0x00000116

http://msdn.microsoft.com/en-us/windows/hardware/gg487368.aspx


258.96_notebook_winvista_win7_64bit_international_whql
260.99_notebook_winvista_win7_64bit_international_whql


All gave 0x00000017 codes.

Mobo BIOS updated incase
bios-20101214131650

Windows Registry cleaned in case
ccsetup304

Other wiping tools
dotNetFx40_Full_setup
DriverSweeper_2.1.0-[Guru3D.com]

Toshiba default drivers attempt to install
display-20100608161152

WIN Dbg debugger installed to check dump files.
Symbols locations - SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Take ownership of all files in C:\Windows\MiniDump and then open Ctrl+D latest mini dumps

Typical 0x00000017 errors dump

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\030111-19531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03651000 PsLoadedModuleList = 0xfffff800`0388ee50
Debug session time: Tue Mar 1 23:18:51.843 2011 (UTC + 1:00)
System Uptime: 0 days 2:11:23.108
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8009a554e0, fffff88004863180, 0, 0}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+15180 )

Followup: MachineOwner

To read up and attempt
http://msdn.microsoft.com/en-us/windows/hardware/gg487368.aspx
update Direct X and finally rip apart the laptop casing and check connections and temperatures!

Anyway back to the task at hand eh.
1st major task, download an updated Toshiba 'tested & certified' driver!
http://uk.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=UK

This search shows 4 pages of updates/downloadable drivers but only 5 caught my attention
* 3 registry patches (no info attached so no idea what it patches)
* nVidia Display Driver Version 8.16.11.8875 (06/08/2010)
   This driver enhances the functionality of your display device and allows you to perform different settings, such as Color Management, Monitor Properties or Overlay Control. You can also get help if you have any display related troubleshooting issues.
* BIOS Update Version 2.00-WIN

For the purpose of ability of testing long term, I'll try options 2 and 3.  Registry patches can wait (as they would have to be applied each system restore, but then again so would the gfx drivers, only BIOS is permanent!)

Ah snap, BIOS update failed cos it already is the latest (at least that's one thing less to have to do and test!)
See post 2.