New
#1
BSOD is bs:
I have been trying Windows 7 and then some, I have the full retail activated, and just clicking on a file on the desktop right after a fresh install and BSOD bs. No kidding. Forced reboot - loss of data, the whole big enchilada...I hate this machine soon ensuing. Well I have my doubts even about all that, so here are my system specs:
Ultra X3 1000W - psu
Intel DX58SO - mobo
Intel Core i7 (920) - processor
Crucial DDR3 3Gb (excellent ram) - ram
and
Seagate SATA II 300 - 500Gb internal - hdd
with Cooler Master Hyper N 520 - air cool
topping off the desert
running Windows 7 Ulitmate 64 Full Retail, on a clean install.
(powered by a brain from God!)
now, you tell me why? At first I was having the issue on changing compatability for a game I was running, namely Star Trek Starfleet Command Orion Pirates, old game but still very playable. This is what happened there. I would try to run my game normal, not good, and knew right away to try compat., so I did run it in XP SP3 mode compat. change, no problem. Well it didn't want to go in Program Files naturally like my gf's Win7 Ultimate 32 bit for whatever reason?? looks around and ?? some more...well needless to say after reinstalling again into Program Files (x86) for best run reasons, I went to do the compatability changes the second or third try and BAM! It hit me. Bs, BSOD!! And it's not over the dreaded BSOD, no, it starts doing that as I merely highlight a file in that folder!!! Oh my. Well pretty soon after this starts I get smart, right? and reinstall. Because, if this is happening I figure let's get our knuckles busting and do the hard work. Well right after reinstalling and I'm really getting the compat. thingy down pat, it happens on the desktop. No, not the thing is fixed or I fly off on a chariot to Heaven, the dam BSOD. Grrrrrrrrrrrrrrrr.
Anyone want to try to tackle this one? Thank you in advance if so. This is okay to troubleshoot, yes? Yes, my gf plays OP with me.