There are two ways you can find out more information about the problem...
1) Cross-reference PID to process name.
Open the command line (run cmd.exe) and type in:
netstat -aon
C:\Users\admin>netstat -aon
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 6200
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 892
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 6200
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 564
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 1056
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 1108
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 620
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 608
TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING 1444
TCP 127.0.0.1:27005 0.0.0.0:0 LISTENING 2200
TCP 192.168.1.100:139 0.0.0.0:0 LISTENING 4
Locate the first line with Local Address of 127.0.0.1:80 or 0.0.0.0:80
Then use Task Manager (ctrl-alt-del) > Processes Tab (show all) to find out which Process has this PID.
2) Check the Apache's error log file or start Apache from the command line and check the error message:
httpd -k start
The IIS Service is called W3svc and you can stop it and also disable it (disables the automatic start-up) via Services window (run servers.msc).
You should also try using WampDeveloper Pro which has a much better setup process that detects and handles other software running on port 80.