Sam & Max 3x05 does not start

edited September 2010 in Game Support
Hi there,

I just downloaded 3x05 but every time I click on "Launch Game", the monitor will turn black for a few seconds, then crash to the desktop with no error message.

Anyone have an idea?

TIA
SoWhy

PS: DxDiag file attached

Comments

  • DjNDBDjNDB Moderator
    edited August 2010
    Wow, that's a lot of partitions.
    On Which Partition did you install the Game?

    You could try disabling the second display before running the game.
  • edited August 2010
    Yeah, it's order and it works^^
    On J:\, just like all other TT Games previously. Never had any problems with the partitions but I changed Mainboard, CPU, graphics card and RAM between 3x04 and 3x05, so I guess it's rather one of those components. never had any problems with the two displays though^^
  • DjNDBDjNDB Moderator
    edited August 2010
    SoWhy wrote: »
    never had any problems with the two displays though^^

    I am suggesting it, because there have been issues with multiple displays and ATI cards in earlier episodes.
  • edited August 2010
    I tried it but no luck :-/
  • DjNDBDjNDB Moderator
    edited August 2010
    Do the earlier episodes still work?
  • edited August 2010
    Good idea, I hadn't actually tried. I had to reinstall Windows after the hardware upgrade (no surprise there) and I haven't played since then.
    I tried 3x02 and 3x04 just now, both crash with standard Windows crash-message (without the black screen prior to crashing, just immediately after clicking the game file). ..very strange indeed...
  • DjNDBDjNDB Moderator
    edited August 2010
    Okay, let's try to narrow it down. It's best if you keep your second display disabled for further tests.
    Did you run the DirectX updater?

    You should also try running the episodes during a clean boot.

    Booting clean in Windows XP:
    1. Click Start --> Run --> Type MSCONFIG --> Click OK
    2. On the General tab, choose Selective Startup
    3. Uncheck Process SYSTEM.INI file
    4. Uncheck Process WIN.INI file
    5. Uncheck Load Startup Items
    6. Click on the Services tab
    7. At the bottom, check Hide All Microsoft Services
    8. Uncheck all boxes in the window or click the button labeled Disable All
    6. Click OK
    7. Click Restart
    8. After reboot, run the game to see if it works.

    After performing the necessary steps, restore your system by doing the following:

    1. Click Start --> Run --> Type MSCONFIG--> Click OK
    2. On the General tab, choose Normal Startup
    3. Click OK
    4. Click YES, when asked to restart your computer

    Based on Will's post
  • edited August 2010
    Tried it, now it crashes either randomly or when I try to change graphics settings (e.g. windowed mode or higher resolution)
  • DjNDBDjNDB Moderator
    edited August 2010
    That's odd. Do other (Non-TTG) 3D Games work?

    Maybe your graphics driver is broken in some way.
    You could try completely uninstalling your ATI driver, rebooting and downloading and installing the latest one.
  • edited August 2010
    I just beat Mafia II, so I'd say yes ;-)

    I only installed this Windows five days ago, so I already have the latest drivers installed.
  • DjNDBDjNDB Moderator
    edited August 2010
    SoWhy wrote: »
    I only installed this Windows five days ago, so I already have the latest drivers installed.

    It was more about reinstalling the driver. You could also try the previous version.

    Earlier, did you mean you could actually start a game but it crashed at some later point?
  • edited August 2010
    DjNDB wrote: »
    It was more about reinstalling the driver. You could also try the previous version.

    Earlier, did you mean you could actually start a game but it crashed at some later point?

    Yes, when disabling all services and stuff but the crash occurs pretty soon. I'll try resintalling the drivers later, currently I don't want to restart my system.
    I did manage to run it on a Virtual Machine, so I can play it but I'd prefer it if it worked on my PC without it. ;-)
  • edited September 2010
    Reinstalled drivers, no luck
  • DjNDBDjNDB Moderator
    edited September 2010
    I am running out of reasonable ideas.
    One more thing you could try is starting the game while disconnected from the internet.

    Besides hat you could look for related error messages in the Windows event viewer.

    Looking for errors in the event viewer
    Take a look into the "application" part of windows "event viewer" after trying to start a game. Set a filter for "application errors" there to make it easier to find earlier attempts.
    If you find anything related to the game you can copy the details by right clicking on the entry.
  • edited September 2010
    btw, same problem with ToMI 1-5. Sam & Max Season 1 and 2 work fine.
  • edited September 2010
    Example entry, similar with ToMI:
    Faulting application sammax303.exe, version 2010.5.24.43307, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x000369da.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
  • DjNDBDjNDB Moderator
    edited September 2010
    SoWhy wrote: »
    Example entry, similar with ToMI:

    Can you copy the details, maybe of multiple events?
  • edited September 2010
    Faulting application monkeyisland101.exe, version 2009.7.6.29796, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00010a1b.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Faulting application monkeyisland104.exe, version 2009.10.29.36411, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00010717.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Unfortunately, Windows does only generate those reports if it crashes with a message. If it simply disappears, no entry is generated.
  • edited September 2010
    I generated a logfile using ProcessMonitor (i.e. monitoring what the application tries to do). It looks as if it tried, unsuccessfully, to access some DLLs and Keys. See here:
    https://spreadsheets.google.com/ccc?key=0AqWRjRP1NYjLdEttSXNVR3NIRWFOZ3Z4SFpSZVRqTHc&hl=en&authkey=CLOc9tQE
  • DjNDBDjNDB Moderator
    edited September 2010
    SoWhy wrote: »
    I generated a logfile using ProcessMonitor (i.e. monitoring what the application tries to do). It looks as if it tried, unsuccessfully, to access some DLLs and Keys. See here:
    https://spreadsheets.google.com/ccc?key=0AqWRjRP1NYjLdEttSXNVR3NIRWFOZ3Z4SFpSZVRqTHc&hl=en&authkey=CLOc9tQE

    You can compare that with what it shows in your VM when the game starts successfully. It will probably look similar. The last time I looked at a similar log there was a lot of probing like that too.

    With details I meant more detailed information from the event viewer. I just realized that it is different in Windows XP.

    Here's a Screenshot of the Button (marked in red) that copies detailed information for an event. Please post that from some Events.

    winxpeventviewerdetails.png
  • edited September 2010
    Event Type: Error
    Event Source: Application Error
    Event Category: None
    Event ID: 1000
    Date: 02.09.2010
    Time: 22:02:46
    User: N/A
    Computer: WUBTM
    Description:
    Faulting application monkeyisland101.exe, version 2009.7.6.29796, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00010a1b.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    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 6d 6f 6e ure mon
    0018: 6b 65 79 69 73 6c 61 6e keyislan
    0020: 64 31 30 31 2e 65 78 65 d101.exe
    0028: 20 32 30 30 39 2e 37 2e 2009.7.
    0030: 36 2e 32 39 37 39 36 20 6.29796
    0038: 69 6e 20 6e 74 64 6c 6c in ntdll
    0040: 2e 64 6c 6c 20 35 2e 31 .dll 5.1
    0048: 2e 32 36 30 30 2e 35 37 .2600.57
    0050: 35 35 20 61 74 20 6f 66 55 at of
    0058: 66 73 65 74 20 30 30 30 fset 000
    0060: 31 30 61 31 62 0d 0a 10a1b..
    Event Type: Error
    Event Source: Application Error
    Event Category: None
    Event ID: 1000
    Date: 02.09.2010
    Time: 21:42:41
    User: N/A
    Computer: WUBTM
    Description:
    Faulting application sammax303.exe, version 2010.5.24.43307, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x000369da.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    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 73 61 6d ure sam
    0018: 6d 61 78 33 30 33 2e 65 max303.e
    0020: 78 65 20 32 30 31 30 2e xe 2010.
    0028: 35 2e 32 34 2e 34 33 33 5.24.433
    0030: 30 37 20 69 6e 20 6e 74 07 in nt
    0038: 64 6c 6c 2e 64 6c 6c 20 dll.dll
    0040: 35 2e 31 2e 32 36 30 30 5.1.2600
    0048: 2e 35 37 35 35 20 61 74 .5755 at
    0050: 20 6f 66 66 73 65 74 20 offset
    0058: 30 30 30 33 36 39 64 61 000369da
    0060: 0d 0a ..

    Not really more info, is it?
  • DjNDBDjNDB Moderator
    edited September 2010
    SoWhy wrote: »
    Not really more info, is it?

    Sadly not. Did you contact support@telltalegames.com yet? This error might be beyond my scope.

    But there's some random ideas left.

    I would try updating all possible drivers (e.g. Mainboard and all other hardware).

    I would also try removing all non essential hardware (USB Devices, or
    your TV card).

    Since you installed new hardware, did you check if your memory runs properly?

    Testing your memory:
    In order to test your memory download http://www.memtest.org/ and make a bootable cd or disk. Start your system from that medium to run the memory test.

    It is probably enough to run it for one pass. Look at the lower table that looks like this after one pass is finished:
    Test Pass Errors
    ---- ---- ------
    Std     1      0
    

    If there are errors they are shown in red.
  • edited September 2010
    I did now, let's see if they have any other ideas.

    All drivers are up to date, I think, after all I just downloaded them a few days ago when I installed XP freshly.

    I'll try the rest of your ideas tomorrow, time to go to bed now^^
This discussion has been closed.