Forum > Bad Threads

Noggit - Ingame Error

(1/2) > >>

KevinBM:
I've got a 132 Error, when I go to a specific zone ingame.


And it's not because of the wmo's. I added them afterwards.



--- Quote ---The instruction at "0x007B31F8" referenced memory at "0x00000010".
The memory could not be "read".

EAX=0BC32BA0  EBX=18FD699C  ECX=00000007  EDX=02D1FB90  ESI=00000000
EDI=000000AF  EBP=02D1FA70  ESP=02D1FA5C  EIP=007B31F8  FLG=00010212
CS =001B      DS =0023      ES =0023      SS =0023      FS =003B      GS =0000

007B31F8 02D1FA70 0001:003B21F8 D:World of WarcraftWow.exe
007D3DAD 02D1FB98 0001:003D2DAD D:World of WarcraftWow.exe
007D407C 02D1FBCC 0001:003D307C D:World of WarcraftWow.exe
0079A7F7 02D1FBF0 0001:003997F7 D:World of WarcraftWow.exe
0079AB27 02D1FC3C 0001:00399B27 D:World of WarcraftWow.exe
0077F003 02D1FC4C 0001:0037E003 D:World of WarcraftWow.exe
004F90A4 02D1FC98 0001:000F80A4 D:World of WarcraftWow.exe
004FB042 02D1FD24 0001:000FA042 D:World of WarcraftWow.exe
00485128 02D1FDE4 0001:00084128 D:World of WarcraftWow.exe
00494F67 02D1FE00 0001:00093F67 D:World of WarcraftWow.exe
0049545B 02D1FE1C 0001:0009445B D:World of WarcraftWow.exe
004A8A42 02D1FEE8 0001:000A7A42 D:World of WarcraftWow.exe
00480B79 02D1FF18 0001:0007FB79 D:World of WarcraftWow.exe
0047DC89 02D1FF40 0001:0007CC89 D:World of WarcraftWow.exe
0047F29A 02D1FF94 0001:0007E29A D:World of WarcraftWow.exe
0047F2E1 02D1FFAC 0001:0007E2E1 D:World of WarcraftWow.exe
0040B7D8 02D1FFB4 0001:0000A7D8 D:World of WarcraftWow.exe
7674735A 02D1FFEC 0001:0003635A C:Windowssystem32kernel32.dll
76747312 02D1FFFC 0001:00036312 C:Windowssystem32kernel32.dll

--- End quote ---

Hope that someone could help me.

- Please leave a link to a thread, if there is one!

Edit: It also happens, when I look in this direction from a short distance like 20 meters ...

schlumpf:
Kevin,

a screenshot does not help at all when looking for such an error. The only thing that could help are your files.

Also, please do not post those stupid wow errors, as most information there is completely useless and they are most of the time not useful at all.

Ascathos:
The 132 Error is often caused by doodads and messed up datas after switching textures - use the doodad fixer or remove them altogether - run the fix afterwards. If this does not work, you have to switch around.

Search might have helped you by the way.

schlumpf:
Correction: A 132 error can be _everything_. It is a generic "something went wrong" error.

Ascathos:
That "0x007B31F8" is often in connection to the texture problem. It might give him a lead.

Navigation

[0] Message Index

[#] Next page
Go to full version