So as I understand it Visio will run in safe mode. That being the case do
you have any add-on for Visio that are being loaded during the normal
startup if so you may want disable them. Have you tried performing a repair
of Visio from add and remove programs? You can also check the event logs
this may offer some clue to what is going on.

James W.

--------------------
From: Honeybunkle
Subject: Visio 2007 Crashes on Start up
Date: Tue, 14 Apr 2009 19:57:28 +0100
Message-ID:
Organization: OfficeFrustration.com
X-Originating-IP: 24.115.133.251
Newsgroups: microsoft.public.visio.general
NNTP-Posting-Host: s15217979.onlinehome-server.info 87.106.16.153
Lines: 1
Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP04.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.visio.general:12241
X-Tomcat-NG: microsoft.public.visio.general


I have tried to install Vision Professional 2007 Professional on a
machine running XP SP3 with an AMD Athlon 64 3400+, with 2GB of RAM. I
previously had installed Office Enterprise 2007, but after getting
frustrated with the new interface, I removed it, an re-installed MS
Office Professional 2003. I did have Visio Professional 2007 installed
along with Office Enterprise, but removed it as well. After
re-installing Office 2003, I then installed Viso Pro 2007. Before I ran
Office update to check for the latest security updates, etc, I was able
to run Visio Pro 2007 and all seemed well. After running Office update,
when I try to start Visio Pro 2007, I immediately get an error which
states that "Microsoft Office Visio has encountered a problem and needs
to close. We are sorry for the inconvenience." If I close the error
message, I get a message stating that "Visio failed to start correctly
last time. Starting Visio in safe mode will help you correct or isolate
a startup problem in order to successfully start the program" Visio
will start and run in safe mode. This behavior is exhibited no matter
how I try to access Visio Pro, if I double click on any Visio file or
open Visio from a shortcut or program menu. What could be causing this
problem?




--
Honeybunkle