"!CLRStack -p" Isn't Always Reliable

As this post demonstrates, using SOS's "!CLRStack -p" command, incorrect parameter values might be shown even at the most basic debugging scenarios