Blue Screens (BS) have driven several of us crazy at one time or another. Usually not associated with Vegas, but rather with systems and configurations. Provide some detail about how your system is set up - external hard drives, PCMCIA cards, computer specs, etc will be a big help in evaluating what's going on. Are your PTTing from timeline or from a rendered *.avi file? Stuff like that. Have you read the Knowledge Base article on optimizing capture and PTT? DGrob

Its just a really straight forward set up, firewire 1394IEE OHCI PCI card , Canon XM1(GL1), 4 hard drives 2 video drives without OE. Trying to print from timeline to Canon, tried from rendered avi, from Vegas capture. Tried most of the things in the knowledge base, now worse than ever. It all worked fine prior to XP. HELP!

I bet it is the firewire card. I deliberately got a new motherboard that had firewire buiit-in. It goes from the camera to the PC fine, never a single dropped fame. However using it to print to tape I'd get a blue screen every so often. Fixed it by putting my old tried and true Siig firewire card back in.

The other likely thing is drivers. You shouldn't need to install any. Firewire cards under XP work best with the default Windows drivers which should be installed transparently.

Have you tried going to Device Manager, totally uninstall the firewirecard, shut down, boot back up. XP should say it found a new device (the firewire card) and install Windows drivers.

I agree with BillyBoy. My Dell PCI IEEE 4-pin would capture just fine, but I never did get it to PTT in any configuration. Added a 2-port PCMCIA adaptor out to my external drive. HOWEVER, cannot PTT from external drive back out through the 2nd PCM port. The data flow in/out seems to overwhelm the card. So I just copy my project to C drive, PTT, then delete the copy. DGrob

Yeah I guess it's of to the PC store to get the SIIG. Ironic really because I bought one last week when configuring the XP set up as the system was not picking up the DV camera, it did not solve the problem so I returned it. We'll try again , also the promise card I have in has a Via chip on it, Via seems to come up so many times as having issues so it would not suprise me if that was the culprit.
This bit is supposed to be easy, the project is finished all I have to do is get it out, so bloody frustrating. Interestingly, I just tried again in hope and if you switch from the ex mon to preview in the software the ex mon still continues to flick between black and blue whilst the preview plays smoothly. What that means, I dunno!
Is there a correct procedure to get the system to recognise the camera after installing the FW card, i seem to be having problems with that.
Finally when I close a project from the file menu it always comes up with an"error occured" listed below (Veg 4d) I never understand these things.

Sonic Foundry Vegas 4.0
Version 4.0d (Build 205)
Exception 0xC0000005 (access violation) READ:0x6F1F4E8 IP:0x101D3C4
In Module 'vegas40k.dll' at Address 0x1000000 + 0x1D3C4
Thread: GUI ID=0x7F4 Stack=0x12F000-0x130000
Registers:
EAX=06f1f4e8 CS=001b EIP=0101d3c4 EFLGS=00010216
EBX=00000000 SS=0023 ESP=0012f1d0 EBP=0000004e
ECX=002c0004 DS=0023 ESI=06e13e98 FS=003b
EDX=0012ed30 ES=0023 EDI=0012f428 GS=0000
Bytes at CS:EIP:
0101D3C4: 8A 08 84 C9 74 24 56 8B ....t: 35 A0 A7 1D 01 57 8B F8 5....W..
Stack Dump:
0012F1D0: 005576E0 00400000 + 1576E0 (vegas40.exe)
0012F1D4: 06F1F4E8 06DC0000 + 15F4E8
0012F1D8: 0000004E
0012F1DC: 0012F428 00030000 + FF428
0012F1E0: 06E13E98 06DC0000 + 53E98
0012F1E4: 0000FDEA
0012F1E8: 00000000
0012F1EC: 00000000
0012F1F0: 0012F1E4 00030000 + FF1E4
0012F1F4: 0012F428 00030000 + FF428
0012F1F8: 06E13E98 06DC0000 + 53E98
0012F1FC: 0000FDEA
0012F200: 00557BB2 00400000 + 157BB2 (vegas40.exe)
0012F204: 000400F2 00030000 + 100F2
0012F208: 0000004E
0012F20C: 0000FDEA
> 0012F214: 00557E91 00400000 + 157E91 (vegas40.exe)
0012F218: 0012F2FC 00030000 + FF2FC
> 0012F21C: 00557B70 00400000 + 157B70 (vegas40.exe)
0012F220: 0012F2B4 00030000 + FF2B4
0012F224: 00000000
0012F228: 00000000
0012F22C: 06EB5C00 06DC0000 + F5C00
> 0012F284: 0101F078 01000000 + 1F078 (vegas40k.dll)
0012F288: 00140000 00140000 + 0
> 0012F28C: 77D67AD7 77D40000 + 27AD7 (USER32.dll)
0012F290: 000400F2 00030000 + 100F2
0012F294: 0000004E
> 0012F2A0: 00557B70 00400000 + 157B70 (vegas40.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0067A82A 00400000 + 27A82A (vegas40.exe)
0012FFFC: 00000000

"Is there a correct procedure to get the system to recognise the camera after installing the FW card?" XP can be odd . . . think it was Chienworks that pointed out that sometimes it's just "windows being windows." Using XP Home I will usually boot up without external drive or camera on, then power them up individually. Usually, XP picks them up and I'm off and running. Occasionally I might have to turn them off and on to get XP off its duff and recognise them. Others on this forum have reported similar personality traits.

The error you report on File-Close seems really odd. I think I'd access SF Support on that one. I went through a few odd error moments when I upgraded to V4 from V3. Turned out I had to not only uninstall V3, but access the still present SF V3 folders in Program Folders and delete them. Then reinstalled V4 and have been happy ever since. Go figure. DGrob