BSOD with different driver causes

Getting a BSOD pretty consistently when first trying to watch any youtube video. After the reboot the videos can be watched. But either after leaving hte laptop on for a while, or after is goes to sleep, upon trying to watch youtube videos again, the BSOD appears. There were a few instances of it occurring more randomly, but this is generally how it happens.

Occasionally it recovers and I get a pop-up saying nvlddmkm.sys driver failed and recovered.

I have BlueScreenView mini-dump. I am unsure if this is all the information needed for a post like this. If i missed anything I would be happy to provide more information.

System specs:
ASUS N61Jq A1 Laptop
i7 CPU Q720 @1.60GHz 1.60GHz
4 GB RAM
Windows 7 Home Premium, 64bit
ATI Mobility Radeon HD 5730; VRAM 1GB

This has been going on for about 2 months now. I have reinstalled all the latest drivers for the obvious culprits, especially the graphics driver. I have not tried to start fresh yet, I wanted to get some 2nd opinions on the matter before that.

Thank you for your time.

 

The txt from BSV shows 3 crashes, each with a different file faulted, it would be better to attach some of the most recent dmps in a zip file so we can see what else may be going on there.

 

Hmm, I am sorry, but those crashes are the most recent three, all happening for the same reason: trying to view a youtube video.

I will trigger the BSOD many more times, and zip those and send you the information again with a higher volume of crashes. Is there a way of doing it so more information is shown? I highlighted the dumps in BlueScreenView and clicked save, and it created this file.

 

Upload the dumps directly from the Minidump folder in Windows, zip them first. With the dumps themselves, we can check many of the driver dates, etc.

 

I have booted into safe mode and disabled all start up programs, as suggested. No problems yet. I am going to goot back into normal mode and start the process of elimination with the start-ups.

Attached are the mini-dump files.

 

This looks like the ATI graphics drivers are at the root of your problem, get the latest chipset drivers for your laptop, and the latest drivers from AMD. Check that you don't have any old versions of Flash or Java installed.

There's always a possibility of your security software interfering somewhere too.

Code:

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


Loading Dump File [C:\Users\Desktop\saabinmash\102010-17487-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`03259e50
Debug session time: Thu Oct 21 04:50:48.739 2010 (UTC + 1:00)
System Uptime: 0 days 5:17:10.769
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004059010, fffff88002ec0dcc, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
[B]Probably caused by : atikmpag.sys[/B] ( atikmpag+6dcc )

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

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

[B]VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.[/B]
Arguments:
Arg1: fffffa8004059010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002ec0dcc, 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: 
atikmpag+6dcc
fffff880`02ec0dcc 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`023c59c8 fffff880`02f5def8 : 00000000`00000116 fffffa80`04059010 fffff880`02ec0dcc 00000000`00000000 : nt!KeBugCheckEx
fffff880`023c59d0 fffff880`02f5dc02 : fffff880`02ec0dcc fffffa80`04059010 fffffa80`0c0eb360 fffffa80`07c55410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023c5a10 fffff880`0a5a3f07 : fffffa80`04059010 00000000`00000000 fffffa80`0c0eb360 fffffa80`07c55410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`023c5a40 fffff880`0a5cdb75 : 00000000`ffffffff 00000000`00129c8e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023c5b20 fffff880`0a5cc2bb : 00000000`00000102 00000000`00000002 00000000`00129c8e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`023c5b50 fffff880`0a59f2c6 : ffffffff`ff676980 fffffa80`07c55410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`023c5bf0 fffff880`0a5cbe7a : 00000000`00000000 fffffa80`0bd40d50 00000000`00000080 fffffa80`07c55410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`023c5d00 fffff800`03330c06 : 00000000`0127e016 fffffa80`07a98a00 fffffa80`03cd3040 fffffa80`07a98a00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`023c5d40 fffff800`0306ac26 : fffff880`009e9180 fffffa80`07a98a00 fffff880`009f40c0 4c54532b`4c465163 : nt!PspSystemThreadStartup+0x5a
fffff880`023c5d80 00000000`00000000 : fffff880`023c6000 fffff880`023c0000 fffff880`08d76b60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6dcc
fffff880`02ec0dcc 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+6dcc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c58bf41

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

===========================================================================================================================

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


Loading Dump File [C:\Users\\saabinmash\102110-21668-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`0329be50
Debug session time: Thu Oct 21 05:36:54.618 2010 (UTC + 1:00)
System Uptime: 0 days 0:45:46.617
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800acbf005, 0, fffff88006a7340c, 0}

Unable to load image BS_DEF.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BS_DEF.sys
*** ERROR: Module load completed but symbols could not be loaded for BS_DEF.sys

Could not read faulting driver name
[B]Probably caused by : BS_DEF.sys[/B] ( BS_DEF+240c )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8800acbf005, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88006a7340c, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033060e0
 fffff8800acbf005 

FAULTING_IP: 
BS_DEF+240c
fffff880`06a7340c 0fb7843b06000100 movzx   eax,word ptr [rbx+rdi+10006h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  [B]VISTA_DRIVER_FAULT[/B]

BUGCHECK_STR:  0x50

PROCESS_NAME:  IKernel.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008f033a0 -- (.trap 0xfffff88008f033a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffff8800acbffff
rdx=fffff8800acbe790 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006a7340c rsp=fffff88008f03530 rbp=0000000000000064
 r8=00000000000119cf  r9=00000000000119cf r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
BS_DEF+0x240c:
fffff880`06a7340c 0fb7843b06000100 movzx   eax,word ptr [rbx+rdi+10006h] ds:00ff:00000000`00010006=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000314ef14 to fffff800030ce740

STACK_TEXT:  
fffff880`08f03238 fffff800`0314ef14 : 00000000`00000050 fffff880`0acbf005 00000000`00000000 fffff880`08f033a0 : nt!KeBugCheckEx
fffff880`08f03240 fffff800`030cc82e : 00000000`00000000 00000000`0000ffff fffff800`03285800 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`08f033a0 fffff880`06a7340c : 00000000`000e0000 00000000`0001ffff 00000000`00009cdf fffff6fc`400565f0 : nt!KiPageFault+0x16e
fffff880`08f03530 00000000`000e0000 : 00000000`0001ffff 00000000`00009cdf fffff6fc`400565f0 00000000`000e0000 : BS_DEF+0x240c
fffff880`08f03538 00000000`0001ffff : 00000000`00009cdf fffff6fc`400565f0 00000000`000e0000 41412400`46534124 : 0xe0000
fffff880`08f03540 00000000`00009cdf : fffff6fc`400565f0 00000000`000e0000 41412400`46534124 24004353`46240046 : 0x1ffff
fffff880`08f03548 fffff6fc`400565f0 : 00000000`000e0000 41412400`46534124 24004353`46240046 00000000`00504141 : 0x9cdf
fffff880`08f03550 00000000`000e0000 : 41412400`46534124 24004353`46240046 00000000`00504141 00000000`00000000 : 0xfffff6fc`400565f0
fffff880`08f03558 41412400`46534124 : 24004353`46240046 00000000`00504141 00000000`00000000 00000000`0000ffff : 0xe0000
fffff880`08f03560 24004353`46240046 : 00000000`00504141 00000000`00000000 00000000`0000ffff 00000000`0000fff0 : 0x41412400`46534124
fffff880`08f03568 00000000`00504141 : 00000000`00000000 00000000`0000ffff 00000000`0000fff0 fffffa80`0b788a01 : 0x24004353`46240046
fffff880`08f03570 00000000`00000000 : 00000000`0000ffff 00000000`0000fff0 fffffa80`0b788a01 fffffa80`0bc70000 : 0x504141


STACK_COMMAND:  kb

FOLLOWUP_IP: 
BS_DEF+240c
fffff880`06a7340c 0fb7843b06000100 movzx   eax,word ptr [rbx+rdi+10006h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  BS_DEF+240c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BS_DEF

IMAGE_NAME:  BS_DEF.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a41d815

FAILURE_BUCKET_ID:  X64_0x50_BS_DEF+240c

BUCKET_ID:  X64_0x50_BS_DEF+240c

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

=============================================================================================================================

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


Loading Dump File [C:\Users\\Desktop\saabinmash\102210-18642-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03062000 PsLoadedModuleList = 0xfffff800`0329fe50
Debug session time: Fri Oct 22 07:58:49.478 2010 (UTC + 1:00)
System Uptime: 0 days 13:40:29.493
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80043330c0, fffff88002ef0dcc, 0, 2}

Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
[B]Probably caused by : atikmpag.sys[/B] ( atikmpag+6dcc )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80043330c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002ef0dcc, 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: 
atikmpag+6dcc
fffff880`02ef0dcc 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`023759c8 fffff880`0989eef8 : 00000000`00000116 fffffa80`043330c0 fffff880`02ef0dcc 00000000`00000000 : nt!KeBugCheckEx
fffff880`023759d0 fffff880`0989ec02 : fffff880`02ef0dcc fffffa80`043330c0 fffffa80`07cc2680 fffffa80`078c3410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02375a10 fffff880`09945f07 : fffffa80`043330c0 00000000`00000000 fffffa80`07cc2680 fffffa80`078c3410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02375a40 fffff880`0996fb75 : 00000000`ffffffff 00000000`0030266c 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02375b20 fffff880`0996e2bb : 00000000`00000102 00000000`00000002 00000000`0030266c 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02375b50 fffff880`099412c6 : ffffffff`ff676980 fffffa80`078c3410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02375bf0 fffff880`0996de7a : 00000000`00000000 fffffa80`04442990 00000000`00000080 fffffa80`078c3410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02375d00 fffff800`03376c06 : 00000000`fffffc32 fffffa80`079e8b60 fffffa80`03cd3040 fffffa80`079e8b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02375d40 fffff800`030b0c26 : fffff880`009e9180 fffffa80`079e8b60 fffff880`009f40c0 fffff880`01455534 : nt!PspSystemThreadStartup+0x5a
fffff880`02375d80 00000000`00000000 : fffff880`02376000 fffff880`02370000 fffff880`0493db60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6dcc
fffff880`02ef0dcc 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+6dcc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c58bf41

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

 

OK, well the good news is there has been no youtube related BSOD episodes while in normal mode and with all the startup programs have been disabled. I have updated the chipset drivers and AMD drivers too.

However, I did get one BSOD when trying to install an ASUS update program, that would allow me to more safely update my BIOS if need be. There were 2 setup executables inside the folder. One called ASUSsetup.exe, and the other just setup.exe. When opening the ASUSsetup it attempts to install something, then fails saying i have no motherboard, the error msg is full of typos though, and then just exits. The setup.exe caused a BSOD, but i think that's the wrong exe to click anyways.

Other than this episode the PC has run fine, with no BSOD interuptions. Here is the minidump of that one episode, including the previous ones.

As for updating java and flash, do i need to uninstall those and then get the new versions to be sure of them not being part of the problem?

 

Per the Java site: "We highly recommend users to remove all older versions of Java from your system."
I'd suggest downloading the latest 64-bit JRE, uninstalling your present version, and then installing the new package.

As far as Flash is concerned, there seems to be a more complicated process involved - I know that at one time Flash Player ran as an Active X component in Internet Explorer, but as an extension in Firefox.
You might check your version first, see if it's up to date before attempting to uninstall/reinstall.