Need Help Analysing BSOF

Desjade · 23 Jun 2010

Hi,

My brother is getting some random BSODs on his laptop and it would be very helpful if anyone could analyse it and tell me what is the right way of path.

I have zipped and attached the minidump files, but if you need anymore information, please let me know.

Thank you in advance.

(Sorry I accidently wrote BSOF instead of BSOD in the title)

Lordbob75 · 23 Jun 2010

Looks like 2 are caused by your graphics drivers, and one is caused by LSASS.exe

You should update your video drivers, and see if that fixes these. If not, then try running sfc /scannow from an elevated command prompt.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

FAULTING_IP: 
atikmdag+f05e
8ee3f05e 8bff            mov     edi,edi

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8aafdb48 8f3d1adb 00000116 8540d008 8ee3f05e nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8aafdb6c 8f3cb698 8ee3f05e c0000001 00000003 dxgkrnl+0x8cadb
8aafdba0 8f3d2991 8540d008 8540d008 88a0107e dxgkrnl+0x86698
8aafdbbc 9023992c 00000000 00000102 85d3d5f0 dxgkrnl+0x8d991
8aafdc34 90263a32 fffffcfb 00068ff7 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8aafdc5c 90264153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8aafdc98 902408f0 8aafdc90 86ebb3c8 86e18658 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8aafdd28 902654b7 85d3d5f0 82a513f1 85d3d5f0 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8aafdd3c 90265573 85d3d5f0 00000000 86553d48 dxgmms1!VidSchiRun_PriorityTable+0xf
8aafdd50 82c236bb 85d3d5f0 970a4107 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8aafdd90 82ad50f9 902654f4 85d3d5f0 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmdag+f05e
8ee3f05e 8bff            mov     edi,edi

SYMBOL_NAME:  atikmdag+f05e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a8a1a1e

FAILURE_BUCKET_ID:  0x116_IMAGE_atikmdag.sys

BUCKET_ID:  0x116_IMAGE_atikmdag.sys

Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

FAULTING_IP: 
atikmdag+f05e
8e24305e 8bff            mov     edi,edi

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8aa0fb48 8e7d5adb 00000116 850bd510 8e24305e nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8aa0fb6c 8e7cf698 8e24305e c0000001 00000003 dxgkrnl+0x8cadb
8aa0fba0 8e7d6991 850bd510 850bd510 88bf207e dxgkrnl+0x86698
8aa0fbbc 8ea4492c 00000000 00000102 86509788 dxgkrnl+0x8d991
8aa0fc34 8ea6ea32 fffffcfb 00028f96 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8aa0fc5c 8ea6f153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8aa0fc98 8ea4b8f0 8aa0fc90 8510b5e8 86abddd0 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8aa0fd28 8ea704b7 86509788 82a5b3f1 86509788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8aa0fd3c 8ea70573 86509788 00000000 86536538 dxgmms1!VidSchiRun_PriorityTable+0xf
8aa0fd50 82c2d6bb 86509788 970613ee 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8aa0fd90 82adf0f9 8ea704f4 86509788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmdag+f05e
8e24305e 8bff            mov     edi,edi

SYMBOL_NAME:  atikmdag+f05e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a8a1a1e

FAILURE_BUCKET_ID:  0x116_IMAGE_atikmdag.sys

BUCKET_ID:  0x116_IMAGE_atikmdag.sys

Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Unknown bugcheck code (c00002e3)
Unknown bugcheck description
Arguments:
Arg1: 8c285c80
Arg2: c0000189
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0xc00002e3

ERROR_CODE: (NTSTATUS) 0xc00002e3 - Security Accounts Manager initialization failed because of the following error:  %hs  Error Status: 0x%x.  Please click OK to shutdown this system and reboot into Safe Mode, check the event log for more detailed information.

EXCEPTION_CODE: (NTSTATUS) 0xc00002e3 - Security Accounts Manager initialization failed because of the following error:  %hs  Error Status: 0x%x.  Please click OK to shutdown this system and reboot into Safe Mode, check the event log for more detailed information.

EXCEPTION_PARAMETER1:  8c285c80

EXCEPTION_PARAMETER2:  c0000189

EXCEPTION_PARAMETER3:  00000000

EXCEPTION_PARAMETER4: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  lsass.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82aee1cb to 828f3e10

STACK_TEXT:  
8c4d28e4 82aee1cb 0000004c c00002e3 8c4d296c nt!KeBugCheckEx+0x1e
8c4d2934 82b405d9 00000001 0000004c c00002e3 nt!PoShutdownBugCheck+0x81
8c4d2af4 829f2c2e c00002e3 00000002 00000001 nt!ExpSystemErrorHandler+0x567
8c4d2ca4 829f2af5 c00002e3 00000002 00000001 nt!ExpRaiseHardError+0xbf
8c4d2d14 8285a47a c00002e3 00000002 00000001 nt!NtRaiseHardError+0x11a
8c4d2d14 77ce64f4 c00002e3 00000002 00000001 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0016fcc0 00000000 00000000 00000000 00000000 0x77ce64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiFastCallEntry+12a
8285a47a f6456c01        test    byte ptr [ebp+6Ch],1

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  nt!KiFastCallEntry+12a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b1e090a

FAILURE_BUCKET_ID:  0xc00002e3_nt!KiFastCallEntry+12a

BUCKET_ID:  0xc00002e3_nt!KiFastCallEntry+12a

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

~Lordbob

**Capt.Jack Sparrow** · 23 Jun 2010

Hello !!

You could check this thread for more info in your Bugcheck https://www.sevenforums.com/crash-loc...eshooting.html

- Captain

ttran · 23 Jun 2010

Hi
I also see that you have some old drivers, please download and install fresh copy of them:

Code:

92938000 92975000   VSTAZL3  VSTAZL3.SYS  Thu Oct 16 07:30:03 2008 (48F68B0B)
81f12000 81fc7000   VSTCNXT3 VSTCNXT3.SYS Thu Oct 16 07:29:13 2008 (48F68AD9)
81e10000 81f12000   VSTDPV3  VSTDPV3.SYS  Thu Oct 16 07:32:04 2008 (48F68B84)

They belong to Conexant SoftK56 Modem Driver, Conexant products

Also, you have some kind of driver related to O2 media products, please update them if you know

Code:

o2media  o2media.sys  Mon Nov 14 12:28:33 2005 (43782081)

Please do this update after all the above suggestion

~Tuan

Desjade · 23 Jun 2010

Thanks a lot for all these suggestions.

The only problem is that my brother (who owns the PC I am talking about) lives 2 hours away from me. So I am going to have to wait for another trip to his place to try these useful tips.

So, it might take sometime before I give you all the results of me trying out your suggestions.

Just one last question: The ELEVATED command prompt is when you run command prompt as administrator right?

**Capt.Jack Sparrow** · 23 Jun 2010

Desjade said:

Just one last question: The ELEVATED command prompt is when you run command prompt as administrator right?

Yes .. !!