Jorge,

It would seem that I am having a problem having to fight this error. NextStart exits immediately and presents me an OK dialog box with Error: Access Violation in it. It would seem that this happens whenever I try to view a menu however I cannot recreate it every time.

What exactly is NextStart trying to access. A memory location?

I'd like to help any way I can.

What NextSTART version are you using? Not the latest beta?

[quote="RIP"]Jorge,

It would seem that I am having a problem having to fight this error. NextStart exits immediately and presents me an OK dialog box with Error: Access Violation in it. It would seem that this happens whenever I try to view a menu however I cannot recreate it every time./quote]

I too am having this problem. Any workarounds?

And none of you have answered my question: which NextSTART version are you using? Is it the latest beta?

You can check the NextSTART version you are using (including the build number) by opening NextSTART Preferences and clicking on the little version number at the bottom right corner of the About tab. This will open the Version Information dialog.

I downloaded NextStart/WorkShelf yesterday and im very impressed, but since today this error started to appear for me, too.

But for me it seems, that WorkSHelf is producing this error (using processExplorer, i know the error window belongs to WorkShelf).

I had this error several times today. Sometimes i dont have it for hours, but then I get it everytime I start WorkShelf or some minutes later.

Anyone know how to fix it?

I'm using
Nextstart 4.02.0339
WorkShelf 2.02.0533

error:
http://img47.imageshack.us/img47/3626/erroroh8.jpg

Are you running Windows XP (if so 32 or 64 bit) or Vista (if so 32 or 64 bit)?

cef100

This is an old thread, and, noticing how nobody ever replied to my question about the NextSTART version and the utter lack of detail in most posts, I would like to point everybody to the Art of Reporting Bugs article right here in the Winstep Forums. It makes a nice reading and gives some insight into what is needed to troubleshoot problems.

This said, an Access Violation usually occurs when a program tries to read memory that has already been freed or that doesn't belong to it. It could be anything, from a bug in the program itself, to a bug in, for instance, an external shell extension. Since only a handful of users seem to run into this problem, I would suspect the later (i.e.; something outside WorkShelf has a problem and, when it crashes, manages to bring WorkShelf down as well). You can read about a problem similar to this in the Crashing when opening a Control Panel shelf/menu? Read this! thread, where the culprit turned out to be a buggy Logitech Control Panel applet.

Bleppo, can you try to find a pattern to this error, that is, are you doing something specific when it happens or is it always random? What modules do you have running? If you close some of them (you will need to remove the in-shelf and in-dock versions for this to work) does the error go away? Does this happen regardless of the current theme you are using?

old thread indeed.
I just started having this problem and i would like to point out to all that it is important to know what kind of hardware you are using ( as i suspect this one is hw driven)
and of course what OS and any other relevant bits you think we might find interesting.
Now. my problem and solution.
XP sp2 updated.
Asus M2N32SLI dlx
ATI Radeon X1650 7.14 drivers
NS WS was just shutting itself off, sometimes i would get the unamed access error dialog box , sometimes i would just not have my nexus dock up and running etc.
my solution was to uninstall Nvidea NAM for this chipset and mobo. Network Access Manager is a problem for ALL asus mobos with NV shitsets and gigabit LAN going back to 2004 and its still a problem now.
so if you have nvidea chipsets, have a look at this component and UNINSTALL it as it is NOT required to run anypart of your OS or hardware.
Im happy again
Hi Jorge, i should start lurking here hehe. I miss teh IRC channle tho, have to tell you .
THanks
s

Hmm, i have an Asus MoBo with nvidia chipset as well and am getting intermittant issues with what apears to be network "timeouts" and Ws seems to "die". I'll look for the Nvidia NAM and see if I can solve my issues if I can find it to uninstall it.

Thanks for the detailed info

cef100

P.S.

Ok, from looking and reading this isn't the source of my problem, cause it isn't installed. for those that might not know Nvidia NAM is apparently Nvidia's attempt at a firewall, came with the Nvidia chipset software; and best I can tell, is garbage as essjay indicated. So, I'll keep looking for where my issues are coming from .