Regarding the widely-discussed problem of persistent crashes to Blue-Screen-of-Death when trying to save when using Giga 3.1:
I've started this as a new thread because I think we should try to focus on solving the problem, not bashing Giga or promoting other products. (We all realize that we can choose to use a different program if we want; some of us would just prefer to try to fix our Giga problems instead, thank you.) So please, let's try to keep postings on this thread confined to asking questions and discussing problem-solving suggestions, not just griping and whining. Thanks in advance.
Since we upgraded to Giga 3.1 we, too, have been experiencing "crash-to-BSOD-when-saving" problems. The error message we kept getting when using "save as" to save a project was: "Page_fault_in_nonpaged_area" .
The only way we could avoid this crash (and only sometimes) was to save the project repeatedly, every few keystrokes or mouse-clicks, over and over and over again (for example, every single time we attached or detached an instrument or adjusted a level). The crashes were NOT occurring because we were using a huge amount of system resources -- we weren't using Gigapulse at the time, for example, and often had only 2 or 3 instruments loaded.
We realize that "save after every keystroke" is not how anyone should have to work. Of course, it is our usual practice to save frequently while working on a project -- for instance, we don't just stack and stack and stack, waiting until the very end to save -- but the effort required to keep 3.1 from crashing was obviously not what Giga's developers intended. There definitely is a problem.
So we decided to completely uninstall 3.1 and reinstall 3.04 to see if the BSOD problem persisted. Then if it would run without crashing, we planned to download 3.1 and try it again. But we never made it that far.
Here's what we did, step-by-step:
1. Burned a back-up image of the system using Symantec Ghost (important!)
2. Uninstalled Giga using the Windows uninstaller.
3. Without rebooting, ran GigaClean, then manually removed Giga icons, etc.
4. Rebooted and verified that Windows XP was properly tweaked (pretty much the same as the more important items suggested in http://www.musicxp.net/tuning_tips.php; our system arrived "pre-tweaked" from Carillon so we kept their tweaks in place).
5. Reinstalled Giga 3.04.
So far, so good. BUT, when we started Giga 3.04 and then opened Cubase, the system instantly crashed to BSOD and we got this stop code: "IRQL_NOT_LESS_OR_EQUAL". This same crash happened without fail on two successive attempts. The stop code, just in case anyone understands them, was: "STOP: 0X000000D1 (0X027AEF95, 0X00000002, 0X000000001, 0X7C9114B6".
So we restored the system using the burned image from Ghost. We're back to Giga 3.1 and still having the original BSOD crash problem ("Page_fault_in_nonpaged_area").
Here are our system specs:
Intel D925XCV (200MHz bus clock), BIOS date 08/19/2004
3.2 GHz Pentium 4 w/ 16 KB primary, 1 MB secondary cache
2 GB memory (4 x 512 MB)
Windows XP Pro, SP2 (Build 2600), tweaked as discussed above
120GB Seagate 7200rpm Barracuda SATA drive
(partitioned C=20 GB, D=100 GB) as Drive 0, FAT 32
320 GB SATA RAID as Drive 1, NTFS
LaCie 400GB external USB-2 drive (for file storage and archive only)
NEC ND-3500AG DVD-RW
Frontier Dakota PCI audio card
Frontier Montana expansion card (for Dakota)
Frontier Sierra external MIDI/SMPTE expansion board
RME ADI-8 DS external A/D-D/A converter
2 Radeon X300 display adapters
2 Princeton VL1716(ANA) 17” monitors
Does anyone have ideas as to why the system crashed after reloading Giga 3.04? Does anyone understand what sorts of conflicts/issues would cause the IRQL_NOT_LESS_OR_EQUAL error? My initial suspicion is that it might have something to do with the Frontier Design Dakota card, but I can't go beyond there. (I verified that we were using the latest drivers for the Dakota card both before and after reloading Giga 3.04.)
Any helpful suggestions will be greatly appreciated!