No display after Windows loads

Fresh 2nd install/running Windows XP 64bit on WD raptor raid0 array with
Asus P5E3 Pro mainboard, one pci-e graphics card and lg 19 inch flat panel
lcd monitor using DVI output. Everything works up until just after the
progress bar and the windows XP are shown on the screen then the normal,
brief, blank screen and a "Ka-click" of the monitor just before the welcome
screen then no display afterwards. All drivers and updates installed with
SP2. No problems/conflicts indicated in device manager or system
information. Hardware interrupts are normal. I know this because the display
works fine when running Driver Verifier on all drivers. And the dislay works
fine in Safe Mode. I tried different VGA cards, different catalyst
versions/drivers (I use ATI cards, 6790 and a 5700 something). Tried
reinstalling monitor drivers and tried a CRT monitor hooked up to an analog
port, makes no difference. Different resolutions do not fix the issue, I
tried a fresh install, still having the same problem. The fact that it works
as it should with Driver Verifier running indicates to me a driver issue but
it has not crashed and I know very little about debugging or what driver to
start with.

The first time I installed this OS on the same setup with the same mainboard
over a year ago I did not have this problem.

If anyone has an idea where to start that would be great. My thinking is
that if the display only works with Driver Verifier running on all drivers
with all settings enabled except Special Pool and Low Resources Sim. then I
could narrow the field by eliminating drivers the verifier looks at,
probably all Microsoft drivers then the others one at a time until the
problem reoccurs. Then, if I am lucky enough to pinpoint a specific driver
or group as the cause I can narrow the DV settings down to one or two that
make the display work as it should. The problem with that is changes to DV
require a reboot and no display means a hard reboot to restart, and that may
further degrade any already established issues and possibly create new ones.
I think I'll try using MS bootvis to map out the the drivers that are loaded
for display and focus on those that load when the issue occurs. I have A 32
bit XP I'm using on this computer so I could compare the two mappings to see
if the 64bit system is missing something. An optimization of boot time files
might even be the ticket. Then, there's the System Configuration drill down
(Turarian's favorite tool) but again, lots of hard boots is asking for
trouble with a RAID0 array. Boot logging is also an option I haven't
tried...

I would really like to learn how to use WinDbg for something other than
veiwing dumps.

Maybe it isn't a video driver at all...

Maybe somehow you've enabled a motherboard component that ought to be
disabled, such as built-in video...

Given we're talking about 64-bit XP, it is probably irrelevant to
mention problems reported when using the /3GB switch to use additional
memory in 32-bit Windows, including conflict with high colour depth /
resolution video memory...

If the system is running normally and just invisi�ble, you could
perhaps set a program to autorun that shuts the PC down again gently,
about a minute after starting, unless you cancel that. So you just
have to wait.