Fedora 20 boot time is too long.

I am using dual boot with win7-64 bit. Its been couple of days fedora boot time is increased dramatically, here is the output of systemd-analyze & systemd-analyze criticalchain. Can any one solve the issue.

systemd-analyze
Startup finished in 1.642s (kernel) + 16.718s (initrd) + 4min 1.362s (userspace) = 4min 19.723s

systemd-analyze blame
    2min 44.675s ModemManager.service
    1min 30.018s firewalld.service
    1min 30.011s chronyd.service
    1min 16.574s NetworkManager.service
         27.440s rsyslog.service
         26.806s gdm.service
         19.139s dnf-makecache.service
         16.119s systemd-tmpfiles-setup.service
         11.636s systemd-random-seed.service
         10.953s lvm2-monitor.service
          9.222s systemd-fsck@dev-disk-by\x2duuid-593a1cbf\x2d012e\x2d46c5\x2d93e4\x2d85cc18088791.service
          8.674s systemd-backlight@backlight:intel_backlight.service
          8.348s proc-fs-nfsd.mount
          8.062s systemd-fsck-root.service
          7.176s systemd-tmpfiles-setup-dev.service
          7.021s systemd-fsck@dev-disk-by\x2duuid-681686da\x2d175c\x2d4d4e\x2d8bc3\x2da3bec44ee936.service
          6.042s dev-hugepages.mount
          6.040s dev-mqueue.mount
          5.794s sys-kernel-debug.mount
          5.225s systemd-fsck@dev-disk-by\x2duuid-1e9ea328\x2d8772\x2d4391\x2d97a6\x2dc127e19b78a2.service
          3.977s systemd-fsck@dev-disk-by\x2duuid-a1b91a9a\x2deef7\x2d4669\x2d84bc\x2da7b4bfc124e6.service
          3.465s systemd-udev-trigger.service
          3.297s tmp.mount
          3.182s home.mount
          2.919s bluetooth.service
          2.889s systemd-fsck@dev-disk-by\x2duuid-03f8c08b\x2dddb3\x2d4b18\x2dae25\x2df115ffb7f5f6.service
          2.423s systemd-tmpfiles-clean.service
          2.396s usr-local.mount
          2.276s systemd-sysctl.service
          1.544s nfs-lock.service
          1.301s user@0.service
          1.240s dev-disk-by\x2duuid-78951d45\x2d83a6\x2d44b5\x2d9190\x2df19121c7241f.swap
          1.212s kmod-static-nodes.service
          1.195s auditd.service

systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @4min 1.346s
└─multi-user.target @4min 1.346s
  └─nfs.target @4min 1.345s
    └─nfs-lock.service @3min 59.798s +1.544s
      └─network.target @3min 59.751s
        └─NetworkManager.service @2min 43.176s +1min 16.574s
          └─netcf-transaction.service @1min 14.078s +141ms
            └─basic.target @1min 13.095s
              └─sockets.target @1min 13.075s
                └─dbus.socket @1min 13.056s
                  └─sysinit.target @1min 12.795s
                    └─systemd-update-utmp.service @1min 11.991s +801ms
                      └─auditd.service @1min 10.792s +1.195s
                        └─systemd-tmpfiles-setup.service @54.669s +16.119s
                          └─local-fs.target @54.342s
                            └─var.mount @48.661s +653ms
                              └─systemd-fsck@dev-disk-by\x2duuid-593a1cbf\x2d012e\x2d46c5\x2d93e4\x2d85cc18088791.service @39.435s +9.2
                                └─dev-disk-by\x2duuid-593a1cbf\x2d012e\x2d46c5\x2d93e4\x2d85cc18088791.device @39.432s