The days I fought with 0xc000007b

Since the new notebook, began to reload the various software, in the beginning of the important days of the soft work, I silently run the client when there is a such error:

In view of my very waste firewood, nature can not go to check memory, so began various degrees Niang Bing and Google, Oh! It should have been DirectX error Ah!

Try this post: http://www.uzzf.com/news/7236.html

Http://jingyan.baidu.com/article/ff42efa9181bbbc19e22022f.html

The above post has been described in detail, according to the method listed to try the day .... ┑ Egg (￣д￣) ┍

Desperate to go down a dependency walker to test the client EXE file, came out of the results shocked me

One by one, I'm going down to se years and falling! Exhausted I went to partner's computer and tried it .... The same result

Abandoning dependency Walker (vertical one middle finger), I began to look at the game client's installation package and saw only the D3dx9d_43.dll library file.

Me: (haha!) It's not easy! All the way to copy to the C-Drive System32 folder is good! Copy--Replace--perfect! ）

But I was 0xc000007b to the face.

Finally holding the dead horse when the survival of the horse medical mentality, the good d3dx9d_43.dll (note is good) copied to the SysWOW64 folder, the results .... Results....... It's all right!

Summary: Generally this error, in addition to the probability of a very small hardware problem, is generally a problem with DirectX, be sure to pay attention to the System32 and SysWOW64 folder to view D3dx9_39.dll, D3dx9_40.dll, D3dx9_41.dll, D3dx9_42.dll, D3dx9_43.dll, xinput1_3.dll these files, not as long as there is the line, be sure to ensure that there is no damage! Sometimes using Directx_repair is not to check out the damage!

The days I fought with 0xc000007b