Boards›Report a Bug

windows 10 issue tried compatibility to windows 7 but still have that "CreateVertexBuffer failed"

hhhs·10/16/2016, 1:21:11 PM·1 votes·3,604 views

i bought a new LAPTOP-S3N1E4MS os: windows 10 home 64 bit HP notebook processor: Intel(R) HD Graphics 520 Core(TM) i3-6100U CPU @ 2.30GHz(4CPU) 8GB Dx12 Okay guys this happen : picked a champ locked wait game start then crashed bugslpat comes-up tried reconnect game keep crashing and so on until the match ends .So i tried to play league form garena and the result always the same then i found at both r3d logs have that "CreateVertexBuffer failed" at the bottom any help ? (i can't show u guys my NA r3d logs files right now cause i deleted everything and reinstalling )

000000.000| ALWAYS| Logging started at 2016-10-16T19:18:50.441 000000.004| OKAY| Riot::RADS::Reader::RadsMain::Initialize: RADS library initializing with specified working directory "C:\Program Files (x86)\LienMinhHuyenThoai\LienMinhHuyenThoai\GameData\Apps\LoLVN\Game". 000000.004| OKAY| Riot::RADS::Reader::RuntimeEnvironment::Create: Creating RADS runtime environment: RADS root directory = "C:/Program Files (x86)/LienMinhHuyenThoai/LienMinhHuyenThoai/GameData/Apps/LoLVN/Game" 000000.004| WARN| Riot::RADS::Reader::RuntimeEnvironment::GetProjectTypeNameAndVersion: Did not find keywords "projects" or "solutions" in path C:/Program Files (x86)/LienMinhHuyenThoai/LienMinhHuyenThoai/GameData/Apps/LoLVN/Game 000000.004| ERROR| Riot::RADS::Reader::RuntimeEnvironment::Create: RADS runtime environment creation failed because it was unable to get the project information. 000000.004| ERROR| Riot::RADS::Reader::RadsMain::Initialize: RADS library initialization failed to create the runtime environment. 000000.004| ERROR| Failed to initialize Rads library. 000000.015| OKAY| Unable to process data overlay file ./ToolsConfig.xml, defaulting to overlay now 000000.015| ALWAYS| Data overlay start folder initialized to DATA, Content/Src 000000.016| ALWAYS| Global logging level set to WARN 000000.017| ALWAYS| GameClock LockToSystemClock time: 0.000000 diff: 0.016976 000000.021| ALWAYS| Build Version: Version 6.20.160.7699 (Oct 03 2016/17:57:47) [PUBLIC] <Releases/6.20> ChangeList: 1607699 000000.170| ALWAYS| Started System Init 000000.171| ALWAYS| Maestro Init 000000.199| ALWAYS| Maestro completed init 000001.188| ALWAYS| WadFile mount: DATA/FINAL/Global.wad 000001.199| ALWAYS| WadFile mount: DATA/FINAL/Shaders.wad 000001.201| ALWAYS| WadFile mount: DATA/FINAL/UI/ui.wad 000001.204| ALWAYS| WadFile mount: DATA/FINAL/Localized/Global.en_us.wad 000001.214| ALWAYS| StartSession called 000001.214| ALWAYS| Started Init event arguments 000001.215| ALWAYS| Waiting until connection... 000001.307| ALWAYS| OS Version String: 7 Home Premium, x64 000001.307| ALWAYS| CPU: GenuineIntel, Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz, Intel64 Family 6 Model 78 Stepping 3, 2304 (0 core) 000001.308| ALWAYS| Measured processor speed: 2348 000001.308| ALWAYS| Display info: Intel(R) HD Graphics 520 1073741824 20.19.15.4390 000001.308| ALWAYS| Physical memory: 8589934592 000001.308| ALWAYS| {"messageType":"hardware_information","message_body":"Hardware Info","operating_system":"7 Home Premium, x64","cpu":"GenuineIntel","cpu_processor":"Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz","cpu_identifier":"Intel64 Family 6 Model 78 Stepping 3","cpu_topology":2,"gpu":"Intel(R) HD Graphics 520","video_memory":"1073741824","driver_version":"20.19.15.4390","physical_memory":8589934592,"wine":false} 000001.308| ALWAYS| -----HARDWARE INFORMATION START----- 000001.308| ALWAYS| Operating System: 7 Home Premium, x64 000001.308| ALWAYS| GPU Manufacturer: Intel(R) HD Graphics 520 000001.308| ALWAYS| GPU Memory: 1073741824 000001.308| ALWAYS| GPU Driver Version: 20.19.15.4390 000001.308| ALWAYS| CPU Brand: GenuineIntel 000001.308| ALWAYS| CPU Processor Name: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz 000001.309| ALWAYS| CPU Identifier: Intel64 Family 6 Model 78 Stepping 3 000001.309| ALWAYS| CPU Speed: 2304 000001.309| ALWAYS| CPU Topology: 2 Core 000001.309| ALWAYS| Physical memory: 8589934592 000001.309| ALWAYS| -----HARDWARE INFORMATION END----- 000001.497| ALWAYS| InitRenderer() enter 000001.498| ALWAYS| r3dRenderLayer::Init(0x00100AEA) enter 000001.506| ALWAYS| r3dRenderLayer::Init() exit successfully 000001.857| ALWAYS| Loaded locale en_us via fontconfig 000001.874| ALWAYS| SharedConfigPath: ../Air/preferences/ 000001.878| ALWAYS| r3dRenderer::SetMode: Trying resolution 1280x720, bpp 32, windowMode 0, vsync on... 000001.878| ALWAYS| In Riot::Win::Resize: Resizing the window and retrieving monitor info 000001.878| ALWAYS| In Riot::Win::Resize: Initial VideoMode(4493ac0) and resolution (1280 x 720) 000001.878| ALWAYS| In Riot::Win::Resize: VideoMode(4493ac0) and resolution (640 x 360) 000001.888| ALWAYS| In Riot::Win::Resize: Resized window to resolution 1280x720 000001.891| ALWAYS| rr3dRenderLayer::InitDevice(XRes = 1280, YRes = 720, BPP = 32, Flags=1280) enter 000001.891| ALWAYS| rr3dRenderLayer::InitDevice: Creating d3d device 000001.891| ALWAYS| CreateDevice: Disabling EnableAutoDepthStencil in favor of an INTZ depth buffer. 000001.891| ALWAYS| CreateDevice: Disabling present depth discard in favor of an INTZ depth buffer. 000002.042| ALWAYS| CreateVertexBuffer failed: 8876086c (s: 16 u: 0, p: 1) 000002.042| ALWAYS| CreateVertexBufferD3D9 failed: 0 000002.495| ERROR| Crash Occurred

6 Comments

Deep Terror Nami10/16/2016, 1:32:29 PM2 votes

After reading a few posts found through googling that, it sounds like a pretty complicated issue, but one that seems to almost always come back around to the video card. I recommend first trying to reinstall/update your video driver. If that doesn't work I'd suggest posting this on the Help & Support board where Riot can hopefully provide some more assistance.

Leanus Crain10/16/2016, 7:51:53 PM2 votes

As DTN said. Update drivers. Also make sure your DirectX isn't in Developer mode. After that if it still is there make sure you have Xbox Game DVR disabled. And if that doesn't work do all the above and run League in Admin. You'll find an .exe in the folder you told your computer to put Lol. Usually it's going to be like C:/Riot Games/ League of Legends/lol.launcher.admin Hope that helps.

hhhs10/16/2016, 1:41:14 PM1 votes

everything about windows 10 with league is over a year so i need alot of reading any links articles can help me or u guys have less time read more time playing just paste it

hhhs10/17/2016, 11:34:16 AM1 votes

i will try thanks for the help guys summoner 3

hhhs10/17/2016, 1:06:07 PM1 votes

ok Xbox Game DVR disabled updated my drivers and i can have a 5-sec macth then bugsplat again which is good but need more than that to play (also how to make sure DirectX not in Developer mode? #LC)[slayer-pantheon-thumbs]

hhhs10/18/2016, 1:20:14 PM1 votes

ok it's was a resolution proplem which can be fix at game.cfg open with notepad and the game works prefect thanks u guys for the help