Event Log Error Question

woode

Bit poster
I am running boot camp 1.2 with Parallels VM (3188). Everything works well in boot camp and VM mode, except for a few strange things. The VM will occasionally just suddenly disappear for no good reason, and only a notification that it stopped suddenly (which was pretty darned apparent without the notification!). Anyway, when I looked in the Windows Event Viewer for some answers, the only things in the System log are tons of error messages, every few seconds, alternating between the following:

ERROR #1
Event Type: Error
Event Source: FW1
Event Category: None
Event ID: 1
Date: 4/15/2007
Time: 7:24:09 PM
User: N/A
Computer: MACWOOD
Description:
FW1: -->rred
Data:
0000: 00 00 00 00 02 00 4c 00 ......L.
0008: 00 00 00 00 01 00 00 c0 .......À
0010: 01 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

ERROR #2
Event Type: Error
Event Source: FW1
Event Category: None
Event ID: 1
Date: 4/15/2007
Time: 7:24:09 PM
User: N/A
Computer: MACWOOD
Description:
FW1: TransferData mismatch: 148 requested 128 transfe-->
Data:
0000: 00 00 00 00 02 00 4c 00 ......L.
0008: 00 00 00 00 01 00 00 c0 .......À
0010: 01 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

The TransferData mismatch has different numbers in every entry. I've searched the Internet, but can't find anything that this might apply to. Has anyone else seen this?
 
FW-1.. thats Checkpoints firewall-1 vpn client right ? Try uninstalling it, reboot, then reinstalling it.

The 1 google page i could find that was remotely related, doesnt seem to indicate this is a critical problem, so this might not be why you have a crash.
 
Last edited:
Thanks for the responses. Yes, I do use the checkpoint client, so I will try the uninstall. Thanks for the suggestion. The errors have been around since I built boot camp, but I haven't noticed if they are appearing when in a boot camp session, a VM session, or both. The sudden crashes are infrequent and recent, so they may very well have nothing to do with the error.
 
Back
Top