Glorious Alpha Two Testers!

Alpha Two Realms are now unlocked for Phase II testing!

For our initial launch, testing will begin on Friday, December 20, 2024, at 10 AM Pacific and continue uninterrupted until Monday, January 6, 2025, at 10 AM Pacific. After January 6th, we’ll transition to a schedule of five-day-per-week access for the remainder of Phase II.

You can download the game launcher here and we encourage you to join us on our for the most up to date testing news.

[Bug Hunting] GPU Crashes and Running Out of VRAM

124»

Comments

  • MortyMorty Member, Alpha Two
    Still can't even make a character. Crashes on 1st screen. Every time.

    "GPU Crash dump Triggered

    AOCClient_Win64_Shipping
    AOCClient_Win64_Shipping
    AOCClient_Win64_Shipping
    AOCClient_Win64_Shipping
    AOCClient_Win64_Shipping
    AOCClient_Win64_Shipping
    AOCClient_Win64_Shipping
    AOCClient_Win64_Shipping
    kernel32
    ntdll"

    I feel like I've tried everything. Someone, please give me a solution.
  • DirtyySauceDirtyySauce Member, Alpha Two
    Having the same problem as many here. I can play for about 5 minutes and then my monitors turn off. I can still hear game sounds, the only way to fix is to hard reset the PC.

    i9-11900KF 3.50ghz
    32GB Ram
    3090GTX
    SSD NVMe

    Its pretty frustrating when I spend over $100 and cant even play the game. Has anyone found an actual fix for this? Or do the Devs have to provide an update with something wrong in their code?
  • jamberjamber Member, Alpha Two
    I've also been plagued by many a crash.
    After updating Bios, updating and rolling back GPU drivers and multiple sensor monitor applications to see what's happening at the time of crash - I still can't pinpoint what is happening at crash.

    My crash event is a full system power off - no launcher error or hang. Computer off - full stop.
    HW is a Ryzen7 3700x CPU, Radeon RX 5700XT GPU, and 32GB of RAM.

    After some testing with settings, I have found that the crash event will not happen (at least after a full hour of playing now, finally) if I keep the game at a Fullscreen or windowed "1920x1080" resolution.
    It seems that, at even high graphics level, the crash will not happen.
    I have FPS locked to 30 and v-sync enabled.

    However, If I play in a resolution higher of the same aspect ratio 2560x1440, even on the lowest graphics setting, I will get the crash.
    If I try to run "fullscreen Windowed", it generally sets my resolution to some value - but the ratio is showing a greyed out 3840x2160 resolution - this will also crash out. My monitor native resolution is 2560x1440, so if full-screen window is using native monitor resolution, this is a condition I find fails.

    So, all in all, it might be worth trying to limit the resolution to see if you can play in the mean time while intrepid finds the issue on their side.
    As many have said here, I can have other AAA games at max resolution and graphics and not crash. It doesn't have pretty FPS, but it also doesn't lock up the computer.
    Running OCCT stress tests on CPU/GPU/VRAM/DDR RAM, and able to stress to 80C without issue, where I never get above 75C with AoC on.
    It's not a straight Power, heat, or VRAM limit issue - It seems like AOC does some spike usages that flub up some HW, which other existing games doesn't.

    Hope this stop-gap helps some of you.
  • ash816ash816 Member, Alpha Two
    edited November 17
    friend has the same issue.

    running a 3080 and 11th gen processor on win 11

    game gets to 11/12% and he hears his gfx card fans turn off. game then loads in very slowly layer by layer and then he crashes.
  • VaknarVaknar Member, Staff
    Hi all!

    The team is still investigating reports of this.

    In addition to sending your logs immediately after having crashed, please also include a dxdiag file so we can better understand what's going on <3
    community_management.gif
  • darknezzszdarknezzsz Member, Alpha Two
    Vaknar wrote: »
    Hi all!

    The team is still investigating reports of this.

    In addition to sending your logs immediately after having crashed, please also include a dxdiag file so we can better understand what's going on <3

    Nothing yet?
  • ShardeeeShardeee Member, Alpha Two
    Problem : Black screen then crash after starting the game from launcher SINCE I had a GPU crash while in game last week.

    CPU use is 100% during the black screen
    GPU : RTX 3080
    CPU : i9 9900k
    RAM : 64go

    Are there any steps you can take to reproduce the issue consistently?

    1 - Start launcher
    2 - Login to Alpha Two
    3 - Click Launch Game
    4 - The game window opens, but stays black for a few seconds before closing

    So I can't launch the game at all since last week-end.
    Tried windows 11 update from 10, bios flash, game / launcher reinstal / repair / Drivers update.

    I have this bug since sunday during the last week-end of test, I remember having a crash ingame after several hours playing, with something like "not enough GPU momory" but I didn't remember it well.

    I attached todays logs from both launcher + AOC folders + Dxdiag + the logs from the last time I was online last week-end, as there is a file saying "Passthrough is not supported, GL is disabled".

    Fortunately the game runs well on my laptop, but looking forward to a fix !
    Hope these files will help !
  • YushaodoYushaodo Member, Alpha Two
    Vaknar wrote: »
    For those of you that are crashing due to VRAM, have you tried lowering your settings? If so, did that fix the issue?

    the problem is.. recommended ram specs are too low.... the true ram requirements for Ashes of Creation, are // minimum - 32GB duel channel 6000+ MT/S ...... I KNOW THIS BECAUSE I PLAY ON A LAPTOP WITH INTERGRATED GRAPHICS AND I had use intel arc boost to have more vram... and it helped a little bit... DUE TO UE5 GRAND WORLD RENDERING, COMMON OR OUTDATED SYSTEMS CANT HANDLE THE RENDER.................................................................................................................................................................................................................... THE SOLUTION IS ......................... HAVE 2-PART SERVERS PER SERVER, RENDER THE PLAYER NEEDED DATA ON THE RENDER REALM (NEEDED DATA ONLY) SO TO ENSURE NO CRASHES, THEN, IF ANY RENDER PROBLEMS EXIST ON THE MAIN SERVER, IT WILL ONLY BE GRAPHICAL ISSUES...................................................................................................................................................................... ............ YOURS FAITHFULLY, YUSHAODO
  • korovitzkorovitz Member, Alpha Two
    i was running fine from friday 11/22/24 to the hot fix on saturday 11/23/24 and now my GPU is crashing every time a try to launch the game.
    GPU; AMD Radeon RX 6600
    CPU; AMD Ryzen 5 5600
    32 GB ram
    AMD driver software version 24.10.1
  • MortyMorty Member, Alpha Two
    GPU CRASH DUMP on 1st screen every time.

    I have updated my Windows 11, ALL my drivers, my BIOS, and the AoC launcher, in addition to changing almost every setting of my BIOS in hopes of correcting this issue, still no change in result. My system exceeds the minimum requirements and I still have not made it past the first screen post-launch. Below is my hardware. Please help me. It's been three weeks of this. I'm very frustrated.

    CPU: AMD Ryzen 7 7800X3D
    MB: ASUS ROG Crosshair X670E Gene Micro ATX
    RAM: CORSAIR Vengeance 32GB DDR5 6000
    GRAPHICS: ASUS Dual AMD Radeon RX 6750 XT OC Edition 12GB
  • grekowskigrekowski Member, Alpha Two
    edited November 24
    Out of memory crash.
    AMD Ryzen 9 3900XT 12-Core Processor 3.80 GHz
    32,0 GB ram Corsair Dominator DDR4 3600Mhz
    Fixed Page file 5GB
    Windows 11 Home 23H2 22631.4460
    msi 3080 suprim x

    Tested on all type sof settings (low to cinematic, different resolutions, disabling/enabling dlss, etc.)
    Logs.zip 196.3K
  • BeatalotBeatalot Member, Alpha Two
    jamber wrote: »
    I've also been plagued by many a crash.
    After updating Bios, updating and rolling back GPU drivers and multiple sensor monitor applications to see what's happening at the time of crash - I still can't pinpoint what is happening at crash.

    My crash event is a full system power off - no launcher error or hang. Computer off - full stop.
    HW is a Ryzen7 3700x CPU, Radeon RX 5700XT GPU, and 32GB of RAM.

    After some testing with settings, I have found that the crash event will not happen (at least after a full hour of playing now, finally) if I keep the game at a Fullscreen or windowed "1920x1080" resolution.
    It seems that, at even high graphics level, the crash will not happen.
    I have FPS locked to 30 and v-sync enabled.

    However, If I play in a resolution higher of the same aspect ratio 2560x1440, even on the lowest graphics setting, I will get the crash.
    If I try to run "fullscreen Windowed", it generally sets my resolution to some value - but the ratio is showing a greyed out 3840x2160 resolution - this will also crash out. My monitor native resolution is 2560x1440, so if full-screen window is using native monitor resolution, this is a condition I find fails.

    So, all in all, it might be worth trying to limit the resolution to see if you can play in the mean time while intrepid finds the issue on their side.
    As many have said here, I can have other AAA games at max resolution and graphics and not crash. It doesn't have pretty FPS, but it also doesn't lock up the computer.
    Running OCCT stress tests on CPU/GPU/VRAM/DDR RAM, and able to stress to 80C without issue, where I never get above 75C with AoC on.
    It's not a straight Power, heat, or VRAM limit issue - It seems like AOC does some spike usages that flub up some HW, which other existing games doesn't.

    Hope this stop-gap helps some of you.

    This is the same issue I've been having except i cant even get into the character select screen to be able to change the graphics settings. I was able to edit the game user settings and that at least bought me a few seconds but not enough to actually have everything load in.

    I see that my CPU maxes out all its cores and then the pc shuts down. This is the only game its happening with so far

    CPU: Ryzen 7 9800x3d
    GPU: RTX 4080
    RAM: 32GB DDR5 - 6000
  • ash816ash816 Member, Alpha Two
    still an issue.
  • Ancient KonoAncient Kono Member, Alpha Two
    Game continues to crash and frezze, sometimes displaying "Out of video memory trying to allocate a rendering resource..."

    Going thorugh the logs I can find "
    [1125/093933.578:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is disabled";

    Tracing it to the AMD and Unreal Forums this is related to the support of DX12;
    (Maybe related to background changes for the upcoming lighting update? Raytracing?)

    The alleged fix is to switch from DX12 to DX11, a setting for which I can not find an option in the launcher or ingame graphics settings;

    Attached Logs

    Hope this will help to fix this.

    BR
    -K
  • ShabooeyShabooey Member, Alpha Two
    jamber wrote: »
    I've also been plagued by many a crash.
    After updating Bios, updating and rolling back GPU drivers and multiple sensor monitor applications to see what's happening at the time of crash - I still can't pinpoint what is happening at crash.

    My crash event is a full system power off - no launcher error or hang. Computer off - full stop.
    HW is a Ryzen7 3700x CPU, Radeon RX 5700XT GPU, and 32GB of RAM.

    After some testing with settings, I have found that the crash event will not happen (at least after a full hour of playing now, finally) if I keep the game at a Fullscreen or windowed "1920x1080" resolution.
    It seems that, at even high graphics level, the crash will not happen.
    I have FPS locked to 30 and v-sync enabled.

    However, If I play in a resolution higher of the same aspect ratio 2560x1440, even on the lowest graphics setting, I will get the crash.
    If I try to run "fullscreen Windowed", it generally sets my resolution to some value - but the ratio is showing a greyed out 3840x2160 resolution - this will also crash out. My monitor native resolution is 2560x1440, so if full-screen window is using native monitor resolution, this is a condition I find fails.

    So, all in all, it might be worth trying to limit the resolution to see if you can play in the mean time while intrepid finds the issue on their side.
    As many have said here, I can have other AAA games at max resolution and graphics and not crash. It doesn't have pretty FPS, but it also doesn't lock up the computer.
    Running OCCT stress tests on CPU/GPU/VRAM/DDR RAM, and able to stress to 80C without issue, where I never get above 75C with AoC on.
    It's not a straight Power, heat, or VRAM limit issue - It seems like AOC does some spike usages that flub up some HW, which other existing games doesn't.

    Hope this stop-gap helps some of you.

    This happened to me last night. I've had a few 3 or 4 game crashes back to desktop since the A2 launch but never a hard shut down before.

    Specs:
    Ryzen 5900x - 6800xt - 32gb Ram - 1440p

    Check on temps seemed fine so not really sure what happened.

    Was playing the game fine for 45mins or so just chopping wood then my PC just hard shutdown, no error or anything just black. Wouldn't boot for a few minutes. Did reboot, haven't tried playing again but will see what happens when I do.
  • KatrenaKatrena Member, Alpha Two
    edited November 30
    Was running smooth from first day of Beta 2 til 11/22, then constant crashed

    Have tried everything including:
    Update GPU drivers
    Flash Bios
    Update chip drivers

    Also used MSI Afterburner to throttle GPU, it worked from 11/23 to 11/29
    Setting Core Clock to -50 and memory clock to -20 let me play for hours, but as of 11/30 this no longer works

    Processor: Intel(R) Core(TM) i5-14600K (20 CPUs), ~3.5GHz
    Memory: 32768MB RAM
    Available OS Memory: 32536MB RAM
    Page File: 9331MB used, 30627MB available
    DirectX Version: DirectX 12
    GPU: Nividia 4080 Super

    98ayy3spv2fc.png
  • MortyMorty Member, Alpha Two
    Morty wrote: »
    GPU CRASH DUMP on 1st screen every time.

    I have updated my Windows 11, ALL my drivers, my BIOS, and the AoC launcher, in addition to changing almost every setting of my BIOS in hopes of correcting this issue, still no change in result. My system exceeds the minimum requirements and I still have not made it past the first screen post-launch. Below is my hardware. Please help me. It's been three weeks of this. I'm very frustrated.

    CPU: AMD Ryzen 7 7800X3D
    MB: ASUS ROG Crosshair X670E Gene Micro ATX
    RAM: CORSAIR Vengeance 32GB DDR5 6000
    GRAPHICS: ASUS Dual AMD Radeon RX 6750 XT OC Edition 12GB

    UPDATE: I have now reinstalled Windows and all drivers. BIOS was reset to defaults. NO CHANGE.

    Still crashes 30 seconds in. I can't change any game settings or even make a toon.

    Dear god, release me from my suffering.
  • Ancient KonoAncient Kono Member, Alpha Two
    edited December 1
    UPDATE: Flashed Bios once more; clean GPU driver installs; and stil happening. Am around 70 crashes so far... FeelsBadMan
  • innairisinnairis Member, Alpha One, Alpha Two, Early Alpha Two
    edited December 3
    I would get this error and crash when running two monitors one with twitch/videos the main screen with AoC. it would normally happen if i left AoC run in the 'background' for a long time without any input.
    Windows 11
    3080 TI
    i9-9900k @ 3.6
    32g ram

  • Arcano_Arcano_ Member, Alpha Two
    edited December 15
    This was pinned and now it's not. Was it solved?
    The best part about mmos is the friends you make along the way.
  • MethlabMethlab Member, Alpha Two
    Seiken - Castus here.

    For some reason the forums preferred my alts name rather than my main.

    For people running into the no-display found issue here is how to fix it.

    3090's are the just in a bad spot and idk why. I ran into the no display found issue and did EVERYTHING under the sun. the ONLY fix for this is to limit my frames. I've set mine anywhere from 30-40 for the time being with zero issues. Haven't tweaked beyond that because I care not to.
Sign In or Register to comment.