BSOD seems to be related to moving system, No Video After.

Boozad said:

No problem. Did you uninstall the ATI card via Device Manager before installing the nVidia one, and then uninstall the nVidia card before re-installing the ATI one? If the nVidia package included the HD Audio feature it could be that it's conflicting with your M-Audio card drivers.

No.
I installed the ATI driver package (Catalyst Control) via it's installer file.
Then I swapped in the Nvidia card without removing the ATI suite and I did not install any Nvidia package, just let Windows use a Driver (did not let Windows search online for driver, PC was actually diisconnected from net at the time).
Then I reinstalled ATI card without removing any driver that Windows was using for the Nvidia card.

Do you recommend a driver sweeper to help me remove any installed drivers that are not needed by my current hardware?

Quite likely. I will investigate that when I get home.


Still not sure why it crashes when I move it gently, (I could see that happening if O/S on HDD and it was jarred) but otherwise pretty stable.
The moving it problem makes me think hardware issue. Thoughts?

No worries and no real rush, just nice to have someone else with more BSOD knowledge having a look, thanks!
Like I said, I have to rule out hardware issues i.e. MOBO before unlocking this software in this build, so If I can't rule out faulty hardware in the next week, I'll start looking at using that software on a different system while I tinker with getting this one's issues resolved or at least definitively diagnosed.

No USB devices attached other than mouse and keyboard.

I'll get rid of the Nvidia mess and check for restore point later tonight and we'll go from there...

Quick update:
Did system restore to point before I had switched GPU.
System wouldn't boot, kept cycling POST, load windows, POST.

Checked BIOS. Somehow it had reset the controller to IDE even though I had not been in the BIOS
! Um, how does that happen?

I reset to ACHI and Windows loads, then a few minutes later, BSOD and then same black screen.

Couple notes:

- Monitor does recognize when it is plugged/unplugged to system while system is on, even though no video coming out of PC.
- I checked all power supply voltages at the 24 pin with DMM and they're fine.

I'm really starting to think this MOBO has problems. Might be time to cut my losses and put this old dog out to pasture.


I'm shopping for a new mobo and CPU. I will tinker and troubleshoot this one later perhaps but I have to get on to a more productive build since this thing is getting nowhere and often won't even get to Win7 loading, so it seems this is not just a Win config issue. At least I didn't pay too much for this used rig and the copy of Win and the HDD are worth what I paid.
Maybe I can find a board that I can use this Xeon in.

Thanks again very much for your help, really appreciate it.
Hope for me that I'm not back with a new BSOD question on my newer build.

p.s.
Something I noticed, when going into bios and it's listing devices, it says 1 keyboard and 2 mice found even when 1 mouse only plugged in. If I unplug the only mouse for next boot, it still says 1 mouse found.


Also, I've been testing the RAM and when it's in single channel mode w/ either one or two sticks, I have no crashes and it seems very stable.
With dual channel mode slots populated, I get crashes and it has even froze in BIOS. Very consistent and repeatable results, so far.

I know I said it was black screen even with just 1 stick of RAM in my OP and it was but that may have been an anomoly and I moved too quickly to assume that RAM was not the problem.
I've tried other RAM with same problems, but it seems single channel is stable, I was always testing in dual channel before except once when I tried a single stick and system did not post.
I have tested all RAM w/ Window Mem diagnostic and it found no errors.

Seems dual channel on mobo may be a problem. Does the dmp files show anything to this affect?
Please share any thoughts on what this may mean on how for my next course of action.

After more testing for the last few weeks, I have concluded this was very likely a faulty hardware issue.
Marking as solved.
Thanks for the help!