InDesign crash on open of Project

Question

This has actually happened quite a few times in the last two weeks. New Windows7 computer. Just installed CS5 a few weeks ago on this machine.
Will open an existing project and InDesign will say it needs to close. When opening the project again, it seems to open just fine. Would appreciate any help with this problem. Here is the event log:
Log Name:      Application
Source:        Application Error
Date:          1/14/2011 10:07:55 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
Description:
Faulting application name: InDesign.exe, version: 7.0.3.535, time stamp: 0x4ca67222
Faulting module name: AdobePSL.dll, version: 12.0.0.7524, time stamp: 0x4b885409
Exception code: 0xc0000005
Fault offset: 0x004e188d
Faulting process id: 0x564
Faulting application start time: 0x01cbb4052e950dcf
Faulting application path: C:\Program Files\Adobe\Adobe InDesign CS5\InDesign.exe
Faulting module path: C:\Program Files\Adobe\Adobe InDesign CS5\AdobePSL.dll
Report Id: 71cf97ef-1ff8-11e0-9ffb-842b2bb0d9fa
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="2011-01-14T16:07:55.000000000Z" />
    <EventRecordID>3284</EventRecordID>
    <Channel>Application</Channel>
    <Security />
  </System>
  <EventData>
    <Data>InDesign.exe</Data>
    <Data>7.0.3.535</Data>
    <Data>4ca67222</Data>
    <Data>AdobePSL.dll</Data>
    <Data>12.0.0.7524</Data>
    <Data>4b885409</Data>
    <Data>c0000005</Data>
    <Data>004e188d</Data>
    <Data>564</Data>
    <Data>01cbb4052e950dcf</Data>
    <Data>C:\Program Files\Adobe\Adobe InDesign CS5\InDesign.exe</Data>
    <Data>C:\Program Files\Adobe\Adobe InDesign CS5\AdobePSL.dll</Data>
    <Data>71cf97ef-1ff8-11e0-9ffb-842b2bb0d9fa</Data>
  </EventData>
</Event>

Answer 1

I can understand entirely how someone used to a structured conversation could get confussed by a group discussion with everyone having the same problem but describing it in different way. I can tell you that productivity is better from unstructured conversations than it is is from structured one-on-one discussion. More people benefit from it.
Let me explain - and tell the OP how to fix the issue. Well... How I fixed it on 4 PCs from taking Peter's advice to someone else.
My Computer is just over 18 months old. An i7 950 with 12 gig of Grade A, DDR3 ram and an ASUS mainboard and Radeon HD5850 graphics card. Everything (board, CPU, graphics and RAM) is fluid cooled and software monitored with log entries whenever there is a hardware glitch.
This system originally ran 64 bit XP Pro but I got so frustrated that none of my applications needing access to the extra RAM seemed comfortable running in 64 bit. In December 2010 I installed a fresh set of hard drives and Windows 7 64 bit. I also updated Indesign to version 5.0. By March 2011 I got so distressed by the continual interuption to my workflow by Microsoft installing updates and not letting me shut down until they were installed, I switch off the whole update system. Apart from keeping Radeon fed with the latest patches and weekly colour profiling, the system has run flawlessly except for InDesign stalling and crashing whenever it is started by selecting a .IDD file.
I bit the bullet yesterday and let Microsoft update my OS (and Office). Six hours later - (I kid you not) with over 250,000 files altered or replaced, the PC reported it needed to be restarted. On restart it reported 4 updates were being installed as I watched in horror as nearly 190,000 additional  files were replaced or altered. This is not a patch or an update. Microsoft needs to warn uses that it is about to replace the entire OS. It smoother and faster now. But the really important thing is that I can now start InDesign by selecting files on any drive with any file manager (Explorer included) without the program hanging or crashing.
So Peter... I know to someone used to working with code or databases, the rambling way this thread has progressed might be cause for frustration but at the end of it all, I'm pretty sure my original assesment that there was a miss-match of code between MS and Adobe seems to be correct. I've installed the service pack and updates on my notebook and both of the art PC as well as my own workstation. The issue appears to have been a flaw in Windows itself because if it were in Adobe's software, the problem would still exist, would it not?
The problem is one that can be cured, even prevented by keeping Windows up to date. I don't recommend doing it my way unless only one machine with no work pending is involved. I wish I could pinpoint the actual link library responsible for the problem but too much was done over too long a time for me to back track and look.  Thanks for the prompt about the service Pack Peter. I always work on the basis "don't fix what isn't broken". Interestingly enough that ID problem didn't exist on the first fresh install of Win 7. Only after MS had fed it daily with "security" patches.
Doug