CTD after exiting a race

Discussion in 'Bug Reports' started by Rony1984, Sep 20, 2014.

  1. Rony1984

    Rony1984 Registered

    Joined:
    May 10, 2012
    Messages:
    500
    Likes Received:
    28
    Hi guys,

    Build 860

    I hoped for this issue to be permanently solved, but it seems to keep on buggering me. Exited a 10 lap offline race with a full field of AI at Malaysia, driving the c6. No true CTD as the screen froze and I had to Ctrl+Alt+delete to get back to the desktop. Here an event log:

    Faulting application name: rFactor2.exe, version: 1.8.6.0, time stamp: 0x54170bce
    Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c4102
    Faulting process id: 0xed8
    Faulting application start time: 0x01cfd4a1dde81d38
    Faulting application path: E:\rFactor2\Bin64\rFactor2.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 4b3dc0dd-4099-11e4-a414-ac4f8bba2d6d

    Cheers,

    Roland
     
    Last edited by a moderator: Sep 20, 2014
  2. Rony1984

    Rony1984 Registered

    Joined:
    May 10, 2012
    Messages:
    500
    Likes Received:
    28
    Another CTD after a couple of laps into the race. The duration of a race/event is the only clue I have to what's causing these CTD's, as they always appear after exiting and having driven a bigger number of laps.

    Faulting application name: rFactor2.exe, version: 1.8.6.0, time stamp: 0x54170bce
    Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c4102
    Faulting process id: 0xf2c
    Faulting application start time: 0x01cfdd99c0f0ea19
    Faulting application path: E:\rFactor2\Bin64\rFactor2.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: dd30900f-4990-11e4-b753-8591382fc16a

    Greets,

    R
     
  3. Rony1984

    Rony1984 Registered

    Joined:
    May 10, 2012
    Messages:
    500
    Likes Received:
    28
    and another one...

    Faulting application name: rFactor2.exe, version: 1.8.6.0, time stamp: 0x54170bce
    Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c4102
    Faulting process id: 0x5c8
    Faulting application start time: 0x01cfdda01666793d
    Faulting application path: E:\rFactor2\Bin64\rFactor2.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: e339f887-4997-11e4-b753-8591382fc16a
     
  4. Rony1984

    Rony1984 Registered

    Joined:
    May 10, 2012
    Messages:
    500
    Likes Received:
    28
    and another one, this time after exiting a MP race.

    Faulting application name: rFactor2.exe, version: 1.8.6.0, time stamp: 0x54170bce
    Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c4102
    Faulting process id: 0x129c
    Faulting application start time: 0x01cfe4b3c8d10dd0
    Faulting application path: E:\rFactor2\Bin64\rFactor2.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 01e07cc8-50b0-11e4-9943-e34d4c8f1a6a

    The funny thing is that when I looked in the event-viewer, I saw this error, which seemed to have happend prior to me entering that race(time stamp 19:50 for this one and 21:02 for the CTD) and was unnoticable in-game. It's the first time I saw this error, and it was not there with previous CTD's:

    Activation context generation failed for "e:\rFactor2\Support\Tools\MAS2.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.

    Would anyone know what exactly this means?

    Greets,

    R.
     
  5. Rony1984

    Rony1984 Registered

    Joined:
    May 10, 2012
    Messages:
    500
    Likes Received:
    28
    another one, first time for me not when exiting a weekend, but when trying to enter the track during a MP practice.

    Faulting application name: rFactor2.exe, version: 1.8.6.0, time stamp: 0x54170bce
    Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c4102
    Faulting process id: 0x808
    Faulting application start time: 0x01cfe53d77d6000e
    Faulting application path: E:\rFactor2\Bin64\rFactor2.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: b62b3d27-5135-11e4-9e29-ed9855f43c6a
     
  6. Rony1984

    Rony1984 Registered

    Joined:
    May 10, 2012
    Messages:
    500
    Likes Received:
    28
    Faulting application name: rFactor2.exe, version: 1.8.6.0, time stamp: 0x54170bce
    Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
    Exception code: 0xc0000005
    Fault offset: 0x0000000000053290
    Faulting process id: 0xabc
    Faulting application start time: 0x01cfe553fd7d9196
    Faulting application path: E:\rFactor2\Bin64\rFactor2.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 1cf906a6-5148-11e4-8bc2-af10c8c255c1
     
  7. Rony1984

    Rony1984 Registered

    Joined:
    May 10, 2012
    Messages:
    500
    Likes Received:
    28
    Faulting application name: rFactor2.exe, version: 1.8.6.0, time stamp: 0x54170bce
    Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c4102
    Faulting process id: 0x510
    Faulting application start time: 0x01cfe55520e8514d
    Faulting application path: E:\rFactor2\Bin64\rFactor2.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 8d2cd5fd-5151-11e4-8bc2-af10c8c255c1


    this is getting frustrating...
     
  8. F1Fan07

    F1Fan07 Member

    Joined:
    Jan 11, 2012
    Messages:
    627
    Likes Received:
    46
    I get those all the time in rF1 then they go away for a while then they come back. I never could find the cause. I've given up caring about that error as it doesn't seem to affect the sim.
     

Share This Page