10.17E Memory Access Violation

Ask a Question
1

Everything was fine until I upgraded to 10.17e from 10.16x. Now when baro read runs there is a Windows memory access violation. These errors pile up over a period of time. I dropped back to 10.17d debug and everything seems fine. I checked the baro read version number and it has been the same for a while. So it must be the changes in wdisplay.exe that caused the problem. The area it is trying to read is reserved for my system board. Any ideas Brian?

Thanks,

Eric :?

2

Hi
what weather statiion type?
strange that 10.17d is ok…i dont remember changing anything to do with the barometer…
maybe try 10.17e agian?

3

Hi Brian,
I have a Dallas 1 wire Ver 3 with a AAG barometer and a modified LaCrosse rain gauge. I will write down the actual address of the violation and post it here.

Thanks,
Eric

4

hi
ah, the aag barometer…
try a reboot of the pc…
its a bit tricky that reading of the aag barometer…
and or also try the aag test program and see if you can reset it

but a PC reboot should hopefully fix it up

i keep intending to improve on the whole thing…but always get bogged down with other things…

5

Brian,
I tried a couple of reboots with ver 10.17e but still got the following error;

“BaroReader.exe caused a memory access violation at address 0032AF35
Read of address 0032AF35”

This happens every time the baroreader runs. With 10.17d everything runs normal until I exit WD, then I get this:

EurekaLog 4.5.5

Application:

1.1 Start Date : Fri, 10 Sep 2004 23:45:51 -0600
1.2 Name/Description: Weather Display
1.3 Version Number : 10.17.0.0
1.4 Parameters :

Exception:

2.1 Date : Sun, 12 Sep 2004 00:51:37 -0600
2.2 Address: 004568FC
2.3 Module : WeatherD.exe
2.4 Type : EAccessViolation
2.5 Message: Access violation at address 004568FC in module ‘WeatherD.exe’. Read of address 00000060.

Active Controls:

3.1 Form Class : Static
3.2 Form Text :
3.3 Control Class:
3.4 Control Text :

Computer:

4.1 Name : SHOPNEW
4.2 User : Snide
4.3 Total Memory: 479 Mb
4.4 Free Memory : 194 Mb
4.5 Total Disk : 74.52 Gb
4.6 Free Disk : 67.64 Gb

Operating System:

5.1 Type : Microsoft Windows XP
5.2 Build # : 2600
5.3 Update : Service Pack 2
5.4 Language: English (United States)

Call Stack Information:

|Address |Module |Unit |Class |Procedure/Method |Line |

|7C910961|ntdll.dll | | |RtlReleasePebLock | |
|7C90EAF5|ntdll.dll | | |KiUserApcDispatcher| |
|7C9134D1|ntdll.dll | | |RtlValidSid | |
|7C90253A|ntdll.dll | | |memmove | |
|77F643CB|SHLWAPI.dll | | |SHRegGetValueW | |
|77F643D8|SHLWAPI.dll | | |SHRegGetValueW | |
|00BDE19E|WeatherD.exe|MainUnit.pas |TMainForm |Timer4Timer |21333|
|77D4BCC7|user32.dll | | |DispatchMessageA | |
|77D4BCBD|user32.dll | | |DispatchMessageA | |
|004D8961|WeatherD.exe|BMDThread.pas|TBMDThread|Destroy |361 |

Scratching my head,
Eric :cry:

6

I have the same problem with my AAG 1 wire Barometer. Memory access violation with every Baro read in the first version of 10.17. I had to drop back to 10.16v for normal operation.

7

Neverlost,

I may need to do the same thing but I dont have a copy of 10.16V

Brian, is there somewhere on your site I can download an older version like this?

Thanks,
Eric

8

ahh, thats the clue…its a change in 10.17e
so, what the change is the timming of 1 wire reads…
i put in a delay…for slow pc’s…
that dealy is use adjustable
so, in the dallas 1 wire setup, set the polling delay for wind direction/temperature, to zer0
that should fix things

i will set that to zero by default, so other aag baro people are not affected

if you dont see that settings, then download a fresh 10.17e version

9

Good News,

1 wire station up and running with 10.17e. Thanks so much Brian. Also got my hobby board lightning counter added today!

Eric