Earlier this week, we had a page 2 item about a possible showstopper bug in Windows 7 and Windows Server 2008 R2, but as I could've probably guessed by taking my time before posting said item, this bug has been way overblown and is anything but a showstopper. Steven Sinofisky himself responded to the bug by commenting on the blog.
To read all comments associated with this story, please click here.
Member since:2006-01-01
I don't know who would be running Chkdsk from within Windows anyhow, I always run it from a boot disk.
Yeah same, hence my question above. Will that not explain than if it is a chipset incompatibility issue? If it is than we should get the same issue even when running it of the boot CD. This means it would be wise to keep your old Vista CD since it would be the only way to run chkdsk properly. Well you can do it with XP too but with Vista you get full NTFS support through the command shell + utilities such as bootrec that would fix your booting should a foreign boot loader corrupt your Windows boot loader. I used bootrec /rebuild (I think) or something like that to fix my laptop's Vista/7 loader.
Edited 2009-08-09 00:59 UTC
Member since:2006-01-12
Sigh did you guys read the article? They improved chkdsk to USE memory to gain SPEED. Only bug is in those rare cases where this causes BSOD, AGAIN in all cases highly increased memory usage is INTENDED behavior.
And yes it happens in recorvery mode also because it's the same chkdsk.
Why would you want to run older tools that are slower if you wont be using machine anyway since you are suspecting it has HDD failure, there is no other reason to run chkdsk with /r.
If you have ever run chkdsk in server you know how much time it takes (days not hours) so I cheer Microsoft for improving such a rarely used tool.
Member since:2006-01-12
Leech: OMG someone call Randall Kennedy there is another bug! And it's infesting like 0,1% users, call the Obama, call the Greenpeace. Also Puppet Walt Mossberg is reporting some other problems. http://www.youtube.com/watch?v=Xdn0AmdXsGg
Member since:2006-01-10
Yeah, and I'm sure that there is only .1% of all people that use more than just stereo speakers....
Or for that matter there is only .1% people that use their computers as media centers. If that were the case, then I'm sure Microsoft would have never bothered developing the Windows Media Center.
Member since:
2006-01-10
Should be the problem with sound.
I don't know if it's the way the sound initializes and de-initializes, but I never had this issue before Windows 7.
Basically when you first load up Windows 7, then you try to play a game in 5.1 sound, the center and surround channels have no output.
So every time I boot up, I have to go into the sound hardware configuration, change it back to Stereo, run the test, then change it back to 5.1 and then run the test again. Then it works properly (well most of the time).
But then the other day, the exact same thing happened to Linux, though at first I thought it was because I still have two sound cards in my computer (I have an Audigy 2 Platinum and the onboard sound) only because of having these weird sound issues in Windows 7.
I can only think that it somehow is initializing the sound wrongly when it first loads up, but then it does that same initializing when it is rebooted.
This SHOULD be a show stopper, especially since it affects the multimedia capabilities of the OS.
Granted I've only tested it why my hardware, but it does do it with both sound cards.
The only other issue I've had with it, is that I have it installed on my Touchsmart with the multi-touch. For whatever reason it keeps randomly making the sound of hardware being removed. The only thing I can think of is that somehow the touchscreen is being initialized differently than it expects. The reason I am thinking that, is because depending on if you run Vista or Windows 7, the pci bus location of the touchscreen is different! (2:1:0 if I recall for vista, and 2:1:1 for 7) Only know this because I dual-boot Ubuntu on it.
These are things that people will notice. I don't know who would be running Chkdsk from within Windows anyhow, I always run it from a boot disk.