I am trying to run a runtime upgrade that changes a single parameter and version number. I picked the compact wasm blobl from the wbuild directory after building from release. Upon sending the TX, the node that receives the TX stalls and drops all its peers. Why is this?

Nodes, upon getting the runtime upgrade tx presumably, also all stop syncing with one another. Eventually they fail to respond to ctrl+c exit commands with high probability.

EDIT: Upon restarting some of the nodes who were attempting to process the upgrade, they eventually began building on the previous runtime, but some began logging this:

2019-09-17 13:48:52 Idle (1 peers), best: #116 (0xbc89…6e07), finalized #62 (0x5c49…859d), ⬇ 2.4kiB/s ⬆ 1.8kiB/s
Hash not equal
41cdbcb7395dde92b3ef669b9fac46830d17f97b6141f297053cec5d0978dc00
8e74fa69f818a50280b822c348220f7224a3c6538db2d6fb7658a884a780b10a
panicked at 'Storage root must match that calculated.', /Users/drewstone/.cargo/git/checkouts/substrate-25d0b09b83fafc89/f6d47ca/srml/executive/src/lib.rs:271:3
2019-09-17 13:48:54 Block import error:
Execution(Wasmi(Trap(Trap { kind: Unreachable })))