Forum Discussion

EA_Barry's avatar
EA_Barry
Icon for Community Manager rankCommunity Manager
11 years ago

Re: "Could not intialize display hadrware" Error.

Can you try hosting your Dxdiag file elsewhere?

The connection has timed out

The server at www.luci5r.com is taking too long to respond.

15 Replies

  • Anonymous's avatar
    Anonymous
    11 years ago

    Barry,

    Sorry about that. The server was undergoing routine maintenance. It's working now; you should be able to download/view the file.

    Thanks.

  • EA_Barry's avatar
    EA_Barry
    Icon for Community Manager rankCommunity Manager
    11 years ago

    Okay, try disconnecting your secondary monitor and install the driver for your primary monitor.

    The dual monitor setup with two different monitors may be confusing the game.

    Thats a rockin' rig BTW :0)

  • Anonymous's avatar
    Anonymous
    11 years ago

    Barry,

    Thanks for helping me resolve this issue; appreciate the response.

    So I disconnected the 2nd monitor completely (Actually unplugged it from the machine); unfortunately that didn't help. I tried with & without Compatibility mode. Same results.

    My primary monitor is an ASUS VS24AH-P and I couldn't locate any drivers for it; historically I don't believe I've ever installed drivers for a monitor since some time now. I think they use the generic Windows or your Graphics Card's drivers. Even on ASUS' website there aren't any drivers for this monitor.

    I also wanted to take the time to post my "Settings.txt" file that is now located in "C:\Users\{user}\AppData\Local\Electronic Arts\Dead Space" ...

    Audio.AltNameColor = false
    Audio.MusicVol = 1.00000000
    Audio.Output = 0
    Audio.SFXVol = 1.00000000
    Audio.Subtitles = true
    Audio.VoiceVol = 1.00000000
    Control.AimAssistEnabled = true
    Control.AimingPosition = 1
    Control.ControllerSensitivity = 2
    Control.FireButtonControls = true
    Control.InvertX = false
    Control.InvertY = false
    Control.MouseSensitivity = 0.20000000
    Control.Shock = true
    Controls.AcL.X = 0x1105FF7E
    Controls.AcL.Y = 0x0003100E
    Game.PDiff = 1
    Game.Played = 1
    Misc.LastSaveSlot = 0
    QualityOptions.ActorMotionBlur = true
    QualityOptions.Bloom = true
    QualityOptions.Blur = true
    QualityOptions.ConfigType = 1
    QualityOptions.Decals = true
    QualityOptions.Distortion = true
    QualityOptions.DoF = true
    QualityOptions.EdgeAA = true
    QualityOptions.Flare = true
    QualityOptions.Glow = true
    QualityOptions.HighLightQuality = true
    QualityOptions.ManipColor = true
    QualityOptions.ShaderQuality = 2
    QualityOptions.Shadows = 2
    Window.Fullscreen = false
    Window.Gamma = 0.50000000
    Window.Height = 1080
    Window.Hz = 60
    Window.Left = 0
    Window.MessageNotification = 1
    Window.State = 0
    Window.Top = 0
    Window.VSync = false
    Window.Width = 1920

    As I stated earlier, the "Window.State" parameter results in different errors, as follows:

    Window.State = 0 : "Dead Space.exe has stopped working"

    Window.State = 2 : "Dead Space.exe has stopped working"

    Window.State = 1 : "Could not initialize display hardware. Please restart Dead Space"

    I'm a CGI Designer/Developer; hence the rig :o)

    Thanks.

  • EA_Barry's avatar
    EA_Barry
    Icon for Community Manager rankCommunity Manager
    11 years ago

    Okay, so try the following steps:

    Disconnect all peripheral devices(USB drives, game controllers, everything) leaving only mouse and KB


    Set the following parameters in the settings file:

    Window.Fullscreen = true
    Window.VSync = true

    Try to play.

    If you continue to see the error message, try cutting that settings file to your desktop and let the game create one with default settings and retry.

  • Anonymous's avatar
    Anonymous
    11 years ago

    Barry,

    Thanks for your response.

    Did as you suggested. Disconnected all peripheral devices from the system; leaving only Keyboard & Mouse (Both are USB). Changed the Fullscreen & VSync settings to true in "Settings.txt".

    Same errors. Without Compatibility mode, I got a full black screen for a brief moment, then back to desktop with "Dead Space.exe has stopped working". With any Compatibility Mode selected, I got the "Could not initialize" error instead.

    Then I removed Settings.txt from the containing folder and retried; exact same results as above. One thing however that I did notice was that no "Settings.txt" was generated by the game. The folder remained empty.

    Thanks.

  • EA_Barry's avatar
    EA_Barry
    Icon for Community Manager rankCommunity Manager
    11 years ago

    So, a couple more things...

    It is not a CPU issue as I thought it could be a compatibility problem. I know that the game will run on a Xeon CPU.

    I still think the issue revolves around a combination of fullscreen and vsync settings. Are you forcing vsync in your GPU control panel? Try resetting your GPU defaults.

    If playing around with the GPU control panel does not help the problem it can never hurt to do a clean install of your video drivers. nvidia make this easy by allowing a clean install to be chosen via the custom driver install option.

  • Anonymous's avatar
    Anonymous
    11 years ago

    Barry,

    Thanks for your patience; I will try your suggestions today - both playing around & resetting the GPU Settings, and if that doesn't help, doing a fresh, clean install of the nVidia drivers.

    I will report back once I've attempted a few of these things.

    Thanks again.

  • Anonymous's avatar
    Anonymous
    11 years ago

    Barry,

    I did get a chance to try your suggestions; played around with the settings in the nVidia Control Panel, especially vSync. Didn't help.

    Finally resorted to reinstalling the nVidia software; checked the "Perform clean install" option. Didn't help.

    Exact same errors all across the board. None of the settings change the error at all. The only thing that seems to change the error or have any impact on the launch are the "Fullscreen" and the "State" settings in the "settings.txt". With Fullscreen true or false you can see black window full screen or windowed. With State, the errors change with 0,1,2 values as I've reported previously.

    Nothing else that I've attempted seems to be have any impact on the launch or the errors.

    I do agree with you; I don't believe it's a Xeon CPU issue. And I've seen posts with people running Windows 8.1 pro x64 who are able to play the game; so I don't believe it's an OS issue either. Which really just leaves GPU as the culprit. I'm just not clear where the issue is though.

    I have a 1200p monitor; I don't know if that could be the issue. I could try my other 1080p monitor but I doubt that would be the issue. I'm quite out of ideas.

    Thanks. 

  • EA_Barry's avatar
    EA_Barry
    Icon for Community Manager rankCommunity Manager
    11 years ago

    Do try the 1080P monitor. Also try setting a low resolution, like 1024x768 in the settings file. Are you sure your Xeon has 100% of its features supported by your motherboard? Is there a firmware update available for your MB? What exact MB are you using?

  • Anonymous's avatar
    Anonymous
    11 years ago

    Barry,

    I did end up trying quite a few things. I switched out my monitor with a 1080p monitor. Lowered resolution in the settings.txt; also tried lower the monitor resolution itself. Tried various different combinations of resolution; fullscreen; window state; monitor resolution, etc.

    Absolutely nothing helped. The errors never changed.

    Yes, the motherboard supports the CPU 100%; and has the latest firmware. I actually went through extensive pre-sale support with the manufacturer before picking the motherboard. Each component had to fit in appropriately with the other; this was very important for me due to the rendering software I use (which are far more picky & cumbersome then games are). I'm using the ASRock EP2C602-4L/D16 SSI EEB Server Motherboard with the Intel Xeon E5-2650 v2 X 2 CPU's. The rendering engines are extremely particular about the CPU features; so I had to spend a considerable amount of time with pre-sale support before selecting a motherboard.

    I have a vast game library on my PC and so far only 2 games have failed to launch; one is Dead Space and the other is Dead Island Riptide. However, with Dead Island Riptide (which is Steam by the way), there is an extensive launch problem which is well documented & found across the Internet. Quite a few suffer from it and there's never been a cure found. People have paid over $40 for that game and Steam support or Deep Silver has never been able to solve those issues.

    With Dead Space however, most people have been able to resolve their issues with the "settings.txt". I just don't understand where I'm stuck.

    There is one other thing I will try today - time permitting - I will download & install Origin & Dead Space on a different PC. That one isn't configured for gaming; it's my wife's PC and is much less equipped handle gaming of any sort, however, I'm curious.

    Do let me know if you have any other suggestions for me.

    Thanks.

  • Anonymous's avatar
    Anonymous
    11 years ago

    DOGGONE IT!

    So I installed Origin & Dead Space on my wife's PC and it worked!! Just simply worked. I didn't even create Settings.txt or touch anything. This is a very basic Intel i5-4200U / Intel HD Graphics 4400, Windows 8.1 64-bit PC.

    After running the game once, it created a Settings.txt; so I stole that file and replace my Settings.txt with the one created on my wife's PC. Still get the same errors on my PC. But works fine on hers.

    I don't get it. I'm baffled.

  • EA_Barry's avatar
    EA_Barry
    Icon for Community Manager rankCommunity Manager
    11 years ago

    Hmmm, it seems like your setup may be a little too specialised toward the hardcore workstation side of things. I know I said previously that the game will work on Xeon processors, but with a dual CPU setup I am not so sure. Let me see if I can find more on dual CPU compatibility...

  • Anonymous's avatar
    Anonymous
    11 years ago

    Thanks Barry; I'm all out of ideas. Will look forward to your response.

  • Anonymous's avatar
    Anonymous
    11 years ago

    Barry,

    I figured it out. You ready for this?

    So as it turns out, you did latch on to the correct problem in your last post. Indeed, much to my dismay, but also to my relief, it appears that some games cannot tolerate 2 physical CPU's. "Dead Space" and "Dead Island Riptide" are 2 prime examples of this.

    After your last post about digging into a dual CPU setup, I spent some time today digging into it myself. I came across a process for turning Off your physical cores in Windows 8 for this exact purpose - applications or games that cannot run on multiple CPU's (or in some cases, multiple cores).

    I followed the instructions and took my system back into the stone age; into the "Core2Duo" era. I disabled all but 2 cores, giving me 4 threads. As soon as I restarted the system & went back in, both Dead Space & Dead Island Riptide fired up immideately. No issues!!

    I bumped up the cores to 4 Cores / 8 Threads ... and they're still working fine. I have two physical 8 Core processors giving me 16 threads a piece; which gives me a total of 32 threads. I haven't tested it far enough but I'm imagining if I essentially disable my 2nd processor and keep only 1 processor running (8 Cores / 16 Threads), both these games should be able to run. I believe it's the 2nd physical CPU that's causing them to crash.

    You may already know the process for turning off cores in Windows, but just in case, here's the process I used:

    Windows 8.1 64-bit

    Type "msconfig" in run or search.

    Under "System Configuration", click the "Boot" tab.

    Click "Advanced Options..."

    Check "Number of Processors:" and choose number of cores to enable in the drop-down.

    Restart.

    You can probably add this to your standard troubleshooting procedures, especially for systems with high end processors or quite a few cores.

    On a side-note, I must say I'm slightly dissapointed. I'm running everything from the original Doom, Duke Nukem 3D & Prince of persia (1995) to Splinter Cell Blacklist, StarCraft, CoH, Borderlands 2, etc ... In total I must have a library of 50 games on my PC spanning decades - from 90's to the very latest titles. I'm astonished that the developers of both these titles, EA & Deep Silver, rendered the applications such that they just won't run on multi-processor systems. If 98% of the titles I've come across run on this system - I can't imagine what was so crucial in the software of these 2 particular games that the developers could not bypass. It's a bit baffling to be honest.

    Either way, the problem is solved. Switching back & forth between enabling & disabling cores isn't all that hard & it's what I'll resort to for these 2 games.

    I must thank you for all your efforts & patience. You definitely pointed out the right possible hurdle.

    Thanks again for all your help.

  • EA_Barry's avatar
    EA_Barry
    Icon for Community Manager rankCommunity Manager
    11 years ago

    Awesome, well done!

    I think your process of disabling the second CPU is the only way you are going to be able to play DS1 and as you said its not that much hassle to turn the second CPU on and off.

    I assume the extra work required to have a game function on the relatively niche segment of the market with dual physical CPUs was not deemed worth it for the number of users with this kind of setup.

    I am glad I could point you in the right direction but you did all the leg work so kudos to you.

    Happy gaming :0)