*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {ffffe0000762b4d0, fffff801fcd7abf8, 0, d}
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+ebf8 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff8020f57a438, 2, 0, fffff801ff559cc0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
This is a little too warm and could be 'part' of the problem.During this test the temperature rose up to 94C so I had to remove the side panel of my case in order to prevent any possible damage, the test kept running at around 86C again under 100% load and 100% fan speed.
Please post any new dump files.I also got one bsod with the same "atikmpag.sys dxgkrnl.sys dxgmms1.sys" when I uninstalled radeon settings and didn't restart yet.
So from what you say above it sounds like you installed your gpu drivers through device manager and then installed the Radeon Software Crimson suite separately?access radeon settings my display would shut down again so I uninstalled it, leaving the drivers only.
So from what you say above it sounds like you installed your gpu drivers through device manager and then installed the Radeon Software Crimson suite separately?
Exactly which is one of the reasons you were asked to run it.I should have at least noticed it while doing a 1 hour stress test with a 100% gpu load,
Why?To be honest, I am more biased towards searching for the problem in memory timings.
What do you normally use to set the RAM speed? As your probably aware when you buy fast RAM you have to set the clocks yourself. Usually the stick will default to something like 1333MHz and you need to use XMP to run the RAM at the correct speed or just can clock it manually.I have just checked my memory clocks through HWInfo and CPU_Z, I don't know why, but they are running at 1066MHz 15-15-15-36.
What do you normally use to set the RAM speed? As your probably aware when you buy fast RAM you have to set the clocks yourself. Usually the stick will default to something like 1333MHz and you need to use XMP to run the RAM at the correct speed or just can clock it manually.
You say yours has dropped to 1066mhz?
Have you tried setting the RAM up to it's proper speed?
Ah ok understood.it appears that cpu_z and other programs show half the speed (double data rate, in my case 2133/2 ~= 1066) and I didn't know that.
So you reduced the clocks and the crashes have stopped.. That's good yes? I've now dealt with a number of users all with the same gpu and the only solution is to under clock the card.I have just reinstalled AMD's drivers, played with clock values and had no crashes. Now I'm completely lost.
Ah ok understood.
So you reduced the clocks and the crashes have stopped.. That's good yes? I've now dealt with a number of users all with the same gpu and the only solution is to under clock the card.
How much did you drop the clocks by, just 50MHz?