This worked for me! Thanks you loord <3!
Been struggeling for a day now to get it to work
This worked for me! Thanks you loord <3!
THIS REALLY WORKS THANKS A LOT !!!
Hello my dear comrades who share my sorrow.
(The thread where I wanted to post this have been locked…So I try to write it here.)
I browse these topics since patch-day and I tought I’ll share my story aswell. Because what else we could do in a crippled-state like thais than having a nice little chat?
Unfortunately I cannot provide any solutions either, because nothing have worked for me. But I think our words must be heard, and the more people tells his/her story the better.
I won’t even start to copy dxdiag any any other things like that, because it won’t worth a ’firetruck’.
So, I have a Lenovo G580. Originally I used Windows 7 operating system, now I have Windows 10.
Here it goes (this will probably be a huge wall-of-text):
So I had Win7 and WOW worked perfectly fine till the latest patch. After the successful upgrade I pushed the ’Play’ button and this little message greeted me:
’Worlf of Warcraft was unable to start up 3D acceleration.’
After the bloodhaze has gone I tried to look up some solutions and I tried a couple of things which were suggested but nothing worked. I decided to bring my machine to a service, because I wanted to get a bigger harddrive sooner or later anyway.
So I got a bigger harddrive, so both the os and WOW had planty space. The os was changed to Win10, and every single driver and every single thing on my computer was updated to the most fresh versions. (Even dust was cleanded.) I needed to reinstall WOW of course, which was…timetaking.
When it was finally done I pushed ’Play ’ button with shaking hands. And it still doesn’t worked.
I didn’t recieved any error messages anymore, and WOW actually did started, but without screen. There was voice, and even the gauntlet-cursore appeared but there wasn’t any screen, any picture. Not even blackscreen. Nothing. Like if it were invisible.
I did some fast research about this kind of problem aswell. And surprise, surprise, it seemed many other people had the same (or very similar) problem aswell.
Later I borught my poor little machine back to the workshop. Unfortunately without any luck.
Poor guy worked a lot, tried to figure out the problem, tested the video card, ran diagnoses, did what he could, even tried out a lot of stuff which were suggested buy guys who have the same issue but nothing worked. He told me that my machine, my cards (and the drivers) are fine, without any problem, so he suspects there is a bigger chance that Blizz messed up something in this situation.
So this is it, I’m sitting here, helpless.
I must confess, I’m not an expert on these things, however, as others mentioned before me: peoples videocards just don’t go wrong under one day.
Besides, while it is imaginable that an expansion-set can change the games requirements, a patch for the same xpac should not. Not even a content-patch.
So dear Blizzard, please stop accusing us and finally do something. Or at least strop trying to hide, and admit that you messed up something.
I mean seriously, you guys made an entire censored version of the game, just to make it acceptable for some countries where you can’t show skeletons or other things, but you refuse to pay attention to customers who are playing for years.
Seriously I play since the…middle of the Vanilla years. Almost permanently. I had a couple of unsubscribed days when my subscription ended just when I needed to leave to somewhere for a couple of days, but my only longer pause was when there was a problem with my PC back than. Even if now I pay my gametime with tokens you can imagine how many cash I – and many others like me- I have in this game. And all we get is ’fix your s….tuff’. I started with a kinda old, PC, which even had some problems with starting up, and WOW still worked on it, now I have a much better machine, and boom, this happened when this patch. I bet many other fellow players have who have the same issue have much better machines than me.
If you made itt o the end of this, congrats and thank you.
So I wish good luck for you bros and sisters.
P.s.: If anyone knows about some nice Hungaryan forums about this topic please let me know. It would make reading easier.
(P.s.2: Sorry for my english.)
how do u change to direct x 11 ingame? or u changed in wow folder cfg?
Latest patch is failing to use a dedicated graphics card/chip and attempting to use the standard onboard graphics (Intel, which cannot run Direct3D/Directx etc).
Either use the advanced power options and set to Maximum Always (on laptops), or check your BIOS to disable onboard graphics (PCs), to force Windows to constantly run everything through your gaming chip, in this way WoW will be forced to use your active graphics chip/card
DirectX version can also be changed out of game through the command line arguments in the BNet desktop app.
- With the BNet desktop app opened and WoW selected click on Options
- Select Game Settings
- Find WoW and check the box for Additional command line arguments
- In the new box enter the command for the desired DirectX version:
- Click Done to save.
I have had the same isssue. I have tried everything I can think of.
I uninstalled the game - both the client and battle.net. I am reinstalling wow for the second time and I have tried to press play (since it’s in playable state) and it still persists with the same issue. I updated my drivers. Before this I did selective start up as well.
I even contacted a technical support and provided my DxDiag and MSINFO and after I tried one of the solutions the technicians suggested which led to me restarting my PC it still didn’t work and the employee has lied (Ingrathor or something like that) and didn’t answer my ticket after I came back from his first step - I only took 2 minutes tops. Live chat wasn’t available for me after but was available on my alt account lol - Are blizzard employees clueless to what the issue is. It defintiely isn’t my PC - I can run WoW past recommended settings on steady FPs.
Yo this just worked for me. You did what a Blizzard employee failed to do. I put in * -d3d11 and it worked.
hello my bois.
i was really struggling same as you do with AMD/intel graphics…what saved me was actually updating drivers (driver which is needed for running wow BFA is called ‘‘amd adrenalin 18.8.1’’) before that i dont know why but my drivers didnt went for actual version…hope it works for you as for me…back to azeroth bois…hey admins…at least instead of telling ppl toupdate, you could find needed drivers and say exact name since we are paying your living
download driver called ‘‘amd adrenalin 18.8.1’’ worked for me…and i was struggling here for 2days…driver didnt udpated itself as i thought it could.
Can u link the download page pelase
just delete those 00 after http and after amd. because we cant post links
Nope dude i even had more updated version still the same
unfortunately it did not work for me.
AMD, win7-64 etc… (
I am done. After tryign everything and more than 4 drivers i dont see a point to continue. I bet they dont even care about that problem.
For those who able to start the game 20+ min later but suffering from bad render scaling and unable to use game setting without crashing this pity game - run this script:
/console set renderscale 1
The issue is clearly with blizzard whether they wish to accept it or not.
found out that driver is good…what actually breaks our game is latest windows update.so try to uninstall that actualization.for me it is called (KB4470630, -||-639)…i uninstalled it and it was working…restart pc…windows updated and same problem)
right now i did it again and it is working…so it is latest update on windows
Probably there is a rather general problem. E.g the handling the keyboard is also crashing. So, if I press the cursor-arrows and the ‘M’ for map near parallel, the WOW-client is crashing. So the double-binding chars also cause problem.
This also suggest a problem with your developing environment, even its parameters, as I mentioned earlier, too.
BTW, the timing seem to be also a joke according to WOW-client’s log.
Resulting 1-2 minutes for session-uptimes, to tend the game unuseable
12/15 19:56:28.656 Stop waiting for active player
12/15 19:56:28.673 Client Object Manager Destroyed
12/15 19:59:00.083 Initial Hotfixes: Requested
12/15 19:59:00.397 Initial Hotfixes: Received
12/15 19:59:00.535 Initial Hotfixes: Applied
12/15 19:59:03.299 Loading Screen Enable : 571 - 1
12/15 19:59:03.362 Client Object Manager Initialized: 571
12/15 19:59:05.235 Client : Load Map Begin : 571
12/15 19:59:05.257 Loading Screen : Loading : Files Read 2593 : Bytes Read 121278900 : Elapsed MS 2038 : MBytes Per Sec 56.752
12/15 19:59:05.257 Loading Screen : XML Loaded 100%
12/15 19:59:07.274 Loading Screen : Loading : Files Read 1357 : Bytes Read 87867204 : Elapsed MS 2097 : MBytes Per Sec 39.960
12/15 19:59:07.274 Loading Screen : XML Loaded 100%
12/15 19:59:07.274 Loading Screen : World Loaded 61%
12/15 19:59:07.617 Client : Load Map End
12/15 19:59:07.617 Start waiting for active player
12/15 19:59:07.623 Character Login SEND
12/15 19:59:07.623 Waiting for active player: 2 ms
12/15 19:59:10.169 Stop waiting for active player
12/15 19:59:10.192 Loading Screen : Loading : Files Read 983 : Bytes Read 23740952 : Elapsed MS 3033 : MBytes Per Sec 7.465
12/15 19:59:10.192 Loading Screen : XML Loaded 100%
12/15 19:59:10.192 Loading Screen : World Loaded 100%
12/15 19:59:10.192 Loading Screen : Spell Loaded 0%
12/15 19:59:10.964 Active Player Created
12/15 19:59:10.964 Player : Exit Loading Screen : World Check Preload Begin
12/15 19:59:10.964 Player : Exit Loading Screen : World Check Preload End
12/15 19:59:10.964 Loading Screen : Streaming 0
12/15 19:59:10.964 Loading Screen : XML Loaded 100%
12/15 19:59:10.964 Loading Screen : World Loaded 100%
12/15 19:59:10.964 Loading Screen : Spell Loaded 100%
12/15 19:59:10.969 Loading Screen Disable
12/15 19:59:10.969 Spellbook : Make Models Local Begin : 159
12/15 19:59:10.969 Spellbook : Make Models Local End
12/15 20:36:15.622 Stop waiting for active player
12/15 20:36:15.691 Client Object Manager Destroyed
12/15 21:04:04.657 Client Object Manager Destroyed
12/15 21:04:39.267 Initial Hotfixes: Requested
12/15 21:04:39.643 Initial Hotfixes: Received
12/15 21:04:39.836 Initial Hotfixes: Applied
12/15 21:04:58.979 Loading Screen Enable : 571 - 1
12/15 21:04:59.039 Client Object Manager Initialized: 571
12/15 21:05:00.931 Client : Load Map Begin : 571
12/15 21:05:00.951 Loading Screen : Loading : Files Read 1301 : Bytes Read 52050691 : Elapsed MS 2432 : MBytes Per Sec 20.411
12/15 21:05:00.951 Loading Screen : XML Loaded 100%
12/15 21:05:02.651 Loading Screen : Loading : Files Read 759 : Bytes Read 84297864 : Elapsed MS 2098 : MBytes Per Sec 38.319
12/15 21:05:02.651 Loading Screen : XML Loaded 100%
12/15 21:05:02.651 Loading Screen : World Loaded 60%
12/15 21:05:03.537 Client : Load Map End
12/15 21:05:03.537 Start waiting for active player
12/15 21:05:03.544 Character Login SEND
12/15 21:05:03.544 Waiting for active player: 3 ms
12/15 21:05:05.288 Stop waiting for active player
12/15 21:05:05.314 Loading Screen : Loading : Files Read 667 : Bytes Read 22768602 : Elapsed MS 3285 : MBytes Per Sec 6.610
12/15 21:05:05.314 Loading Screen : XML Loaded 100%
12/15 21:05:05.314 Loading Screen : World Loaded 100%
12/15 21:05:05.314 Loading Screen : Spell Loaded 0%
12/15 21:05:06.125 Active Player Created
12/15 21:05:06.125 Player : Exit Loading Screen : World Check Preload Begin
12/15 21:05:06.125 Player : Exit Loading Screen : World Check Preload End
12/15 21:05:06.125 Loading Screen : Streaming 0
12/15 21:05:06.125 Loading Screen : XML Loaded 100%
12/15 21:05:06.125 Loading Screen : World Loaded 100%
12/15 21:05:06.125 Loading Screen : Spell Loaded 100%
12/15 21:05:06.125 Loading Screen Disable
12/15 21:05:06.145 Spellbook : Make Models Local Begin : 159
12/15 21:05:06.145 Spellbook : Make Models Local End
12/15 21:05:10.728 Stop waiting for active player
12/15 21:05:10.739 Client Object Manager Destroyed
Parallel with these. The opening screen sign x64 release, while the game is installing under x86 branch (Program files x86). This suggest several x86 (32 bit) modules in the game. But, this could cause problems by try to using x64 drivers from x86 modules or versus. I think so, this is probably handling by revision of parameters for compiling the product-version, which revision probably missed for new codes, libs, etc.
So, please take a look again for our money.
Are you sure? That patch you quoted (KB4470630) is a security patch for an exploit in .Net 3.5 framework. Supposedly it just patched some method validation. Only for Windows 8/8.1/2012 Server as far as I can see. Would be quite strange if that was causing an issue here.