Trouble transferring ROMs to Retropie (RasPi3 keeps shutting down mid-transfer)

Shockwave

Required info:
Hardware: Raspberry Pi 3 Model B
PSU: Northpada 2.5V 3A power supply with Northpada Push Button Switch
Micro SD card: Sandisk Ultra Class 10 200 GB Micro SC card AND Sandisk Ultra UHS-1 200 GB Micro SD card (yup, tried two different micro SD cards)
Controller: Wii U Pro Controller (not bluetooth sync'ed at the time of incident) and USB keyboard (Logitech K370)
Connection to HDTV: HDMI
Software Version: 4.3.3 (updated from 4.3.1)
Obtained from: Retropie Downloads Page
Network connection: Ethernet

Additional Info (could be useful, maybe not):
Micro SD cards formatted FAT32 (SD card formatter + Fat32Formatter (Win10 Command Line))
Win32DiskImager to create/burn image to micro SD card (Win10)
Performed update after installing all core/main/optional/driver packages, and a few experimental ones (Drastic, Attract mode).
Turned on USB ROM service and Samba shares in Configuration Tools

Description of Problem:
I do believe that's all I can obtain without trying this again. It seems to shut down in mid-transfer when I'm transferring ROMs over the Samba share (network). The power is still going to the Pi 3 (red LED is still lit on the board, no green LED to indicate activity), and I have to reboot the Pi 3, and when I do, it locks up at the splash screen.

Trobleshooting Steps I've done already (that haven't worked):

Different Micro SD card
Disconnect the Wii U Pro Controller and use keyboard only
Different HDMI cable/input and PSU

Not sure if it's a software bug I'm not aware of or what. Maybe I'm doing something wrong. Wouldn't be the first time. Any help would be appreciated. Thanks in advance.

danielmewhouse

@shockwave hi. Did you tried burning the image with etcher instead of win32disk imager? I've got some problems working with images burned with win32disk and DD on Linux. Etcher is multiplatform, easy to install and easy to use. Give it a shoot 😁

Shockwave

I have Etcher, so I'll give it a shot. Thanks for the suggestion.

Shockwave

@danielmewhouse Tried it and got the same shutdown as last time, but I did get some more information this time around.

Got the time of the shutdown: during the update process in the Retropie Configuration -> Update menu. It was during the course of the ControlBlock update is when the shutdown occurred. And I'm pretty sure it's that because of the fact that when I reboot it, the ControlBlock job is the one that holds up the Pi 3 from completely booting (as per the boot text when the Pi 3 is booting after the splash screen).

Hope that helps. I guess not to install the Control Block from the Driver menu, huh? :p

Shockwave

Yup, confirmed. Don't install the Control Block module from the Drivers list if you're not using it and updating with Retropie 4.3.5, because it looks for it and if not detected, initiates the shutdown sequence.