Recommended Posts

On neowin member chris123NT website Steven Sinofsky states the so called memory bug in windows 7 when running the chkdsk /r command on a secondary disk is by design in an attempt by Microsoft to speed things up.

In the quote as highlighted you can see he also states that they assumed that most users would prefer to run the command and basically let it do its job quickly and that most users wouldn't carry on working during the process.

He also states as you can see that any system crashes caused maybe a chipset controller issue that can in most circumstances could be resolved by updating the chipset driver. This has yet to be confirmed however.

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 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.ing.

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

Edited by lee26

I did some more testing last night and was noticing that there was no crashing this time around, BUT the high memory usage was causing both systems to grind to a halt, and disk I/O was low which makes no sense as chkdsk is supposed to be hitting the disk every second it's running. If high memory usage is supposed to speed up the process then fine, but in this case I have observed high memory usage and decreased performance, which is definitely not right.

Really? They are going with the old "It's not a bug, it's a feature" excuse? :laugh:

It might be a bug but certainly not a showstopper one. :/ Those calling it "showstopper" or "derail product launch" don't know **** about how those words are used. This might be Microsoft's way of controlling bad PR (even if it is a legitimate bug).

The anti-MS trolls (the infoworld article), apple etc. will have a field day blowing a non-issue out of proportion. Win7 RTM is not bug-free but I'd hate to see it going the Vista way (PR wise) because of a low-risk bug.

I did some more testing last night and was noticing that there was no crashing this time around, BUT the high memory usage was causing both systems to grind to a halt, and disk I/O was low which makes no sense as chkdsk is supposed to be hitting the disk every second it's running. If high memory usage is supposed to speed up the process then fine, but in this case I have observed high memory usage and decreased performance, which is definitely not right.

Do you have Vista? Maybe you can compare the time taken to really confirm the decrease in performance. They could have just transferred the hard disk data to memory and do the work there.

No need for a duplicate thread. What Sinofsky said was already covered in https://www.neowin.net/news/main/09/08/05/w...asty-chkdsk-bug and there is a thread for the issue here: https://www.neowin.net/forum/index.php?showtopic=806282

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Valve finally confirms Steam Machine prices, starts at $1049 for 512GB option by Pulasthi Ariyasinghe The $1,428 option The Steam Hardware lineup that Valve announced last year is slowly starting to roll out. Following the recent Steam Controller launch, Valve has now confirmed the price of the Steam Machine, its all-in-one console-like solution for PC gaming in the living room. There are currently four variants being presented, with only the storage and the included controller being the biggest differences. All of the Steam Machines have the same internals consisting of a semi-custom AMD Zen 4 CPU with six cores and 12 threads, an RDNA 3 28CU GPU, 16GB of DDR5 memory, and 8GB of GDDR6 VRAM, all inside the familiar box Valve has been showing off for months now. The Steam Machine base model starts at $1,049. This has a 512GB NVMe SSD but does not come with a Steam Controller. Keep in mind that storage can be expanded with the microSD card slot too. Next, the $1,128 model has the exact same storage as the previous one but it does come with the new Steam Controller. If you need the Steam Machine to have more storage for games and apps than that, then the 2TB tiers are also available. The $1,349 Steam Machine has no controller once again, but it does ship with two extra faceplates (red fabric and solid walnut) to replace the standard black one. The final option costs $1,428, and it adds the controller back into the bundle. The Steam Machine ships with the Linux-based SteamOS. The box has a 1 Gigabit Ethernet port, DisplayPort 1.4, and HDMI 2.0, as well as one USB-C and four USB-A ports. Keep in mind that when purchasing standalone, the Steam Controller has a $100 price tag. With the above bundles, that drops to $80. It's a rather expensive machine for the internals it is touting, though the design and small form factor do help it somewhat. However, at the same time, the lack of upgradability hurts it. Valve says the ongoing parts shortages and massive price hikes for memory were the leading causes for this price. "The overall effect is that our original goal for the price of Steam Machine is no longer viable," added the company. "So the prices we're sharing today reflect the state of the world for manufacturing; or, more accurately, it reflects the price of the components as we've secured them over the past 6 months." Valve wants interested gamers to reserve it now to get the chance to pre-order a Steam Machine starting June 25, with shipping starting on June 29. Head here to sign up. The invites to buy it will be sent in a randomized order.
    • What the press release doesn’t mention, however, is how much water the natural gas plant itself will consume, Natural gas plants use about 2,803 gallons of water per megawatt-hour produced, which is significantly less than coal-fired plants that use around 19,185 gallons per megawatt-hour. Overall, natural gas plants are more water-efficient, using 584% less water than traditional power plants on average. AI generated
  • Recent Achievements

    • Dedicated
      tuben earned a badge
      Dedicated
    • Week One Done
      mnsgroup earned a badge
      Week One Done
    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      +Edouard
      203
    3. 3
      PsYcHoKiLLa
      97
    4. 4
      Michael Scrip
      82
    5. 5
      neufuse
      67
  • Tell a friend

    Love Neowin? Tell a friend!