The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    MS Flight Sim X crash on Vista 64/M570RU

    Discussion in 'Gaming (Software and Graphics Cards)' started by Mumble Man, Feb 6, 2008.

  1. Mumble Man

    Mumble Man Notebook Geek

    Reputations:
    0
    Messages:
    92
    Likes Received:
    0
    Trophy Points:
    15
    Hey everyone,
    I'm having troubles with MS FSX crashing, and I'm afraid it's a symptom of a bigger problem. Here's what happens: I start up FSX, run it fine for awhile at high settings (I've tried low too, that doesn't seem to be the issue) and then crashes to desktop. I then get an error message. I had installed new drivers on my video card, but they caused a blue screen (when the sim crashed) and I've reverted. I've gotten a few, but here are the last two I got (simultaneously):

    #1
    Problem signature:
    Problem Event Name: BEX
    Application Name: fsx.exe
    Application Version: 10.0.61355.0
    Application Timestamp: 4643ee0a
    Fault Module Name: unknown
    Fault Module Version: 0.0.0.0
    Fault Module Timestamp: 00000000
    Exception Offset: 0ddacba4
    Exception Code: c0000005
    Exception Data: 00000008
    OS Version: 6.0.6000.2.0.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    LCID: 1033

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

    #2
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: svchost.exe_SysMain
    Application Version: 6.0.6000.16386
    Application Timestamp: 4549b5f5
    Fault Module Name: sysmain.dll
    Fault Module Version: 6.0.6000.16551
    Fault Module Timestamp: 46d4ef44
    Exception Code: c0000005
    Exception Offset: 0000000000017e13
    OS Version: 6.0.6000.2.0.0.768.3
    Locale ID: 1033
    Additional Information 1: 5b06
    Additional Information 2: 3ab7c7209a3192146aee3c491587ed94
    Additional Information 3: 63e9
    Additional Information 4: 7bf546c26b7932bd793f440df607cc2f

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

    I formatted my HD and reinstalled Vista 64 and reinstalled the drivers for everything. The vents are clear.I've tried three sets of video drivers, the ones I'm running now seem to prevent blue screen of death in addition to the CTD I'm getting.

    The only hint I've gotten so far from searching the internet for several days is that video cashing/shading (excuse me if I got the terms wrong) may have caused the problem, and I might want to disable them. I'm worried about performance if I do, and besides that, I don't know how I would go about doing that.

    Here come the specs:
    M570RU
    2ghz Dual Core T7300
    7950 GTX
    2 GB Ram
    All stock drivers

    Thanks a ton, in the past NR guys have been the most helpful I've found. I hope that I can get this problem solved with your help. Thanks again...
     
  2. Mumble Man

    Mumble Man Notebook Geek

    Reputations:
    0
    Messages:
    92
    Likes Received:
    0
    Trophy Points:
    15
    So I think I've found the solution; two guys having exactly the same problem. Unfortunately, I don't really know how to implement the solution. The link is below and the quote is the relevant reply. Note that I am not overclocking.

    Here
     
  3. Mumble Man

    Mumble Man Notebook Geek

    Reputations:
    0
    Messages:
    92
    Likes Received:
    0
    Trophy Points:
    15
    Turns out one of my sticks of ram crapped out on me. Memtest86 caught that there was an error, and I removed one stick, ran it, then the other, and ran it. Only one detected errors. When I replaced the broken stick, the game was fixed.