eeek BSOD is back... and worse.

[ubern00ber]

The BSOD problem is back(haven't seen it since some time in October) and seemingly worse. It's not only happening when I log in but rather also randomly as i walk around... =(

in any case both my chars are now stuck to it which sucks

[Cagen]

I can move them for you if you PM me your account number and password.

Are you running the game in 800x600? (I think it is defaulted to this.) I was running it windowed in 800x600 and at a specific point in the map it would always give me a BSOD. I upped the window resolution to 1024x768 and I now never get a BSOD.

If you don't know how to change it, go to your start menu > programs > evidyon > change display mode, then change the X and Y resolutions.

[ubern00ber]

hmm ok upped the res... will play in a bit again and see how it is.

[Karl G.]

Ugh. The BSOD bug is really annoying. What is your GFX card/system specs? I'm trying to get a collection of the data on this.

[ubern00ber]

Specs:

GFX: NVIDIA Quadro FX 570M
CPU: Intel core2 duo - 2.40GHz 2CPUs
2gigs ram
windows XP
direct x 9.0c
(it's a Lenevo T61p laptop)

on my much shittier desktop i never had the BSOD problem.. it uses a much older NVIDIA card too (GeForce 4 mx440)
Ima try and do some research as to why the problem happens... heh. also, i'm gonna pm you my account number/password and tell you which characters are stuck... so you can go ahead and see the crash site for yourself. Two of them appear to be in the same place, one in a totally different place. (2 are near water, one is near cliffs).

EDIT:
Eeek I just realized that nv4_disp.dll is my main driver =/ heh

[Karl G.]

So I've done extensive research on the BSOD error, and it seems to be pretty common across the web, but there is no consensus as to a solution. For some people, distributor-overclocked hardware matched with incompatible memory causes the issue; for others, entering 3d acceleration mode on the chipset with a weak power supply is the culprit. In all cases, however, nv4_disp.dll is the source of the problem and the bug reported is the dreaded 0xC0000005, with parameters indicating that an invalid part of memory was accessed or an infinite tight hardware loop was encountered.

As far as I can tell, there is no fix once this bug is encountered; however, the fact that it occurs frequently at a certain map location (the western entrance to the mountain pass) of Evidyon is peculiar, and leads me to believe that this region has something special about it. One possibility might be that the rendering buffers there are larger than in other areas--but this doesn't make a whole lot of sense to me, because there is more scenery in places like the forest and those ares don't have this error at all. Less likely, it could be that people have happened to arrive at that location after playing the game for a significant amount of time, and setting up the rendering buffers there causes the card to temporarily draw excess power and either overheat or cause some other glitch in the card.

Needless to say, this is giving me a huge headache. Those of you who encounter the BSOD, if you could try logging in using different display resolutions, fullscreen/windowed mode, etc. I would be very grateful for any kind of insight. At this point it could be anything from a memory allocation issue to a buffer overrun.