I believe it should say in CPUz, but your Mobo manual should tell you which one it has. I'm not sure about this, but I believe that because it is using the 1.3 means your ram has a 1.3 profile and so does your Mobo. Otherwise it wouldn't/couldn't use that version. But, don't hold me to that.
So it looks like I only have one profile which I am guessing is ok since it is 1.3??
Correct :)
I'll go through the thread later today to see if anything has been missed for a next step.
Should I move this to the "Gaming" section?
I don't know. Once in a blue moon I will still bet PFN List corrupt BSOD's like just now.
Here you go Axe0
MEMORY3.DMP - Google Drive
Please follow this post again and install a few different drivers, if there is no stability improvement we'll be looking for memory hardware problems.
As I explained in this post many memory hardware variants show signs which I have not seen back in the dumps except for the display drivers, this may mean that the RAM is causing the crashes even though MemTest86+ did not find errors (tests are not 100% as @Arc mentioned in this post). However that the RAM may cause the crashes is not being said with 100% certainty, it needs to be tested by replacement.
Code:ffffd000`23e50318 fffff800`36e5fce0Page 101619 not present in the dump file. Type ".hh dbgerr004" for details Page 101619 not present in the dump file. Type ".hh dbgerr004" for details *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x1dfce0 3: kd> lmvm nvlddmkm Browse full module list start end module name fffff800`36c80000 fffff800`379b5000 nvlddmkm (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Browse all global symbols functions data Timestamp: Fri Jun 03 05:11:28 2016 (5750F560) CheckSum: 00CEE995 ImageSize: 00D35000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Quote