Page MenuHomeFeedback Tracker
Feed Advanced Search

May 11 2016

nemesis_fs added a comment to T111276: The game crashes to desktop regularly since 0.57.

Have same Issue in experimental. It is a memory access violation at 0067D88C. I've uploaded the dump-files.

hope it is resolved soon.

EDIT:
I have Windows 7 x64 SP1 / ATI HD5800 Series 1024MB / i5-750 4x2,67Ghz. All driver up-to-date.

May 11 2016, 5:47 AM · DayZ
nemesis_fs added a comment to T109190: 0x00540680 referenced memory... 0x0000000 memory could not be read!.

Uploaded files are mine. Sorry for unpacked version. i've too late read the "compress them".. But, i still have the same Problem after verious tests (reinstall, uninstall, old driver, new driver) always the same with BE.. Intresseting thing is, that DayZ starts normaly since the last update wednesday or thursday, only if i start dayz.exe (not dayz_BE.exe) with parameter "-dologs". But no server with no Battleye deactivated is out there to test.
if i change to experimental, the game crashs at start, but with this error code: 0x00548516. the experimental with "-dologs" starts normaly. if i start with dayz_be.exe and "-dologs", the game crashs with "D24S8 for x8r8g8b8". Hardware acceleration is managed by ati driver and cannot be changed. second thing is, BE shows me at start with "-dologs" INFO: blocked file: "C:\Windows\SysWOW64\aticfx32.dll" ... or so

greets

May 11 2016, 4:36 AM · DayZ
nemesis_fs added a comment to T109171: Memory read problem when starting the game.

@orhangazi

  1. I've used AMD and Intel drivers unifL (Leshcat) because the original AMD driver does not recognize my switchable graphics card. But now, battleye does not accept this drivers for now since 0.54 update. And if you want to use a newer driver version, the dynamic mode you will not be spared. After Catalyst 14.4, the fixed mode is no longer supported.
  1. I think the Intel Driver blocks the original AMD driver. so, try to deactivate installing drivers via Windows Updates and manually deinstall the intel display driver in device manager by rightclicking on it and "deinstall". than refresh the device manager to initialize looking for new devices. if your intel is already installed, deinstall it again till your intel is shown as "standard vga..." and than, deinstall AMD display drivers same way. after that reactivate installing driver via Windows update, let him search and install, and reboot. after that you have to download the cataslyst 14.13 for your 6770m with dropdown selection menu on AMD website.

No need to change bios settings about dynamic mode!

i'll hope i've help you.

Greets

May 11 2016, 4:36 AM · DayZ
nemesis_fs added a comment to T109171: Memory read problem when starting the game.

@orhangazi: u're right! i've deleted my unifL Driver-set and installed Intel HD via Windows Updates, but Windows Updates had no driver for my amd gpu. so, i downloaded the newest 14.12 Catalyst from AMD directly (earlier, it wasn't possible - no compatibility), rebooted and the fucking game starts without any problems...

thanks so much for this hint!

May 11 2016, 4:36 AM · DayZ
nemesis_fs added a comment to T109171: Memory read problem when starting the game.

@orhangazi: do you have a switchable graphic-card? Intel HD 3000 & AMD 6770m? And you used only windows update to get driver for your gpu?! ok, but.. inefficient.. what driver version do you get form microsoft? do you already have the "fixed" Switchmode by rightclick on desktop, if you have a switchable gpu?

Thanks!

May 11 2016, 4:36 AM · DayZ
nemesis_fs added a comment to T109171: Memory read problem when starting the game.

I have the same issues in dayz-standalone. With dologs it appears with D24S8 ... and without it crashs only with 0x00540680. with experimental (0.55) the problems doesnt gone.. but new error 0x00548516. And it has to be anything with battleye, because the game starts with manualy started "dayz.exe" with parameter "-dologs". so, battleye seems to block anything nescessary of the driver and dayz.exe, witch is started from dayz_be.exe would to read something from the VRAM and boom.. Nothing there... Crash... i think..

May 11 2016, 4:36 AM · DayZ