Solved Multiple BSODS 0x00000116 and 0x00000124 errors

[Ruga]

Hi to everyone.

Recently I've been experiencing some really annoying BSODS.

Here's my minidump.

View attachment 66883

Here's also a screenshot from Bluescreenview just in case

I think they might be related to the graphics card drivers, since they started happening after I installed the new Crimson drivers for my R9 270, but I can't really be sure since I'm no expert on the topic. It could also be my overclocked CPU but I never had problems with it before these BSOD , so I'm not sure, I'll try to keep it off for the time being.

Any help would be greatly appreciated!

 

[lifetec]

The dumpfiles are (possible) related to your AMD GPU.
2 of the dumpfile are:

  [BugCheck 116, {ffffe00071c4d010, fffff80046051e98, 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+ce98 )

The atikmpag.sys is the driver for your AMD GPU. As you already installed the latest Crimson Driver. I suspect there are other reasons for the BSOD on your system.
But it could be that the driver is corrupt and a clean reinstall of the driver is necessary.

The other dumpfile has

  WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00185617038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Analysing the M.C.E. it gives a Bus Error, this could point to the PCIe bus of your Graphic Card.
System bus errors: (error communicating between the processor and the motherboard).

Normal causes for MCE errors include overheating and/or incorrect hardware installation. Specific manually-induced causes include:

• overclocking (which normally increases heat-output)
• poorly-fitted heatsink/computer fans (the same problem can happen with excessive dust in the CPU fan)
• an overloaded internal or external power-supply (fixable by upgrading)

Did you also update the AMD chipset driver Crimson Edition 15.12 to be found under Optional Downloads. see here Desktop

Maybe this improves the communication/stability of your motherboard.
Also because there are no BIOS updates for your motherboard GA-78LMT-USB3 rev. 5.0, only FA first release.
And there are almost no windows 8.1 drivers avaliable for your motherboard.

If this does not help/stopping the BSOD, rollback to the the latest previous good working driver to keep your system stable.

 

[axe0]

Remove any OC on your system, OC'ing often is the root cause of a 0x124.

 

[Ruga]

Thanks for the answers! I removed the OC and for now I didn't get any BSOD, will report back if I get one.

As for the AMD Chipset drivers, I downloaded them but I get this from Windows:

If I try to run it as admin I get this instead:

For the crimson drivers, I already tried using Display Driver Uninstaller twice and re-installing them again after the first BSOD, but that didn't seem to solve anything. If I run into a BSOD again I'll try to rollback the drivers to previous version, since that one didn't give me any trouble.

With overclock I was reaching temperatures of 60C max while playing games with my GPU, I'll try to clean the CPU fan as soon as I can, maybe there could be some dust in there.

Thanks again for the quick replies!

 

[Ruga]

Got another BSOD today while I was playing.

View attachment 66952

I already rolled back to the previous AMD drivers since the newer ones were giving me problems, I'm on 15.11.1, the ones before crimson update if I remember correctly.

The error is again 0x124 so maybe it's overclock related, tho I did take off my OC... so I don't know what it could be this time.

 

[axe0]

Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to ONLY install the display drivers using custom/advanced options.
View attachment 66953

 

[lifetec]

Did you already take out your GPU and reseated it and look for dirt or dust etc. in the PCIe socket and inside your GPUcard.

 

[Ruga]

Ok cleaned all drivers and amd stuff with DDU and reinstalled latest graphics drivers together with the chipset drivers, also cleaned off all dust from PC and reseated GPU, hopefully now everything works.

During drivers installation this popped up

can this be related to the problems? The installation carried on till the end and finished even if that came up.

Is it also normal that my FX-6300 runs at 3.8Ghz after I resetted it to stock speed? Is this related to the turbo feature?

 

[lifetec]

Yes, that is related to the Turbo core feature. In short if one or more cores are idle, the active core of the processor increases the core speed.
See this article AMD

The cncmd.exe is Catalyst Control Center.exe of the former AMD Driver Package.
What driver version have you now installed, the new Radeon Package.
Maybe it is just a notice.

 

[Ruga]

Yes, that is related to the Turbo core feature. In short if one or more cores are idle, the active core of the processor increases the core speed.
See this article AMD

The cncmd.exe is Catalyst Control Center.exe of the former AMD Driver Package.
What driver version have you now installed, the new Radeon Package.
Maybe it is just a notice.

I have installed the 15.12 Crimson drivers for Windows 8.1 x64 and the chipset package aswell. So Catalyst isn't there anymore since it got replaced by Crimson...?

UPDATE: Got another crash and it's like the first crashes I had

It's like the video card keeps trying to reboot and then it results in BSOD, because the screen just goes black and it says no signal and then I get the usual BSOD screen saying it's caused by atikmpag.sys. This kind of BSOD happened only with the new drivers so it might be a corrupted installation? I already tried to uninstall them with DDU and re-install them like 5 times... Also this happened while just watching a youtube video with my GPU being at like 28C so not really overheating or anything.

Here's the new dump file:

View attachment 66960

 

[axe0]

Please test your system without GPU.

Do you have another (compatible) GPU to test?

 

[Ruga]

Please test your system without GPU.

Do you have another (compatible) GPU to test?

Nope, I don't have any other GPU I could use, only this one since this desktop is still "relatively" new (I bought it on November 2014)

Update: So I noticed AMD released 16.1 hotfix for crimson, gonna give that a try to see if it works.

After uninstalling the old drivers with DDU and rebooting PC I got a SYSTEM_SERVICE_EXCEPTION BSOD almost immediately (this happened prior to installing 16.1, basically when I just uninstalled all AMD related drivers). Kinda weird.

Here's the dump:

View attachment 66966

Will test if I have any more BSODs with the new drivers and report back, hopefully doesn't happen again.

• [83484] "Cannot find cncmd.exe" error message may appear during installation

This was also in the release notes so I guess it was just a bug.

 

[axe0]

The 0x3B is caused by a Razer driver
Driver Reference Table - rzendpt.sys
Do you have Razer devices?

ffffd000`712f77a8  fffff800`eec50001Unable to load image \SystemRoot\System32\drivers\rzendpt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rzendpt.sys
*** ERROR: Module load completed but symbols could not be loaded for rzendpt.sys
 rzendpt+0x9001
1: kd> lmvm rzendptstart             end                 module name
fffff800`eec47000 fffff800`eec56000   rzendpt  T (no symbols)           
    Loaded symbol image file: rzendpt.sys
    Image path: \SystemRoot\System32\drivers\rzendpt.sys
    Image name: rzendpt.sys
    Timestamp:        [COLOR=#ff0000]Fri Jul 10 10:32:47 2015[/COLOR] (559F832F)
    CheckSum:         0000DA85
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Ruga]

The 0x3B is caused by a Razer driver
Driver Reference Table - rzendpt.sys
Do you have Razer devices?

ffffd000`712f77a8  fffff800`eec50001Unable to load image \SystemRoot\System32\drivers\rzendpt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rzendpt.sys
*** ERROR: Module load completed but symbols could not be loaded for rzendpt.sys
 rzendpt+0x9001
1: kd> lmvm rzendptstart             end                 module name
fffff800`eec47000 fffff800`eec56000   rzendpt  T (no symbols)           
    Loaded symbol image file: rzendpt.sys
    Image path: \SystemRoot\System32\drivers\rzendpt.sys
    Image name: rzendpt.sys
    Timestamp:        [COLOR=#ff0000]Fri Jul 10 10:32:47 2015[/COLOR] (559F832F)
    CheckSum:         0000DA85
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Yes I have a Razer DeathAdder mouse, how can I solve that?

 

[axe0]

I would suggest to reinstall the software and drivers.
In case the software and drivers are already updated, corruption will be removed, in the other case the software and drivers will be updated

 

[Ruga]

I would suggest to reinstall the software and drivers.
In case the software and drivers are already updated, corruption will be removed, in the other case the software and drivers will be updated

Ok thanks!

Updated the mouse since there was an update, should be fixed now!

If any other BSOD comes up related to GPU I will bump this thread

Hopefully the new drivers fixed that

 

[Ruga]

Just got another crash sadly

Error 0x124, wasn't doing anything in particular, just browsing some forums and bam, PC reboots, no blue screen or anything, just hangs and reboots.

Here's the dump:

View attachment 66994

It's weird because I didn't really have 0x124 errors before, only the 0x116 ones, and the 0x124 ones started on the 3rd of January after I uninstalled some programs (can't really recall what atm, I think AVG was one of them). Maybe this can be related but I have no way to exactly pinpoint what's causing it...

 

[axe0]

Please test your system without GPU.

Already tried above?

 

[Ruga]

Please test your system without GPU.

Already tried above?

Tried this before going to sleep, (so 8-9 hours while I was sleeping pc was on without GPU), no BSOD for now.

Might I ask if the dumps point to anything specifically? Is it always the GPU?

 

[axe0]

The 0x116 is GPU related and the 0x124 is hardware related.
This is combining the 0x116 with 0x124 together, making the graphics card suspect (or the slot).