Hi all,
I'm the owner of a HP Envy 15-1060ea. It comes with a Windows 7 Home Premium license.
I've formatted it and installed the operating system from scratch. I downloaded all the HP drivers that were available on the HP website. Everything worked well except for the video drivers. As soon as I install them and restart the system, it crashes at Windows startup. I thought the HP drivers were bugged, So I downloaded latest ATI catalyst drivers from AMD website, but my PC keep crashing.
I don't know what else should I try. Any hint? It looks like a problem related to ATI drivers (atikmpag.sys).
This is the minidump log:
Could you help me? Any help will be really appreciated.
Regards
I'm the owner of a HP Envy 15-1060ea. It comes with a Windows 7 Home Premium license.
I've formatted it and installed the operating system from scratch. I downloaded all the HP drivers that were available on the HP website. Everything worked well except for the video drivers. As soon as I install them and restart the system, it crashes at Windows startup. I thought the HP drivers were bugged, So I downloaded latest ATI catalyst drivers from AMD website, but my PC keep crashing.
I don't know what else should I try. Any hint? It looks like a problem related to ATI drivers (atikmpag.sys).
This is the minidump log:
Code:
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 88fe3510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8f9a5c7a, 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.
FAULTING_IP:
atikmpag+5c7a
8f9a5c7a 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:
8f279b74 95ac0adb 00000116 88fe3510 8f9a5c7a nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8f279b98 95ac18fa 8f9a5c7a 00000000 00000002 dxgkrnl+0x8cadb
8f279bbc 95af192c 00000000 00000102 8894a788 dxgkrnl+0x8d8fa
8f279c34 95b1ba32 fffffcfb 000005c1 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8f279c5c 95b1c153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8f279c98 95af88f0 8f279c90 82a443f1 8894a788 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8f279d28 95b1d4b7 8894a788 82a443f1 8894a788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8f279d3c 95b1d573 8894a788 00000000 88a95538 dxgmms1!VidSchiRun_PriorityTable+0xf
8f279d50 82c166d3 8894a788 94a74fac 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8f279d90 82ac80f9 95b1d4f4 8894a788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
FOLLOWUP_IP:
atikmpag+5c7a
8f9a5c7a 8bff mov edi,edi
SYMBOL_NAME: atikmpag+5c7a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d409c77
FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
BUCKET_ID: 0x116_IMAGE_atikmpag.sys
Regards