2 Replies Latest reply on Feb 13, 2016 1:25 AM by seraphyx

    Win 7 x64 | BSOD Crimson 15.12 and 16.1 - REFERENCE_BY_POINTER Error


      Hello, been having this BSOD issue for a few weeks. Sometimes it happens once or twice a week, sometimes it can happen twice or three times a day. Seems to be random, it has happened twice when I was just starting up a game (nothing crazy, binding of isaac while viewing videos online. doubt it's BoI related, it has happened with other games too).


      At first I thought it might either be my memory or maybe even HDD. Ran memtest and everything passed, ran disk check with multiple programs and all passed with no errors.


      The error was reference_by_pointer. I couldn't view the crash logs because it said something about the version being outdated, not sure what it was talking about but there was too much gibberish when opening it with notepad. I finally found a program called WhoCrashed and it's amazing, not sure how accurate but it's better than the bsod error messages at least. It pointed to a file called atikmdag.sys being out of date or a probable cause for the issues. Here's the full message:


      crash dump file: C:\Windows\Minidump\011916-56659-01.dmp

      uptime: 04:37:43

      This was probably caused by the following module: atikmdag.sys (atikmdag+0x2A2E4)

      Bugcheck code: 0x18 (0xFFFFFA8006E09A40, 0xFFFFFA800CF18720, 0x1, 0x1)


      file path: C:\Windows\system32\drivers\atikmdag.sys

      product: ATI Radeon Family

      company: Advanced Micro Devices, Inc.

      description: ATI Radeon Kernel Mode Driver

      Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.

      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

      A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).

      Google query: Advanced Micro Devices, Inc. REFERENCE_BY_POINTER


      I read on another forum somewhere to try and ONLY install the display driver rather than the entire suite. So far I haven't had a bsod (been about 2 days, but I would be able to go a week sometimes without a bsod). I do like the Crimson software, is there any possible solution or other testing I can run to see exactly what the issue is if it's not that file?


      Running Win 7 x64, R9 380, FX 8320 cpu, Asus m5a97 le r2.0 mobo,


      Any help would be appreciated, thanks!

        • Re: Win 7 x64 | BSOD Crimson 15.12 and 16.1 - REFERENCE_BY_POINTER Error

          I have the same problem, it has also been with these two versions , 15.12 and 16.1, even with the latest version, the error jumping me three times a day. do you finally did it solve ? The only difference is I run with this:



          Intel (R ) Core ( TM ) i5-2320 CPU @ 3.00GHz ,
          System Memory 12 GB ,
          Graphics Chipset AMD Radeon HD 6670 ,
          Asus P8H61 -M LE .

            • Re: Win 7 x64 | BSOD Crimson 15.12 and 16.1 - REFERENCE_BY_POINTER Error

              I believe the solution to stop this from happening is just installing the "minimal" version which is ONLY the display driver and not the rest of the software. I ran with that for about a week and had no crashes.


              Get the program Display Driver Uninstaller to completely remove your current display driver and install the minimal version instead. I have no solution for stopping the bluescreens with the full software versions 15.1 and 16.1


              Something in the full version must be causing the crash. I don't have the desire to install and uninstall the full version several times to test out which thing specifically is causing the crash for me. Until this is fixed I'm just going to stick with the display driver only, don't have much of a choice.


              I've wiped my hdd and reinstalled OS on an ssd so I don't have any previous crash logs apart from the one I provided above. Since I'm going with the display driver rather than the full software this thread is probably going to remain unresolved because I don't plan to reinstall the full software to troubleshoot. It has caused too much annoyance. I will wait for another major release and then perhaps give it another shot.