Punctual and constant Bsod 0x124 using software Fusion

papapalo · 08 Feb 2016

Hi all,

I ask help about a mysterious (for me!) BSOD I have in my pc.

0x124 BSOD appears ALWAYS and ONLY when I use the software Fusion of Blackmagicdesign, a (great) program about visual effects, rendering 3D and more.

Pc crashes always when I try to render a video, also with minimal effects (in which the components are not stressed). I updated the bios, the CPU is not overclocked, and the temperature of CPU and GPU are ok.
Again, I had this problem with the previous version of Fusion (now I use the last free version) and with Windows 8.1, and I rendered video and compositions (similar or more intensive) with other similar software like After Effects, Blender 3D, Sony Vegas, and I had no problems....sometimes it wasn't fast, but it always arrived at the end of process.

Looking at the logs I suppose that there some conflict with CPU....but my knowledge ends here

So I ask help, and I thank you in advance for the support

Paolo

axe0 · 10 Feb 2016

Hi papapalo,

Welcome to the 10forums :)

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:

Please uninstall Daemon Tools, it is a known BSOD cause since Windows 7.

Code:

dtsoftbus01	DAEMON Tools Virtual Bus Driver	c:\windows\system32\drivers\dtsoftbus01.sys

Please uninstall ASUS software while troubleshooting, software from the motherboard or manufacturer usually isn't proper created and thus may cause instability.

If after removing ASUS and Daemon tools you still get crashes, please try following below to find any other violating drivers

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

This is an instruction error on the cache of the CPU, unfortunately with 1 dump there is no way to tell if this is consistent. If a crash is consistent it might give a better indication of what is wrong.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffe00158346028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000100153, Low order 32-bits of the MCi_STATUS value.

4: kd> !errrec ffffe00158346028
===============================================================================
Common Platform Error Record @ ffffe00158346028
-------------------------------------------------------------------------------
Record Id     : 01d162de54e1a29a
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/9/2016 2:40:26 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe001583460a8
Section       @ ffffe00158346180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Instruction Execute
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000004

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe001583460f0
Section       @ ffffe00158346240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000004
CPU Id        : 20 0f 60 00 00 08 08 04 - 0b 32 98 3e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffe00158346240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe00158346138
Section       @ ffffe001583462c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : ICACHELG_IRD_ERR (Proc 4 Bank 1)
  Status      : 0xb600000000100153
  Address     : 0x0000000000000007
  Misc.       : 0x0000000000000000