ASP crashes after splash screen.

[csprucefield]

Windows 7, no changes to system.
All of a sudden, thee ASP refuses to run after the splash screen.
Everything else works just fine.
Have uninstalled, reinstalled, cleared out registry, cleared out all settings in appdata, forcing a complete reinstall/startup.
The initialisation works, but it crashes immediately after, and following this, it just dies after the splash screen.

What's quite interesting is that it thinks there are no physical memory, despite there being 10+ Gb free
All other applications runs fine, and a memory test comes out clean.

Attached the crash log files.
If this isn't solved quickly, i will have to go lightroom.

AfterShotPro caused an Access Violation (0xc0000005)
in module AfterShotPro.exe at 0023:00000000.

Exception handler called in main.
Error occurred at 2013-16-11 17-31-20.
C:\Program Files (x86)\Corel\Corel AfterShot Pro\build\AfterShotPro.exe, run by csprucefield.
Application vers.: 1.2.0.7
Product Name: AfterShot Pro
Language: en
App Path: C:/Program Files (x86)/Corel/Corel AfterShot Pro/build/AfterShotPro.exe
System Home: C:/Program Files (x86)/Corel/Corel AfterShot Pro/supportfiles
User Home: C:/Users/csprucefield/AppData/Local/Corel/AfterShot Pro
Prefs Home: \HKEY_CURRENT_USER\Software\Corel\AfterShot Pro
Processors: 8
CPU Threads: 8
RAM: 16284 MB
SIMD Version: SSE2
OS Name: Microsoft Windows 7 Ultimate Edition Service Pack 1
OS Version: 6.1 (Build 7601)
Processor speed: 3.6 GHz
System architecture: x64
23% memory in use.
0 MBytes physical memory.
0 MBytes physical memory free.
0 MBytes paging file.
0 MBytes paging file free.
0 MBytes user address space.
3923 MBytes user address space free.
Write to location 00000000 caused an access violation.

[afx]

Windows 7, no changes to system.

I doubt that.
I guess there was an update to the video drivers as AS quits setting up the OpenCL interface, that is pretty much clear on the last line of the log.
And the Windows dump info shows an access violation at address 0, so AS tries to dereference a NULL pointer.

Have uninstalled, reinstalled,

Why should that fix anything?
I never understood why people thing a re-install is a solution....
After all, anything specific is set up in the user settings, the install does not change them.

What's quite interesting is that it thinks there are no physical memory, despite there being 10+ Gb free

AS does not say anything about memory. You misinterpret the Windows crash info.

The only thing I could think of to get that fixed on the AS side would be to disable OpenCL.
But, it happens so early in the setup phase that I doubt any settings are read yet.

The other thing you could tried is to get a newer video driver directly from the card vendor or revert to an older one.

cheers
afx

[csprucefield]

Windows 7, no changes to system.

I doubt that.
I guess there was an update to the video drivers as AS quits setting up the OpenCL interface, that is pretty much clear on the last line of the log.
And the Windows dump info shows an access violation at address 0, so AS tries to dereference a NULL pointer.

No, there has not been any updates on the system since last time i ran the ASP.
Even some of the more iffy ones that relies heavily on things like CUDA, and is known to throw a strop for any reason, works.

I don't think you should be talking down to me as you are, telling me what/not happened on my system.
I've been a user of bibble since long before it sadly became corel, and know quite a few of it quirks on both Windows and Linux, and managed to resolve quite a few of them, but this one has me stumped due to the unusal behaviour.
Not all of us that show up here are corel or otherwise computer newbies...

Have uninstalled, reinstalled,

Why should that fix anything?
I never understood why people thing a re-install is a solution....
After all, anything specific is set up in the user settings, the install does not change them.

On a windows system, that may fix any kind of nasty problems, especially ones down to registry issues.
As a Linux SA, I am very well familiar with the fact that doing a reinstall will fix nothing, but please don't apply Linux knowledge and expected behaviors to a Windows system - they are two very different breeds and architechtures, albeit having quite a bit in common.

What's quite interesting is that it thinks there are no physical memory, despite there being 10+ Gb free

AS does not say anything about memory. You misinterpret the Windows crash info.

You clearly misread it yourself, as this is not a windows crash log, but the the ASP crash log, stating that there are no memory available, despite there being plenty of memory left.
The last line, does indicate a null pointer exception, and would be something internal to the software, making me think that there is a bug, triggered by something, for some reason. My thinking is that the zero memory reported, is an effect of this, with some internal pointer to some data array gone bonkers.

RAM: 16284 MB
23% memory in use.
0 MBytes physical memory.
0 MBytes physical memory free.
0 MBytes paging file.
0 MBytes paging file free.
0 MBytes user address space.
3923 MBytes user address space free.
Write to location 00000000 caused an access violation.

The only thing I could think of to get that fixed on the AS side would be to disable OpenCL.

But, it happens so early in the setup phase that I doubt any settings are read yet.

See, this is exactly what worries me, that it happens so early on, that there has to be something fundamentally wrong in the startup of the application, and this is why i went here to look for some help, not being lectured with "your doing it wrong".
The application has been running fine since July, but stopped working a few days ago, crashing on the splash screen.

To my knowledge, and looking at updates, nothing has happened (been installed/removed, checking install and patch logs in windows update etc) since the last good start, bar reinstalling the application to get a fresh registry set, which is a known source of issues.

The other thing you could tried is to get a newer video driver directly from the card vendor or revert to an older one.

Running the latest driver from Nvidia already, so that's a no.

cheers
afx

Now, if someone at Corel, could take a look at the crash logs supplied, and tell me what's going on here, that would be useful. especially since there are previous cases where it seems that the ASP has crashed in a similar manner, at the splash screen, in version 1,0 and lately, on Win 8.1.

[afx]

Windows 7, no changes to system.

I doubt that.
I guess there was an update to the video drivers as AS quits setting up the OpenCL interface, that is pretty much clear on the last line of the log.
And the Windows dump info shows an access violation at address 0, so AS tries to dereference a NULL pointer.

No, there has not been any updates on the system since last time i ran the ASP.
Even some of the more iffy ones that relies heavily on things like CUDA, and is known to throw a strop for any reason, works.

Just because some other tool works does not mean AS works...
And it is not necessarily only direct updates of the driver that could screw up the underlying driver communication.
A shared library involved with the driver communication on the system could lead to such issues.

I don't think you should be talking down to me as you are, telling me what/not happened on my system.

I not talking down at you, I just question your statement.
You claim to be A Linux SA, then you should know that all users miss tiny important bits when reporting errors because of wrong assumptions

Have uninstalled, reinstalled,

Why should that fix anything?
I never understood why people thing a re-install is a solution....
After all, anything specific is set up in the user settings, the install does not change them.

On a windows system, that may fix any kind of nasty problems, especially ones down to registry issues. [/quote]
That rarely happens nowadays, we are not in NT times anymore. And AS is definitely not one of the broken apps that has only one set of settings for the whole machine.
I've been playing with more AS and Bibble betas than I could count and never ever was there something fixable by a re-install.

As a Linux SA, I am very well familiar with the fact that doing a reinstall will fix nothing, but please don't apply Linux knowledge and expected behaviors to a Windows system - they are two very different breeds and architechtures, albeit having quite a bit in common.

I actually had more Linux application re-installs to fix things than on Windows. All because of weird dependency crap that needed a re-run of the initialization routines of the packages to fix.

What's quite interesting is that it thinks there are no physical memory, despite there being 10+ Gb free

AS does not say anything about memory. You misinterpret the Windows crash info.

You clearly misread it yourself, as this is not a windows crash log, but the the ASP crash log, stating that there are no memory available, despite there being plenty of memory left. [/quote]
AS does not write a crash log. It only writes the regular log file. And the last interesting tidbit in there is the statement about setting up the Open CL Manager, nothing about memory at all.
The memory info is some Windows crash info thing not generated by AS itself.

The application has been running fine since July, but stopped working a few days ago, crashing on the splash screen.

To my knowledge, and looking at updates, nothing has happened (been installed/removed, checking install and patch logs in windows update etc) since the last good start, bar reinstalling the application to get a fresh registry set, which is a known source of issues.

So it was running fine after the MS patchday last week?
Do not assume just because there was no explicit driver update that nothing in the underlying system was changed.

cheers
afx

[proshotphoto]

I have the same issues

DId you resolve your problem?

[afx]

I have the same issues

Hard to say without the aftershot log.

cheers
afx

[csprucefield]

I have the same issues

DId you resolve your problem?

Nope. ASP is still stone cold DEAD..,..

[csprucefield]

See these little attachments, on m y first mail ....

ATTACHMENTS
2013-16-11 17-31-20-LOG.TXT
(66.16 KiB) Downloaded 9 times
2013-16-11 17-31-20-DEBUG.TXT
(1.23 KiB) Downloaded 6 times
AfterShotPro.log
(1.23 KiB) Downloaded 10 times

These are the DEBUG and other logs that ASP dumps in
C:\Users\{username]}\AppData\Local\Corel\AfterShot Pro\CRASHLOG\* and
C:\Users\{username]}\AppData\Local\Corel\AfterShot Pro\*

Seems that i won't get any kind of useful answer here, and stick with the lightroom.
At least, that one works, even if it may not have all the features, and having to re-import everything again, which is a major PITA, but what do you do in an emergency?

The quality of the support, has definitely gone down since Corel took over.

I suspect that they will have lost a long time customer from now.

[SteveCase]

Are you really using those 2 older video cards at the same time?