Hi there,

While racing online I was suddenly thrown back to desktop. It happens very fast and LFS is just gone, as if it was never running. Happened twice so far in the last two days. It each time occured on a different server with different config. As far as I can tell, nothing unusual happens before I'm back to my desktop, just racing along really with not much traffic near me . I don't have an error report because I don't know where I could find one (never had problems with LFS before). So please tell me what info you need and how I can obtain it.

edit: just asked on the server but nobody noticed anything weird

patch T
AMD Athlon 3000+
ATI Radeon 9800 pro 128 MB
1.5 Gig RAM
(for all other system specs I'd have to look).

We were having a good race too, another lap and I would have been on your arse.

Quote from Linsen :

....As far as I can tell, nothing unusual happens before I'm back to my desktop, just racing along really with not much traffic near me . I don't have an error report because I don't know where I could find one (never had problems with LFS before). So please tell me what info you need and how I can obtain it....

Let lfs run windowed and check what scawen wrote and need for a crash report:

http://www.lfsforum.net/showthread.php?p=109816#post109816

btw the same thing happend to me today (never ever had any LFS problems/crashes) but just got a "lfs exe problem message" and was back on desktop. Unfortunatly it was in the lag lap of a league race so I had no time to do an error report ;-)

Quote from Linsen :

So please tell me what info you need and how I can obtain it.

Please run Dr Watson (it's part of Windows and provided detailed crash reports).

Before you start LFS : Start... Run... drwatson

When LFS crashes, Dr Watson will create an error log / crash report. I think it will tell you where it saved the report. You can then attach the watson log here or send it to us by email. Thanks.

Quote from Bob Smith :

We were having a good race too, another lap and I would have been on your arse.

Yeah, you were probably a second faster per lap, even though I was on a role and on my way to a pb .

@Scawen: thx, I will try that next time I run LFS.

Quote from Scawen :

Please run Dr Watson (it's part of Windows and provided detailed crash reports).

Before you start LFS : Start... Run... drwatson

When LFS crashes, Dr Watson will create an error log / crash report. I think it will tell you where it saved the report. You can then attach the watson log here or send it to us by email. Thanks.

Just to confirm/annul my doubts, would this produce the same info/file I sent to you yesterday? Or was the file I sent different/incomplete? (excluding the 6.5 megs of nonrelated program crashes I pruned...)

Quote from Krane :

Just to confirm/annul my doubts, would this produce the same info/file I sent to you yesterday? Or was the file I sent different/incomplete? (excluding the 6.5 megs of nonrelated program crashes I pruned...)

No Krane - your one is fixed in T2. Your logs helped me to track it down.

It was the one that could happen when you leave a multiplayer game - same as the report on the other thread in fact (i'll paste a link) though the crash was in a very slightly different place - it was due to the same problem.

http://www.lfsforum.net/showthread.php?t=6938

I guess I was bit vague... of course the info in the file would be different, I meant different as in quality and quantity.

My question is, does your way, starting watson, waiting/making program crash contra experiencing a program crash and after it going to ?:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log & user.dmp.

Would you find the same (quality & quantity) info from either way?

Ah... I misunderstood your question at first.

Well, all I know is in both cases (how you did it, and what i stated above) I would see the exact place in the code, and I get some information about the processor state, and also the call stack which gives me some information about which functions called the function which crashed.

So, I didn't need more info than you gave. Actually, I only needed the drwtsn32.log - i didn't need to look at the system information you also provided.