Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSoD w/error code


  • Please log in to reply
7 replies to this topic

#1 mxlm

mxlm

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:05 AM

Posted 29 December 2009 - 08:49 PM

I have a Toshiba Qosmio X505-Q830. I was a few minutes into a game of Majesty 2 last night (well, er, this morning) when I got a BSOD and the system rebooted. The system will boot in safe mode but it will not boot in normal mode unless I disable or uninstall the drivers for my nvidia GPU.

I did check toshiba's page for alternate drivers in the hope that might fix the problem, but they appear to only have one option for my system, which are the drivers I am currently unable to use.

Majesty--Steam, actually, as I'm running a digital copy through that service--did install something before the session which preceded the crash, but I'm unsure what (the installation was very brief and I was unable to read the message before it went away and the game started, and my efforts to search the game-related forums haven't borne fruit), and so have nothing to bolster my suspicion that there's some sort of incompatibility between whatever was installed and the nvidia drivers (I thought it might have been one of the vc++ libraries, but I uninstalled all of those and that didn't resolve the problem). Also, well, I'm only as computer literate as I need to be to play games, so my suspicion isn't worth much.

I would use a system restore point but I neglected to create one. A mistake I'll not repeat.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03205000 PsLoadedModuleList = 0xfffff800`03442e50
Debug session time: Tue Dec 29 11:44:55.767 2009 (GMT-8)
System Uptime: 0 days 0:00:20.032
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols

Loading unloaded module list
...
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80070a7010, fffff880058996a0, 0, 2}

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+146a0 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80070a7010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880058996a0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+146a0
fffff880`058996a0 48895c2420	  mov	 qword ptr [rsp+20h],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`051469c8 fffff880`044ffef8 : 00000000`00000116 fffffa80`070a7010 fffff880`058996a0 00000000`00000000 : nt!KeBugCheckEx
fffff880`051469d0 fffff880`044ffc02 : fffff880`058996a0 fffffa80`070a7010 fffffa80`06ac6680 fffffa80`06ab2010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05146a10 fffff880`045a6f07 : fffffa80`070a7010 00000000`00000000 fffffa80`06ac6680 fffffa80`06ab2010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05146a40 fffff880`045d0b75 : 00000000`ffffffff 00000000`00000414 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05146b20 fffff880`045cf2bb : 00000000`00000102 00000000`00000000 00000000`00000414 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05146b50 fffff880`045a22c6 : ffffffff`ff676980 fffffa80`06ab2010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05146bf0 fffff880`045cee7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`04f2ac68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05146d00 fffff800`0351a166 : 00000000`016a25f7 fffffa80`06b89620 fffffa80`03c6e890 fffffa80`06b89620 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05146d40 fffff800`03255486 : fffff800`033efe80 fffffa80`06b89620 fffff800`033fdc40 fffff880`01258a90 : nt!PspSystemThreadStartup+0x5a
fffff880`05146d80 00000000`00000000 : fffff880`05147000 fffff880`05141000 fffff880`07a2db60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck; kb

FOLLOWUP_IP: 
nvlddmkm+146a0
fffff880`058996a0 48895c2420	  mov	 qword ptr [rsp+20h],rbx

SYMBOL_NAME:  nvlddmkm+146a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a935c1d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------


BC AdBot (Login to Remove)

 


#2 keyboardNinja

keyboardNinja

    Bleepin' Ninja


  • Members
  • 4,815 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh interwebz
  • Local time:05:05 AM

Posted 29 December 2009 - 09:35 PM

Yeah, I have Recovery Commander bundled with my Fix-It Utilities software. It automatically creates system restore and recovery commander checkpoints whenever I install something. It's saved my butt more than once.

As far as the graphics card goes, this is not the first time I have seen issues with that brand. And also with a Toshiba, I'm not surprised you're having problems (Toshiba is on my list of brands I'll never buy).

The memory dump gave you the problem:

"GRAPHICS_DRIVER_TDR_FAULT

...

nvlddmkm.sys"

^That's the driver causing the problems. Seeing as how you cannot use any other drivers, and the system cannot work with the current one, the only solution I see is to get another graphics card.

Uninstalling the game might take away whatever installed that you suspect caused the problems, but that is not likely. That is the first thing I would try, though (before dropping some dough on a new GPU). If that doesn't work, trying to locate some older drivers would be your next option (since the current ones don't work and newer ones don't exist). Sometimes rolling back new, faulty drivers to the old, faithful ones can fix things. But that is no guarantee either.

Driver problems can be a major pain in the Windows world, but we have to learn to live with them. :huh:

Let me know what happens....
PICNIC - Problem In Chair, Not In Computer

Posted Image Posted Image

20 Things I Learned About Browsers and the Web

#3 mxlm

mxlm
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:05 AM

Posted 30 December 2009 - 04:20 AM

Uninstalling the game didn't help, installing various driver versions found on video2go didn't help. At this point my plan is to go buy some blank DVDs tomorrow and reinstall windows. Uh, and not reinstall that particular game, ever. Ah well.

Thanks for your input, though!

Edited by mxlm, 30 December 2009 - 04:20 AM.


#4 keyboardNinja

keyboardNinja

    Bleepin' Ninja


  • Members
  • 4,815 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh interwebz
  • Local time:05:05 AM

Posted 30 December 2009 - 03:58 PM

Yeah, reinstalling Windows is almost always a surefire method of fixing problems (albeit time-consuming). I'll bet you'll remember that Restore Point next time. :huh:

You're welcome. :huh:

Enjoy Windows 7 (and your games)! :thumbup2:
PICNIC - Problem In Chair, Not In Computer

Posted Image Posted Image

20 Things I Learned About Browsers and the Web

#5 mxlm

mxlm
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:05 AM

Posted 02 January 2010 - 03:32 PM

Heh. So reinstalling windows didn't help. During the 'install driver, reboot; install driver, reboot; ad infinitum' phase of the installation, well, after one install/reboot sequence I started getting the same BSoD on startup again. Except this time I can't get into safe mode because windows hasn't finished installing. Heh. (Er, I want to make it clear that the amused irritation I'm displaying here is in no way directed at keyboard ninja).

So, I'm thinking that means the video card is dead. That sound right/wrong to anyone?

ETA: Since it might matter, I was using the Toshiba Recovery Wizard to return the computer to its factory settings, which evidently includes a reinstall of windows.

Edited by mxlm, 02 January 2010 - 03:38 PM.


#6 keyboardNinja

keyboardNinja

    Bleepin' Ninja


  • Members
  • 4,815 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh interwebz
  • Local time:05:05 AM

Posted 03 January 2010 - 08:04 PM

Huh....that's weird.

But when I said reinstalling Windows, I meant a fresh, clean install off the disk. Not a factory restore. That might make a difference.

It very well could be the video card itself. Although on a new computer, it seems unlikely.

Not really sure. You got a spare GPU you can drop in it?
PICNIC - Problem In Chair, Not In Computer

Posted Image Posted Image

20 Things I Learned About Browsers and the Web

#7 mxlm

mxlm
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:05 AM

Posted 04 January 2010 - 05:12 PM

But when I said reinstalling Windows, I meant a fresh, clean install off the disk. Not a factory restore. That might make a difference.

In its infinite wisdom, Toshiba did not see fit to supply a windows disc; as best I could tell, there was no way to do a proper Windows reinstall with what was provided. I should have made that clear, sorry. No spare GPU, and I wouldn't know how to go about dropping one into a laptop. Desktop, sure, but I don't even know how this case opens.

I ended up packing the thing off to Toshiba's repair center (actually, didn't I read something about that really being UPS' repair center? Well, whatever). Presumably they'll figure it out.

Once again, thanks!

#8 keyboardNinja

keyboardNinja

    Bleepin' Ninja


  • Members
  • 4,815 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh interwebz
  • Local time:05:05 AM

Posted 04 January 2010 - 10:37 PM

Well, good luck with that.

And you're welcome. :huh:
PICNIC - Problem In Chair, Not In Computer

Posted Image Posted Image

20 Things I Learned About Browsers and the Web




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users