Elements: Organiser crashes - "CRT not initialised"

  • 2
  • Problem
  • Updated 6 years ago
  • (Edited)
Program: Photoshop Elements 10
Operating system: Windows XP

I have just purchased this product. It successively found about 37 GB of photos on my hard disk. Unfortunately I can't proceed much further because Organiser can't run for more than one or two minutes without crashing. There does not seem to be any pattern to when in crashes relative to what is being done (which is usually selecting a set of photos to operate on - I never get as far as the actual operation before the crash). However, the Windows report of the crash is always the same (after the usual bit about "Organiser has hit a problem and needs to close). The error box says:

Microsoft Visual C++ Runtime Library
Runtime error
Program: C:\Program Files\Adob...
R6030
- CRT not initialised

Is there any solution known for this?
Photo of Lynne Williamson

Lynne Williamson

  • 3 Posts
  • 0 Reply Likes

Posted 7 years ago

  • 2
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14149 Posts
  • 1765 Reply Likes
Have you installed any third party plug-ins? Rad Lab or Totally Rad Software?

http://boardreader.com/thread/Trying_...
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
It is also possible that a system driver could cause such an error (C runtime library not being called correctly).
Photo of Lynne Williamson

Lynne Williamson

  • 3 Posts
  • 0 Reply Likes
This is a totally new installation, so there are no third party plugins. There was an older version of Photoshop installed (without plugins). I'm a little reluctant to deinstall the older version because I've lost the installation CD, and if version 10 doesn't work then the older version is the only Photoshop I have.

How would I identify the faulty module if it's a system driver? The error messages aren't very informative. The first error popup simply says "Elements 10 Organizer has encountered a problem and needs to close. We are sorry for the inconvenience.", and then the usual stuff about sending an error report to Microsoft. This is while Elements Organiser is in the middle of its "Preparing files" progress bar. I have discovered that Organiser continues its "Preparing files" operation as long as I don't touch a button on that error popup, i.e. as long as I don't say whether I want to send an error report. After a while a second error popup appears, this time saying that ElementsAutoAnalyzer has encountered a problem and needs to close. As I'm writing this I'm leaving those two popups up on the screen, which seems to have the effect that Organiser continues with its slow "Preparing files" operation. In fact it's possible that the operation I was trying to do completed while I was writing that. (It was a Fix/Full Photo Edit operation on a group of a couple of hundred files. I think I've finally found a small enough subset of my photos to do the operation on without crashing.)

So, in fact, I can report partial success. The trick seems to be not to respond to those "needs to close" popups. The crash doesn't seem to occur until I have responded to the two popups. Of course it's an awful nuisance trying to do any work while the two error popups are obscuring a large part of the screen.

To continue with symptoms: Once I click on "Do not send" on either of the error popups then I get the error message I originally reported: R6030 - CRT not initialised. But the faulty module is not identified because the error box is not wide enough to contain the full path name. All that I can tell is that it is somewhere in C:\Program Files\Adobe ...

Throughout all this organiser seems to keep running - I guess I just had to avoid responding to the error popup while an operation is in progress. But about half a minute later we're back to the "encountered a problem and needs to close" popup again.

Further information: it turns out that the crash also occurs if I just boot up my system and wait a while, without starting Photoshop Elements 10 at all. This one I can fix, however. The "Services" section of Control Panel shows that /two/ programs called "Adobe Active File Manager v10" and "Adobe Active File Manager v6". I can stop the crash at Windows startup by disabling both of these. Of course, the crash comes back once I start Photoshop Elements 10.

(Once I send this message I'll try disabling only the v6 one and rebooting; but I don't expect that to help because Photoshop version 6 works for me (or at least it did until I installed version 10 - maybe it has now stopped working, so I'd better check too).
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
Do you have either PSE6 or PSE10 set up with Watch Folders? (File > Watch Folders) This is a menu command to set up a folder to be watched by Elements Organizer, so if images are placed in that folder they are automatically imported. The "Adobe Active File Manager" (AAFM) is the program that sits in the background watching your Watch Folders. Try disabling this, especially if you are not using it, by simply unchecking the "Watch Folders and their Sub-Folders for New Files" option.

You can also disable the AAFM entirely from the Control Panel. Select Administrative Tools, then Services. Find AAFM (spelled out) on the list and double-click on it. Change the Startup type to Disabled and click the Stop button under Service status.

Additionally, you may want to try disabling the Elements Organizer Auto-Analysis. This can be done by going to Edit > Preferences > Media Analysis and uncheck all of the options.
Photo of Akshaya Saxena

Akshaya Saxena, Employee

  • 97 Posts
  • 4 Reply Likes
Lynne,

Does disabling of Adobe Active File Monitor service solves your problem?
Photo of Lynne Williamson

Lynne Williamson

  • 3 Posts
  • 0 Reply Likes
As mentioned earlier, I had already disabled Adobe Active File Monitor, both the v6 and v10 versions. With those running, the crash happened _before_ Elements is started. With them disabled, the crash did not happen until a little while after Elements was started. I haven't tried turning off the "Watch Folders" option, and I can't do that check right now because v10 has been completely removed from my computer. However, I'll give it a try the next time I reinstall.

Meanwhile, I have v6 working again. Initially v6 was also crashing, in the same way, after the installation of v10, and deinstalling v10 did not fix this, even though v6 had been working before I bought v10. (I didn't mention this above because at the time I hadn't tested it; I thought I could simply revert to v6 and avoid the problem that way.)

I did, however, discover that XP Service Pack 3 was a prerequisite for version 10. (I had had Windows Update turned off because it, and the other culprit Adobe Reader, were killing my internet access by chewing up my monthly ADSL quota.) So I installed lots of Windows updates including SP3. After this both v6 and v10 continued to crash. Luckily, however, deinstalling v10 fixed the v6 crash. So I now have partial success: v6 now works again.

When I get my courage back, I'll try installing v10 again with "Watch Folders" disabled, and then remove both AAFM and that annoying "Premium Trial" that keeps coming back like a bad smell, and see if that does anything. I'm hoping that some time this year I'll finally get around to looking at my photos.
Photo of Andre D'Iorio

Andre D'Iorio

  • 5 Posts
  • 0 Reply Likes
I am having exactly the same issue! Just bought Photoshop Elements straight from the Adobe online store.

The Elements organizer crashes randomly, but much worse, my whole PC started freezing after suddenly running out of the 4GB of RAM (usually sits at 1GB). I had the task manager open and it showed the memory hog to be Elements Organizer process.

Not impressed...
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
This doesn't sound like the same issue at all. Instead, try disabling the Auto Analysis (Edit>Preferences>Media Analysis and disable all the options).
Photo of Andre D'Iorio

Andre D'Iorio

  • 5 Posts
  • 0 Reply Likes
I've entered a separate thread --- turning off a feature of the app to prevent it from crashing the PC is not a satisfactory solution.
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
If your whole computer is freezing (i.e. you can no longer move the mouse cursor) then you are looking at larger problems than an application is capable of causing on it's own. Task Manager reports Paging File usage, which is virtual RAM. Verify you have allocated enough space to your Paging File (it should be at least 1.5 times larger than the amount of RAM installed, but you may want to increase it to 2x). Make sure the drive you are using for the Paging File has more than enough free space. Make sure that drive is fast (external drives tend to be slower).
Photo of Andre D'Iorio

Andre D'Iorio

  • 5 Posts
  • 0 Reply Likes
The mouse cursor still moves, but the system is so busy swapping virtual memory that it can't even start or stop anything. The problem occurs very suddenly after the elements analyzer process has been running - it goes from using steadily a small amount of RAM (< 100MB) for a few seconds to a few minutes to taking up 3 GB of RAM within seconds.

If I kill this process as it's running away before it hits 3GB and renders the PC useless, all returns to normal. No other process on my PC does that and all the rest plays nicely.

My theory is that your process encounters a video file on my disk that it wants to "organize" and something about it like a weird format or its size makes it mishandle it.
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
It is not trying to organize your file, it is trying to analyse it. It is opening the file into memory, breaking down every frame of the video and determining characteristics, such as blur, multiple person, etc. If you have very large video files, then it will take up very large chunks of memory.

I would recommend that you simply disable the auto analysis if you have such large video files that still haven't been analyzed. If you want them analyzed, you can do so while you aren't using the computer in the middle of the night or something.
Photo of Andre D'Iorio

Andre D'Iorio

  • 5 Posts
  • 0 Reply Likes
I understand ... I'm still surprised that the analysis process will try to use far more resources than the host that it's running on can provide, rendering the PC unusable. Yes the feature can be turned off, but to my earlier point, it's a poor way to solve the issue.
Photo of Mary Francia

Mary Francia

  • 2 Posts
  • 0 Reply Likes
Do we have a solution? I have the same problem - I thought it was because I had a trial only as when I called for support they refused to support if not purchased..... now I purchased it but the error is the same? it crashes and i get the error of the elements analyzer that hangs

Thanks
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
Are you getting the same error as posted here, "CRT not initialized"?
Photo of grace thornhill

grace thornhill

  • 3 Posts
  • 0 Reply Likes
yes but haven't tried the options mentioned above if they solve my problem I'll let you know
Photo of grace thornhill

grace thornhill

  • 3 Posts
  • 0 Reply Likes
I tried the above options still have the same problem what next buddy. I want to open and print these pictures what's the next step that would work. HELP!!!!!!!
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
Grace, what exactly have you tried from what is mentioned above? Have you tried any of the steps from here?: Troubleshoot system errors, freezes | Windows | Adobe software
Photo of Mary Francia

Mary Francia

  • 2 Posts
  • 0 Reply Likes
I have the same issue - I had it in the windows PC so I took it to the imac with 20GB of ram thinking it could be a memory issue - yet it is the same problem it halts and i do no know what else to do
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
PSE on a Mac can't run into this same issue. The problem being discussed here is a C++ Runtime error, which Mac doesn't use. What is the exact error you get on the Mac? You may need a new thread (or find another existing thread).

For the Windows side, did you try any of the suggestions above?