Chkdsk bug in Windows 7 RTM Build 7600.16385/16399


Recommended Posts

As for illeagle software!! YES IT IS ! as there are no official legitmate downloads out yet! you must have it from a torrent ! therefore illeagle

If you have a problem speak to the staff, stop trolling this thread with your worthless posts. Also, how do you know where I got my ISO from, are you telepathic or something? it is possible to get them from insider contacts, work, TAP, ETC...

SO is this happening on all those *LEAKED* builds...with the chinese altered files? SO you guys are sending an unknown third party all kinds of data from your computer, when you think your chkdsk is bugged? hahahaha... :)

You got an MVC award posting nonsense like that? wow. The ISO I have is actually a totally untouched English install image, guess that argument failed pretty quickly.

The original user who found the bug stated to me that he had his unit BSOD. I haven't let my chkdsk run long enough to risk a BSOD and cannot confirm if BSODs are true.

Actually, since my XPS has 8 gigs of RAM, I didn't get a BSOD. All I found was that there is an obvious memory leak within chkdsk.exe. If anybody is experiencing BSOD's, that is definitely news to me. With the amount of RAM that is being consumed, I wouldn't be surprised.

But, since I see this thread has gone to sh*t, I'm gonna go back to my forums, where we try to resolve issues or create workarounds, rather than start a flame war over illegal software or whatever else you folks are complaining about. Thanks to everybody who actually contributed to this and let's hope we get some resolve through a hotfix/QFE before too long. Back to W7C I go! If you want to get people to actually help, I recommend going there instead.

I investigated this a bit further, and it isn't a leak as such, but it is still rather worrying. It climbed to about 95% of my available memory then stopped climbing, with no BSOD resulting.

UPDATE:

After emailing back and forth with the VP Sinofsky, it was found that the chkdsk /r tool is not at fault here. It was simply a chipset controller issue. Please update you chipset drivers to the current driver from your motherboard manufacturer. I did mine, and this fixed the issue. Yes it still uses alot of physical memory, because your checking for physical damage, and errors on the Harddrive your testing. I'm currently completed the chkdsk scan with no BSOD's or computer sluggishness. Feel free to do this and try it for yourselves. Again, there is no Bug.

Thanks all.

fixed.jpg

Edited by FireRx
It was simply a chipset controller issue.

But I was able to reproduce the fault in a VM also..?

Yes it still uses alot of physical memory, because your checking for physical damage, and errors on the Harddrive your testing.

Um - care to elaborate here? Why is it still using a lot of physical memory to accomplish which the same task on Windows Vista does not? Myself and a few other folks here report that Vista uses between 8MB and 16MB when running chkdsk..

I still think this is a bug.

UPDATE:

After emailing back and forth with the VP Sinofsky, it was found that the chkdsk /r tool is not at fault here. It was simply a chipset controller issue. Please update you chipset drivers to the current driver from your motherboard manufacturer. I did mine, and this fixed the issue. Yes it still uses alot of physical memory, because your checking for physical damage, and errors on the Harddrive your testing. I'm currently completed the chkdsk scan with no BSOD's or computer sluggishness. Feel free to do this and try it for yourselves. Again, there is no Bug.

Thanks all.

Ok, but the memory usage is supposed to be that high? Just checking. :)

Why does it seem I'm the only one not having this problem? :blink:

Oh, and to the people yelling at me on the first page, I posted that before anyone had added screenshots. It seemed logical at the time that a new guy posting a bug that I couldn't reproduce with no screenshots was fake. Others have confirmed it now, but it doesn't happen to me. Check the time I posted and the times people edited their posts before you get all upset.

UPDATE:

After emailing back and forth with the VP Sinofsky, it was found that the chkdsk /r tool is not at fault here. It was simply a chipset controller issue. Please update you chipset drivers to the current driver from your motherboard manufacturer. I did mine, and this fixed the issue. Yes it still uses alot of physical memory, because your checking for physical damage, and errors on the Harddrive your testing. I'm currently completed the chkdsk scan with no BSOD's or computer sluggishness. Feel free to do this and try it for yourselves. Again, there is no Bug.

Thanks all.

fixed.jpg

I am using version 15.35 of my chipset drivers, the latest available so I don't buy that for a second. Especially seeing as under the same circumstances in Vista you don't get this issue. Not to mention high data throughput doesn't automatically equal high memory usage.

Also, my Laptop has an ATI chipset, and my desktop an nVidia chipset, I see you have and others that are experiencing this have an Intel chipset as well, so please tell me what exactly is the common link here? Are you telling me that 3 different chipsets from 3 different manufacturers ALL have bugs in them that cause the same memory issue, in exactly the same set of circumstance, even with different brands, sizes, and speeds of hard drives? please.

The process ended without any BSOD at all for me (I posted the screenshot of my laptop running CHKDSK earlier on).

Could be as well the chipset's driver or not. I'm using the latest from Intel.

However, I'm still thinking this is normal (As weird as this huge amount of RAM usage is).

I know that many of the users who have posted their own tests here have plenty of RAM (4gb and more) and are surprised to see some process use GB's of free RAM like nothing before.

Has someone tried this on a computer with 2gb or even 1gb to see how it ends up?

Just because I don't think anyone has confirmed whether this behaviour is "by design" or not (i.e. was present in Vista too) I'm running a chkdsk /r on a 500GB volume here on a Windows Vista Enterprise x64 SP2 system and memory usage has not gone above 17,204K for the chkdsk process yet.. so it's definitely a fault in Windows 7!

chkdsk can run automatically if a system was not cleanly rebooted. If you end up where a user is being forced through a chkdsk process, then the system blue screens too then you're potentially into a data loss. The scenario is easy to forsee so I agree when everyone is saying that this is a critical bug which needs fixing and is definitely bordering on being a showstopper.

That is the big thing I was trying to hammer home when people would look at me and say something about theatrics... I was trying to say this is definantly show stopper seeing the point that if a BSOD were to occur during chkdsk fixing a hard drive this could lead to perminant data deletion/loss. Unfortunatly, there are some who thought i was taking it a bit too far. Look at my screen shot also. My RAM maxes out on stage 4 of 5 and doesn't even start to show a % of Stage 4 completed. I can't complete a check disk and it uses 2,901,000K of memory on a 4GB system. Tell me that I'm not doing a set of Theatrics!

Has someone tried this on a computer with 2gb or even 1gb to see how it ends up?

I ran it on a Windows Server 2008 R2 Virtual Machine (under VMware Workstation 6.5) - it used up about 540MB RAM for the chkdsk process. I think the VM only had 1.5GB allocated to it, but it took physical memory usage up to about 95% so was definitely near to maxing it out. If I'd allocated 4GB to the VM I've no doubt it would have ate enough to take it up to 95% still.

I am using version 15.35 of my chipset drivers, the latest available so I don't buy that for a second. Especially seeing as under the same circumstances in Vista you don't get this issue. Not to mention high data throughput doesn't automatically equal high memory usage.

Also, my Laptop has an ATI chipset, and my desktop an nVidia chipset, I see you have and others that are experiencing this have an Intel chipset as well, so please tell me what exactly is the common link here? Are you telling me that 3 different chipsets from 3 different manufacturers ALL have bugs in them that cause the same memory issue, in exactly the same set of circumstance, even with different brands, sizes, and speeds of hard drives? please.

I agree I have 2 nVidia chipsets doing this and also on my Intel Chipset MacBook.

Just as a additional FYI this issue is present in WinPE when booting directly from the Windows 7 DVD also and I have photos of the proof coming soon.

Just to clarify something to everyone, we are still using drivers that are either beta, or designed to work with a different operating system (Vista), so this could be very well a chipset problem, but we'll have to see as Microsoft look more into the problem.

Yeap, confirmed here too, though I wouldn't necessarily call it a showstopper bug :p

No, not a showstopper. Kind of like the old Marx Brothers joke: "Doc, it hurts when I do this..."

"Then don't do that!"

I'm pretty sure I can go a day or two without running chkdsk until a patch is applied.

BTW, is this present in both x86 and x64?

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

    • No registered users viewing this page.
  • Posts

    • Hello, Hope all is well. I am in UK.  
    • I'm not happy with myself for it, but I've gone and got hold of it. Just another 45 minutes and I'll be Bond, James Bond. In my defence, IO's Hitman series is awesome, and I'm a sucker for 007. So while it might seem a bit simplified compared to Hitman, I'm sure I'll be right at home.
    • Or just check the script yourself ^^. I hate having a Microsoft account tied to my windows install.
    • 007 First Light review: Satisfying spy adventure that James Bond needed by Pulasthi Ariyasinghe I have fond memories of classic James Bond games from the Electronic Arts era. Using high-tech gadgets, sneaking into parties, and dispatching bad guys were wildly exciting activities for my younger self. In recent years, Bond games have entirely disappeared, alongside the super spy genre. Fast forward to 2020, imagine my surprise when IO Interactive announced it had secured the Bond IP to make a game. Considering the studio’s Hitman history, this project is one I keenly kept an eye on. Six years later, 007 First Light is finally here, and after spending time inside this globe-trotting adventure, I can safely say that my excitement for this developer’s take on this universe was not unfounded. IO has taken lessons it has learned from Hitman and combined them with what I would expect from a directed cinematic experience like James Bond. I have refrained from mentioning major plot points to save you from story spoilers in this review. This is an original story that doesn’t tie into any movies, so there isn’t an expectation of knowing the backstory or the decades of movies either. Bond, James Bond When 007 First Light begins, Bond is just Bond. There isn’t a spy angle, fancy gadgets, or even a secret mission. The introductory mission is framed to show how James Bond handled himself and how he does not care about the odds when it comes to saving lives. It’s a gorgeous level as well, showing off an island scattered with cliffs in the middle of a storm. Looking back, this is probably the best-looking level in the game, with IO showing off all its abilities with its custom engine, Glacier. But my favorite ended up being the follow-up to this level. Once the United Kingdom's foreign intelligence agency, MI6, recruits our daring youngster into its super-spy “00” program, training begins. However, instead of treading through the same tutorial missions where the game teaches you to run and jump and drive, IO opted for a montage, and it’s amazing. The scenes cut between Bond practicing and improving his marksmanship, parkour, hand-to-hand combat, and driving as weeks go by in his training. What impressed me here was the lack of any loading screens or stutters as scenes instantly switched to different locations entirely, as if I was watching a movie. This creativity is a trend I noticed in most levels, where there is some sort of gameplay or choreography mechanic being introduced to keep things interesting. Soon, the rest of the cast is introduced, bringing other agents that our favorite secret agent will be working with, the scientists and engineers that build MI6’s spy gadgets, as well as higher-ranking officers that either appreciate or (at best) tolerate Bond’s rebellious attitude. It’s a tight cast, all with incredibly good voice acting and personalities that quickly grew on me. The casting for Bond himself is also an excellent one. From showing his iconic soft spot for women to the condescending smiles that get a rise out of enemies, I had no issues getting immersed into this universe as this new face of James Bond. The missions take place in a wide range of locations as MI6 sends Bond to tackle dangers that are growing everywhere from the UK to Africa. These aren’t unrelated adventures where MI6 is sending secret agents, which is an angle I would love to see in another game, but a part of a bigger conspiracy affecting the entire world. Some of the twists and turns were all too predictable, and the character that Lenny Kravitz played made me cringe a little too much. But all in all, I enjoyed the campaign’s storyline that sets the stage for this new agent joining the illustrious “00” program. Plenty of Possibilities The third-person style of IO Interactive fits this role quite well. Bond is presented as a master at hand-to-hand combat as well as firearms, while also having a knack for being stealthy when required. Most sections of missions have a lot of freedom. This means I could beat up every goon and security guard on the way to an objective, slip past them without sounding a single alarm, or do a mix of both. My sessions usually end up with the third option because I tend to be impatient about waiting for a patrol to move. Drawing from its Hitman genes, the developer almost always gives multiple routes for going through missions. Levels can be massive, sometimes sporting hundreds of NPCs going their own ways and having conversations. If my objective is to break into a security room on the third floor, I could look around for roof access, eavesdrop on conversations to find out where someone lost a key, create a distraction and pickpocket a guard for a keycard, sneak in through the vents, or simply kick down the offending door. I enjoyed the variety on offer, especially because the same solutions didn’t usually show up in different missions. Before heading out into a secret MI6 escapade, the gadget specialist of the branch walks Bond through the organization's latest and greatest achievements. This can be cool little devices like a laser built into the watch, a phone that fires poison darts, or a camera that emits a powerful shockwave. The choice of what can be taken into the mission is up to the player. I could usually find fresh routes or get out of tough situations with a punch or two, so I never had the feeling of missing out by not choosing the right equipment. It’s still a fun practice. Choosing the armaments before a mission enhanced the super spy feeling quite a bit. As I mentioned, stealth comes in as a very viable option for most of the missions, letting Bond sneak past foes or knock them out silently. While it is satisfying to clear entire areas of goons and walk away without any alarms, the way of accomplishing this could have been done better. Bond can lure enemies, sneak up and knock them out, or use a gadget to disorient them before dealing a nasty blow. Bodies cannot be moved or hidden afterward either. It’s a very simple system, which I wish were more exciting to pull off. Perhaps more stealth-orientated gadgets, distraction options, or multi-takedowns could have helped here, I think. Getting caught while attempting to be in stealth does not mean a game over. Other than getting into a fist fight, an interesting twist of 007 First Light is the bluffing option. While an enemy is confused as to what you are doing in a restricted location, Bond has the option to improvise and persuade them that you are exactly where you’re supposed to be. These are fun little dynamic interactions with unique dialog depending on the mission and location, giving a few extra moments for Bond to go past suspicious guards smoothly. It’s the first time I’ve witnessed this system in a game, and I hope to see more. License to Kill Bond isn’t just dealing with security guards or civilians. From time to time, entire gangs of gun-toting mercenaries show up in levels looking to take down our protagonist. It is then that License to Kill mode is activated for Bond, letting him use firearms with no restrictions. I was surprised by just how tight gunplay is in 007 First Light. The weapons feel powerful and satisfying to fire, with single bullets capable of taking down an enemy with a headshot. Ammo is scarce, and enemies don’t drop weapons with full magazines most of the time. This forces a hectic kind of gameplay where I am always advancing towards enemies to take their weapons after they are downed. Things like shooting legs to immobilize, aiming at the hands to make their weapon go flying, blowing up nearby fire extinguishers for cover, and using gadgets to halt a goon in their tracks while I reload, make up enjoyable levels. I had to hold back my disappointment when the enemy count in these action sequences dropped to zero and I had to go non-lethal again. Speaking of action sequences, First Light isn’t just offering sandbox levels to complete at the player’s own leisure either. Each level comes with specific linear and directed scenes to move the story forward and put Bond in tight situations. These usually end up with high-octane chases or driving sections, offering the chance to witness chaining explosions, hails of gunfire, and scripted parkour scenes that remind me of Mission Impossible movies more than Bond. Elements like seeing James Bond jump out of a plane without a parachute or drive through buildings in London inside a trash truck were fantastic and always left me at a high point when finishing a mission. The classic James Bond theme is sprinkled in here too, which only happens a handful of times in the game, but at just the right moments. Visuals and Performance Compared to Unreal Engine 5 games we are seeing nowadays, 007 First Light isn’t flexing a huge amount of realism when it comes to graphics. The models, textures, and effects all feel a little dated, with the starting mission that I mentioned being the most visually striking. However, the complete lack of stutters, the hundreds of NPCs that can be on screen without a single hitch, massive sandbox levels, and smooth transitions between them all play a part in making this an immensely immersive and complex experience. The in-engine cutscenes are gorgeous as well, offering an upgraded visual style and model detail over the gameplay sections. Animations are one aspect that jumps out at me about any new game, and First Light has nailed what a third-person action game should feel like. Walking, sneaking, and running all have a heaviness to them that I appreciate. Whenever Bond moves past a wall or a ledge, his arms reach out to lightly hold those structures until he moves away. NPCs actually react to my character and move out of the way. Even during melee combat or takedown animations, the fists impacting a body or a head hitting a wall all have that same weight. Even the more frivolous animations, like catching a gun in midair or chucking an empty one at a goon (yes, you can do that), are satisfying to pull off. Of course, the in-engine cutscene animations are remarkably well done too, with facial animations and the upgraded model details improving my engagement with the characters. I have an AMD Radeon RX 9070 XT 16GB paired with an eight-core Ryzen 7 3700X and 32GB of RAM, with the game running at 1440p resolution. Deciding to completely max out all the graphics options gave me a range of frame rates between 60 and 100 depending on the scene and level. While I did try to enable AMD FSR, which bumped up the frame rates by a good 20% at Quality mode, IO Interactive’s implementation of the technology wasn’t that great. Every corner and edge in levels began shimmering, and I was also seeing smearing issues in fast-moving sections. The title seemingly uses the older generation FSR 3.1 and not the machine learning-assisted FSR 4, leading to these artifacts. Unfortunately, there isn't a way to manually upgrade this right now either. I opted to turn off the upscaling and play the game in native 1440p to avoid problems. I would say the FPS range I was getting was an acceptable one for a single-player action game for my setup. I do wish there were an FOV slider option in the settings. While the camera is far enough back for my tastes in most situations in this third-person adventure, at times the perspective is far too close. When trying to look around quickly and spot targets, I realized I was getting a slight headache at times due to the use of an almost over-the-shoulder close-up camera. Conclusion Being James Bond in 007 First Light is a treat. Traveling around the world chasing conspiracies, using high-tech gadgets disguised as everyday accessories, and improvising on the spot to fool foes all give a fantastic feeling of being a super spy. For an origin story, IO Interactive has done a great job at introducing the character and his motives for doing what he does. The satisfying combat animation and fantastic voice acting are definitely high points, with the License to Kill moments being my favorite. Not being able to move bodies and the simplistic stealth of mechanics does hurt its presentation a little. The NPC logic and intelligence is easy to manipulate and trick, repeating the same actions over and over again if I keep making distractions. The lack of an FOV slider was also a pain (quite literally) at times, and the FSR implementation is quite poor. These are things I hope the studio will improve upon with updates. Even with its faults, IO Interactive and James Bond are a match made in heaven. The studio knows how to make a main character that oozes charm and competency while also leaning heavily into its Hitman experience to make gigantic levels with what looks like hundreds of NPCs roaming around. Being an origin story, IO’s Bond has a way to go before he becomes the highly effective agent we see in the movie world. I am hoping the studio will continue this series alongside its Hitman ventures going forward, just so we get to experience the journey for longer. 007 First Light is available on PC (Steam, Epic Games Store, and Xbox PC), Xbox Series X|S, and PlayStation 5 for $69.99. This review was conducted on the PC version of the game provided by IO Interactive.
  • Recent Achievements

    • Collaborator
      conkir earned a badge
      Collaborator
    • Rising Star
      olavinto went up a rank
      Rising Star
    • One Month Later
      lamborghiniv10 earned a badge
      One Month Later
    • Week One Done
      lamborghiniv10 earned a badge
      Week One Done
    • Reacting Well
      X-No-file earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      PsYcHoKiLLa
      271
    3. 3
      +Edouard
      75
    4. 4
      Skyfrog
      74
    5. 5
      Steven P.
      71
  • Tell a friend

    Love Neowin? Tell a friend!