Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: BSOD while idle or using opera

05 Jan 2010   #1

Windows 7 x64
 
 
BSOD while idle or using opera

Hi,
I bought Toshiba Satellite A500-1DN few feeks ago, and soon after i started experiencing BSOD's quite frequently.

They happened mostly, while computer was either idle, or I was using opera. Before seeing BSOD cursor steadily stopped moving, and computer won't respond at all. I could only turn it off with the power button, or wait until BSOD would appear. It never happened while playing games, or watching movies, but maybe I was just lucky.

I have updated my graphic drivers from the manufacture website, most recent bios, but the problem still persists. I am using Windows 7 x64. I am attaching dump files, maybe someone can help me solve this problem.

My System SpecsSystem Spec
.

05 Jan 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Argalt View Post
Hi,
I bought Toshiba Satellite A500-1DN few feeks ago, and soon after i started experiencing BSOD's quite frequently.

They happened mostly, while computer was either idle, or I was using opera. Before seeing BSOD cursor steadily stopped moving, and computer won't respond at all. I could only turn it off with the power button, or wait until BSOD would appear. It never happened while playing games, or watching movies, but maybe I was just lucky.

I have updated my graphic drivers from the manufacture website, most recent bios, but the problem still persists. I am using Windows 7 x64. I am attaching dump files, maybe someone can help me solve this problem.

Hi and welcome

you sure had enough of them. These were all caused by your video driver nvlddmkm.sys. you should ungrade it you you problems should diminsh.

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

I would also run a system file check to repair your system files to do that type
cmd in search>right click and run as admin>sfc /scannow

Ken J+


Code:
010110-18704-01.dmp    1/1/2010 5:24:49 PM        0x00000116    fffffa80`0442b010    fffff880`04ec8f90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
010410-18330-01.dmp    1/4/2010 3:10:33 PM        0x00000116    fffffa80`0409a4e0    fffff880`04ee0f90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
120509-21871-01.dmp    12/5/2009 8:03:22 PM        0x00000116    fffffa80`07b18130    fffff880`04ea3f90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
120909-18049-01.dmp    12/9/2009 10:19:08 PM        0x00000116    fffffa80`04049010    fffff880`04e1df90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
120909-20935-01.dmp    12/9/2009 9:35:24 PM        0x00000116    fffffa80`0422c4e0    fffff880`04dfbf90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
121109-18470-01.dmp    12/11/2009 2:50:57 AM        0x00000116    fffffa80`0460f010    fffff880`04eaff90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
121109-25474-01.dmp    12/11/2009 7:03:23 PM        0x00000116    fffffa80`07f664e0    fffff880`04ebaf90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
121509-20514-01.dmp    12/15/2009 10:48:22 AM        0x00000116    fffffa80`06d8d4e0    fffff880`04df1f90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
122509-21762-01.dmp    12/25/2009 7:31:16 PM        0x00000116    fffffa80`04182010    fffff880`04e3df90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
122809-18735-01.dmp    12/28/2009 10:21:33 PM        0x00000116    fffffa80`07a79010    fffff880`04df0f90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
122909-16738-01.dmp    12/29/2009 12:16:10 AM        0x00000116    fffffa80`045b64e0    fffff880`05c1bf90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
123009-17160-01.dmp    12/30/2009 8:10:05 PM        0x00000116    fffffa80`040d24e0    fffff880`04e5ff90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
123009-17534-01.dmp    12/30/2009 7:51:40 PM        0x00000116    fffffa80`0426f010    fffff880`04e47f90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder (2)\122509-21762-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`0324fe50
Debug session time: Fri Dec 25 13:30:13.824 2009 (GMT-5)
System Uptime: 0 days 6:17:49.791
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004182010, fffff88004e3df90, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\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+5e7f90 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+5e7f90
fffff880`04e3df90 4053            push    rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06844b48 fffff880`040c8ef8 : 00000000`00000116 fffffa80`04182010 fffff880`04e3df90 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`06844b50 00000000`00000116 : fffffa80`04182010 fffff880`04e3df90 ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5cef8
fffff880`06844b58 fffffa80`04182010 : fffff880`04e3df90 ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
fffff880`06844b60 fffff880`04e3df90 : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`04182010 : 0xfffffa80`04182010
fffff880`06844b68 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`04182010 fffff880`0409c867 : nvlddmkm+0x5e7f90
fffff880`06844b70 00000000`00000004 : 00000000`00000001 fffffa80`04182010 fffff880`0409c867 fffff880`04e3df90 : 0xffffffff`c000009a
fffff880`06844b78 00000000`00000001 : fffffa80`04182010 fffff880`0409c867 fffff880`04e3df90 fffffa80`06abd000 : 0x4
fffff880`06844b80 fffffa80`04182010 : fffff880`0409c867 fffff880`04e3df90 fffffa80`06abd000 00000000`00000000 : 0x1
fffff880`06844b88 fffff880`0409c867 : fffff880`04e3df90 fffffa80`06abd000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`04182010
fffff880`06844b90 fffff880`04e3df90 : fffffa80`06abd000 00000000`00000000 ffffffff`c000009a ffffffff`ff676980 : dxgkrnl+0x30867
fffff880`06844b98 fffffa80`06abd000 : 00000000`00000000 ffffffff`c000009a ffffffff`ff676980 fffffa80`06abc010 : nvlddmkm+0x5e7f90
fffff880`06844ba0 00000000`00000000 : ffffffff`c000009a ffffffff`ff676980 fffffa80`06abc010 00000000`00000000 : 0xfffffa80`06abd000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+5e7f90
fffff880`04e3df90 4053            push    rbx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+5e7f90

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a6827e0

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

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

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

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


FAULTING_IP: 
nvlddmkm+5e7f90
fffff880`04e3df90 4053            push    rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06844b48 fffff880`040c8ef8 : 00000000`00000116 fffffa80`04182010 fffff880`04e3df90 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`06844b50 00000000`00000116 : fffffa80`04182010 fffff880`04e3df90 ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5cef8
fffff880`06844b58 fffffa80`04182010 : fffff880`04e3df90 ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
fffff880`06844b60 fffff880`04e3df90 : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`04182010 : 0xfffffa80`04182010
fffff880`06844b68 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`04182010 fffff880`0409c867 : nvlddmkm+0x5e7f90
fffff880`06844b70 00000000`00000004 : 00000000`00000001 fffffa80`04182010 fffff880`0409c867 fffff880`04e3df90 : 0xffffffff`c000009a
fffff880`06844b78 00000000`00000001 : fffffa80`04182010 fffff880`0409c867 fffff880`04e3df90 fffffa80`06abd000 : 0x4
fffff880`06844b80 fffffa80`04182010 : fffff880`0409c867 fffff880`04e3df90 fffffa80`06abd000 00000000`00000000 : 0x1
fffff880`06844b88 fffff880`0409c867 : fffff880`04e3df90 fffffa80`06abd000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`04182010
fffff880`06844b90 fffff880`04e3df90 : fffffa80`06abd000 00000000`00000000 ffffffff`c000009a ffffffff`ff676980 : dxgkrnl+0x30867
fffff880`06844b98 fffffa80`06abd000 : 00000000`00000000 ffffffff`c000009a ffffffff`ff676980 fffffa80`06abc010 : nvlddmkm+0x5e7f90
fffff880`06844ba0 00000000`00000000 : ffffffff`c000009a ffffffff`ff676980 fffffa80`06abc010 00000000`00000000 : 0xfffffa80`06abd000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+5e7f90
fffff880`04e3df90 4053            push    rbx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+5e7f90

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a6827e0

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------
My System SpecsSystem Spec
05 Jan 2010   #3

Windows 7 x64
 
 

Thanks, I appreciate your fast response.

I've run the system scan but it didn't show any violation of system integrity.

As for the first advice - how should I downgrade this driver or file? There is only one display driver on manufacturer website, the one I installed. Is there any way to do that without formating the system?

Is there possibility that's the graphic card is faulty?

Thanks again
My System SpecsSystem Spec
.


05 Jan 2010   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Argalt View Post
Thanks, I appreciate your fast response.

I've run the system scan but it didn't show any violation of system integrity.

As for the first advice - how should I downgrade this driver or file? There is only one display driver on manufacturer website, the one I installed. Is there any way to do that without formating the system?

Is there possibility that's the graphic card is faulty?

Thanks again
A
The other thing you might want to try is directx. It was also involved. you should search for that subject here

Ken J+
My System SpecsSystem Spec
05 Jan 2010   #5

Windows 7 x64
 
 

I've downloaded direct'x installer app, from microsoft website, during installation it added 'additional content' only, will see if it helps.
My System SpecsSystem Spec
21 Jan 2010   #6

windows 7 x64 6.1.7600
 
 
solved or not?

heloo everyone

i have the same notebook and the same problem! ony that i'm not using opera!
could you plesc let us know if your directx upgrade solved the problem?
also seems that my notebook is taking too long to start up! more then 25 second!
thank you and good day!
My System SpecsSystem Spec
21 Jan 2010   #7

windows 7 x64 6.1.7600
 
 

sorry, i forgot a detail! action center says that my graphic card was crashed 3 times! and whet it tryes to search for solutions finds nothing!
thanks
My System SpecsSystem Spec
21 Jan 2010   #8
Microsoft MVP

 
 

andreipga85 - Please start your own topic so that your issue can get the individual attention that it deserves.
My System SpecsSystem Spec
22 Jan 2010   #9

windows 7 x64 6.1.7600
 
 

hello, thanks for your indication!
i will do that asa soon as i will get home because i need to complet my profile with all the data of my notebook!

thank you,
have a nice day!
My System SpecsSystem Spec
Reply

 BSOD while idle or using opera





Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:46 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33