I have 8 x BLT4G3D1869DT2TXRG in my Intel Xeon E5-2696 v2 (Ivy Bridge-EP) and 1.3.3 can only see/control 4 of them.

You should also be aware MOD fails to use the Global\Access_SMBUS.HTP.Method lock so running other programs that access the SMBus at the same time as MOD will likely cause issues.

What system are you using and what is the part number of your DIMMs?

If you post the SIV [SPD] + [SMB Bus] panels I may be able to comment further

For you does MOD only see the memory in slots 1,2,5,6 even if you swap the DIMM's
or does it always follow the same 4 DIMM's even if you move to another slot?

I have 3x BL25664TN1608.16FF (1600MHz 8-8-8-24) in an Asus P6T (x58 chipset)
OS is a clean install of Win7

Requested siv reports below

chinny22 wrote on 2025-10-05, 01:41:

For you does MOD only see the memory in slots 1,2,5,6 even if you swap the DIMM's or does it always follow the same 4 DIMM's even if you move to another slot?

The issue with my Intel Xeon E5-2696 v2 (Ivy Bridge-EP) system is that it has 4 x IMC SMBus and MOD only sees the DIMMs on the one @ [ 255 - 15 - 0], see attached.

As I recall at the time I raised the issue with Crucial and they failed to fix it along with failing to start using the Global\Access_SMBUS.HTP.Method lock.

chinny22 wrote on 2025-10-04, 07:29:

However the software does not recognise my memory.

From the MOD screen shot you posted it does, I guess you mean it can't control the LEDs.

I also have an X58 system with Crucial Ballistix Tracer DDR3 RAM and MOD can control the LEDs of all 6 DIMMs, what happens when you select Lights?

My DIMMs also report their temperature and from the [SPD] screen I can see yours don't as MTS is not set, further on [SMB Bus] there is nothing @ [ 0_18 ] to [ 0_1D ].

I just spotted the INUSE Wait 811 of 811 ms, this does not normally happen (it should be 0 of 811 ms) and is almost certainly trigged by MOD failing to correctly process the INUSE Wait hardware semaphore.

Also notice how my part numbers are totally different and end RG or OB, further the XMP voltage is 1.50 rather than 1.65 Volts.

My guess is that any LEDs on your DIMMs can't be controlled by any software, where does it specify they can be?

Your response from Crucial doesn't surprise me if their "fix" for the software vulnerability was simply take down the software and tell everyone to go use something else!

I've since tried the RAM and software in a HP Z230 (C226 chipset) Same thing in MOD . Selecting temperature or lights will give an error about not finding any supported memory.

It's possible these are not controllable, I'm basing my knowledge on 15 year old reviews. But is strange as 1 DIMM is set to a different pattern to the rest and seems like the LEDs at the bottom on all 3 have been turned off where every article I read says they are included. All 3 have identical part numbers but naturally I've no history on the RAM

I'm guessing not much can be done though and we have hit a brick wall?

chinny22 wrote on 2025-10-05, 08:17:

It's possible these are not controllable, I'm basing my knowledge on 15 year old reviews. But is strange as 1 DIMM is set to a different pattern to the rest and seems like the LEDs at the bottom on all 3 have been turned off where every article I read says they are included. All 3 have identical part numbers but naturally I've no history on the RAM

I'm guessing not much can be done though and we have hit a brick wall?

How on earth can you say "I'm basing my knowledge on 15 year old reviews" without including a link to them?

Because I didn't save the links and doubt they are relevant anyway.
I researched the product to the best of my ability, then check availability. No point saving links to reviews that I've extracted the information I think I need from.

I'm not saying they MUST be configurable because the articles are 15 years old. I'm saying the articles will be out of date, so part numbers if any in the article will be incomplete as new modules or kits are released with new part numbers wont be reflected in the article.

As with anything second hand, a little bit of luck is always involved.

Far as I recall, the original Ballistix Tracer DDR3 (red\green activity + blue ground effect LEDs) weren't programmable...that function of the MOD utility only appeared with the later Ballistix Smart Tracer DDR3. Sort of confirmed as there's no mention of it on the spec sheet

I'm still using v1.0.0.2 with my Ballistix Tactical DDR3 (4GB BLT4G3D1869DT1TX0.16FM 1866MHz) and it seems to read all the DIMMs OK

PC Hoarder Patrol wrote on 2025-10-05, 11:53:

I'm still using v1.0.0.2 with my Ballistix Tactical DDR3 (4GB BLT4G3D1869DT1TX0.16FM 1866MHz) and it seems to read all the DIMMs OK

I am trying to understand what all the different types are, do your DIMMs also report their temperature and/or can MOD control the LEDs? Please will you post the SIV [SPD] + [SMB Bus] screen shots.

I have also been looking into why MOD 1.3.3 fails to report all 8 DIMMs on my Intel Xeon E5-2696 v2 (Ivy Bridge-EP) system and found:

Clearly it's only using [ 255 - 15 - 0 ] when it should also be using [ 255 - 29 - 0 ], further it's using the PCIEBAR address to decide which buses to read. This is incorrect and it should be using the internal bus numbers BOX buses. With a single socket it half works and with a quad socket system it's hopeless. I also just spotted for the modelId == 12032u (Haswell-E) there is no default: and I expect there should be.

Next I wondered how MOD would do with other than Crucial DIMMs, it reported their SPD, but not their temperature. I was amused that 2.00 GB ECC DIMMs are reported as 2.25 GB.

I wondered if it would report the temperature for Micron DIMMs, as my HP DL580 Gen8 has 96 x 36JSF2G72PZ-1G9N1 Micron DIMMs I tried to run MOD, it would not even start.

I tried to find a 1.0.0.2 download but failed, please will you post it.