Crash Address Important! [Archive]

View Full Version : Crash Address Important!

Gunn

6th November 2006, 14:38

If your software crashes you can provide valuable feedback. Please record the crash address information to help Scawen pinpoint the problem. You might see an error window appear with crash information...

... that window is a great opportunity, because if you click the blue button "view more info" then "view technical info" you are given a crash address. I can often use that address to work out find the exact line of code that caused the crash.

It's a hexadecimal number - a load of zeros followed by 6 digits (numbers and letters A to F) - that is the crash address that I need. Please make sure you report the crash address if you ever get a crash.

Please, if you use the test patches then act like a tester: provide feedback about crashes and include the crash address or other error details. This can save Scawen a lot of time and effort!

George Kuyumji

7th November 2006, 11:11

Where are crash reports saved?

Eleanor SpeedGT

7th November 2006, 12:41

Where are crash reports saved?

When it crashes, then there should appear one window about error report or something, there should be some button (or something) to show information about that crash. Hope you find it.

Hyperactive

7th November 2006, 13:14

Where are crash reports saved?

In some cases you can find the addresses and stuff here:
Start -> Programs -> accesories -> System tools -> system information
The program starts. Choose software environment on the "folder tree" on the left and click Windows error reporting. Now you should have a list of windows errors in front of you.

Note: I'm using finnish windows XP so the translations are not probably precise :)

fujiwara

7th November 2006, 15:14

Try looking for minidump files in c:\windows\minidump for files like
minixxxxxxxx.dmp (the xxxx are the date of the created dump)
and for sysdata.xml files, usually in Documents and Settings\User\Local Def...\Temp

Flame CZE

29th September 2008, 19:11

A crash caused by quitting list of hosts

Flame CZE

4th December 2008, 21:17

A crash caused by selecting one lesson... LFS just freezed. It happened to me first time.

Scawen

5th December 2008, 00:17

The crash address is not inside the LFS exe so unfortunately I can't get anything from this one.

Can you reproduce the bug? And if so, which lesson was it that you selected?

Flame CZE

5th December 2008, 06:28

Ah ok.

I clicked at Chicane course - FBM and LFS freezed and then it crashed.
But it probably was rare case that it happened - it never happened before.

dawesdust_12

13th December 2008, 19:58

Scawen, I just had LFS crash on me. Before this I duplicated a setup for the XRG, jacked it up to max brake force and added ABS to it. Crash details are as follow:

Problem Event Name: APPCRASH
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 4943e997
Fault Module Name: d3d8.dll
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bcbf
Exception Code: c0000005
Exception Offset: 00045bd7
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
Additional Information 1: eb67
Additional Information 2: e67445a67aa3c06fb52c4c1d1e07154f
Additional Information 3: dff1
Additional Information 4: a4af7b53c316c648cb0063ba984e35a7

Hope this helps?

dougie-lampkin

13th December 2008, 20:02

Bump - LFS just crashed for me for no apparent reason. I was testing out the XFG's ABS setting, cruising up BL1 straight and locking the brakes. Just before T1, "LFS.exe has stopped working". Weird thing is, my FFB is still pulling to the left, as it was when LFS crashed. I'm running Vista, and I'm not sure where to get error information, but this is what comes up when you click "Problem details" :shrug:

Problem signature:
Problem Event Name: APPCRASH
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 4943e997
Fault Module Name: d3d8.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a65b
Exception Code: c0000005
Exception Offset: 00045bf7
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 6153
Additional Information 1: 64ea
Additional Information 2: cce9f653dd0f8eec446de52154d2f82d
Additional Information 3: bc8e
Additional Information 4: a8695c495b6422110fd841b26f6810d9

Hope that has everything needed, I don't know where else to get further crash info :shy:

E: Exact same thing as Dustin, oh wow :D

dawesdust_12

13th December 2008, 20:16

Only difference I can see is I'm running Vista SP0, and you're running SP1. Also different memory addresses, but the same thing crashing (DirectX8 DLL).

dougie-lampkin

13th December 2008, 22:20

Just got the exact same error on leaving FE6R pits in a LX4. It's happened a few times here, I thought it was due to the copious amounts of AI I was using :shy: No AI this time though...

It works most of the time, and continues to work with no problems. But leaving the pits the odd time, it crashes for some reason :shrug:

Scawen

14th December 2008, 09:57

Thanks for the crash report. Unfortunately the information is not enough to help me locate the problem - all I know from that is that something has gone wrong is some function call to DirectX.

I really need a call stack, so I know which part of LFS called DirectX. Is Dr Watson included with Vista?

Try : Start... Run... drwatson

Then you should get a more detailed crash report if there is a crash, hopefully with a call stack included.

Alternatively, any reliable way to reproduce the bug would also be a solution, maybe I could catch it in the debugger then.

Which track were you on, which car were you driving, which view were you using, were there any other cars on the track, AI or multiplayer, which screen overlays were switched on?

mtbdescender

14th December 2008, 21:08

I have a crash with Z5. I start the game, choose hotlap, press ready and drive a few seconds, press "1" and watch the replay a few seconds, press esc + exit and press ready to start driving again, and get this crash:

Nombre del evento de problema: APPCRASH
Nombre de la aplicación: LFS.exe
Versión de la aplicación: 0.0.0.0
Marca de tiempo de la aplicación: 49451a54
Nombre del módulo con errores: d3d8.dll
Versión del módulo con errores: 6.0.6001.18000
Marca de tiempo del módulo con errores: 4791a65b
Código de excepción: c0000005
Desplazamiento de excepción: 00045bf7
Versión del sistema operativo: 6.0.6001.2.1.0.768.3
Id. de configuración regional: 3082
Información adicional 1: 64ea
Información adicional 2: cce9f653dd0f8eec446de52154d2f82d
Información adicional 3: bc8e
Información adicional 4: a8695c495b6422110fd841b26f6810d9
This only occurs at Kyoto Ring GP Long with all cars.

My system:

Vista X64 SP1
Intel E6300
Asus P5B Mobo
Nvidia 8800GT drivers 180.48

I don't know how to obtain a call stack, sorry.

heson

16th December 2008, 13:07

I have a crash with Z5. I start the game, choose hotlap, press ready and drive a few seconds, press "1" and watch the replay a few seconds, press esc + exit and press ready to start driving again, and get this crash:
I can also reproduce, does the "send a bugreport report data help?"

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="LFS.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="AnalyzeForSpeed.exe" SIZE="196608" CHECKSUM="0xA69BE1B4" BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1" PRODUCT_VERSION="1.0" FILE_DESCRIPTION="AnalyzeForSpeed" COMPANY_NAME="Bullzode Productions" PRODUCT_NAME="AnalyzeForSpeed" FILE_VERSION="1.0" ORIGINAL_FILENAME="AnalyzeForSpeed.exe" INTERNAL_NAME="AnalyzeForSpeed.exe" LEGAL_COPYRIGHT="(c) Bulldoze Prodictions. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1" UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="03/02/2005 21:52:39" UPTO_LINK_DATE="03/02/2005 21:52:39" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="LFS.exe" SIZE="1843200" CHECKSUM="0x9643A6E9" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="12/14/2008 14:38:12" UPTO_LINK_DATE="12/14/2008 14:38:12" />
<MATCHING_FILE NAME="LFS_PATCH_X30_TO_X31.exe" SIZE="1173219" CHECKSUM="0x7185E246" BIN_FILE_VERSION="4.42.0.0" BIN_PRODUCT_VERSION="4.42.0.0" PRODUCT_VERSION="4.42" FILE_DESCRIPTION="7z SFX" COMPANY_NAME="Igor Pavlov" PRODUCT_NAME="7-Zip" FILE_VERSION="4.42" ORIGINAL_FILENAME="7z.sfx.exe" INTERNAL_NAME="7z.sfx" LEGAL_COPYRIGHT="Copyright (c) 1999-2006 Igor Pavlov" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.42.0.0" UPTO_BIN_PRODUCT_VERSION="4.42.0.0" LINK_DATE="05/14/2006 04:24:40" UPTO_LINK_DATE="05/14/2006 04:24:40" />
<MATCHING_FILE NAME="LFS_PATCH_X_TO_X30.exe" SIZE="67132539" CHECKSUM="0x7185E246" BIN_FILE_VERSION="4.42.0.0" BIN_PRODUCT_VERSION="4.42.0.0" PRODUCT_VERSION="4.42" FILE_DESCRIPTION="7z SFX" COMPANY_NAME="Igor Pavlov" PRODUCT_NAME="7-Zip" FILE_VERSION="4.42" ORIGINAL_FILENAME="7z.sfx.exe" INTERNAL_NAME="7z.sfx" LEGAL_COPYRIGHT="Copyright (c) 1999-2006 Igor Pavlov" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.42.0.0" UPTO_BIN_PRODUCT_VERSION="4.42.0.0" LINK_DATE="05/14/2006 04:24:40" UPTO_LINK_DATE="05/14/2006 04:24:40" />
<MATCHING_FILE NAME="LFS_PATCH_Y_TO_Y24.exe" SIZE="5112834" CHECKSUM="0x7185E246" BIN_FILE_VERSION="4.42.0.0" BIN_PRODUCT_VERSION="4.42.0.0" PRODUCT_VERSION="4.42" FILE_DESCRIPTION="7z SFX" COMPANY_NAME="Igor Pavlov" PRODUCT_NAME="7-Zip" FILE_VERSION="4.42" ORIGINAL_FILENAME="7z.sfx.exe" INTERNAL_NAME="7z.sfx" LEGAL_COPYRIGHT="Copyright (c) 1999-2006 Igor Pavlov" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.42.0.0" UPTO_BIN_PRODUCT_VERSION="4.42.0.0" LINK_DATE="05/14/2006 04:24:40" UPTO_LINK_DATE="05/14/2006 04:24:40" />
<MATCHING_FILE NAME="LFS_PATCH_Z_TO_Z5.exe" SIZE="1688156" CHECKSUM="0x7185E246" BIN_FILE_VERSION="4.42.0.0" BIN_PRODUCT_VERSION="4.42.0.0" PRODUCT_VERSION="4.42" FILE_DESCRIPTION="7z SFX" COMPANY_NAME="Igor Pavlov" PRODUCT_NAME="7-Zip" FILE_VERSION="4.42" ORIGINAL_FILENAME="7z.sfx.exe" INTERNAL_NAME="7z.sfx" LEGAL_COPYRIGHT="Copyright (c) 1999-2006 Igor Pavlov" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.42.0.0" UPTO_BIN_PRODUCT_VERSION="4.42.0.0" LINK_DATE="05/14/2006 04:24:40" UPTO_LINK_DATE="05/14/2006 04:24:40" />
<MATCHING_FILE NAME="lfs_restart.exe" SIZE="45056" CHECKSUM="0xDE1D8EB4" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="12/21/2006 15:23:59" UPTO_LINK_DATE="12/21/2006 15:23:59" />
</EXE>
<EXE NAME="d3d8.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="d3d8.dll" SIZE="1179648" CHECKSUM="0xBF9F7FE2" BIN_FILE_VERSION="5.3.2600.5512" BIN_PRODUCT_VERSION="5.3.2600.5512" PRODUCT_VERSION="5.03.2600.5512" FILE_DESCRIPTION="Microsoft Direct3D" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.03.2600.5512 (xpsp.080413-0845)" ORIGINAL_FILENAME="D3D8.dll" INTERNAL_NAME="D3D8.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1213A1" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.3.2600.5512" UPTO_BIN_PRODUCT_VERSION="5.3.2600.5512" LINK_DATE="04/14/2008 00:09:12" UPTO_LINK_DATE="04/14/2008 00:09:12" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="989696" CHECKSUM="0x7D737C09" BIN_FILE_VERSION="5.1.2600.5512" BIN_PRODUCT_VERSION="5.1.2600.5512" PRODUCT_VERSION="5.1.2600.5512" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5512 (xpsp.080413-2111)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF44A2" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5512" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5512" LINK_DATE="04/14/2008 00:11:24" UPTO_LINK_DATE="04/14/2008 00:11:24" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

DR watson says no faults detected. (?) Have i not configured it correctly?

From event viewer, two carshes with diffrent address:
Faulting application lfs.exe, version 0.0.0.0, faulting module d3d8.dll, version 5.3.2600.5512, fault address 0x0003ae72.
Faulting application lfs.exe, version 0.0.0.0, faulting module d3d8.dll, version 5.3.2600.5512, fault address 0x0003ac11.

Question: What (free) debugger can I install (to generate a call stack) that does not interfere with securom games I must play daily (GTA IV). Ollydbg?

System:
E6600 core2duo
Asus p5w dh deluxe mobo
asus nvidia 8800gts 640mb
win xp sp3

heson

16th December 2008, 13:32

Ollydbg screenie, Im too rusty at this, please advice.

With ollybg running it took several retries to get the crash.

Velociround

16th December 2008, 23:32

I have a crash with Z5. I start the game, choose hotlap, press ready and drive a few seconds, press "1" and watch the replay a few seconds, press esc + exit and press ready to start driving again, and get this crash

I don't know how to obtain a call stack, sorry.

I was able to reproduce this crash doing the same thing you did but just once. When the game crashed I had to ctrl + alt + del and close it otherwise I wouldn't be able to see the desktop and
When I tried to reproduce it on a second time I had a error message when saving the replay (pressing 1):
Could not rename SPR. Access denied
pressed it again, and then got another error
Replay was not being recorded
I didn't try for a third time, but I wasn't able to crash it on my second attempt.

Dr Watson said there were no problems here too. (although I opened it after the crash occurred :scratchch )

XP Home x32 SP3
Pentium D 820 2.8Ghz
nVidia 8600GT drivers 180.84

Flame CZE

24th December 2008, 11:48

Next crash address, I quit list of hosts

edit: oh, it seems to be the same as the address I posted before in this thread...

Gil07

27th December 2008, 13:30

After I Shift-S'ed out of hotlapping, in windowed mode and clicked on another window:

Problem Event Name: APPCRASH
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 494e9ccf
Fault Module Name: d3d8.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a65b
Exception Code: c0000005
Exception Offset: 0004c952
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2070
Additional Information 1: 64ea
Additional Information 2: cce9f653dd0f8eec446de52154d2f82d
Additional Information 3: 8dc8
Additional Information 4: 0a5bb3b56cc694b98e1f4a3a36903eec

RaceUK

5th January 2009, 15:01

Problem signature:
Problem Event Name: APPCRASH
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 4958fd75
Fault Module Name: StackHash_64ea
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 8a0c8d24
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057
Additional Information 1: 64ea
Additional Information 2: cce9f653dd0f8eec446de52154d2f82d
Additional Information 3: 8dc8
Additional Information 4: 0a5bb3b56cc694b98e1f4a3a36903eec

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Thats the report from my most recent crash 2 minutes before this post

xaotik

21st January 2009, 14:08

Here's an odd one - resumed the system from S3 mode and LFS.exe crashes on start. I tried a few other D3D games and OpenGL apps, including the CMX Viewer, and they start-up just fine. I'm assuming that if I restart the PC it'll be ok - but it's obviously something that LFS is doing when it's initing that makes it crash currently.

It consistently comes up with:
Code: 0xc0000005
Address: 0x000000000046b082

I've attached a memory dump of it as well.

EDIT: This is with Z10 btw, but I don't think it's a test patch issue.

dawesdust_12

21st January 2009, 20:23

xaotik, I've had the same bug before with my Laptop resuming it from a sleeped state, and it's happened with various versions of LFS and the Viewer. A restart DOES cure it in my experience. However I don't have a crash dump relating to it as it's very rare and only happened a relatively long time ago. Other games do launch too without flaw.

amp88

17th February 2009, 13:25

http://www.lfsforum.net/showthread.php?p=1076608#post1076608

pearcy_2k7

17th February 2009, 15:21

Everytime i search the list of hosts, then whilst it is still searching, i press the "?" on one of the hosts it won't load and just freezes for about 30secs, then takes a couple of tries to get the host list back up again.

Hope this is the right place.

Flame CZE

17th February 2009, 15:40

henrico-20-

24th February 2009, 20:08

My video card crashed sathurday the 14th.

i was training online with my team on SO sprint with RAC/FZ5. at the moment i wanted to quit LFS my videocard started to do weird, i only could see an coloured snow screen. even after a few times restarting and also after a day. i have Z10 installed.

it was an ATI RADEON 9600 256MB DDR1 AGP.

i dont want a refund for this. because it wassnt verry expencive ( 60 euro's ) and it was already 6 years old. 3rd reason is that i think scawen has enough on his mind with the new patch!

i hope you guys can do something with this information.

good luck!

hendrik.

dougie-lampkin

24th February 2009, 20:46

It's a 6 year old card, what do you expect TBH :shrug: LFS didn't cause it, it's just an old card.

Marco1

24th February 2009, 20:51

It's a 6 year old card, what do you expect TBH :shrug: LFS didn't cause it, it's just an old card.

my lfs runs whit my nforce ti4200 at high settings ^^

DarkTimes

24th February 2009, 21:47

my lfs runs whit my nforce ti4200 at high settings ^^
I think he meant that's why the card burnt out, cause it was really oldy. Obviously one of the best things about LFS has always been that works well on crappy hardware, because it has been so lovingly built.

Plus, you know, the EULA says the devs ain't libel for any damages to hardware.

dougie-lampkin

24th February 2009, 22:13

I don't mean there's anything wrong with having an old card (Hell, my last card was the 9800 PRO :shrug:), but a card that old can't be blamed for giving up the ghost. (Having said that, my 9800 is still going strong after 6 and a half years :schwitz: As in, Crysis strong :D)

Trekkerfahrer

24th February 2009, 23:48

henrico-20-

25th February 2009, 22:20

yeah 6 years is a long time :) same age as my computer! i hope it last a little longer though!! :schwitz:

Shadowww

26th February 2009, 11:02

my lfs runs whit my nforce ti4200 at high settings ^^Yeah, and on mine 9800GT even GTA IV can run on ultra settings.
10 fps, but yeah. :D

Monkay

28th February 2009, 08:15

It's happened more and more lately. Once wile I was playing, and Twice when i was exiting the game:

From Event Viewer:

- System

- Provider

[ Name] Application Error

- EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2009-02-28T07:57:09.000Z

EventRecordID 8997

Channel Application

Computer REMOVED-PC

Security
- EventData

LFS.exe

0.0.0.0

4958fd75

atiumdva.dll

7.14.10.211

496d6888

c0000005

00001545

218c

01c9995d77ceeda0

ATI 4870 512mb DDR5

:shrug:

ACCAkut

7th September 2009, 18:56

just crashed while on a drift server

Flame CZE

7th September 2009, 19:39

I think you should click on the extended report to see the address.

LSDBlackWolf

8th September 2009, 10:57

just crashed while on a drift server

It looks to me somebody was driving ilegal mod cars no? couldn't this be a cause?

Scawen

8th September 2009, 12:12

just crashed while on a drift serverThanks. You should click the button to see technical information, so you can report the crash address.

But anyway in this case it would not help, because the module where the crash occurred was ntdll.dll (not a line in LFS).

LFS may or may not have caused the crash.

Bombenleger

8th September 2009, 16:20

Just connected on a LFS server and it came up with this:

Ereignistyp: Fehler
Ereignisquelle: Application Error
Ereigniskategorie: Keine
Ereigniskennung: 1000
Datum: 08.09.2009
Zeit: 17:15:20
Benutzer: Nicht zutreffend
Computer: IDK-8XRUIHAZQ2F
Beschreibung:
Fehlgeschlagene Anwendung lfs.exe, Version 0.0.0.0, fehlgeschlagenes Modul ntdll.dll, Version 5.1.2600.3520, Fehleradresse 0x00011948.

Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.
Daten:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6c 66 73 ure lfs
0018: 2e 65 78 65 20 30 2e 30 .exe 0.0
0020: 2e 30 2e 30 20 69 6e 20 .0.0 in
0028: 6e 74 64 6c 6c 2e 64 6c ntdll.dl
0030: 6c 20 35 2e 31 2e 32 36 l 5.1.26
0038: 30 30 2e 33 35 32 30 20 00.3520
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 31 31 39 t 000119
0050: 34 38 0d 0a 48..

Luke.S

9th September 2009, 16:36

Translated to English for easier understanding

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 08.09.2009
Time: 17:15:20
User: Not applicable
Computer: IDK-8XRUIHAZQ2F
Description:
Lfs.exe Faulting application, version 0.0.0.0, faulting module ntdll.dll, version 5.1.2600.3520, fault address 0x00011948.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Dates:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6c 66 73 ure lfs
0018: 2e 65 78 65 20 30 2e 30. Exe 0.0
0020: 2e 30 2e 30 20 69 6e 20 .0.0 in
0028: 6e 74 64 6c 6c 2e 64 6c ntdll.dl
0030: 6c 20 35 2e 31 2e 32 36 l 5.1.26
0038: 30 30 2e 33 35 32 30 20 00.3520
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 31 31 39 t 000119
0050: 34 38 0d 0a 48th.

BIzO

9th September 2009, 16:45

Lfs.exe Faulting application, version 0.0.0.0, faulting module ntdll.dll, version 5.1.2600.3520, fault address 0x00011948.

But anyway in this case it would not help, because the module where the crash occurred was ntdll.dll (not a line in LFS).

A part from crash quote of Bombenleger can't help

NoYPiDRiFTER

10th September 2009, 04:39

Description of the ntdll.dll.

http://www.computerhope.com/issues/ch000960.htm

Flame CZE

23rd September 2009, 19:34

I got this error when my LFS was freezing and some errors appeared. But I think it is maybe my GPU, because it is a little bit hot now...

SF-Turdtron

17th May 2010, 23:56

Scawen

18th May 2010, 09:36

This happens all the time, Online/Offline, in any car, any server..I've uninstalled/installed again..installed on my external hard drive, It might be my download, but it was fine for about a week before I started getting problems.I can locate the function where the crash occurs but I can't see any obvious reason why it would crash there. It is in an object drawing function.

That limited description suggests to me that something is corrupted. Here are three possibilities that have all come up in the past.

1) Possibly a corrupted track file. If that is the case then it would only crash on one particular track.

2) A memory problem. I guess that this might give a different crash address on different tracks, or be quite unpredictable.

3) CPU problem - are you overclocking your CPU? If so then please try at normal speed. Sometimes overclocked computers run just until LFS has been running a while.

Any more information? Which tracks does it happen on / does it happen on the first lap / if not then around how long until it happens / does it happen every time without fail?

SF-Turdtron

18th May 2010, 12:08

It happens when: I do a lengthy burnout, I have a high speed crash, just when I'm driving around.

Any tracks, mainly SO though..I have not overclocked my CPU, but it could be my GPU as its quite old (GeForce 6200). Ive tested my RAM, and that 100% ok.

Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_qfe.080423-1303)
Language: English (Regional Setting: English)
System Manufacturer: American Megatrends Inc.
System Model: K7S41
BIOS: Version 1.00
Processor: AMD Athlon(tm) XP 3000+, MMX, 3DNow, ~2.2GHz
Memory: 1024MB RAM
Page File: 357MB used, 2104MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode

------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.

rockclan

18th May 2010, 17:53

Krane

18th May 2010, 19:40

Scawen, my LFS already 2 times had a hard crash out of nowhere.

I'm using Windows 7 32bit.

The problem is, it starts collecting the info what caused the crash, and then I can only select close program.

Could you please tell me where I can find the crash report, so that I can post the crash address here?

Control Panel->System and security->Action Center->Under maintenance, view reliability history. (or click start, type reliab... link to same thing should popup)
Left click on day
Double click on LFS or Right click on LFS->view technical details

rockclan

19th May 2010, 10:28

Control Panel->System and security->Action Center->Under maintenance, view reliability history. (or click start, type reliab... link to same thing should popup)
Left click on day
Double click on LFS or Right click on LFS->view technical details

Thank you very much! :)

Will look at that when back home.

hotmail

19th May 2010, 18:57

It happens when: I do a lengthy burnout, I have a high speed crash, just when I'm driving around.

Any tracks, mainly SO though..I have not overclocked my CPU, but it could be my GPU as its quite old (GeForce 6200). Ive tested my RAM, and that 100% ok.

are you getting every time the same crash address / crash report, if not can you upload 2 or 3 more ?

if you are getting sort of random crash address, just a note of out dated drivers:

some outdate driver:
bios: from 1/14/2004
a new one is over here:
http://www.asrock.com/mb/download.asp?Model=K7S41&o=BIOS

GPU: Nvidia 6200 (xp 32-bit)
http://www.nvidia.com/object/winxp_197.45_whql.html
( i know that yours is not too old, but you can allways give it ago)

i wasnt sure about the audio drivers but it looked like they where from 2004 too.

EDIT: As far as i can see does Bios V1.00 not fully support the AMD 3000+, you might want to start updating your bios

g7usl

27th April 2011, 23:58

Whiskey

28th April 2011, 12:46

Probably you just have to press Shift+Z (or was it Ctrl+Z ?) in LFS

NotAnIllusion

28th April 2011, 12:56

Since Z30, I have been experiencing sudden lack of control like you get running more than one monitor and your cursor is in the wrong monitor.

Everything is okay most of the time and by clicking on the screen it repairs the situation.
I tried the CTRL+C to clip the mouse to the screen and that didn't work so, I went out and bought a new mouse/keyboard today.

Later the same thing happened both in windowed view and a 'minimize' function happened during 'full screen'.

Any help would be appreciated please, I don't know if this is a bug but it didn't happen at all running under Z28. All multiplayer of course.

O.S. is XPpro. Card is Nvidea 8800gt 3800 dual core cpu. 2gig RAM
There are two possible reasons for this, and you must be in windowed mode for both:
- if not clipped to the window, the mouse cursor can go outside of the LFS window and then you get no mouse function in the game.
- if clipped to the window, upon reaching the edge of the window, will turn into a resize cursor instead and you get no mouse function in the game (very annoying).

It happens in Z28 in windowed mode too, including windowed-but-maximised. The best fix is to shift-f4 into the true full screen mode where the mouse cursor cannot misbehave. If you absolutely must run windowed, afaik there is no cure (please change window style to one without resize controls).

DarkKostas

28th April 2011, 16:38

Facebook had some problems getting the focus when you were receiving a new message. Make sure you have nothing to your background that involves with it. Also this is not a "Crash" so it shouldnt belong here, anyway!

Tango

30th April 2011, 19:43

just had first crash for over 12 months,running z31,e6600 cpu @ 3.2 (no probs for 4 years) nvidia 8800gt gfx and 6 gb mem

Problem Event Name: APPCRASH
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 4db995d7
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7ba58
Exception Code: c0000005
Exception Offset: 0002e39e
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 4709
Additional Information 2: 4709938665fa84e3ff99c8cbe11223bb
Additional Information 3: 14f9
Additional Information 4: 14f98f3b771a83e84953d1aa18bd29fe

Tango

Tango

7th May 2011, 22:17

another crash

Problem Event Name: APPCRASH
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 4dc422ff
Fault Module Name: WmJoyF32.dll
Fault Module Version: 5.9.129.0
Fault Module Timestamp: 4bd74ea1
Exception Code: c0000005
Exception Offset: 000089ee
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Tango

Tango

11th June 2011, 16:39

test patch 0.6a1

Problem Event Name: APPCRASH
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 4df23fa2
Fault Module Name: d3d8.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bd9a7
Exception Code: c0000005
Exception Offset: 0004bf62
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 4709
Additional Information 2: 4709938665fa84e3ff99c8cbe11223bb
Additional Information 3: f4c6
Additional Information 4: f4c66b313fb0ab14aef0709e1b1f1251

Tango

Scawen

11th June 2011, 17:25

Any way to reproduce it?

Was it in 0.6A1? While driving / entry screen / etc?

Problem is, that crash is not in the LFS module - it was in d3d8.dll. Might have been caused by LFS but I can't get any info from that address.

Scawen

12th June 2011, 11:07

Tango, I'm just wondering if your computer might be overheating or something like that. I guess it's not overclocked - if so then that would be the most obvious reason. Have you blown out the dust inside recently? I hope there isn't 4 years of dust in the fans and cooling fins. :)

It just seems unlikely that LFS can really cause crashes in all those funny places. Your last 3 posts are crash reports from 3 different Microsoft modules (called by LFS). I'm just supposing this might be a hardware problem rather than a MS or LFS bug.

E.Reiljans

13th June 2011, 21:57

Scawen, would it be possible to make LFS save dumps into subfolder of it's main folder, like some Steam games do (for example, Garry's Mod)? That would make finding dump files a lot easier for most people.

PoVo

16th June 2011, 21:52

0.6A3:

Wrote "/end" in my server when I was still on track. Don't send window appeared.

It didn't say the address, so I pressed debug, and Visual Studio came up with this address:
Unhandled exception at 0x004ef449 in LFS.exe: 0xC0000094: Integer division by zero.

Hope it helps.

Scawen

17th June 2011, 09:01

I can see the line where it happened, but I can't see why that value would be zero at that time, so could you give me some more details about exactly what was happening at the time?

- Were you running a server in your client LFS? So that was the only LFS running on your computer at the time? No dedicated server involved?
- Were you running in dedicated mode or just normal mode, where you can drive on the server?
- Which track and config was selected at the time?
- Was there a layout loaded?
- Any other cars on the track or was it just you?
- Could the track have been changing? Someone or InSim selecting a track?

To try and reproduce the bug I'd just like as much info as possible.

Thanks.

EDIT : I have added a simple line of code to check if this operation is safe, so that divide by zero can no longer happen. Let's hope that was the only possible consequence of the unexpected state your LFS was in at that point.

Flame CZE

26th June 2011, 21:10

My LFS crashed when I tried to load a layout in multiplayer. Track BL3. I was there with one player.

Problem Event Name: APPCRASH
Application Name: LFS.exe
Version: 0.0.0.0
Application Timestamp: 4dfb4e32
Fault Module Name: LFS.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4dfb4e32
Exception Code: c0000005
Exception Offset: 0015d573
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1029
Additional Information 1: 4709
Additional Information 2: 4709938665fa84e3ff99c8cbe11223bb
Additional Information 3: f4c6
Additional Information 4: f4c66b313fb0ab14aef0709e1b1f1251