Quote:
Originally posted by G_yoshi
Just as it sounds. Its dumping everything in memory into a file which Windows will send off to Microsoft if you allow it. It just tells them what was running at the time of the dump and so forth. Helps them find a bug in their code that they can solve with one of the millions of XP patches they release almost everyday 
And yes, I was exagerating on the number of patches released. Its only 1000...erm...100...well...::runs and hides::
Anyway, it would be nice to have some kind of image filtering for showimgs that you use zoom or alpha effects on.
And someone said they can't play GK because of they use a 56k dialup? Pheh. I can and I'm on 56k dialup. Its more your processor, RAM, sound card, and GFX card that have the impact on lag. I can play GK without hardly any lag. Plays like a normal graal server except it will lag when lots of people are on screen or when there are lots of showimgs :x
|
No...what he witnessed is called a stop error. It happens when the kernel crashes in an NT5 based system (not sure if it applies to NT4). I believe the memory dump is for debugging purposes, but it is definitely not sending Microsoft any information. It dumps the contents of the memory into a file so you can examine what was happening when the kernel crashed.
As far as GK, it does lag connection wise from time to time because the NPC-server lags, most notably on enemies and signs. My system well exceeds the recommended requirements (see workstations thread in NGRT for specs) with a broadband connection and I still experience serverside lag from time to time.
Quote:
Originally posted by Matman58
Alright when this error happens it says it is doing a complete memory dump. Now what exactly does that mean.
|
Read above for why it happened. Your kernel crashed...Why Graal would cause your kernel to crash is a mystery. But you still didn't post the error message. I mean the COMPLETE message as it looks on the screen (including all those little numbers etc.)...The reason I need this is because I can find out exactly what happened to make it crash. Just write it on a piece of paper or something. Stefan would probably like to know this also for debugging purposes.