Sorry, I posted that comment before you edited in the link, then I removed it. Yes, the photos were way too huge, so I could clearly see plenty.
This is how you send someone BIOS images to look at all you sent under 500KB total - http://s000.tinyupload.com/index.php?fil...614197340958961

Sounds like a funky caddy, if it works sometimes, but not always. Does it act that way on other devices, and have you tested it on others long around to confirm it's only an issue on this system?

RST v13 was already in there, so I doubt RST 13.xx is going to make much difference, but I guess you never know. That really only matters in RAID mode anyway, your caddy is connecting via USB anyhow correct?

I tested with other laptops and it works.Also i bought 3 of them from different manufactures and still the same...I suspect there is not enough power from the sata plug but first i want to try this last thing before giving up.

Maybe going to older would be better, like V10-V12?

i cant say for sure.... and trying a lot of different versions is a lot of work.. i will try latest v13.5(its a little newer than the one it has inside and then i will leave it at that).

I'd at least give a V10 and V12 a shot, in case it's some bug of 13 series, or some incompatible with the controller in the caddy and V13.
It only takes a second to switch rom versions. Once I get that final module sorted, I'll make you BIOS set w 10-13.x

If its not too much work for you i will try. Thanks

@ektorasdj - Please show me expanded image of >> "Device Manager" - "Network"

And no, it's simple to switch out RAID roms

Here is the screenshot:

@ektorasdj - Thanks for the image, all sorted on that now! Almost done, well done, but redoing some copies now with other RAID for your testing. What is the actual chipset in this system?

I am not really sure since i cant find any information on hwinfo but i think its a 8 or 9 series chipset. Boat are compatible with v12 v13.5

I already have V12 and V13.1/13.2 selected as additional builds, was checking to see if V11 was a possibility or not.
HWINFO64 shows chipset at the large window, select motherboard, then in the right side you'll see chipset line - CPU-z also shows at motherboard tab, shoot me an image of both of those apps at these locations

Here are the photos(sorry for not being screenshots , i was not the one who took them):


Personally i still cant make out if its an 8 or 9 series system.

@ektorasdj - Thanks, I think none of what we've been trying to consider in regards to generation apply to this type of PCH (it's "5th" Generation), there is no 8-9-10 etc series chipset used here.
https://www.intel.com/content/www/us/en/...u/overview.html
http://www.cpu-world.com/news_2013/20131...p_features.html
https://en.wikipedia.org/wiki/Broadwell_(microarchitecture)

We'll just have to try and see, when it (some version) fails you just wont be able to initialize disks on the controller, so then you'll know that one is not compatible
Here is package with the following changes, if none of these help with the caddy and you want to try more later, we can try RST 11 and see if that matters or works

RAID oRom & EFI RST 13.5.0.2188 >> 13.5.0.2164
CPUID uCode 306D4 >> to latest Rev 2D (3/7/2019)
Realtek EFI UNDI 2.027 >> 2.048
GOP 5.5.1032 >> 5.5.1034
vBIOS oRom 1032 >> 1044
Intel Boot agent GE 1.5.48 (x2) >> 1.5.62
Intel Undi PXE 2.1 build 2.1 / Realtek PCI GBE controller 2.57 >> 2.66

+ Additional BIOS x3 with all of above except RAID changed to
1. UPDFinal-1.bin = v13.1.0.2126
2. UPDFinal-2.bin = v13.2.0.2134 + orom v13.2.2.2224 (No matching orom)
3. UPDFinal-3.bin = v12.9.0.2006

Apologies for sendpace link, tinyupload wasn't working for me tonight - https://www.sendspace.com/file/vyh6bx

.

@Saba09 - do not use BIOS in this thread, you will loose your serial, UUID, LAN MAC ID etc, this was built with ektorasdj BIOS dump from flash programmer (and that is how he's putting back into BIOS)
As for flashing in a modified BIOS, maybe ektorasdj can tell you from experience if that's possible or not, I may need to edit Insyde flash tool for you if this is Insyde BIOS (Unsure, have not looked at stock BIOS exe package)
Link me to stock BIOS, I will send you simple mod BIOS with one edit, so you can test flashing and show me the error you get, so we can see if I can help you to work around it.

Also, do this - go to this thread and in the section "C" download the V10 ME System Tools Package
Intel Management Engine: Drivers, Firmware & System Tools

Once downloaded, inside you will find Flash Programming Tool folder, and inside that a Windows or Win/Win32 folder. Select that Win folder, hold shift and press right click, choose open command window here (Not power shell).
At the command prompt type the following command and send me the created file to modify >> FPTw.exe -bios -d biosreg.bin

Right after you do that, try to write back the BIOS Region dump and see if you get any error, if you do show me image of the command entered and the error give >> FPTw.exe -bios -f biosreg.bin

If you are stuck on Win10 and cannot easily get command prompt, and method I mentioned above does not work for you, here is some links that should help
Or, copy all contents from the Flash Programming Tool \ DOS folder to the root of a USB Bootable disk and do the dump from DOS (FPT.exe -bios -d biosreg.bin)
https://www.windowscentral.com/how-add-c...creators-update
https://www.windowscentral.com/add-open-...menu-windows-10
https://www.laptopmag.com/articles/open-...ator-privileges