News
Comments
Print
Email
Rest Assured: Windows 7 Still Features the BSOD
Posted 01/13/09 at 04:23:31 PM | by Andy Salisbury
To much interest, Microsoft recently released their open beta for Windows 7. Heck, there was so much interest that it brought down even Microsoft’s servers! But while it was on us to bring down Microsoft’s servers, it’s on them to bring down our precious computers. Their weapon of choice? Why the blue screen of death, of course!
Thanks to the intrepid work of the crew at Gizmodo, they’ve run into the BSOD after a few days of messing around. Surprisingly it looks exactly as it has for a while, the simple blue background with the traditional white text.
What’s nice is that this BSOD provided the driver that was the culprit before it automatically restarted. But, it’s pointed out, that it’d be nice if it were to identify exactly what type of component (video, sound, USB, etc.) was to blame, for people that aren’t looking to learn how to read code.
Still though, we’re willing to let this one slide. It is a beta after all. And a public one at that! Aren’t all these crashes, in some convoluted way, the point of all this?
Image Credit: Gizmodo
Comments Print Email RE WhiteRabbit22
Submitted by SANMANx on Wed, 2009-01-14 14:41
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
A beta not fully ready? Wow.
Submitted by einstein1971 on Wed, 2009-01-14 11:27
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!
Submitted by BrookV on Wed, 2009-01-14 07:27
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!
BSoD everytime I try to install my sound card drivers
Submitted by WhiteRabbit22 on Tue, 2009-01-13 22:03
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.
This isn't that special, in fact.....
Submitted by ghot on Tue, 2009-01-13 21:51
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 :/
Submitted by ikleinit on Tue, 2009-01-13 21:19
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
Submitted by The Relic on Tue, 2009-01-13 19:28
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...
Submitted by mariotagle57 on Tue, 2009-01-13 18:53
windows 7 sucks vista is better...
Submitted by pratt on Tue, 2009-01-13 18:49
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
I bet this is the what all
Submitted by Keith E. Whisman on Tue, 2009-01-13 16:03
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.
Well, although I generally
Submitted by I Jedi on Tue, 2009-01-13 16:02
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.
what id like is if the BSoD
Submitted by nekollx on Tue, 2009-01-13 16:27
what id like is if the BSoD would dump its findings into a low level .txt file so when you do rebot you can open /system(x86)/BsoD.txt and have all the time in the world to trouble shoot.
Submitted by BrookV on Wed, 2009-01-14 11:45
Go under SYSTEM and under STARTUP and RECOVERY, have the mem dump go to a text file. It's not always exactly whats in the BSOD, but it will help point the way.
Good luck
Submitted by BrookV on Wed, 2009-01-14 11:45
Go under SYSTEM and under STARTUP and RECOVERY, have the mem dump go to a text file. It's not always exactly whats in the BSOD, but it will help point the way.
Good luck
RESOURCE CENTER
MOST COMMENTED ARTICLES
MOST RECENT COMMENTS
THIS MONTH's ISSUE 
FEATURE 21 Instant PC UpgradesBUYER'S GUIDE Budget videocards: which pass, which fail?HOW TOSupercharge Firefox & Maximize your SSDFEATURE3 trends that will save PC Gaming WHITE PAPERSurge supression
Technology News
Computer Cooling Fans
Computer Cases
PC Game Controllers
PC Games
Computer Hardware
Headphones
MP3 Players
Stream Video
Computer Mouse
Monitors
Motherboards
NAS Storage
Networking
Laptop Computers
DVD Burner
Digital Cameras
Portable Storage
Computer Accessories
Smartphone
Antivirus Software
Sound Cards
Speakers
Computer Systems
Thumb Drives
Video Cameras
Video Card Reviews
Water Cooling
Gadgets
- Keyboards
© 2009 Future US, Inc. All Rights Reserved.