FP-DI-301: All channels went "HIGH" at the same time.

Question

Will FP-1001 "Watchdog" settings or FP-DI-301 module/channel settings cause digital inputs to go "High" regardless of the connected swithes positions?
On 4/29/2009 @ 07:11:30 AM, while running a known good process, all of my FP-DI-301 input channels (48) on a individual network bank went "High"!!!
I am currently running a "Lookout" process with 6, FP-1001 network banks connected via rs485.  This process has been in operation for more than five years.  On the date in question, maintenance personnel informed me that a machine had gotten jammed and they had cleared the jam and it was now running.  After watching the video playback of the machines operation, I realized that it did not operate as programmed.  I also noticed that three other like machines associated with the same network bank performed EXACTLY the same way at EXACTLY the same time.  All other machines associated with the other 5 network banks functioned normally.
After reviewing the collected data (citadel 4 database) I found that all of the channels of the DI-301's went "High" together for a period of time, then they reverted to normal operation for a few seconds and then go "High" again in unison.  This back-and-forth continued for aproximately 15 minutes, until the whole process was shutdown and restarted.
All of the channels are connected to field mounted prox switches, there is no way that all the switches toggled/sensed at the same time.  This has to be a network/module problem. 

Answer 1

Kyle
A lot have things have happened and have changed.
Original problem #1:  Lookout 4.0.1 sees my inputs (All 48, DI-301's)@ Fieldpoint address bank "30" turning on and off, staying on, changing state, etc.... for a short period of time.  This problem happened once at the end of April (all came on and stayed on for about 15 minutes) and again about mid-end of May (This time they were blinking on and off).  During the last event I noticed that the actual DI-301 channels were stable and were not changing state like Lookout was seeing.
I think I have fixed this problem.  It hasn't shown up again and I cannot recreate it.
What I have done to address the above problem:
Cleaned out the PC (NT os), uninstalled unneeded programs.
Reconfigured all fieldpoint 1001 watchdogs.
Imported my reconfigured IAK file into my fieldpoint object of my Lookout process.  
Problem #2:  While troubleshooting problem #1; I found, that occasionally upon power-up I would not get my "ready" LED's on my I/O modules of address bank "30" and subsequently red X's would appear on some of my Lookout panels. 
What I have done to address the above problem:
If you push on the first I/O module the ready lights will come on.
I replaced the FP1001 and other modules and terminal bases and this problem would not go away.  I swapped out the FP1001 again, with a known working one from address bank "10", and problem dissapears.  Strange that it does not show up @ address bank "10" now.
Current problem #3:  Programmed machines associated with address bank "20" (1-FP1001 and 5-RLY420's) will stop for about 10-30 seconds then restart and finish their program.  This may only happen once every 2 days or 3-4 times in one day.  Occassionally I will get a fieldpoint generated alarm "Channel Specific error, DEV:21-24, CH: 00-07, ERR:3"  I even got "Channel Specific error, DEV:22, CH:09, ERR:3".  The RLY-420 module @ this address does not have a channel "9".
What I have done to address the above problem:
This is when I found and repaired the corrupt source code, LKS file.  Problem returned the next day though.
I have found out that the outputs are de-energizing.  That's all so-far.
Could changing baud rates or poll rates and times help?  Could some sort of weird comm interference cause my outputs to de-energize and not give me a COMM fail?  I am still thinking it is fieldpoint related somehow since the LKS file fix did not help. 
Chip.