jalaffa Posted August 5, 2009 Share Posted August 5, 2009 As most of you know, Windows 7 is expected to hit technet and MSDN by August 6th to a image much anticipated welcome. However, this particlar issue looks strangely out of place and makes you wonder how exactly this passed through validation:To Reproduce: 1. Run an elevated CMD prompt 2. Run CHKDSK <drive letter:> /r 3. With task manager open, you should see your memory quickly gobbled away in the chkdsk.exe process until it either stops at or around 90% or it maxes completely out and crashes the computer.A response from Steven Sinofsky (president of Microsoft's Windows Division) in thread:Hi there…sorry to get dragged into this. Of course always want to investigate each and every report of any unexpected behavior.In this case, we haven’t reproduced the crash and we’re not seeing any crashes with chkdsk on teh stack reported in any measurable number that we could find. We had one beta report on the memory usage, but that was resolved by design since we actually did design it to use more memory. But the design was to use more memory on purpose to speed things up, but never unbounded — we requset the available memory and operate within that leaving at least 50M of physical memory. Our assumption was that using /r means your disk is such that you would prefer to get the repair done and over with rather than keep working.While we appreciate the drama of “critical bug” and then the pickup of “showstopper” that I’ve seen, we might take a step back and realize that this might not have that defcon level. Bugs that are so severe as to require immediate patches and attention would have to have no workarounds and would generally be such that a large set of people would run across them in the normal course of using their PC.We appreciate the kind words that such a bug as above is “out of place” with Windows 7–we’re working hard. We are certainly going to continue to look for, monitor, and address issues as they arise if required. So far this is not one of those issues.Some have reported (as above) that this specific issue repros and then goes away with updated drivers. We haven’t yet confirmed that either but continue to try. We just kicked off overnight stress testing of 40 machines of variants as reported by FireRx. We’ll see.Let’s see if we can work on this one and future issues together. Deep breath :-)–Steven View: Original Article Link to comment Share on other sites More sharing options...
Administrator DKT27 Posted August 5, 2009 Administrator Share Posted August 5, 2009 The first quote is telling that it is using 90% of CPU and crashing.And Steven is telling that they have made the progam use more RAM?ANW this can be solved in Windows Update. If it is not fixed before the release. Link to comment Share on other sites More sharing options...
donizme Posted August 5, 2009 Share Posted August 5, 2009 I have the RTM! I'm gona try this out now and update this post. If I don't reply in the next couple of minutes, something's gone horribly wrong... :oEdit:I did on my Windows RTM 32-bit. The chkdsk.exe. took over 1.6GB RAM! Check it below: :why: Edit 2:This isn't even a critical bug, in fact this is just a misunderstanding. Read carefully Microsoft's response:But the design was to use more memory on purpose to speed things up, but never unbounded — we requset the available memory and operate within that leaving at least 50M of physical memory. Our assumption was that using /r means your disk is such that you would prefer to get the repair done and over with rather than keep working.This is true because My memory usage didn't go above 85%. I don't think there is any issue here... Link to comment Share on other sites More sharing options...
donizme Posted August 5, 2009 Share Posted August 5, 2009 The first quote is telling that it is using 90% of CPU and crashing.And Steven is telling that they have made the progam use more RAM?ANW this can be solved in Windows Update. If it is not fixed before the release.Yeah I think the first quote guy just got a little carried away by looking at the memory usage! There is no crash... :rolleyes: Link to comment Share on other sites More sharing options...
Administrator DKT27 Posted August 5, 2009 Administrator Share Posted August 5, 2009 Indeed. ANW can you post a bigger resolution image? Link to comment Share on other sites More sharing options...
donizme Posted August 5, 2009 Share Posted August 5, 2009 Indeed. ANW can you post a bigger resolution image?Done ;). Link to comment Share on other sites More sharing options...
Anteus Posted August 5, 2009 Share Posted August 5, 2009 Well tried it on my x64 RTM and it worked fine, 1,6GB of my 2GB and it left 5% free.Why would it crash when the physical memory is full :frusty: Maybe go fucking slow when the pagefile kicks in but still not crash. Link to comment Share on other sites More sharing options...
shought Posted August 5, 2009 Share Posted August 5, 2009 It's a bit of a silly implementation nevertheless, just like CHKDSK is going to use even half a gigabyte of RAM... I mean they should limit it at a maximum of 256-512 MB or something... Link to comment Share on other sites More sharing options...
Toshiro Posted August 5, 2009 Share Posted August 5, 2009 If you let it run alone (no programs on background..) it shouldn't give a blue screen..(coreect me if i'm wrong..)If another problem can't get enough RAM.. it gives you a BSOD.. I saw @ another forum that someone's chkdsk took 7.5 GB of his 8 GB.. then he shut it down.. Dunno what they did with it.. but they only say this is the showstopper because a lot of companies AND people rely on it. Link to comment Share on other sites More sharing options...
Administrator DKT27 Posted August 6, 2009 Administrator Share Posted August 6, 2009 @shought you are right.@Haantjuh. You idea is wrong. BSoD is not caused by that. Link to comment Share on other sites More sharing options...
MrVoice Posted August 6, 2009 Share Posted August 6, 2009 Sometimes I wonder if people even read what the experts write. Why don't we open up a bunch of programs, then force the system to use up lots of memory on something else? HELLO! That's a dumb idea ANYTIME. This isn't a "bug" it's dumb usage of your hardware/software. Link to comment Share on other sites More sharing options...
FreeRyde Posted August 6, 2009 Share Posted August 6, 2009 Honestly, how often does anybody use CHKDSK. I'm sure we'll get by until a hotfix is released. It wouldn't be the first bug in a new system. Overall Win7 is quite stable. Link to comment Share on other sites More sharing options...
Administrator DKT27 Posted August 6, 2009 Administrator Share Posted August 6, 2009 In real, when I purposely start chkdsk on boot, it has never helped me, infect it has created some major problems on my PC. That is what I have found out using my XP. It may not be right and nor I know what exactly it does but this is what I have found out. Link to comment Share on other sites More sharing options...
donizme Posted August 6, 2009 Share Posted August 6, 2009 At 6pm GMT today, Windows 7 RTM will be released to Technet/MSDN/Connect. I read that jalaffa has a Technet account. So jalaffa can you let us all know of the hashes of the technet release? Maybe you can post them in this topic, or in a new thread? Thanks. :rolleyes: Link to comment Share on other sites More sharing options...
Bizarre™ Posted August 6, 2009 Share Posted August 6, 2009 @DKT27:If you have NTFS, believe me, chkdsk can be a godsend. Link to comment Share on other sites More sharing options...
Administrator DKT27 Posted August 6, 2009 Administrator Share Posted August 6, 2009 I have two HDDs. One is a old one and the other is a new one. The old one was formatted FAT32 but wanted to convert it to NTFS. Many people told be I have to reformat all the drives which I wanted to convert but because of my intelligence, I converted it to NTFS without formatting. Actually it was because of Cnet's former online classes :P . ANW it seems to cause problems even on NTFS. I don't remember that it caused any problems on FAT32. Link to comment Share on other sites More sharing options...
Bizarre™ Posted August 6, 2009 Share Posted August 6, 2009 For me, FAT32 causes way more bad sectors than NTFS.FAT32 is also quite slow for hard drives with large capacity. Link to comment Share on other sites More sharing options...
Administrator DKT27 Posted August 6, 2009 Administrator Share Posted August 6, 2009 NTFS is indeed the best one. FAT32 is old tech. Link to comment Share on other sites More sharing options...
irefay Posted August 7, 2009 Share Posted August 7, 2009 NTFS is old tech also. Vista was suppose to use a new file system... guess not. 7... doesnt look like its manking that dream come true eather. Link to comment Share on other sites More sharing options...
Bizarre™ Posted August 7, 2009 Share Posted August 7, 2009 I'm eagerly anticipating for a new file system... getting tired of FAT32 and NTFS :bag: Link to comment Share on other sites More sharing options...
Anteus Posted August 7, 2009 Share Posted August 7, 2009 WinFS, the new filesystem from Windows, it's NTFS + journal like Ext3... Link to comment Share on other sites More sharing options...
demonon Posted August 7, 2009 Share Posted August 7, 2009 I don't think M$ will improve their OS drastically for a long time because it will cause compatibility issues.Of course, Win7 is an improvement, but shouldn't every new OS be better? Link to comment Share on other sites More sharing options...
Bizarre™ Posted August 7, 2009 Share Posted August 7, 2009 I think WinFS is meant for something else :think:Link 1Link 2 Link to comment Share on other sites More sharing options...
Anteus Posted August 7, 2009 Share Posted August 7, 2009 I think WinFS is meant for something else :think: Link 1Link 2Whops! :rolleyes: Link to comment Share on other sites More sharing options...
Administrator DKT27 Posted August 7, 2009 Administrator Share Posted August 7, 2009 Yea even I thought so. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.