Did you also clean the GPU heatsink and fan? If so try furmark again making sure you monitor temps (oh and if you send another HWiNFO64 result please keep it in the original format)Should I just go ahead with the Furmark test, with the new PSU?
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EA, {ffffaf01fd58f800, 0, 0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f )
Followup: MachineOwner
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EA, {ffffc200219c1080, 0, 0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f )
Followup: MachineOwner
I also gamed a bit the last couple days, and monitoring the temps on my second monitor, they never even reached 80C. :/
This actually relates more to the driver than the CCC and the type of crash your getting. This is called a TDR and can be caused by many different things. Basically the system detects an issue with the card and tries to reset the driver. If this doesn't happen within 2 seconds then a bsod ensues.atikmdag.sys
Try using all DVI if you can.Would it be worth it to swap out the DVI and/or Display port cables for HDMI/another DVI/etc?
Very possible actually and I'd disable it asap...is it possible hardware acceleration is causing it, just from using web browsers? Or is it probably something deeper, that hardware acceleration is just triggering, or is it not related to hardware acceleration at all and it's just purely coincidence since I enabled it? lol
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EA, {ffffb80b6d08a800, 0, 0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EA, {ffffd507b9966080, 0, 0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f )
Followup: MachineOwner
Ok thank you, I think Chrome crashing was more of a red herring than anything else and the true issue lay's else where.I don't know if this means anything, but hardware acceleration was never on in Chrome, apparently.
Yup it could be down to a number of things which is why we test in a methodical manner. Let's first try and determine if it's the card or software.This might just be my mind rambling, but could there be a conflict with the DisplayPort cable, the new 144hz monitor, or the fact that it's my second monitor and I'm using an extended windows display setting? Should I be testing everything with my previous second monitor? with DVI, HDMI, or Display Port connectors?