Topic: VWS Suddenly Quits on Windows 7

[WeatherBeacon]

I've been running VWS 14.01 for several years on the same Windows 7 desktop. A few weeks ago VWS stopped inexplicably. When I restart it, it runs for about 8 minutes and stops with the same error message (shown in attached images):

 [ You are not allowed to view attachments ]  [ You are not allowed to view attachments ]

I would appreciate any insight into the cause of this problem.

Thanks much!

[waiukuweather]

the C0000005 is the clue
that is a memory access violation
usually when a variable is accessed in memory but it has not been loaded into memory yet or has gone from memory

I can only suggest deleting the settings files and starting over?

[longmire]

Hi, Keven! Steve here - I finally upgraded to 15p03 in mid 2016 because of repeated app crashes under Win 7 64-bit. Everything was frighteningly stable UNTIL - a Microsoft update decided to "protect" me from elevation of privileges and hosed my wininet.dll. This made VWS   S   L  O  W - "Rapid Fire" updated every 3 minutes instead of every three seconds! I had to uninstall the last two windows updates just to get VWS to run again. So your problem may not have anything to do with VWS but rather with Microsoft's update arms race instead.

My approach was to clone the wounded drive and then use the clone to tinker with fixes. You -might- want to clone and upgrade to VWS 15, as that version has proven far more stable than any of its predecessors for me.

That's the best I can offer until we find "the russian hackers" who broke our vws!

-Steve

[longmire]

PS - be sure to check the \setup\summary and \setup\summary1 directories for BIN files with impossible date names (22012312359 - for example) as well as "future" bin files like 201712.bin. My vws nearly always creates these sorts of files when it crashes, and if you don't delete them first- vws will again crash every time you launch it until you do.

You should check dbase.csv as well for RecDate values like these bad filenames because if they are there, vws databases won't update until after the last bad date passes.

Steve

[WeatherBeacon]

PS - be sure to check the \setup\summary and \setup\summary1 directories for BIN files with impossible date names (22012312359 - for example) as well as "future" bin files like 201712.bin. My vws nearly always creates these sorts of files when it crashes, and if you don't delete them first- vws will again crash every time you launch it until you do.

You should check dbase.csv as well for RecDate values like these bad filenames because if they are there, vws databases won't update until after the last bad date passes.

Steve

Hi, Steve! Good to "hear your voice" again!

Thanks for the very helpful information. I'll give yor suggestions a try.

Regards,

-- Kevin

[WeatherBeacon]

That's the best I can offer until we find "the russian hackers" who broke our vws!

-Steve