BSOD windows...Think its BIOS..going crazy. Done a lot of ..

Hi.

I have a p4 3.6 2gb name-brand asus p5ld2vm motherboard- about one
month old. I am getting a BSOD when booting into windows. I have
tried the followiing with no success:

1) safe mode (all versions). screen comes up, goes bank (with video
signal) on loading.
2) last known good config. boots to the windows loading screen and then
goes black..video signal still being sent to the computer but no video.
3) and on that note, swapped video cards; still happens
4) swapped monitor
5) swapped out memory for known working memory. (also swapped to
different slots)
6) turned off a lot of features I had on on the motherboard-
audio/lan/etc
6) played around with PNP vs. no pnp in the BIOS
7) checked the cpu/mobo operating temperature (within spec).
let the computer sit to cool in case it was an hd overheating issue.
9) removed all cables to the pc but video (dvi) and usb keyboard
10) tried the db15 analog cable from the monitor to boot into a
graphical environment

and some more i'm probably missing....

There are a few things that are odd:

1) the bios acts odd and occasionally complains of over voltage or
overclocking when I boot up after changing *nothing* in the bios.
2) the bios "forgets" certain settings like "no graphical boot screen"
but will "remember" the fact that I Have a bios password.

I have tried the following software:

1) ubcd 3.3 (will crash when trying to boot into a linux kernel saying
"there is a serious problem with your bios")- but i've seen that before
with a good bios.
2) erd commander (it blue screens when going graphical)
3) memtest x89 bootable (doesn't boot for some reason)
4) original win xp cd for a restore. bsod's when I get to where it
goes graphical.

So, obviously, the problem is where it goes graphical, YET, I have
tried other video cards. Are there settings in the bios I can change?
Is the BIOS just broken? I'm having a *hard* time loading a new bios
but it seems the most logical thing.

For those that decode error messages (I don't know how to or know if
you even can) the bsod partially reads:

0000007b f78d2524 c0000034

its the same bsod hex dump every time.