Access Violation 1.3.6.2

Feared_1 · Post by **Feared_1** » Mon Dec 19, 2011 5:59 pm

---- Battlezone II Log File ----
//=====================================================
App version: bzone 1.3.6.2 Public Beta Jul 29 2011 21:43:22
Windows version: Windows Version: 6.1.7601 'Service Pack 1' PlatformID=2

Last few battlezone.log lines (may or may not be relevant):
DIAG|            runcodes:159  |11:35:17|1390070|[View] Entering run code [COCKPIT]
DIAG|            runcodes:159  |11:35:17|1390074|[Main] Entering run code [MISSION]
DIAG|              icroot:193  |11:35:17|1390077|Root window now 1366x768
DIAG|            runcodes:159  |11:35:17|1390080|[Mission] Entering run code [RUN]
WARN|          GameObject:3549 |11:35:19|1391282|User team # suspect. Changed 6 -> 1
DIAG|      STJoinHandlers:469  |11:35:19|1391294|-- Resynchronized gamestate to server at timestep 47
WARN|          GameObject:3549 |11:42:02|1795158|User team # suspect. Changed 6 -> 1
DIAG|      STJoinHandlers:469  |11:42:03|1795172|-- Resynchronized gamestate to server at timestep 4084
(done)

Exception code: C0000005 (ACCESS VIOLATION) READING from 00000000h
Message :  Exception
Error occurred at 12/19/2011 11:56:00.
C:\Program Files (x86)\Battlezone II\bzone.exe, run by Adam.
C:\Program Files (x86)\Battlezone II\bzone.exe, run by Adam.
CPU: 2 processor(s), Intel(R) Core(TM)2 Duo CPU     T6400  @ 2.00GHz
     Intel64 Family 6 Model 23 Stepping 10
Process Memory :   1375 MB free out of   2048 MB total
Physical memory:   2427 MB free out of   4059 MB total
Page(swap) file:   5589 MB free out of   8115 MB total
This exe is using 290 MB (104 MB dlmalloc), peak use 313 MB

Fault address:  012CD168 01:0006C168 C:\Program Files (x86)\Battlezone II\bzone.exe

Registers:
EAX:00000008
EBX:00000003
ECX:00000000
EDX:00000000
ESI:1614A34C
EDI:1614A3B4
CS:EIP:0023:012CD168
SS:ESP:002B:007ADD40  EBP:007ADDA4
DS:002B  ES:002B  FS:0053  GS:002B
Flags:00210202

Call stack:
Address  Offset1  Offset2  Module              SourceFile
012CD168 +0006D168 00000084 bzone            (bzone): : Carrier::TriggerSelected

012D5716 +00075716 00000018 bzone            (bzone): : Craft::TriggerCarrierWeapons

012D5616 +00075616 00000166 bzone            (bzone): : Craft::SimulateCarrier

012D54A7 +000754A7 00000559 bzone            (bzone): : Craft::Simulate

012F053B +0009053B 0000209E bzone            (bzone): : HoverCraft::Simulate

012B9A54 +00059A54 0000047C bzone            (bzone): : MissionHandler::State::RunState::Enter

012BAA60 +0005AA60 0000045C bzone            (bzone): : MissionHandler::State::RunState::Process

0145C87F +001FC87F 000001BF bzone            (bzone): : RunCodes::Process

012B8164 +00058164 0000001E bzone            (bzone): : MissionHandler::Process

0145C87F +001FC87F 000001BF bzone            (bzone): : RunCodes::Process

01463D74 +00203D74 00000064 bzone            (bzone): : Main::MessagePump

012AAE6D +0004AE6D 000004F1 bzone            (bzone): : HandledMain

012AAB1F +0004AB1F 000001A3 bzone            (bzone): : HandledMain

012A7AB7 +00047AB7 0000005E bzone            (bzone): : WinMain

0140B30F +001AB30F 00000191 bzone            (bzone): : strcat

758A339A +0001339A 00000012 kernel32         (kernel32): : BaseThreadInitThunk

76EF9ED2 +00039ED2 00000063 ntdll            (ntdll): : RtlInitializeExceptionChain

76EF9EA5 +00039EA5 00000036 ntdll            (ntdll): : RtlInitializeExceptionChain

I was just playing a DM on Volcano and randomly got this Access Violation, not sure what caused it.

Col Klink · Post by **Col Klink** » Thu May 24, 2012 5:17 pm

I wonder if the screen resolution had anything to do with the crash?

DIAG| icroot:193 |11:35:17|1390077|Root window now 1366x768

Does BZII support 1366?

Post by **GSH** » Thu May 24, 2012 5:24 pm

All versions of BZ2 1.3 have supported higher resolutions than 1.0-1.2 ever did. High resolutions are almost certainly not the issue here -- the callstack lists weapon code.

-- GSH

Zero Angel · Post by **Zero Angel** » Thu May 24, 2012 6:33 pm

BZ2 should support any widescreen resolution that the DirectX says it can handle. So I don't think resolutions are an issue.

I do notice a "User Team Suspect" warning in there. These errors and accompanying resyncs happened during pilot deaths whenever custom pilots (via pilotConfig) were implemented previously in VSR. However they should be much rarer now that it is not, but they still crop up every once in awhile and i'm trying to narrow down other causes for them. If you can provide any further details I might be able to develop a workaround for it in VSR.

As to the code that appears to be related to weapon code -- can you explain in more detail if there were any unusual weapons you picked up, the craft present and anything else that was out of the ordinary?

Zax · Post by **Zax** » Thu May 24, 2012 6:38 pm

Workarounds aren't always necessary, as even if an AV is occurring due to something you are NEVER meant to do in stock, it is a good idea to plug the hole in the ever lengthening quest to make bz2 bulletproof. Pun absolutely intended.

Zero Angel · Post by **Zero Angel** » Thu May 24, 2012 6:46 pm

The whole point of workarounds is to plug the holes until undesired behaviors or bugs get fixed 'upstream'. If your basement is flooding due to a faulty water line, do you put duct tape around the hole in the line to plug the leak temporarily, OR do you call the plumber? The smart answer is, you do both.

Zax · Post by **Zax** » Thu May 24, 2012 8:04 pm

Zero Angel wrote:The whole point of workarounds is to plug the holes until undesired behaviors or bugs get fixed 'upstream'. If your basement is flooding due to a faulty water line, do you put duct tape around the hole in the line to plug the leak temporarily, OR do you call the plumber? The smart answer is, you do both.

I move somewhere with a dry climate and do not concern myself with the flooding at all. Which is how I fixed my AV problem with dispenser class

Feared_1 · Post by **Feared_1** » Thu May 24, 2012 8:23 pm

I don't remember anything about this AV. It was from last December... check the date

Zax wrote:I move somewhere with a dry climate and do not concern myself with the flooding at all.

...analogous to quitting BZ2.

Zax · Post by **Zax** » Thu May 24, 2012 8:44 pm

Feared_1 wrote:I don't remember anything about this AV. It was from last December... check the date

Zax wrote:I move somewhere with a dry climate and do not concern myself with the flooding at all.
...analogous to quitting BZ2.

Or not using the part that AVs.

Ded10c · Post by **Ded10c** » Thu May 24, 2012 9:34 pm

...how can you keep finding topics to bump?

Zero Angel · Post by **Zero Angel** » Thu May 24, 2012 9:40 pm

Wow, the OP is dated Dec. 19, 2011.

BNG, huh?

Zax · Post by **Zax** » Thu May 24, 2012 10:15 pm

I will relent that "random" avs are harder to avoid or steer the ship around but more reproducible ones where the cause is obvious are easier to kind of ignore, unless that AV is particularly nasty (lobby crashes). Easiest to fix (easiest being referential) since reproduction is a big step in isolating and repairing.

General BlackDragon · Thu May 24, 2012 10:30 pm

Zero Angel wrote:Wow, the OP is dated Dec. 19, 2011.

BNG, huh?

Well, his name was "Bump n Go"

DarkCobra262 · Post by **DarkCobra262** » Thu May 24, 2012 11:13 pm

General BlackDragon wrote:
Zero Angel wrote:Wow, the OP is dated Dec. 19, 2011.

BNG, huh?

Well, his name was "Bump n Go"

lmao

Ded10c · Post by **Ded10c** » Fri May 25, 2012 3:20 pm

Right on both counts, it would appear.

Battlezone Forums

Access Violation 1.3.6.2

Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2

Re: Access Violation 1.3.6.2