TriggeredBox

I got another crash this morning. In that case though, the same error message appeared during (re)startup. MS has no say on the problem and the cause, as written in the error reporting page, was "unknown". The device wasn't enumerated either. Only a bunch of log files were included in the report wich I doubt would help. I've noticed that OpFor leaves sound hardware acceleration off. When the sound disappears, I've noticed that turning on hardware acceleration for sound makes it come back on. This hasn't solved the problem though - it will crash when you try to go to Windows in any way but the random crashing seems to have stopped. I'm going to try leaving audio hardware acceleration on by default and see if that works. BTW, like I said earlier, the MS report insists it's a BSoD error but I haven't seen any Blue Screen myself yet.

As I continue playing OpFor, I also continue damaging my hard drive slowly. Before I get to the problem, I must say I've never experienced this problem on an older computer of mine and has so far only occured in this new one I'm using. Current specs: -Windows XP Pro w/ Service Pack 2 -Intel Pentium 4 (3.00GHz - 1GB of RAM) -NVidia GeForce 6200 (93.71 driver update) w/ Direct X 9.0c My problem is that the game seems to suddenly crash and directly reboots my PC. (which the computer thinks is an improper shut down causing disk check to come up during startup - it picks up some corrupt files) This happens during gameplay - the primary symptom is that all sound disappears prior to the crash. (sometimes, it doesn't disappear and just goes to the crash directly) When the crash DOES happen, the screen instantly goes black and reboots my terminal giving me the improper shut down error and a disk check prompt. As Windows loads, it gives me a "Windows has encountered a serious error." message. Reporting it to MS leaves me with no solution and tells me that it's a "Blue Screen Type Error caused by a Device Driver". (I never saw any Blue Screen of Death however.) This has happened on: -Operation Flashpoint 1.20 -Operation Flashpoint 1.30 -Operation Flashpoint 1.46 -Operation Flashpoint 1.30 with Red Hammer Gold Edition -Operation Flashpoint GOTY 1.96 Drastic times when the problem happened: *Previewing a mission personally made in the Editor - after about up to thirty minutes of play. *Just plainly playing through the campaign - crash comes after completing at least two to three levels. Up to six during a fresh install. *Crash was most persistent in Hold Malden mission, some tank missions, and the Malden beach mission in Red Hammer. Loading the saved games did the same thing and crashed at some point. *Leaving the game during gameplay for a while and coming back to it. Spending too much time in one mission lets the problem "catch-up". Things I tried to remedy the problem: *Install different versions of OpFor testing each version out - happened anyway. *Reinstall. Still happened anyway. *Picked between Direct3D with and without HW T&L. Happens on both. No Glide support for me of course. I suspect that it has mostly something to do with this. *Abort the mission and application itself using the in-game menus after disappearance of sound - crash comes during loading screens or exit screens. *Alt+tab out and end the process using Task Manager after disappearance of sound. OpFor silently closes - reboot happens anyway after a few moments or when the screen tries to go to Windows. Things that have happened here: *Corrupted Editor missions. *Corrupted single and campaign mission saves. *Corrupted single and campaign missions. *Entirely corrupted Campaign option in one profile - selecting it via Main Menu forces the game to freeze.