My summarized question:  Is there a way to enable deeper error logging while VS2008 loads a solution?

I really been struggling to solve this one, but I have a VS2008 solution that has been working for over a year now, no problems when it was upgraded from a VS2005 solution months back.  The solution targets the .NET 2.0r3 CLR and contains a few class libraries and a Web site project.  Just recently however, every time I open the solution and while the status bar shows VS2008 running through the load of each project in the solution, but just before the solution loading finishes, I immediatly receive the generic general error: "Microsoft Visual Studio has encountered a problem and needs to close."

Watching the status bar it never "hangs" on any particular project in the solution, and I even tried changing the solution file format version back to 9.00 instead of 10.00 and using VS2005 to load it, but received the same "encountered a problem and needs to close," and no chance to respond before it simply terminated VS2005.  I eliminated file corruption and the usual problems, different machine, fresh repository checkout, etc....  There is nothing special about this solution, no non-Microsoft controls, 3rd party libaries, or anything recently added.  Is there a way I can turn on more in depth logging for the solution loading process to find out where the problem exactly occurs?

I'm running VISTA Ultimate 32-bit, I've tried it under XP, Vista 64-bit, etc., VS2008 Professional and have tried opening this solution with/without SPBeta1, with/without Silverlight Beta2 and related, with/without the latest MVC/Dynamic Data/ASP.NET AJAX 4/Futures, etc., and I've even tried it with and without Vista SP1...no difference, always the same error now.  All I have to go on is the following error log files and I'm stuck. 

Here is the the Windows Error Reporting report file contents from under C:\Users\[my login]\AppData\Local\Microsoft\Windows\WER\ReportArchive\Report1376a4b9

Version=1
EventType=CLR20r3
EventTime=128625268616151751
ReportType=1
Consent=1
UploadTime=128625268646727751
Response.BucketId=4
Response.BucketTable=5
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=devenv.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=9.0.30428.1
Sig[2].Name=Problem Signature 03
Sig[2].Value=4815597f
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.0.6001.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe
UI[3]=Microsoft Visual Studio has encountered a problem and needs to close.
UI[4]=If you had files open that contained unsaved changes, these changes might be lost.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
Sec[0].Key=LCID
Sec[0].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=4/nBucketTable=5/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Microsoft Visual Studio
AppPath=C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe

 And the Widows Aplication Log error:

First, have you deleted the (hidden) .suo file? Most solution loading problems are down to .suo corruption.

If that does not fix it, create a new solution and add the existing projects to it (and validate inter-project dependencies), there so little real data stored at a solution level it is not worth trying to be clever.