BSOD - Visiting websites

Casuaisxtynine said:

Really really random bsod's. help please! :<

This is a repost.. I'm sorry for this but I need help

Hi Casuaisxtynine.

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

I already have uploaded the latest DM log for this.

Here it is.

Asking for the files once again. If you want us to assist you with your issue, we need ALL THE FILES GENERATED BY DM LOG COLLECTOR.

Used the SF tool. Tried using the DM logs and running it as admin to no avail.. It only collects the dmp files...

Is this ok?

So it is a branded desktop.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of your PSU.

Is the computer hot? 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: Speccy - Publish Snapshot of your System Specs .

Uninstall your installed version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• Drivers - Clean Left over Files after Uninstalling

Then install version 13.9 WHQL only.

• Previous AMD Catalyst? Display Drivers

When the driver is applied, stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.
____________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006f89420, fffff88002c3e45c, 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+745c )

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: fffffa8006f89420, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002c3e45c, 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+745c
fffff880`02c3e45c 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.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`03e95718 fffff880`044d2140 : 00000000`00000116 fffffa80`06f89420 fffff880`02c3e45c 00000000`00000000 : nt!KeBugCheckEx
fffff880`03e95720 fffff880`044d1e4a : fffff880`02c3e45c fffffa80`06f89420 fffffa80`041d4950 fffffa80`05677010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03e95760 fffff880`04578f13 : fffffa80`06f89420 00000000`00000000 fffffa80`041d4950 fffffa80`05677010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03e95790 fffff880`045a6ed6 : fffffa80`ffffffff 00000000`000fd035 fffff880`03e958f0 fffffa80`05677010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03e95870 fffff880`045a2a6c : 00000000`00000000 ffffffff`feced300 fffffa80`03b56a30 fffff880`045a3bee : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`03e958b0 fffff880`045a1679 : fffffa80`05677110 00000000`00005fec fffffa80`05677010 fffff880`03e95bc0 : dxgmms1!VidSchiWaitForFence+0xf4
fffff880`03e959a0 fffff880`045a1514 : fffff880`009f2f40 fffff880`045a0f3c fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0xe1
fffff880`03e95b90 fffff880`045a1012 : 00000000`00000000 fffffa80`05739170 00000000`00000080 fffffa80`05677010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03e95bc0 fffff800`02f1473a : 00000000`fffffc32 fffffa80`05493a00 fffffa80`0396eb30 fffffa80`05493a00 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03e95c00 fffff800`02c698e6 : fffff880`009ee180 fffffa80`05493a00 fffff880`009f8fc0 ffffffff`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`03e95c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+745c
fffff880`02c3e45c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+745c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dae3558

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`02c37000 fffff880`02c87000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Apr 20 06:52:32 2011 (4DAE3558)
    CheckSum:         00050398
    ImageSize:        00050000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Speccy: http://speccy.piriform.com/results/6...3ixVkvvsfeQUXF

Also ran Stress test, it leveled out on 87 Degrees Celsius so I stopped it.

*Edit: I installed 13.9 WHQL just as you said. :)

Good. :)

Let us know for any further BSOD.

Okay. :) Quick question, Are you considering this as a hardware issue?

Not at this stage. If the computer runs fine with 13.9 whql installed, there is no need to blame the hardware.

But otherwise, the question will definitely arise.