The amazing BLUESCREEN!

Bluescreen is almost ALWAYS a hardware issue (or a virus). It tends to point to faulty memory (google memtest86 and run that, it's not perfect but finds memory errors 95% of the time) or a failing HDD (if you're in a laptop I'd check that first). Do a full bad sector scan (rightclick on your main HDD and choose "Properties" -> "Tools" -> "Error checking" and select "scan for and attempt recovery of bad sectors" (you might have to reboot for your main HDD)

See whether you still have warranty for either of those parts and send it in for them to check out if either are having issues. Repairing bad sectors on a HDD will rarely solve the issue (if it's only one on, maybe... more, forget it, the head is damaged), memory issues = replacement (unless you're on Linux, but then I'd still replace it as part of your memory will not be usable).

Most of the time players with issues are having these due to hardware faults (in my experience 5% of all hardware gets returned due to faults) or old / incorrectly installed drivers.

A PC does not crash or bluescreen regularily, it can happen once in a blue moon, if it happens more often there's other causes!

Well the problem is that its only demigod that give me bluescreen on regular bases, no other games i have do that and i do have most of the new games. It could be my network card, however still strange it only happens to this game.. and really painful :/

hardware failures can by caused by software. Did you try to reinstall demigod? Maybe its a dumb awnser but its worth trying, it fixed some other issues for me too.

BSODs are generally caused by hardware or driver problems, and the error message it shows can help pin down exactly what the issue is.

The next time it crashes, you may get a BSOD similar to the one below (not all highlighted parts may be present):


Write down the information in the highlighted areas before turning your computer off. The information there can then be researched online to see if others have experienced similar problems, and what the cause was. You may also get a 'windows has recovered from a serious error' message when you turn your computer back on--if you do this, you should agree to send the report to microsoft. You'll then be forwarded to information about that error on Microsoft's knowledgebase, if they have any.

A helicopter was flying around above Seattle yesterday when an
electrical malfunction disabled all of the aircraft's electronic
navigation and communication equipment.  Due to the clouds and haze
the pilot could not determine his position or course to steer to the
airport.  The pilot saw a tall building, flew toward it, circled, drew
a handwritten sign and held it in the helicopter's window.  The sign
said "WHERE AM I ?" in large letters.
 
People in the tall building quickly responded to the aircraft, drew a
large sign and held it in a building window.  Their sign said, "YOU
ARE IN A HELICOPTER."  The pilot smiled, waved, looked at his map and
determine the course to steer to SEATAC (Seattle/Tacoma) airport and
landed safely.
 
After they were on the ground, the co-pilot asked the pilot how the
"YOU ARE IN A HELICOPTER" sign helped determine their position.  The
pilot responded, "I knew that had to be the MICROSOFT building
because they gave me a technically correct but completely useless
answer.

   

Just started getting blue screens of death in the middle of playing Demigod.  Started last night and has now

happend twice today.  I don't have time to read too much of it as it does a countdown 'system memory dump'

and restarts. 

I have not once seen a blue screen on this computer with Vista.  It's only a year old and this is actually the only

time I've ever had it reset because of an error.  I'll run the HD check, but I thought I'd post to let you know there's

more than one person experiencing this durning Demigod play, only demigod play, and for the 1st time ever last

night.

Thanks for the support help.  I'll post if they stop after the check.

Ditto.  I'd played some earlier versions without getting BSOD but I only played a couple because it was really laggy for me in the earlier versions.  I thought I'd try and see if the lag was better after this last update and I connected fine and it was not laggy but 10 minutes in, it just bluescreened.  I tried another game and same thing happened after about 5 minutes.  I didn't really have time to read much of it, but I did notice there was no "The problem seems to be caused by the following file" on it.

Alright I ran both the memtest and the HD error checking and neither came up with any errors.  I also checked my graphics

drivers, and they were in fact up to date.

I'll give it a few more tries and see if I get more blue screens.  Hopefully not.  Just wanted to tell you both those gave no errors.

First chance this week I've had a chance to play Demigod, & the 3rd game I play I got BSoD.

Any ideas? It is clearly only Demigod that is causing this to happen, as I play many other

graphic intensive games and have never seen this, nor do I see it now.

Thanks for any help :/

--

Adam H. Knudsen

I'm getting the same issue. Demigod, and only Demigod, has started causing BSODs.

The BSOD goes directly to a reboot after a few seconds so I haven't the time to write down any info.

I've gotten this a couple times with Win7RC 64 bit.  Its only happened maybe 3 times total, but as others have said, its only ever happened with demigod.  Something about the pagefile and then it restarts so I don't get to read all the details.  Its certainly not consistent.  Although I wonder if it happens when I am talking on teamspeak at the same time.  Anyone else running multiple stuff whilst playing?  Its always happened to me with hamachi, teamspeak server, and teamspeak running.

How long did you run the memtest program? 1 cycle is not enough, some faults happen seldomly but can regularly crash 1 certain type of game. I've had this before.

WOW crashed every so often, and only WOW, no other application, and I couldn't find out why. I was raiding at the time so I wanted it fixed. Memtest did not indicate an error after 30 minutes of testing. But I kept having the errors. Then later I ran the test the whole night, running over 6+ hours (I don't sleep that long :P). It finally reported 2 errors. I replaced the RAM and ever since the computer never crashed again.