Login    Forum    Search    FAQ

Board index » Upgrading and Repairing Forum » Windows OS




Post new topic Reply to topic  [ 15 posts ] 
Author Message
 Post subject: Minidump stuff
 Post Posted: Wed Jun 08, 2011 6:37 pm 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1001
Scott, I was installing stuff today when the PC I was trying to shut down crashed. I've examined the dump file and came up with stuff. Here's "Command" stuff:


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


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

Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x82a49000 PsLoadedModuleList = 0x82b60c70
Debug session time: Wed Jun 8 13:06:01.314 2011 (UTC - 7:00)
System Uptime: 0 days 0:14:50.970
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {89e5a510, 947b9d68, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\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
Probably caused by : atikmpag.sys ( atikmpag+5d68 )

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: 89e5a510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 947b9d68, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+5d68
947b9d68 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:
ad320bc0 8fbb3046 00000116 89e5a510 947b9d68 nt!KeBugCheckEx+0x1e
ad320be4 8fbb3d36 947b9d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
ad320c04 8fb504fd 00000000 00000102 8853b008 dxgkrnl!TdrIsRecoveryRequired+0xa1
ad320c6c 8fb6cf8b 8853b008 0000dc46 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
ad320c98 8fb6cceb 8853b008 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
ad320cc4 8fb3e5c0 00000002 82a8d906 8853b008 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
ad320d54 8fb6d032 8853b008 82a8d906 8853b008 dxgkrnl!VidSchiScheduleCommandToRun+0xac
ad320d68 8fba2698 8853b008 00000000 89af5670 dxgkrnl!VidSchiRun_PriorityTable+0xf
ad320d7c 82c1ef7a 8853b008 31882630 00000000 dxgkrnl!VidSchiWorkerThread+0x62
ad320dc0 82a87efe 8fba2636 8853b008 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+5d68
947b9d68 8bff mov edi,edi

SYMBOL_NAME: atikmpag+5d68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3541

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

BUCKET_ID: 0x116_IMAGE_atikmpag.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: 89e5a510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 947b9d68, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+5d68
947b9d68 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:
ad320bc0 8fbb3046 00000116 89e5a510 947b9d68 nt!KeBugCheckEx+0x1e
ad320be4 8fbb3d36 947b9d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
ad320c04 8fb504fd 00000000 00000102 8853b008 dxgkrnl!TdrIsRecoveryRequired+0xa1
ad320c6c 8fb6cf8b 8853b008 0000dc46 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
ad320c98 8fb6cceb 8853b008 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
ad320cc4 8fb3e5c0 00000002 82a8d906 8853b008 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
ad320d54 8fb6d032 8853b008 82a8d906 8853b008 dxgkrnl!VidSchiScheduleCommandToRun+0xac
ad320d68 8fba2698 8853b008 00000000 89af5670 dxgkrnl!VidSchiRun_PriorityTable+0xf
ad320d7c 82c1ef7a 8853b008 31882630 00000000 dxgkrnl!VidSchiWorkerThread+0x62
ad320dc0 82a87efe 8fba2636 8853b008 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+5d68
947b9d68 8bff mov edi,edi

SYMBOL_NAME: atikmpag+5d68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3541

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

BUCKET_ID: 0x116_IMAGE_atikmpag.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: 89e5a510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 947b9d68, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+5d68
947b9d68 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:
ad320bc0 8fbb3046 00000116 89e5a510 947b9d68 nt!KeBugCheckEx+0x1e
ad320be4 8fbb3d36 947b9d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
ad320c04 8fb504fd 00000000 00000102 8853b008 dxgkrnl!TdrIsRecoveryRequired+0xa1
ad320c6c 8fb6cf8b 8853b008 0000dc46 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
ad320c98 8fb6cceb 8853b008 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
ad320cc4 8fb3e5c0 00000002 82a8d906 8853b008 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
ad320d54 8fb6d032 8853b008 82a8d906 8853b008 dxgkrnl!VidSchiScheduleCommandToRun+0xac
ad320d68 8fba2698 8853b008 00000000 89af5670 dxgkrnl!VidSchiRun_PriorityTable+0xf
ad320d7c 82c1ef7a 8853b008 31882630 00000000 dxgkrnl!VidSchiWorkerThread+0x62
ad320dc0 82a87efe 8fba2636 8853b008 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+5d68
947b9d68 8bff mov edi,edi

SYMBOL_NAME: atikmpag+5d68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3541

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

BUCKET_ID: 0x116_IMAGE_atikmpag.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: 89e5a510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 947b9d68, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+5d68
947b9d68 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:
ad320bc0 8fbb3046 00000116 89e5a510 947b9d68 nt!KeBugCheckEx+0x1e
ad320be4 8fbb3d36 947b9d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
ad320c04 8fb504fd 00000000 00000102 8853b008 dxgkrnl!TdrIsRecoveryRequired+0xa1
ad320c6c 8fb6cf8b 8853b008 0000dc46 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
ad320c98 8fb6cceb 8853b008 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
ad320cc4 8fb3e5c0 00000002 82a8d906 8853b008 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
ad320d54 8fb6d032 8853b008 82a8d906 8853b008 dxgkrnl!VidSchiScheduleCommandToRun+0xac
ad320d68 8fba2698 8853b008 00000000 89af5670 dxgkrnl!VidSchiRun_PriorityTable+0xf
ad320d7c 82c1ef7a 8853b008 31882630 00000000 dxgkrnl!VidSchiWorkerThread+0x62
ad320dc0 82a87efe 8fba2636 8853b008 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+5d68
947b9d68 8bff mov edi,edi

SYMBOL_NAME: atikmpag+5d68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3541

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

BUCKET_ID: 0x116_IMAGE_atikmpag.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: 89e5a510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 947b9d68, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+5d68
947b9d68 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:
ad320bc0 8fbb3046 00000116 89e5a510 947b9d68 nt!KeBugCheckEx+0x1e
ad320be4 8fbb3d36 947b9d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
ad320c04 8fb504fd 00000000 00000102 8853b008 dxgkrnl!TdrIsRecoveryRequired+0xa1
ad320c6c 8fb6cf8b 8853b008 0000dc46 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
ad320c98 8fb6cceb 8853b008 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
ad320cc4 8fb3e5c0 00000002 82a8d906 8853b008 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
ad320d54 8fb6d032 8853b008 82a8d906 8853b008 dxgkrnl!VidSchiScheduleCommandToRun+0xac
ad320d68 8fba2698 8853b008 00000000 89af5670 dxgkrnl!VidSchiRun_PriorityTable+0xf
ad320d7c 82c1ef7a 8853b008 31882630 00000000 dxgkrnl!VidSchiWorkerThread+0x62
ad320dc0 82a87efe 8fba2636 8853b008 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+5d68
947b9d68 8bff mov edi,edi

SYMBOL_NAME: atikmpag+5d68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3541

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

BUCKET_ID: 0x116_IMAGE_atikmpag.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: 89e5a510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 947b9d68, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+5d68
947b9d68 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:
ad320bc0 8fbb3046 00000116 89e5a510 947b9d68 nt!KeBugCheckEx+0x1e
ad320be4 8fbb3d36 947b9d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
ad320c04 8fb504fd 00000000 00000102 8853b008 dxgkrnl!TdrIsRecoveryRequired+0xa1
ad320c6c 8fb6cf8b 8853b008 0000dc46 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
ad320c98 8fb6cceb 8853b008 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
ad320cc4 8fb3e5c0 00000002 82a8d906 8853b008 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
ad320d54 8fb6d032 8853b008 82a8d906 8853b008 dxgkrnl!VidSchiScheduleCommandToRun+0xac
ad320d68 8fba2698 8853b008 00000000 89af5670 dxgkrnl!VidSchiRun_PriorityTable+0xf
ad320d7c 82c1ef7a 8853b008 31882630 00000000 dxgkrnl!VidSchiWorkerThread+0x62
ad320dc0 82a87efe 8fba2636 8853b008 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+5d68
947b9d68 8bff mov edi,edi

SYMBOL_NAME: atikmpag+5d68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3541

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

BUCKET_ID: 0x116_IMAGE_atikmpag.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: 89e5a510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 947b9d68, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+5d68
947b9d68 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:
ad320bc0 8fbb3046 00000116 89e5a510 947b9d68 nt!KeBugCheckEx+0x1e
ad320be4 8fbb3d36 947b9d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
ad320c04 8fb504fd 00000000 00000102 8853b008 dxgkrnl!TdrIsRecoveryRequired+0xa1
ad320c6c 8fb6cf8b 8853b008 0000dc46 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
ad320c98 8fb6cceb 8853b008 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
ad320cc4 8fb3e5c0 00000002 82a8d906 8853b008 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
ad320d54 8fb6d032 8853b008 82a8d906 8853b008 dxgkrnl!VidSchiScheduleCommandToRun+0xac
ad320d68 8fba2698 8853b008 00000000 89af5670 dxgkrnl!VidSchiRun_PriorityTable+0xf
ad320d7c 82c1ef7a 8853b008 31882630 00000000 dxgkrnl!VidSchiWorkerThread+0x62
ad320dc0 82a87efe 8fba2636 8853b008 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+5d68
947b9d68 8bff mov edi,edi

SYMBOL_NAME: atikmpag+5d68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3541

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

BUCKET_ID: 0x116_IMAGE_atikmpag.sys

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

Here's "!analyze -v" stuff:

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

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

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


FAULTING_IP:
atikmpag+5d68
947b9d68 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:


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+5d68
947b9d68 8bff mov edi,edi

SYMBOL_NAME: atikmpag+5d68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3541

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

BUCKET_ID: 0x116_IMAGE_atikmpag.sys

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

Can you possible help me out with this stuff, Scott?


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Wed Jun 08, 2011 7:34 pm 
Offline

Joined: Thu Jan 15, 2009 1:27 pm
Posts: 1105
Location: Stowmarket, Suffolk England
Clue is the display driver, try latest :)


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Wed Jun 08, 2011 8:50 pm 
Offline
Site Admin

Joined: Sun Feb 04, 2007 11:44 am
Posts: 5936
Although I originally recommended using the Debugging Tools for Windows for troubleshooting BSOD errors, I now recommend using BluescreenView instead. Scott.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Wed Jun 08, 2011 9:04 pm 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1001
I have installed BlueScreenView. Check out the stuff below:

Mini060811-01.dmp 6/8/2011 1:08:24 PM 0x00000116 0x89e5a510 0x947b9d68 0x00000000 0x00000002 atikmpag.sys atikmpag.sys+5d68 AMD multi-vendor Miniport Driver AMD driver Advanced Micro Devices, Inc. 8.14.01.6210 32-bit ntkrnlpa.exe+cdb3f dxgkrnl.sys+7c046 dxgkrnl.sys+7cd36 dxgkrnl.sys+194fd C:\Windows\Minidump\Mini060811-01.dmp 2 15 6002 155,208


atikmpag.sys atikmpag.sys+5d68 0x947b4000 0x947f4000 0x00040000 0x4dae3541 4/19/2011 6:22:09 PM AMD driver AMD multi-vendor Miniport Driver 8.14.01.6210 Advanced Micro Devices, Inc. C:\Windows\system32\drivers\atikmpag.sys

dxgkrnl.sys dxgkrnl.sys+7c046 0x8fb37000 0x8fbd7000 0x000a0000 0x4d383dc1 1/20/2011 6:50:57 AM Microsoft® Windows® Operating System DirectX Graphics Kernel 7.0.6002.18107 (vistasp2_gdr_win7ip_dgt(wmbla).090924-1550) Microsoft Corporation C:\Windows\system32\drivers\dxgkrnl.sys

ntkrnlpa.exe ntkrnlpa.exe+2a8d7dc0 0x82a49000 0x82e03000 0x003ba000 0x4cb710d6 10/14/2010 7:16:54 AM Microsoft® Windows® Operating System NT Kernel & System 6.0.6002.18327 (vistasp2_gdr.101014-0432) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe


Basically, I had just installed a certain video card today. I was at least in the process of installing both a driver for it and a Windows Update thing, plus I was in the process of shutting the system down.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Wed Jun 08, 2011 10:00 pm 
Offline
Site Admin

Joined: Sun Feb 04, 2007 11:44 am
Posts: 5936
Here's your homework assignment: Read the article I posted on troubleshooting BSOD errors. Apply what you learn from reading that to analyzing your specific problem here. Then let us know the results of your analysis (what you think is the root cause), and what you end up doing to solve the problem. Thanks, Scott.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Thu Jun 09, 2011 7:06 am 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1001
Believe it or not, I was reading your article on BSOD stuff when my computer crashed again. This time around, the "blue" screen involved funky colors. Problem Reports and Solutions claims it involves a problem with my antivirus software. Below is stuff from BlueScreenView:

Mini060911-01.dmp 6/9/2011 5:48:44 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x0000001c 0x00000002 0x00000000 0x82ac08c1 hal.dll hal.dll+997f Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.0.6002.18005 (lh_sp2rtm.090410-1830) 32-bit ntkrnlpa.exe+4dfd9 ntkrnlpa.exe+7b8c1 ntkrnlpa.exe+7a661 ntkrnlpa.exe+77bab C:\Windows\Minidump\Mini060911-01.dmp 2 15 6002 140,096


fltmgr.sys fltmgr.sys+2490a5bc 0x807a9000 0x807db000 0x00032000 0x49e01907 4/10/2009 9:13:59 PM Microsoft® Windows® Operating System Microsoft Filesystem Filter Manager 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\fltmgr.sys

hal.dll hal.dll+997f 0x82a12000 0x82a45000 0x00033000 0x49e018d9 4/10/2009 9:13:13 PM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\hal.dll
NAVEX15.SYS NAVEX15.SYS+fba546d0 0xa965f000 0xa97d5e80 0x00176e80 0x4dcc44a1 5/12/2011 1:35:45 PM

Ntfs.sys Ntfs.sys+1a4a6588 0x8ac0d000 0x8ad1d000 0x00110000 0x49e0192a 4/10/2009 9:14:34 PM Microsoft® Windows® Operating System NT File System Driver 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\Ntfs.sys


ntkrnlpa.exe ntkrnlpa.exe+7b8c1 0x82a45000 0x82dff000 0x003ba000 0x4cb710d6 10/14/2010 7:16:54 AM Microsoft® Windows® Operating System NT Kernel & System 6.0.6002.18327 (vistasp2_gdr.101014-0432) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe

SRTSP.SYS SRTSP.SYS+fbaab68c 0xa9608000 0xa965f000 0x00057000 0x4b85bc4b 2/24/2010 4:54:51 PM

As far as yesterday's crash is concerned, I believe it has something to do with the driver for my new video card. I will uninstall it or whatever. I will also try to update my antivirus software. I have a weird feeling the video-card driver played a part in this morning's crash, too. The latest crash appears to have something to do with the hardware abstraction layer.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Thu Jun 09, 2011 7:16 am 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1001
Update: I've uninstalled the driver for my new video card. Unfortunately, my antivirus software already has the latest updates. Let's see what happens.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Thu Jun 09, 2011 7:36 am 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1001
Update: Unless I'm mistaken, the ATI Radeon HD 5450 driver has been reinstalled. Again, let's see what happens.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Fri Jun 10, 2011 3:07 pm 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1001
Just now, basically, my HP Pavilion Media Center m8300f PC crashed as I was trying to take it out of "sleep" mode. The "blue" screen had funky colors this time around. Here is some info about the crash from BlueScreenView:

Mini061011-01.dmp 6/10/2011 1:52:49 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x00780089 0x00000002 0x00000000 0x82a874e1 ntkrnlpa.exe ntkrnlpa.exe+4dfd9 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.0.6002.18327 (vistasp2_gdr.101014-0432) 32-bit ntkrnlpa.exe+4dfd9 ntkrnlpa.exe+444e1 ntkrnlpa.exe+86f5d ntkrnlpa.exe+221506 C:\Windows\Minidump\Mini061011-01.dmp 2 15 6002 140,096

ntkrnlpa.exe ntkrnlpa.exe+444e1 0x82a43000 0x82dfd000 0x003ba000 0x4cb710d6 10/14/2010 7:16:54 AM Microsoft® Windows® Operating System NT Kernel & System 6.0.6002.18327 (vistasp2_gdr.101014-0432) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe


It seems to me like the ATI Radeon HD 5450 driver for my new video card is bad. Hopefully, the video card itself is not bad. Should I bother returning a video card all because its driver is bad? Check out the following link:

http://www.amd.com/us/products/desktop/graphics/ati-radeon-hd-5000/hd-5450-overview/pages/hd-5450-overview.aspx


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Fri Jun 10, 2011 3:37 pm 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1001
Update: I've removed the the ATI Radedon HD 5450 driver from the PC in question. A generic driver for the ASUS EAH5450 Series is now being used. Let's see what happens.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Fri Jun 10, 2011 4:55 pm 
Offline
Site Admin

Joined: Sun Feb 04, 2007 11:44 am
Posts: 5936
If you can't use the card with the proper driver, then the OS install, card, or motherboard may be bad. Try temporarily installing a known-good drive with a clean install of Windows and the latest drives. If that works, then the original load was most likely the source of the problem. If not, then that leaves the driver/card and/or motherboard. Let me know what the solution turns out to be. Scott.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Fri Jun 10, 2011 6:19 pm 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1001
Scott, I searched for an update online for the generic ASUS EAH5450 Series driver, and apparently I ended up installed the dreaded ATI Radeon HD 5450 driver. In the process of installation, the PC crashed yet again. Here's info from BlueScreenView:

Mini061011-02.dmp 6/10/2011 2:45:33 PM 0x00000116 0x86901008 0x947c3d68 0x00000000 0x00000002 atikmpag.sys atikmpag.sys+5d68 AMD multi-vendor Miniport Driver AMD driver Advanced Micro Devices, Inc. 8.14.01.6210 32-bit ntkrnlpa.exe+cdb3f dxgkrnl.sys+7c046 dxgkrnl.sys+7cd36 dxgkrnl.sys+194fd C:\Windows\Minidump\Mini061011-02.dmp 2 15 6002 157,952

atikmpag.sys atikmpag.sys+5d68 0x947be000 0x947fe000 0x00040000 0x4dae3541 4/19/2011 6:22:09 PM AMD driver AMD multi-vendor Miniport Driver 8.14.01.6210 Advanced Micro Devices, Inc. C:\Windows\system32\drivers\atikmpag.sys

dxgkrnl.sys dxgkrnl.sys+7c046 0x8fb45000 0x8fbe5000 0x000a0000 0x4d383dc1 1/20/2011 6:50:57 AM Microsoft® Windows® Operating System DirectX Graphics Kernel 7.0.6002.18107 (vistasp2_gdr_win7ip_dgt(wmbla).090924-1550) Microsoft Corporation C:\Windows\system32\drivers\dxgkrnl.sys

ntkrnlpa.exe ntkrnlpa.exe+47e96dc0 0x82a3d000 0x82df7000 0x003ba000 0x4cb710d6 10/14/2010 7:16:54 AM Microsoft® Windows® Operating System NT Kernel & System 6.0.6002.18327 (vistasp2_gdr.101014-0432) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe

It appears to be the same kind of crash that happened when I installed the ATI Radeon HD 5450 driver from an optical disc that came with the card. I went back to using the generic ASUS EAH5450 Series driver. However, that driver also seemed to have problems. When the PC didn't seem to be going into "sleep" mode by itself, I put it in sleep mode manually. When I deliberately brought it out of sleep mode, various glitches (but no BSOD) happened. In frustration, I decided to uninstall the generic driver and physically remove it from the system. I plan to return it to Amazon.com via UPS or whatever. I guess I should just buy a replacement fan for my NVIDIA GeForce 9500 GT card. I don't recall any blue screens being associated with that card.

For the record, I just now put the PC into sleep mode and quickly took it out of it. No BSOD showed up. No real glitches occured. There's currently no video card installed. The PC is relying on onboard video.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Sat Jun 11, 2011 12:39 am 
Offline

Joined: Thu Jan 15, 2009 1:27 pm
Posts: 1105
Location: Stowmarket, Suffolk England
I would reload Windows and install all latest drivers, if card still faulty then RMA, also Onboard GPU drivers might clash with ATI driver, especially if the OEM driver


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Sat Jun 11, 2011 11:08 am 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1001
Sorry, David. The video card is already packed and ready to be mailed back.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Minidump stuff
 Post Posted: Sat Jun 11, 2011 11:25 am 
Offline

Joined: Thu Jan 15, 2009 1:27 pm
Posts: 1105
Location: Stowmarket, Suffolk England
hehe, don't be sorry if it was a bad GPU, then you will hopefully get a good one now :)

If not then follow Scott's advise (Above) :)


Top 
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
 
Post new topic Reply to topic  [ 15 posts ] 

Board index » Upgrading and Repairing Forum » Windows OS


Who is online

Users browsing this forum: No registered users and 1 guest

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron