We are suffering from mass crashes again.
Out of a sudden it hits like 20 people within 2 minutes.

I was able to get a stracktrace:

Unhandled exception at 0x771fe29b in LFS.exe: 0xC0000005: Access violation writing location 0x000038ae.

ntdll.dll!RtlInitUnicodeString() + 0x1f3 bytes
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
> ntdll.dll!RtlFreeHeap() + 0x7e bytes
kernel32.dll!HeapFree() + 0x14 bytes
LFS.exe!00545cd3()
LFS.exe!00543b29()
LFS.exe!004c1b76()
LFS.exe!0042a26c()
LFS.exe!004ec271()
LFS.exe!004f1abd()
LFS.exe!0048c27b()
gdi32.dll!D3DKMTRender() + 0x15 bytes
d3d8.dll!Direct3DCreate8() + 0xd3ce bytes
d3d8.dll!Direct3DCreate8() + 0xde23 bytes
nvd3dum.dll!QueryOglResource() + 0xffab bytes
nvd3dum.dll!QueryOglResource() + 0x10d2b bytes
nvd3dum.dll!QueryOglResource() + 0x1b341 bytes
nvd3dum.dll!QueryOglResource() + 0xfcd0a bytes
nvd3dum.dll!QueryOglResource() + 0xfce01 bytes
nvd3dum.dll!QueryOglResource() + 0x680ab bytes
ntdll.dll!NtQueryPerformanceCounter() + 0x15 bytes
ntdll.dll!RtlQueryPerformanceFrequency() + 0x15 bytes
ntdll.dll!RtlImageNtHeader() + 0xb6a bytes
LFS.exe!0054aeec()
LFS.exe!0054571b()
kernel32.dll!BaseThreadInitThunk() + 0x12 bytes
ntdll.dll!RtlInitializeExceptionChain() + 0x63 bytes
ntdll.dll!RtlInitializeExceptionChain() + 0x36 bytes
LFS.exe!00730049()
LFS.exe!00730049()
LFS.exe!00720065()
LFS.exe!0069006e()
LFS.exe!00720065()
LFS.exe!00720065()
LFS.exe!0069006e()
LFS.exe!00730049()
LFS.exe!00730049()
LFS.exe!00720065()
LFS.exe!0069006e()
LFS.exe!0069006e()

I don't wanna be rude but where is the point in this
sub-forum if nobody cares about it?

Probably noone has a solution or nobody encountered a problem like that, so nobody can actually help...

Quote from chucknorris :

I don't wanna be rude but where is the point in this
sub-forum if nobody cares about it?

The devs do read this forum and they note the problems, maybe not right away, and maybe they don't always post, but they do look into the crashes.

Also it might be helpful if you explained what was happening at the time of the crash (what were you doing, what screen were you on, what did you do you think may have triggered the crash), so as to narrow down the problem.