Also doing this will help us help you (if we know the code it gives).

Please follow these steps so next time you have a bluescreen we can get the code in it to identify your issue. To make sure you can read the blue screen (as in if you see the blue screen for a second or two and your PC auto-reboots and you can't read it ... then follow the instructions below to disable auto reboot so you can write down the code).

You should turn off the BSOD auto-reboot so next time you can see it and write down the error code.

(Note: I am assuming you are running windows XP. If you are not re-post and tell me you are not running windows XP. If you are please follow the instructions below.)

To do this ...

1) Right click on the "My computer" icon in the desktop...

2) Go to properties

3) Go to "Advanced"

4) Go to "Startup and Recovery" and hit the "settings" button.

5) Now where it says in the "System failue" box un-tick the box that says "Automatically re-start".

Now you just have to hope you will have another BSOD (or maybe never have it again) ... but if you do we will need the code from it.

If you get a screen like this the code we will need is after the "***  STOP:" after the bottom (so its STOP: 0x00000050 and so on and so on.

OK, I didn't get BSOD so far, but during one of the app switching, Demigod crashed (in Demigod, I was at the debrief screen after first tournament mission. I will try to add the log now.

Edit: OK, I *will* add the file, as soon as I find out how to do that. Any ideas?

I have been having this same issue. Bought a new PC a month ago, here are the specs:

Windows Vista-64

Intel Core i7 CPU

920 @ 2.67GHz

6.00 GB RAM

nVidia GeForce 9400 GT

I have run and played through Fallout 3, Bioshock, Call of Duty 2, Hearts of Iron 2, Sins of a Solar Empire without any problem. Then, three days ago, I began getting sudden and inexplicable BSODs when running Demigod. Same issue as Kovin, only, I will add that it never seems to happen when I'm in-game. It only happens when I am in the Demigod menu. I have received 15+ of these in the last three days on a computer that never BSODded before. Also, I have received varied and interesting BSODs, including, but not limited to:

IRQL_NOT_LESS_OR_EQUAL

PAGE_FAULT_IN_NONPAGED_AREA

Now, if either of these were true, you'd think I would have run into problems earlier, no?

Let me just add that I did a lot of tinkering over the weekend, and I have failed to find a solution. I went as far as to reformat my harddrive, downgrade from Vista-64 to XP-32, and the problem still occurs. I get random, and seemingly-impossible BSOD error messages within 5 minutes of running Demigod. I have run several hardware diagnostic tools (memtest86, etc.) and none of them reported that I have RAM-related issues--which is what PAGE_FAULT_IN_NONPAGED AREA means. Also, I have updated Windows (Vista and XP), my nVidia and DirectX drivers, and even my ethernet drivers in an attempt to stave off the IRQL_NOT_LESS_OR_EQUAL, but I will still get that occasionally.

My conclusion is this: the latest build of Demigod is not compatible with Window Vista or XP. You guys are having this problem, friends of mine are having crashes all over the place; if not BSODs, its something. Sure, I can play 1 game out of 3 or 4 attempted games, but at this point, it's almost too much trouble to continually restart my computer after each failure. I can only hope that a new path is released for Demigod, or a new update is released for Windows.

I get a BSOD every time I play Demigod unless I use /nosound.

I'm okay with using /nosound, though obviously I wish I didn't have to.

Oddly enough, not to place the blame and saying Demigod is coded wrong, but it could be the game causing it, be it fully or only halfway. Why do I say this? I've had it before, in another game.

I was playing WOW a few years back and had a Radeon 9800 in my system. Can't remember the exact name, but it was one of those superfast cards when it was first released and it sold a lot. Anyway, in one area in the game it would always crash my videocard, after which it would recorrect itself with a soft reset which was built in the ATI driver. I think the driver thought I overclocked my videocard wrong, but I never did that and it only happened in that specific zone in WOW. Long story short, Blizzard blames ATI, ATI blamed Blizzard, and neither bothered to find a solution. In the end I kept having the problem and had to avoid the whole zone till I got a new system with an Nvidia card....

To GPG, who will never ever read this: don't shove off responsibilty, but contact Nvidia and try to find a solution together.