BSOD – several times a day

[Rod101]

BSOD – several times a day

Please Help: Keep getting – BSOD – several times a day

I hope the following information helps.


Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033



Additional information about the problem:

BCCode: 116

BCP1: FFFFFA80118A34E0

BCP2: FFFFF88004E48738

BCP3: 0000000000000000

BCP4: 0000000000000002

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1





OS Name MicrosoftWindows 7 Home Premium

Version 6.1.7601Service Pack 1 Build 7601

Other OS Description NotAvailable

OS Manufacturer MicrosoftCorporation

System Manufacturer Hewlett-Packard

System Model h8-1050

System Type x64-based PC

Processor Intel(R)Core(TM) i7-2600 CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 8 Logical Processor(s)

BIOS Version/Date AMI7.05, 5/18/2011

SMBIOS Version 2.6

Windows Directory C:\Windows

System Directory C:\Windows\system32

Boot Device \Device\HarddiskVolume1

Installed Physical Memory (RAM) 8.00GB

Total Physical Memory 7.98 GB

Available Physical Memory 5.91GB

Total Virtual Memory 16.0 GB

Available Virtual Memory 13.9GB

Page File Space 7.98 GB


Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
PEGATRON CORPORATION 2AB5
Ver: CHG_7 5.bin vCHG7.05
(1) WDC WD15EARS-60MVWB0 (2) Generic- Compact Flash USB Device (3) Generic- MS/MS-Pro USB Device (4) Generic- SD/MMC USB Device (5) Generic- SM/xD-Picture USB Device (6) WD Elements 1042 USB Device (7) WD Elements 1042 USB Device (8) WD Elements 10A8 USB Device

(1) IDT High Definition Audio CODEC (2) Hauppauge WinTV 723x (ATSC/NTSC) (3) AMD High Definition Audio Device
AMD Radeon HD 6850
Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1

 

[Arc]

Hi Rod101.

Install the display driver 14.9 WHQL (the first one) from here: Desktop

What is the wattage of the PSU of the computer? Let us know.

Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Let us know the results.
_____________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80118a34e0, fffff88004e48738, 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+8738 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80118a34e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004e48738, 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+8738
fffff880`04e48738 4055            push    rbp

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`079e0888 fffff880`04ef5134 : 00000000`00000116 fffffa80`118a34e0 fffff880`04e48738 00000000`00000000 : nt!KeBugCheckEx
fffff880`079e0890 fffff880`04ef4e3e : fffff880`04e48738 fffffa80`118a34e0 fffffa80`0a547940 fffffa80`0bef9410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`079e08d0 fffff880`06380f13 : fffffa80`118a34e0 00000000`00000000 fffffa80`0a547940 fffffa80`0bef9410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`079e0900 fffff880`063aacf1 : 00000000`ffffffff 00000000`00047deb 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`079e09e0 fffff880`063a9437 : 00000000`00000102 00000000`00000002 00000000`00047deb 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`079e0a10 fffff880`0637c2d2 : ffffffff`ff676980 fffffa80`0bef9410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`079e0ab0 fffff880`063a8ff6 : 00000000`00000000 fffffa80`0c18e680 00000000`00000080 fffffa80`0bef9410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`079e0bc0 fffff800`0311173a : 00000000`fffffc32 fffffa80`0bc6ab50 fffffa80`06d0a040 fffffa80`0bc6ab50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`079e0c00 fffff800`02e668e6 : fffff880`009eb180 fffffa80`0bc6ab50 fffff880`009f60c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`079e0c40 00000000`00000000 : fffff880`079e1000 fffff880`079db000 fffff880`0c284d40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+8738
fffff880`04e48738 4055            push    rbp

SYMBOL_NAME:  atikmpag+8738

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f98c1dd

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
---------

2: kd> lmvm atikmpag
start             end                 module name
fffff880`04e40000 fffff880`04e98000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Apr 26 09:02:45 2012 (4F98C1DD)
    CheckSum:         000546EA
    ImageSize:        00058000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4