Page 1 of 1

Standalone Crash

Posted: Thu Feb 16, 2012 8:54 pm
by xfratboy
I'm wondering if something is wrong with my computer or my friend's. I've never had this problem on my computer, but whenever I send a friend a program to look at, she can't open it. Anything I build and send to her causes her to get a fatal windows error 0xc0000005. The link below is just an example. It is just a single button that answers "hello world" but even this will crash on her computer. Works fine on every computer I've tested it on.

http://dl.dropbox.com/u/17067840/test.zip

Re: Standalone Crash

Posted: Thu Feb 16, 2012 9:12 pm
by Mark
Hi,

What are the specifications of your friend's computer? I used to have a video card in my PC that consistently crashed Revolution. When I replaced the mother board with one that had an AGP slot, I could use an AGP card and the problem was solved.

Kind regards,

Mark

Re: Standalone Crash

Posted: Thu Feb 16, 2012 9:15 pm
by xfratboy
It's just one of those HP desktop rigs running Vista Home Premium (32bit).

Re: Standalone Crash

Posted: Sat Feb 18, 2012 3:32 pm
by doc
Hey xfratboy, I tried your test app on two machines...

Toshiba Laptop:
32 Bit Vista Home Premium/AMD Dual Core/ATI Radeon Graphics

HP Desktop:
64 Bit Win 7 Home Premium/AMD Semipron/NVIDIA GeForce Graphics

It ran without any problems on both.

Best regards,
Doc

Re: Standalone Crash

Posted: Sat Feb 18, 2012 8:23 pm
by Mark
Hi,

So, what are the specs of those HP rigs?

Mark

Re: Standalone Crash

Posted: Mon Feb 20, 2012 1:59 am
by mwieder
The test stack works fine here on XP as well. It's certainly tempting to blame this on Vista...

Does she have UAC turned on? Is she logged on as an admin user or a serf? Does Vista have compatibility mode settings? Where on her computer is the program downloaded to?

Re: Standalone Crash

Posted: Tue Feb 21, 2012 7:47 am
by AndyP
Hi,
I've had this problem before and The most common reason for this 0xc0000005 error is because of corrupt or outdated entries in the windows registry.
It can also be caused by malware infections, and memory module problems

Try these steps.

1. Make sure that Vista is up to date with the all the latest patches etc.

2. Use a registry cleaner. CCleaner has one built in and the program is Free.http://www.piriform.com/ccleaner

3. Run an anti-malware program. This is great and also Free. http://www.malwarebytes.org/products/malwarebytes_free

3. I also remember that Symantics ant-virus can throw up these problems?

Let us know how you get on.