Access violation in beta 8

57 views
Skip to first unread message

cyoram

unread,
Feb 4, 2010, 3:24:12 AM2/4/10
to WhatsRunning
My system is Windows XP Home Edition SP3, with IE 8.
I just downloaded WR 3.0 BETA 8, and while trying to rum it, got the
following errors:

Access violation at address 0072CE77 in module 'WhatsRunning.exe'.
Read of address 0000000C.
(after clicking a desktop icon)

What's wrong ?

sjc...@googlemail.com

unread,
Mar 2, 2010, 11:20:15 AM3/2/10
to WhatsRunning
Me Too .. when I try and run it on Windows 7 Ultimate .. I get

"Access violation at address 00763E1B ine module 'WhatsRunning.exe'.
Read of address 0000000C

I have loaded it twice and same thing. Im also running AVG and the
normal Windows firewall.

ChristerF

unread,
Mar 2, 2010, 12:48:25 PM3/2/10
to WhatsRunning
Can you send me the whatsrunning.log file that is in the application
directory? That might give me a clue on what is wrong on your system.

/Christer

On Mar 2, 8:20 am, "sjc8...@googlemail.com" <sjc8...@googlemail.com>
wrote:

Jack

unread,
Apr 4, 2010, 9:41:43 PM4/4/10
to WhatsRunning
I got this same error recently WhatsRunning 3 beta still has access
violations without a FIX yet!
WhatsRunning should be called Why Isn't It Running
When is a fix coming? Why has this been let remain, broken code?

On Mar 2, 12:20 pm, "sjc8...@googlemail.com" <sjc8...@googlemail.com>
wrote:

ChristerF

unread,
Apr 5, 2010, 1:33:43 AM4/5/10
to WhatsRunning
Jack (and others)

Sorry for a long time with no updates.

Unfortunately this is a really tricky problem. The root cause of this
issue seems to be an issue with the WMI subsystem which seems to be
far too common out there in the wild.

The core problem here is this line:
WBEM_E_INVALID_CLASS:Win32_PerfFormattedData_PerfProc_Process

This means basically that the WMI class can't get instantiated for
some reason.

If you would run Microsofts own diagnostic utility, it would find that
your installation has an issue with instantiating certain classes:
http://www.microsoft.com/downloads/details.aspx?FamilyID=d7ba3cd6-18d...

The previous What's Running version (2.2) didn't use WMI at all, and
that is why that version may work for people who have a malfunctioning
WMI subsystem.


I would be happy if any daring soul would try to fix his WMI subsystem
using any of the instructions available below and report back if it
was successful:
http://myitforum.com/cs2/blogs/socal/archive/2007/08/22/troubleshooting-wmi-with-wmidiag.aspx
http://blogs.technet.com/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx
http://www.microsoft.com/events/series/detail/webcastdetails.aspx?seriesid=88&webcastid=312
http://whitepapers.zdnet.com/abstract.aspx?docid=382991


Thanks for your patience!

/Christer

Reply all
Reply to author
Forward
0 new messages