The mkl bug showed up as a crash in rtknavi.exe when kinematic mode was invoked, with
"illegal instruction at offset 001d59c7 in mkl-p4p.dll" under details in microsoft popup.
Tomoji sent me a rtknavi_nomkl.exe patch which completely cured the problem.
I see he has not released it generally, I assume he is waiting to see if other people have a similar problem.
Tips to get you running in kinematic mode.
Use RMX-RAW and RMX-SFRB outputs only, thats all you need.
Under 'options-positions' make sure you enter the base station position as accurate as you can the more accurate the quicker will be the fix.
if using moving base mode you don't need the base station position but you need to enter the baseline length constraint between receivers, under 'options-settings2'.
For example I use two ublox receivers 1 meter apart so enter 1.000 0.1 , say, the second number is the stdev
If using input (3) corrections eg IGS ftp be sure to enter a temporary file location under 'options-files'.
everything else I started out with the default settings.
If you are within say 50km of an NTRIP base station you can use this as a base to locate your ublox base position fairly accurately. (100km will work too but not as accurate)
Check at www.igs-ip.net for your nearest station.
You can register at that site to receive realtime input via internet.

my startup commands are:
!UBX CFG-RATE 50 5 1
!UBX CFG-PRT 1 0 0 2256 57600 0 0 0
!UBX CFG-PRT 2 0 0 2256 57600 0 0 0
!UBX CFG-PRT 3 0 0 0 0 1 1 0
!UBX CFG-MSG 2 16 0 0 0 1
!UBX CFG-MSG 2 17 0 0 0 1
for 20 Hz raw updates, 4Hz navi. operation (works on my lea-4T)
USB only in UBX mode only RAW and SFRB only
note that the message ID in the last two entries is two seperate bytes eg 2 16 not as implied in the rtklib manual.

Start off in single mode first then try kinematic or moving base. Set L1 only.

Let me know how you get on.

Regards
Anthony