I Need HELP this is inportan!!! Really inportan!!

#1
Problemsignatur:
Navn på problemhendelse: BlueScreen
OS-versjon: 6.1.7600.2.0.0.256.1
ID for nasjonal innstilling: 1044

Tilleggsinformasjon om problemet:
BCCode: 116
BCP1: FFFFFA8004938010
BCP2: FFFFF88003C42024
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Filer som bidrar til å beskrive problemet:
C:\Windows\Minidump\071410-34710-01.dmp
C:\Users\Ole\AppData\Local\Temp\WER-91572-0.sysdata.xml

071410-34710-01.dmp and
WER-91572-0.sysdata.xml Downlode link :
MEGAUPLOAD - The leading online storage and file delivery service

I need your help!! :(
 


#2
This is a 0x116 VIDEO_TDR_FAILURE (116), Attempt to reset the display driver and recover from timeout failed.


BugCheck 116, {fffffa8004938010, fffff88003c42024, 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+6024 )

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

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

BUGCHECK_STR: 0x116

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`05dd42e8 fffff880`03f22ef8 : 00000000`00000116 fffffa80`04938010 fffff880`03c42024 00000000`00000000 : nt!KeBugCheckEx
fffff880`05dd42f0 fffff880`03f22c02 : fffff880`03c42024 fffffa80`04938010 fffffa80`04038d50 fffffa80`0399a310 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05dd4330 fffff880`03fc9f07 : fffffa80`04938010 00000000`00000000 fffffa80`04038d50 fffffa80`0399a310 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05dd4360 fffff880`03ff7d7e : fffffa80`ffffffff 00000000`000006bf fffff880`05dd44b0 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05dd4440 fffff880`03fddbb1 : fffffa80`04469000 ffffffff`feced300 00000000`00000000 fffff880`05dd45f0 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`05dd4480 fffff880`03fe0aaf : 00000000`00000001 00000000`00000000 fffff880`05dd45f0 fffff8a0`018f33c0 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`05dd4580 fffff880`03fdcc28 : fffff8a0`018f33c0 00000000`00000001 fffffa80`04469000 fffff880`05dd45f0 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`05dd45c0 fffff880`03fdcbc3 : fffff8a0`018f33c0 fffff8a0`018f3478 00000000`00000001 fffff8a0`018f33c0 : dxgmms1!VIDMM_GLOBAL::FillAllocationInternal+0x34
fffff880`05dd4750 fffff880`03fe9029 : 00000000`00000000 fffff8a0`018f33c0 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::FillAllocation+0x15f
fffff880`05dd47c0 fffff880`03fde26b : fffffa80`0404d830 fffff8a0`018f33c0 00000000`00000000 00000002`00000000 : dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0xb5
fffff880`05dd48a0 fffff880`03fd9a8f : fffff8a0`018f33c0 fffff8a0`018f33c0 fffffa80`04469000 fffffa80`0409f900 : dxgmms1!VIDMM_GLOBAL::AllocateResourceForPinnedAllocation+0x21b
fffff880`05dd4920 fffff880`03fd938f : fffff880`05dd4c78 00000000`00000000 fffff880`05dd4bf0 fffff880`05dd4c88 : dxgmms1!VIDMM_GLOBAL::processDeferredCommand+0x19f
fffff880`05dd4a40 fffff880`03ff3231 : 00000000`0040003e fffff8a0`018f25d0 fffffa80`043d1bc0 fffffa80`0404a8c8 : dxgmms1!VidMmiProcessSystemCommand+0x23
fffff880`05dd4a70 fffff880`03ff23bc : fffff880`05dd4bd0 00000000`00000000 fffffa80`0404a8c0 00000000`00000001 : dxgmms1!VidSchiSubmitSystemCommand+0x39
fffff880`05dd4aa0 fffff880`03fc477a : 00000000`00000000 fffffa80`043d1bc0 fffffa80`0404a8c0 fffffa80`0404a8c0 : dxgmms1!VidSchiSubmitQueueCommand+0x74
fffff880`05dd4ad0 fffff880`03ff4927 : fffffa80`04354af0 fffffa80`043e2000 fffffa80`0404a8c0 fffff800`6d4d6956 : dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6
fffff880`05dd4b60 fffff880`03fd94b9 : fffffa80`00000001 fffffa80`0399a310 fffffa80`04469000 fffff880`05dd4c78 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f
fffff880`05dd4bd0 fffff880`03fd98dc : fffff880`05dd4d30 fffff8a0`018f33c0 fffff880`05dd4d30 fffff8a0`018f33c0 : dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0xf9
fffff880`05dd4c40 fffff880`03fd4faa : 00000000`00000000 00000000`00000000 fffffa80`04469000 fffff8a0`018f0260 : dxgmms1!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x4c
fffff880`05dd4cb0 fffff880`03fbbaa7 : fffff8a0`018f2e50 fffff8a0`018f3e00 fffff880`05dd4e20 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x2da
fffff880`05dd4d90 fffff880`03f073a1 : fffff8a0`0190f6a0 fffff880`05dd5260 00000000`00000000 00000000`00000000 : dxgmms1!VidMmOpenAllocation+0xeb
fffff880`05dd4de0 fffff880`03f00554 : fffff880`05dd5048 fffff8a0`0576e640 fffff880`05dd5220 fffff880`05dd5220 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x28d
fffff880`05dd4e70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateAllocation+0xca8


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+6024
fffff880`03c42024 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+6024

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b68ec4f

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------
As you can see the .dmp file points directly at this being a gfx driver error and your version is
atikmpag.sys atikmpag.sys+6024 fffff880`03c3c000 fffff880`03c70000 0x00034000 0x4b68ec4f 03/02/2010 04:23:59
you need to get the latest driver version for your graphics card ?

----------------------------------------

Also unless you really need them you would be better off unninstalling* the asus motherboard utilities ?

named in the crash this driver needs updating or removing (see above)*
AsIO.sys fffff880`03dd9000 fffff880`03de0000 0x00007000 0x47663d55 17/12/2007 10:11:49
AsIO.sys is ASUS Probe V and older versions are known to cause bluescreen crashes ?

Let us know how it goes, and don't panic a BSOD is windows way of protecting your system ;)
 


Last edited:
#3
lol..at first i cant even see the bios....:confused:
now i changed the HDD and did try 4 or 5 times and now the pc works...
i will reinstall my gfx driver...
(I hope you understand me, my english is not really good..)
i had some really inportan files on the pc ..
well thx 4 your fast answer.
 


#4
lol..at first i cant even see the bios....:confused:
now i changed the HDD and did try 4 or 5 times and now the pc works...
i will reinstall my gfx driver...
(I hope you understand me, my english is not really good..)
i had some really inportan files on the pc ..
well thx 4 your fast answer.
I didnt refer to your BIOS ?
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.