🛈 Announcement
Greetings! Far Cry forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game.
  1. #1

    Steam version Far Cry 4 crashing at splash screen

    I bought the game after finishing Far Cry 5 and enjoying it. I hadn't played FC since the 1st/2nd one came out and bought FC4 and was about 30% through with FC4 when it refused to start any longer. I'm betting it is a driver issue as all my other games play ok. I've also tried stopping all services or SW.

    Experiments I've performed:

    1. verified local content
    2. Full uninstall and fresh reinstall
    3. Disabling any services/apps


    Error Message:
    [Windows Error Reporting]


    Time Type Details
    10/12/2018 5:33 PM Application Error Faulting application name: FarCry4.exe, version: 0.1.0.1, time stamp: 0x552190c2
Faulting module name: FC64.dll, version: 0.1.0.1, time stamp: 0x5521908b
Exception code: 0xc0000005
Fault offset: 0x00000000000016a1
Faulting process id: 0x3628
Faulting application start time: 0x01d46251b9fdac18
Faulting application path: E:\games\Steam\steamapps\common\Far Cry 4\bin\FarCry4.exe
Faulting module path: E:\games\Steam\steamapps\common\Far Cry 4\bin\FC64.dll
Report Id: 3af01901-7135-4288-b09a-d55631d5333a
Faulting package full name: 
Faulting package-relative application ID:



    [System Summary]

    Item Value
    OS Name Microsoft Windows 10 Pro
    Version 10.0.17134 Build 17134
    Other OS Description Not Available
    OS Manufacturer Microsoft Corporation
    System Name
    System Manufacturer ASUS
    System Model All Series
    System Type x64-based PC
    System SKU All
    Processor Intel(R) Xeon(R) CPU E5-2696 v4 @ 2.20GHz, 2199 Mhz, 22 Core(s), 44 Logical Processor(s)
    BIOS Version/Date American Megatrends Inc. 3801, 9/15/2017
    SMBIOS Version 3.0
    Embedded Controller Version 255.255
    BIOS Mode Legacy
    BaseBoard Manufacturer ASUSTeK COMPUTER INC.
    BaseBoard Model Not Available
    BaseBoard Name Base Board
    Platform Role Desktop
    Secure Boot State Unsupported
    PCR7 Configuration Binding Not Possible
    Windows Directory C:\WINDOWS
    System Directory C:\WINDOWS\system32
    Boot Device \Device\HarddiskVolume3
    Locale United States
    Hardware Abstraction Layer Version = "10.0.17134.285"

    Time Zone Central Daylight Time
    Installed Physical Memory (RAM) 32.0 GB
    Total Physical Memory 31.9 GB
    Available Physical Memory 24.7 GB
    Total Virtual Memory 36.7 GB
    Available Virtual Memory 26.5 GB
    Page File Space 4.75 GB
    Page File C:\pagefile.sys
    Kernel DMA Protection Off
    Virtualization-based security Not enabled
    Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
    Hyper-V - VM Monitor Mode Extensions Yes
    Hyper-V - Second Level Address Translation Extensions Yes
    Hyper-V - Virtualization Enabled in Firmware No
    Hyper-V - Data Execution Protection Yes

    [Display]

    Item Value
    Name NVIDIA GeForce GTX 1070
    PNP Device ID PCI\VEN_10DE&DEV_1B81&SUBSYS_85971043&REV_A1\4&FC7 F53B&0&0018
    Adapter Type GeForce GTX 1070, NVIDIA compatible
    Adapter Description NVIDIA GeForce GTX 1070
    Adapter RAM (1,048,576) bytes
    Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_ dispi.inf_amd64_54bd1f10ac116cd5\nvldumdx.dll,C:\W INDOWS\System32\DriverStore\FileRepository\nv_disp i.inf_amd64_54bd1f10ac116cd5\nvldumdx.dll,C:\WINDO WS\System32\DriverStore\FileRepository\nv_dispi.in f_amd64_54bd1f10ac116cd5\nvldumdx.dll,C:\WINDOWS\S ystem32\DriverStore\FileRepository\nv_dispi.inf_am d64_54bd1f10ac116cd5\nvldumdx.dll
    Driver Version 25.21.14.1616
    INF File oem17.inf (Section108 section)
    Color Planes Not Available
    Color Table Entries 4294967296
    Resolution 1920 x 1080 x 60 hertz
    Bits/Pixel 32
    Memory Address 0xFA000000-0xFB0FFFFF
    Memory Address 0xC0000000-0xD1FFFFFF
    Memory Address 0xD0000000-0xD1FFFFFF
    I/O Port 0x0000E000-0x0000EFFF
    IRQ Channel IRQ 40
    I/O Port 0x000003B0-0x000003BB
    I/O Port 0x000003C0-0x000003DF
    Memory Address 0xA0000-0xBFFFF
    Driver c:\windows\system32\driverstore\filerepository\nv_ dispi.inf_amd64_54bd1f10ac116cd5\nvlddmkm.sys (25.21.14.1616, 19.65 MB (20,605,496 bytes), 10/6/2018 4:47 PM)
     1 people found this helpful
    Share this post

  2. #2
    Anyone home?
    Share this post

  3. #3
    WID992007's Avatar Senior Member
    Join Date
    Sep 2007
    Posts
    2,280
    you sir possibly have an unsupported CPU ask Ubi Support

    XEON's are not supported ..your clock speed on that chip is 2.2 ghz with turbo boost only on a single core

    and it is in fact a server CPU ..so the game probably can not load properly

    see https://en.wikichip.org/wiki/intel/xeon_e5/e5-2696_v4

    The Xeon E5-2696 v4 is a 64-bit docosa-core x86 microprocessor introduced by Intel in 2016. This server MPU is designed for 2S environments. Operating at 2.2 GHz with a turbo boost frequency of 3.7 GHz for a single active core, this MPU has a TDP of 150 W and is manufactured on a 14 nm process (based on Broadwell).
     1 people found this helpful
    Share this post

  4. #4
    Hi WID992007,

    Thanks for the response! The part I have is one that was never sold to the public. I'll let you guess where I work. With that said. the game ran perfectly for a month or so before it started throwing exceptions each time at startup. The Asus board has full support for it and I've seen no issues on many games ranging from HL2 various mods such as CS1.6 - CSGo. Fallout 3/4, many flight sims, UT, pretty much all versions, BattleFront 1/2, Dirt 3/4, GTA 4/5, LFD 1/2, Payday variants, BF1/2, and many others which work fine. This is the only title I have that worked perfectly and then suddenly stopped.

    I do have all cores sync'd in the BIOS and am OC'ing to 2.8GHz on all cores, but have since dropped it back down to 2.2GHz doing further experiments SpeedStep/C-states disabled. These parts work perfectly in both a 2S as well as a 1S configuration. You'd be surprised what all we run on SRV/WS/DT parts. Being as I work in validation they do offer us parts from time to time at the completion of projects This has been about the craziest ones they have given us. I'm continuing to debug/experiment by further disabling stuff via the BIOS. I was really enjoying the game until it kicked the can.

    Thanks!
    Share this post

  5. #5

    Fixed!

    Clock speed had no bearing. Looks like the Uplay update seems to have magically fixed the issue. Sweet! I was suspecting an update broke it.
    Share this post

  6. #6

    Exact same issue now on 2 computers that both worked upto a month ago

    Same error on 2 Windows 10 device, one MSI gaming laptop and i7 970GTX workstation (played FC3, 4 and 5 game on it for 3 years now).

    FC3 and FC5 work fine, so not my hardware or OS.

    Did all the typical fixes and tests to no avail, stream or ubsoft broke something


    Here is the error text:

    Log Name: Application
    Source: Application Error
    Date: 4/11/2019 9:01:57 AM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: MSI
    Description:
    Faulting application name: FarCry4.exe, version: 0.1.0.1, time stamp: 0x5b348883
    Faulting module name: FC64.dll, version: 0.1.0.1, time stamp: 0x5c6150fe
    Exception code: 0xc0000005
    Fault offset: 0x000000000007d330
    Faulting process id: 0x262c
    Faulting application start time: 0x01d4f06f1fa03d0a
    Faulting application path: D:\Program Files\SteamLibrary\steamapps\common\Far Cry 4\bin\FarCry4.exe
    Faulting module path: D:\Program Files\SteamLibrary\steamapps\common\Far Cry 4\bin\FC64.dll
    Report Id: c2c7fb0f-0364-4105-944e-d91f1c65b2b1
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-04-11T14:01:57.731977000Z" />
    <EventRecordID>11250</EventRecordID>
    <Channel>Application</Channel>
    <Computer>MSI</Computer>
    <Security />
    </System>
    <EventData>
    <Data>FarCry4.exe</Data>
    <Data>0.1.0.1</Data>
    <Data>5b348883</Data>
    <Data>FC64.dll</Data>
    <Data>0.1.0.1</Data>
    <Data>5c6150fe</Data>
    <Data>c0000005</Data>
    <Data>000000000007d330</Data>
    <Data>262c</Data>
    <Data>01d4f06f1fa03d0a</Data>
    <Data>D:\Program Files\SteamLibrary\steamapps\common\Far Cry 4\bin\FarCry4.exe</Data>
    <Data>D:\Program Files\SteamLibrary\steamapps\common\Far Cry 4\bin\FC64.dll</Data>
    <Data>c2c7fb0f-0364-4105-944e-d91f1c65b2b1</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    </EventData>
    </Event>
    Share this post

  7. #7
    Steve64b's Avatar Senior Member
    Join Date
    Jul 2016
    Location
    http://steve.farcry.eu/
    Posts
    1,628
    Did you DELETE the files from the game, and then do a validation? I found that in Far Cry 5's latest Title Update 12, the patcher seems to think it had validated/fixed/updated some files, but instead corrupted the ones installed.So maybe uplay's update routine is messed up, possibly same for Steam's.

    Removing the game data files & downloading the latest version again should resolve it.
    Share this post

  8. #8
    UbiGabrinth's Avatar Ubisoft Support Staff
    Join Date
    Mar 2017
    Posts
    6,366
    I've seen a number of reports in the last few days of this on Steam, so I'm trying to look into this issue. Does reinstalling Far Cry 4 resolve the issue? Have you recently installed the latest version of Uplay?
    Share this post