Resolved Crash Code 0xC000001D

Discussion in 'Community Support' started by lenkradquaeler66, Jul 29, 2019.

  1. lenkradquaeler66

    lenkradquaeler66 New Member

    Joined:
    Oct 22, 2015
    Ratings:
    +0 / 0 / -0
    Anyone an idea? Have already checked files for errors. Tried with and then without VR and start options. Old scores deleted and restored. Deleted and reinstalled the Game, sorry, the Sim. Windows restarted, Steam restarted ...
    What else can I do?

    [​IMG]
     

    Attached Files:

  2. StepUnique

    StepUnique Active Member

    Joined:
    Feb 22, 2019
    Ratings:
    +27 / 0 / -0
    What system do you have 64 or 32bit? It could be that you're trying to launch the game in 64 bit, while your system only supports 32.
    Another possible scenario is that you don't have some MS Visual C++ packages installed, or maybe the ones you already have installed are corrupted. Try to delete all Visual C++ packages from your PC and then in Steam run the verification of the integrity of the game cache, RRRE should redownload all the needed stuff.
     
  3. lenkradquaeler66

    lenkradquaeler66 New Member

    Joined:
    Oct 22, 2015
    Ratings:
    +0 / 0 / -0
    Thanks for your reply. The System is Win10 64bit and so i start the game in 64bit too.
    The deleting of all C++ packages did not help, it is still the same as before. See the
    newest .dmp below.
     

    Attached Files:

  4. StepUnique

    StepUnique Active Member

    Joined:
    Feb 22, 2019
    Ratings:
    +27 / 0 / -0
    Here are some more things you could try:
    • Launch the game from RRRE folder as administrator;
    • Run command line (cmd.exe) as administrator and then use command "sfc /scannow" to see if there are any errors;
    • Try to install latest drivers for your GPU.
     
  5. StepUnique

    StepUnique Active Member

    Joined:
    Feb 22, 2019
    Ratings:
    +27 / 0 / -0
    After taking a look at your crash dump it really seems like the main issue is memory corruption caused by the driver of your GPU. So yes, either try to upgrade to a newer driver version or downgrade from your current one to see if it helps.
    Also posting the first crash dump (same as the 2nd) if anyone can be more precise on the issue:
    Code:
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Version 18362 MP (12 procs) Free x64
    Product: WinNt, suite: SingleUserTS
    18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Debug session time: Mon Jul 29 17:06:23.000 2019 (UTC + 2:00)
    System Uptime: not available
    Process Uptime: 0 days 0:00:11.000
    ................................................................
    ................................................................
    ..............................
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (2ea8.46d0): Illegal instruction - code c000001d (first/second chance not available)
    For analysis of this file, run !analyze -v
    ntdll!NtWaitForSingleObject+0x14:
    00007ff9`afbbc0e4 c3              ret
    0:000> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************
    
    *** WARNING: Unable to verify timestamp for gameoverlayrenderer64.dll
    *** WARNING: Unable to verify timestamp for RRRE64.exe
    *** WARNING: Unable to verify timestamp for protect.dll
    *** WARNING: Unable to verify timestamp for nvd3dumx.dll
    *** WARNING: Unable to verify timestamp for libcef.dll
    *** WARNING: Unable to verify timestamp for mss64.dll
    *** WARNING: Unable to verify timestamp for nvwgf2umx.dll
    
    KEY_VALUES_STRING: 1
    
        Key  : Timeline.Process.Start.DeltaSec
        Value: 11
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    Timeline: !analyze.Start
        Name: <blank>
        Time: 2019-07-30T05:44:46.986Z
        Diff: 52703986 mSec
    
    Timeline: Dump.Current
        Name: <blank>
        Time: 2019-07-29T15:06:23.0Z
        Diff: 0 mSec
    
    Timeline: Process.Start
        Name: <blank>
        Time: 2019-07-29T15:06:12.0Z
        Diff: 11000 mSec
    
    
    DUMP_CLASS: 2
    
    DUMP_QUALIFIER: 400
    
    CONTEXT:  (.ecxr)
    rax=00000b0000000000 rbx=0000000050d88120 rcx=0000000050d88128
    rdx=0000000050d88128 rsi=0000000000000000 rdi=0000000000000000
    rip=00007ff9a1fac8c2 rsp=00000000010feb90 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=0000000050d88128
    r11=00000000010febd8 r12=0000000011246301 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    d3d9!CBaseDevice::present+0x52:
    00007ff9`a1fac8c2 37              ???
    Resetting default scope
    
    FAULTING_IP:
    d3d9!CBaseDevice::present+52
    00007ff9`a1fac8c2 37              ???
    
    EXCEPTION_RECORD:  (.exr -1)
    ExceptionAddress: 00007ff9a1fac8c2 (d3d9!CBaseDevice::present+0x0000000000000052)
       ExceptionCode: c000001d (Illegal instruction)
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    DEFAULT_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
    
    PROCESS_NAME:  RRRE64.exe
    
    ERROR_CODE: (NTSTATUS) 0xc000001d - <Unable to get error code text>
    
    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - <Unable to get error code text>
    
    EXCEPTION_CODE_STR:  c000001d
    
    WATSON_BKT_PROCSTAMP:  4614489d
    
    WATSON_BKT_PROCVER:  9.18.944.0
    
    PROCESS_VER_PRODUCT:  Microsoft® DirectX for Windows®
    
    WATSON_BKT_MODULE:  d3d9.dll
    
    WATSON_BKT_MODSTAMP:  945f2ea5
    
    WATSON_BKT_MODOFFSET:  ac8c2
    
    WATSON_BKT_MODVER:  6.2.18362.267
    
    MODULE_VER_PRODUCT:  Microsoft® Windows® Operating System
    
    BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202
    
    MODLIST_WITH_TSCHKSUM_HASH:  e2726ad681976ae205ee2af420a803ea646baa41
    
    MODLIST_SHA1_HASH:  1b1041647d00ff33c338350b10c266f45ff55593
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !d3d9
        7ff9a1fac870-7ff9a1fac874  5 bytes - d3d9!CBaseDevice::present
       [ 4c 8b dc 49 89:e9 97 39 8a 0c ]
        7ff9a1fac8c0-7ff9a1fac8c4  5 bytes - d3d9!CBaseDevice::present+50 (+0x50)
       [ 24 70 4c 8b cf:e9 3b 37 fe bf ]
        7ff9a1fac910-7ff9a1fac914  5 bytes - d3d9!CBaseDevice::presentEx (+0x50)
       [ 4c 8b dc 49 89:e9 eb 36 fd bf ]
    15 errors : !d3d9 (7ff9a1fac870-7ff9a1fac914)
    
    DUMP_FLAGS:  0
    
    DUMP_TYPE:  2
    
    ANALYSIS_SESSION_HOST:  STPC
    
    ANALYSIS_SESSION_TIME:  07-30-2019 07:44:46.0986
    
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    
    THREAD_ATTRIBUTES:
    ADDITIONAL_DEBUG_TEXT:  Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]
    
    BUGCHECK_STR:  MEMORY_CORRUPTION_LARGE
    
    PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION
    
    PROBLEM_CLASSES:
    
        ID:     [0n209]
        Type:   [MEMORY_CORRUPTION]
        Class:  Primary
        Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
                BUCKET_ID
        Name:   Add
        Data:   Omit
        PID:    [0x2ea8]
        TID:    [0x46d0]
        Frame:  [Unspecified]
    
        ID:     [0n155]
        Type:   [LARGE]
        Class:  Addendum
        Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
                BUCKET_ID
        Name:   Add
        Data:   Omit
        PID:    [0x2ea8]
        TID:    [0x46d0]
        Frame:  [Unspecified]
    
    LAST_CONTROL_TRANSFER:  from 00007ff9286db992 to 00007ff9a1fac8c2
    
    STACK_TEXT:
    00000000`00000000 00000000`00000000 memory_corruption!d3d9+0x0
    
    
    FAILED_INSTRUCTION_ADDRESS:
    d3d9!CBaseDevice::present+52
    00007ff9`a1fac8c2 37              ???
    
    THREAD_SHA1_HASH_MOD_FUNC:  1ed9f5e64424c54ded9db5066c5b8f6f831e1d2f
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  a2b35f56811c2c5d69e2c2e7c4c5ed5708e0d049
    
    THREAD_SHA1_HASH_MOD:  7da7fbec386ce361a40d03d69a994bc4836f03e8
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  memory_corruption!d3d9
    
    FOLLOWUP_NAME:  MachineOwner
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    STACK_COMMAND:  ** Pseudo Context ** ManagedPseudo ** Value: 2b1db213920 ** ; kb
    
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_c000001d_memory_corruption!d3d9
    
    BUCKET_ID:  MEMORY_CORRUPTION_LARGE_BAD_IP_memory_corruption!d3d9
    
    FAILURE_EXCEPTION_CODE:  c000001d
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_IMAGE_NAME:  memory_corruption
    
    BUCKET_ID_IMAGE_STR:  memory_corruption
    
    MODULE_NAME: memory_corruption
    
    FAILURE_MODULE_NAME:  memory_corruption
    
    BUCKET_ID_MODULE_STR:  memory_corruption
    
    FAILURE_FUNCTION_NAME:  d3d9
    
    BUCKET_ID_FUNCTION_STR:  d3d9
    
    BUCKET_ID_OFFSET:  0
    
    BUCKET_ID_MODTIMEDATESTAMP:  0
    
    BUCKET_ID_MODCHECKSUM:  0
    
    BUCKET_ID_MODVER_STR:  0.0.0.0
    
    BUCKET_ID_PREFIX_STR:
    
    FAILURE_PROBLEM_CLASS:  MEMORY_CORRUPTION
    
    FAILURE_SYMBOL_NAME:  memory_corruption!d3d9
    
    WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/RRRE64.exe/9.18.944.0/4614489d/d3d9.dll/6.2.18362.267/945f2ea5/c000001d/000ac8c2.htm?Retriage=1
    
    TARGET_TIME:  2019-07-29T15:06:23.000Z
    
    OSBUILD:  18362
    
    OSSERVICEPACK:  86
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  256
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt SingleUserTS
    
    OS_LOCALE:
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  unknown_date
    
    BUILDDATESTAMP_STR:  190318-1202
    
    BUILDLAB_STR:  19h1_release
    
    BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202
    
    ANALYSIS_SESSION_ELAPSED_TIME:  3171
    
    ANALYSIS_SOURCE:  UM
    
    FAILURE_ID_HASH_STRING:  um:memory_corruption_large_c000001d_memory_corruption!d3d9
    
    FAILURE_ID_HASH:  {8f61dc76-f0c9-14e8-a713-36bde5798654}
    
    Followup:     MachineOwner
    ---------
    
     
    Last edited: Jul 30, 2019
  6. lenkradquaeler66

    lenkradquaeler66 New Member

    Joined:
    Oct 22, 2015
    Ratings:
    +0 / 0 / -0
    Ok... What can i say? One word: NVidia
    I went back from the newest Driver to 431.36 and it works. Thank you so much! I should have known better (NVidia).
    After all the tests i have 13 of the dump files. I will send the very first one. Should i go again to the newest driver?
     

    Attached Files:

  7. StepUnique

    StepUnique Active Member

    Joined:
    Feb 22, 2019
    Ratings:
    +27 / 0 / -0
    Just wait till they release a newer version and try to switch again to see if it works and for now you can stay on the 431.36.
    I doubt it will impact the GPU performance in any way.
     
  8. Paul Darke

    Paul Darke Moderator Beta tester

    Joined:
    Jan 29, 2015
    Ratings:
    +199 / 0 / -0
    @lenkradquaeler66 If this is fixed can you please change the "Problem" to "Resolved"?
     
  9. lenkradquaeler66

    lenkradquaeler66 New Member

    Joined:
    Oct 22, 2015
    Ratings:
    +0 / 0 / -0
    I will do so. Again, thank you so much for your help!
    Have a nice one
     
  10. lenkradquaeler66

    lenkradquaeler66 New Member

    Joined:
    Oct 22, 2015
    Ratings:
    +0 / 0 / -0
    Sorry Paul, i must be blind. How the heck can i do this. :flushed:
     
  11. Paul Darke

    Paul Darke Moderator Beta tester

    Joined:
    Jan 29, 2015
    Ratings:
    +199 / 0 / -0
    No problem I will fix it.
     
  12. lenkradquaeler66

    lenkradquaeler66 New Member

    Joined:
    Oct 22, 2015
    Ratings:
    +0 / 0 / -0
    Thank you too, this is embarrassing. How can i do it next time?
     
  13. Paul Darke

    Paul Darke Moderator Beta tester

    Joined:
    Jan 29, 2015
    Ratings:
    +199 / 0 / -0
    @lenkradquaeler66 Unfortunately I don't know how a normal user does it. I never had to before I became a moderator. Lol
     
    • Like Like x 1
  14. StepUnique

    StepUnique Active Member

    Joined:
    Feb 22, 2019
    Ratings:
    +27 / 0 / -0
    Normally, in the top right corner, right above your first message you will have the following option:

    [​IMG]

    Then in "Edit Title" menu you can set your post's prefix from "Problem" to "Resolved".
     

    Attached Files:

    • edt.png
      edt.png
      File size:
      4.1 KB
      Views:
      106
    • Like Like x 1
    • Informative Informative x 1
  15. lenkradquaeler66

    lenkradquaeler66 New Member

    Joined:
    Oct 22, 2015
    Ratings:
    +0 / 0 / -0
    As i said, i must be blind. There it is! Thanks for your help, again.
    Cheers
     
  16. Case

    Case Well-Known Member

    Joined:
    Apr 7, 2017
    Ratings:
    +98 / 0 / -0
    I have come upon this issue today as well. I haven't tried downgrading the nVidia driver yet, but two things I've found so far is that the 32bit client is apparently not affected...and that I can get the 64bit one start just fine if I disable the detection for this .exe in Afterburner. Interestingly enough, the 32bit client runs just fine with Afterburner active.

    (In fact, these two things are my general go-to tries whenever I encounter an issue with Raceroom. One of those usually works ;) )
     
    • Useful Useful x 1
  17. Ablaze

    Ablaze Well-Known Member

    Joined:
    Mar 16, 2018
    Ratings:
    +82 / 0 / -0
    Same here. Thanks for the workaround. :)
     
    • Like Like x 1