BSOD Kernal_data_inpage_error 0x0000007A

olsendp · 31 Oct 2014

I've tried everything but still am getting the BSOD. UNLESS I swap out the HDD to the original 5400 rpm drive that came with the laptop. These drives are exact clones of each other with regards to software and partition info. I have even tried a different new 7200 rpm drive and still get the BSOD. I'm attaching the mini dump with hopes someone can glean something out of it.

Arc · 31 Oct 2014

The minidump you provided does not match with your thread title, original post and explanations. It points to a totally different issue, display error/failure. (The thread title has parity with the explanations of the original post, they are in the same line).

Update the display driver from Download Drivers

If you get any further BSOD, post it following the Blue Screen of Death (BSOD) Posting Instructions. Otherwise, with partial data you will get a partial help only.
_______________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a17d010, fffff88003aba900, 0, 2}

*** 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+7900 )

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: fffffa800a17d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003aba900, 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+7900
fffff880`03aba900 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`021bd9c8 fffff880`052fe134 : 00000000`00000116 fffffa80`0a17d010 fffff880`03aba900 00000000`00000000 : nt!KeBugCheckEx
fffff880`021bd9d0 fffff880`052fde3e : fffff880`03aba900 fffffa80`0a17d010 fffffa80`08eaac50 fffffa80`0877e410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`021bda10 fffff880`053a5f13 : fffffa80`0a17d010 00000000`00000000 fffffa80`08eaac50 fffffa80`0877e410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`021bda40 fffff880`053cfcf1 : 00000000`ffffffff 00000000`0007b9c3 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`021bdb20 fffff880`053ce437 : 00000000`00000102 00000000`00000000 00000000`0007b9c3 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`021bdb50 fffff880`053a12d2 : ffffffff`ff676980 fffffa80`0877e410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`021bdbf0 fffff880`053cdff6 : 00000000`00000000 fffffa80`08eaac50 00000000`00000080 fffffa80`0877e410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`021bdd00 fffff800`0312a73a : 00000000`fffffc32 fffffa80`087ebb50 fffffa80`06c71890 fffffa80`087ebb50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`021bdd40 fffff800`02e7f8e6 : fffff800`03009e80 fffffa80`087ebb50 fffff800`03017cc0 73345267`32426d6b : nt!PspSystemThreadStartup+0x5a
fffff880`021bdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7900
fffff880`03aba900 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7900

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6a7fc8

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

0: kd> lmvm atikmpag
start             end                 module name
fffff880`03ab3000 fffff880`03b08000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Mar 22 06:56:32 2012 (4F6A7FC8)
    CheckSum:         000591B3
    ImageSize:        00055000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4