Forums WoW Modding Support Archives WoWModding Support Archives [DiscordArchive] Does somebody know why wow can crash with this error 0xC0000005 (ACCESS_VIOLATION) at 0023:007CC41F

[DiscordArchive] Does somebody know why wow can crash with this error 0xC0000005 (ACCESS_VIOLATION) at 0023:007CC41F

[DiscordArchive] Does somebody know why wow can crash with this error 0xC0000005 (ACCESS_VIOLATION) at 0023:007CC41F

rektbyfaith
Administrator
Find
0
06-12-2022, 07:07 PM
#1
Archived author: Simple_Spectr • Posted: 2022-06-12T19:07:56.771000+00:00
Original source

Does somebody know why wow can crash with this error 0xC0000005 (ACCESS_VIOLATION) at 0023:007CC41F
When trying teleport to converted map (Draenor, Pandaria, Broke Isles etc from Legion 7.3.5). In noggit everything works fine. All maps, vmaps, mmaps. dbcs extracted to server, checked it. Idk what the problem. Who know?
Reply
Reply
rektbyfaith
06-12-2022, 07:07 PM #1

Archived author: Simple_Spectr • Posted: 2022-06-12T19:07:56.771000+00:00
Original source

Does somebody know why wow can crash with this error 0xC0000005 (ACCESS_VIOLATION) at 0023:007CC41F
When trying teleport to converted map (Draenor, Pandaria, Broke Isles etc from Legion 7.3.5). In noggit everything works fine. All maps, vmaps, mmaps. dbcs extracted to server, checked it. Idk what the problem. Who know?

Reply
Reply
rektbyfaith
Administrator
Find
0
06-12-2022, 07:10 PM
#2
Archived author: <o> • Posted: 2022-06-12T19:10:36.237000+00:00
Original source

use this page for wow crash codes, it has a lot of useful information:
<https://wowdev.wiki/Client_Error_Analysis>

the value you're after is the address, not the error itself. In your case it's "0023:007CC41F", we can look the last part of that up on this page and we get this:

<https://wowdev.wiki/Client_Error_Analysis#0x007CC41F_read_0x.2A.2A.2A.2A.2A.2A.2A.2A_.28bogus_value.29>
Reply
Reply
rektbyfaith
06-12-2022, 07:10 PM #2

Archived author: <o> • Posted: 2022-06-12T19:10:36.237000+00:00
Original source

use this page for wow crash codes, it has a lot of useful information:
<https://wowdev.wiki/Client_Error_Analysis>

the value you're after is the address, not the error itself. In your case it's "0023:007CC41F", we can look the last part of that up on this page and we get this:

<https://wowdev.wiki/Client_Error_Analysis#0x007CC41F_read_0x.2A.2A.2A.2A.2A.2A.2A.2A_.28bogus_value.29>

Reply
Reply
rektbyfaith
Administrator
Find
0
06-12-2022, 07:10 PM
#3
Archived author: Simple_Spectr • Posted: 2022-06-12T19:10:54.045000+00:00
Original source

Thanks
Reply
Reply
rektbyfaith
06-12-2022, 07:10 PM #3

Archived author: Simple_Spectr • Posted: 2022-06-12T19:10:54.045000+00:00
Original source

Thanks

Reply
Reply
rektbyfaith
Administrator
Find
0
06-12-2022, 07:10 PM
#4
Archived author: Titi • Posted: 2022-06-12T19:10:55.269000+00:00
Original source

0x007CC41F read 0x******** (bogus value)
Your WDL file is broken. The WotLK parser is very picky about the files it reads. It assumes that if there is a WDL#MWMO chunk as the first chunk, the WDL#MWID and WDL#MODF chunks follow in that order. Otherwise, or after the three, it *will* be WDL#MAOF. In your case, the first three have been fine or not present, but there was no valid WDL#MAOF chunk.

Alternatively, your WDL#MAOF chunk has a bad offset in one of the entries.
Reply
Reply
rektbyfaith
06-12-2022, 07:10 PM #4

Archived author: Titi • Posted: 2022-06-12T19:10:55.269000+00:00
Original source

0x007CC41F read 0x******** (bogus value)
Your WDL file is broken. The WotLK parser is very picky about the files it reads. It assumes that if there is a WDL#MWMO chunk as the first chunk, the WDL#MWID and WDL#MODF chunks follow in that order. Otherwise, or after the three, it *will* be WDL#MAOF. In your case, the first three have been fine or not present, but there was no valid WDL#MAOF chunk.

Alternatively, your WDL#MAOF chunk has a bad offset in one of the entries.

Reply
Reply
rektbyfaith
Administrator
Find
0
06-12-2022, 07:12 PM
#5
Archived author: Simple_Spectr • Posted: 2022-06-12T19:12:23.617000+00:00
Original source

0xC0000005 (ACCESS_VIOLATION) at 0023:007CC41F
Reply
Reply
rektbyfaith
06-12-2022, 07:12 PM #5

Archived author: Simple_Spectr • Posted: 2022-06-12T19:12:23.617000+00:00
Original source

0xC0000005 (ACCESS_VIOLATION) at 0023:007CC41F

Reply
Reply
rektbyfaith
Administrator
Find
0
06-12-2022, 07:12 PM
#6
Archived author: Simple_Spectr • Posted: 2022-06-12T19:12:31.420000+00:00
Original source

Still crash without wdl
Reply
Reply
rektbyfaith
06-12-2022, 07:12 PM #6

Archived author: Simple_Spectr • Posted: 2022-06-12T19:12:31.420000+00:00
Original source

Still crash without wdl

Reply
Reply
rektbyfaith
Administrator
Find
0
06-12-2022, 07:14 PM
#7
Archived author: Simple_Spectr • Posted: 2022-06-12T19:14:32.018000+00:00
Original source

I did offsetfix, mfbo fix etc
Reply
Reply
rektbyfaith
06-12-2022, 07:14 PM #7

Archived author: Simple_Spectr • Posted: 2022-06-12T19:14:32.018000+00:00
Original source

I did offsetfix, mfbo fix etc

Reply
Reply
rektbyfaith
Administrator
Find
0
06-12-2022, 07:14 PM
#8
Archived author: Simple_Spectr • Posted: 2022-06-12T19:14:39.367000+00:00
Original source

Doesnt help
Reply
Reply
rektbyfaith
06-12-2022, 07:14 PM #8

Archived author: Simple_Spectr • Posted: 2022-06-12T19:14:39.367000+00:00
Original source

Doesnt help

Reply
Reply
rektbyfaith
Administrator
Find
0
06-12-2022, 07:19 PM
#9
Archived author: Simple_Spectr • Posted: 2022-06-12T19:19:43.044000+00:00
Original source

My fault, yes, it works without wdl. Thanks
Reply
Reply
rektbyfaith
06-12-2022, 07:19 PM #9

Archived author: Simple_Spectr • Posted: 2022-06-12T19:19:43.044000+00:00
Original source

My fault, yes, it works without wdl. Thanks

Reply
Reply
Recently Browsing
 
Recently Browsing