SANMANx

January 14, 2009 at 1:41pm

My Onboard sound was blue screening mine as well. Haven't tried the soundblaster yet. My windows 7 installed on my old MSI K7N2 ILSR Athlon XP 3200+ YAAA! Wouldn't take the Nvidia nforce onboard NIC either. I had to install an old PCI Intel Pro/100

 

I am Recession Proof

einstein1971

January 14, 2009 at 10:27am

Who ever heard of beta code not being 100% ready to go?  I mean really, beta code is a code word for 100% done.  Everyone in the biz knows that when something is beta its actually done that's why it's called "beta"...which ryhmes with Data, as in Commander Data.  He was 100% done and if Commander Data worked then so should Commander Beta.  It's called logic people!

BrookV

January 14, 2009 at 6:27am

 

  When idiot users start "messing around" and get in over their heads, they should get more than the BSOD, they should get a slap upside the head too! Also, if you know what the heck your doing, then having the blue screen point out the driver at fault should be sufficient. It shouldn't have to point out what component or anything else you were tinkering with.

 What a bunch of noob turkeys! Go get a MAC, you dopes!

 

WhiteRabbit22

January 13, 2009 at 9:03pm

I can repeatedly porduce the BSoD every time I try to install the drivers for my Creative X-Fi Extreme Audio card. Granted the Os doesn't even recognize that it's there, but it won't take my AC'97 drivers either, and the USB audio sucks.

 I'm using the 32-bit version on a 64-bit machine, so hopefully the 64 bit version won't have this issue. But so far, the sound cards are the only problem I've had.

ghot

January 13, 2009 at 8:51pm

They could easily port this to Vista and XP.  What's much more interesting is that its already BSODing...granted its a beta...but sheesh  :/

ikleinit

January 13, 2009 at 8:19pm

I installed windows 7 64bit on jan. 11,2009 and I just got my first BLUE SCREEN OF DEATH

Hardware:

Msnv-939 amd nforce4 chipset

amd socket 939 dual core

4gb in 4 slots 1gb each

NVIDIA EVGA 8400gs discrete PCIE card

Audigy SE Card

   The BSOD occured after I installed the latest NFORCE 64bit vista drivers

 as I was installing the newest vista 64bit drivers direct from Nvidias driver page

I got the BSOD 

The Relic

January 13, 2009 at 6:28pm

Double-darn. I didn't get a BSOD while messing with Win 7, but I DID get an interesting screw-up while testing programs with it. Namely, after putting a number of programs and they generally worked fine, I put Alcohol 52% on, and as requested, rebooted.

When Windows tried to boot, it went directly into the repair console, finished, went into Windows, where I discovered that all the programs I loaded from the original bootup (about an hour earlier) to Alcohol were not only removed from the desktop, the executables on the desktop were gone and uninstall references were gone from Programs (curiously, the installs, minus the .exe files, were still in the x86 folder).

After filing a report to MS, I went about isolating the problem. I was able to repeat the screw-up with Alcohol, so that confirmed the miscreant program. 

But no BSOD, no comment on the bootup that "A Serious Error Has Occured", no nuthin'. But suffice to say, I will keep Alcohol within the confines of XP...

mariotagle57

January 13, 2009 at 5:53pm

windows 7 sucks vista is better...

pratt

January 13, 2009 at 5:49pm

lol I actually hit a BSOD within the first hour of using Windows 7. I had installed Call of Duty 4 and was messing around seeing how well it would perform in the Windows 7 environment. It worked well enough. As I was changing various video settings (within the game), I entered a server, moved about 4 inches and BAM! I saw my old friend the BSOD for the first time in what seems like ages. I've yet to make it happen again but it somehow didn't like my ATi drivers I suppose. Either that or it didn't like punkbuster. Who knows? I have no idea what all that mumbo jumbo letters and numbers mean anyway lol

 

In all honesty, I was actually proud I found a BSOD :D lol for once I wasn't raving mad that what I was doing was ruined

Keith E. Whisman

January 13, 2009 at 3:03pm

I bet this is the what all MS sever screens looked like after they opened the valves on the Win7 Beta release on the 9th.

I Jedi

January 13, 2009 at 3:02pm

Well, although I generally (Always, duh!) hate getting the BSoD. I have to admit that it's very useful for figuring out "what" the issue is or may be. I applaud MS for this thing, even if no one wants to get it. At least then we can fix our problems more easily, rather than search every-fucking-thing... I'd rather get a streaming line of text/code that will help me troubleshoot and issue, rather than the middle finger everytime a crash happens.