General discussions, bugs, support, suggestions
Brian Collins
Posts: 6 Joined: 14.06.2013 12:24
Post
by Brian Collins » 14.06.2013 12:34
Having just installed to test before purchase, Helicon Remote will not start. The event log shows an Access Violation error (bug!) c0000005 :
Code: Select all
+ System
- Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2013-06-14T09:18:58.000000000Z
EventRecordID 2100
Channel Application
Computer Brian-Surface
Security
- EventData
HeliconRemote.exe
0.0.0.0
51598faf
ig7icd32.dll
9.17.10.2867
50635085
c0000005
0003b60e
12a0
01ce68e0337df24e
C:\Program Files (x86)\Helicon Software\Helicon Remote\HeliconRemote.exe
C:\windows\SYSTEM32\ig7icd32.dll
715a2dcb-d4d3-11e2-be76-6045bdeecd0b
This is 100% reproducible
Brian
Brian Collins
Posts: 6 Joined: 14.06.2013 12:24
Post
by Brian Collins » 20.06.2013 14:35
Sorry about the delay.
Nope - #266 is no better:
Code: Select all
Log Name: Application
Source: Application Error
Date: 20/06/2013 12:31:16
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Brian-Surface
Description:
Faulting application name: HeliconRemote.exe, version: 2.6.6.0, time stamp: 0x51c2b278
Faulting module name: ig7icd32.dll, version: 9.17.10.2867, time stamp: 0x50635085
Exception code: 0xc0000005
Fault offset: 0x0003b60e
Faulting process ID: 0x1078
Faulting application start time: 0x01ce6da9ab4eb78b
Faulting application path: C:\Program Files (x86)\Helicon Software\Helicon Remote\HeliconRemote.exe
Faulting module path: C:\windows\SYSTEM32\ig7icd32.dll
Report ID: eab495fb-d99c-11e2-be7e-6045bdeecd0b
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-06-20T11:31:16.000000000Z" />
<EventRecordID>4484</EventRecordID>
<Channel>Application</Channel>
<Computer>Brian-Surface</Computer>
<Security />
</System>
<EventData>
<Data>HeliconRemote.exe</Data>
<Data>2.6.6.0</Data>
<Data>51c2b278</Data>
<Data>ig7icd32.dll</Data>
<Data>9.17.10.2867</Data>
<Data>50635085</Data>
<Data>c0000005</Data>
<Data>0003b60e</Data>
<Data>1078</Data>
<Data>01ce6da9ab4eb78b</Data>
<Data>C:\Program Files (x86)\Helicon Software\Helicon Remote\HeliconRemote.exe</Data>
<Data>C:\windows\SYSTEM32\ig7icd32.dll</Data>
<Data>eab495fb-d99c-11e2-be7e-6045bdeecd0b</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Brian
Stas Yatsenko
Posts: 3825 Joined: 06.05.2009 15:05
Contact:
Post
by Stas Yatsenko » 21.06.2013 14:20
Thanks Brian. The faulty module is ig7icd32.dll, which is a part of Intel's video driver software. Try updating / reinstalling the driver.
Brian Collins
Posts: 6 Joined: 14.06.2013 12:24
Post
by Brian Collins » 21.06.2013 21:01
Thanks Stas,
Unfortunately Windows Update suggests I am already on the latest driver. But I am traveling this week so I shall investigate more deeply on the Intel support site when I return.
Brian
Brian Collins
Posts: 6 Joined: 14.06.2013 12:24
Post
by Brian Collins » 21.06.2013 21:22
Actually, I just went on a hunt and found a later driver - and that appears to work fine. Thanks for the analysis - I should have worked it out for myself.
But this is for my new Surface Pro, which I think is an ideal machine for Helicon. So others may have a similar problem with the shipped driver, and this thread may help them.