TheHotfix.net Forums: CRITICAL SHOW STOPPER BUG in Windows 7 RTM Build 7600.16385 and Patched 7600.16399 - TheHotfix.net Forums

Jump to content

  • (3 Pages)
  • +
  • 1
  • 2
  • 3
  • You cannot start a new topic
  • You cannot reply to this topic

CRITICAL SHOW STOPPER BUG in Windows 7 RTM Build 7600.16385 and Patched 7600.16399

Poll: CRITICAL SHOW STOPPER BUG in Windows 7 RTM Build 7600.16385 and Patched 7600.16399 (71 member(s) have cast votes)

What should Microsoft do about this bug?

  1. Recall/Redistribute RTM Including OEMs, fix the issue, then re-RTM (15 votes [21.13%])

    Percentage of vote: 21.13%

  2. Integrate fix with TechNet, MSDN, and GA copies before making it available (3 votes [4.23%])

    Percentage of vote: 4.23%

  3. Patch with a Windows Update Hotfix (48 votes [67.61%])

    Percentage of vote: 67.61%

  4. Nothing at all (3 votes [4.23%])

    Percentage of vote: 4.23%

  5. I don't know what problem your talking about (2 votes [2.82%])

    Percentage of vote: 2.82%

Vote Guests cannot vote

#1 User is offline   Jordan M. Jacob 

  • Hardcore Nerd
  • PipPipPipPipPip
Group:
Member
Posts:
140
Joined:
09-November 06
Gender:
Male
Location:
Ellerslie, GA
Country:
Interests:
Computers, Storm Chasing, and Video/TV Production.

Post icon  Posted 04 August 2009 - 02:15 AM

A critical show stopper bug has been found in the Final Windows 7 RTM 7600.16385 and in the updated 7600.16399 builds! Thanks to mikerolsonw7c of Windows7Center for informing us of the critical bug. The issue is related to the "chkdsk /r" command on a drive other than the system drive. For example if you have drive C: and drive D: with C: being Windows 7. If you open "cmd" and run "chkdsk /r D:" on "Stage 4" of chkdsk it will have a very critical memory leak and max out the system memory then BSOD due to lack of memory available. This issue is present on non-Patched 7600.16385 and Patched 7600.16399 RTM builds. This is a very critical bug that Microsoft should have caught before sending 7600.16385 to OEMs. Sadly, now Microsoft will have to fix this and then re-distribute RTM code to OEMs or patch it. I would not doubt myself when Microsoft gets word of this Show Stopper bug if the TechNet/MSDN releases on Thursday the 6th get pushed back to re-implement new code into the RTM build.


#2 User is offline   Jordan M. Jacob 

  • Hardcore Nerd
  • PipPipPipPipPip
Group:
Member
Posts:
140
Joined:
09-November 06
Gender:
Male
Location:
Ellerslie, GA
Country:
Interests:
Computers, Storm Chasing, and Video/TV Production.

Posted 04 August 2009 - 02:49 AM

UPDATED ARTICLE!

A critical show stopper bug has been found in the Final Windows 7 RTM 7600.16385 and in the updated 7600.16399 builds on both 32-bit (x86) and 64-bit (x64) installs! Thanks to mikerolsonw7c of Windows7Center for informing us of the critical bug. The issue is related to the "chkdsk /r" command on a NTFS drive other than the system drive (Issue not present for FAT32 Drives). For example if you have drive C: and drive D: with C: being Windows 7. If you open "cmd" and run "chkdsk /r D:" on "Stage 4" of chkdsk it will have a very critical memory leak and max out the system memory then BSOD due to lack of memory available. This issue is present on non-Patched 7600.16385 and Patched 7600.16399 RTM builds. This is a very critical bug that Microsoft should have caught before sending 7600.16385 to OEMs. Sadly, now Microsoft will have to fix this and then re-distribute RTM code to OEMs or patch it. I would not doubt myself when Microsoft gets word of this Show Stopper bug if the TechNet/MSDN releases on Thursday the 6th get pushed back to re-implement new code into the RTM build.

http://img43.imageshack.us/img43/4471/windows7bug.th.png


#3 User is offline   #13 D. Limes 

  • Daniel J. Limes
  • Icon
Group:
Exclusive Member
Posts:
1207
Joined:
31-May 06
Gender:
Male
Location:
Perrysburg, Ohio
Country:
Interests:
Sports, Girls, Computers, the usual

Posted 04 August 2009 - 02:57 AM

Nice find!

Off-Topic



#4 User is offline   Jordan M. Jacob 

  • Hardcore Nerd
  • PipPipPipPipPip
Group:
Member
Posts:
140
Joined:
09-November 06
Gender:
Male
Location:
Ellerslie, GA
Country:
Interests:
Computers, Storm Chasing, and Video/TV Production.

Posted 04 August 2009 - 03:14 AM

View Post#13 D. Limes, on 03 August 2009 - 10:57 PM, said:

Nice find!

Off-Topic


Off-Topic

This post has been edited by Jordan M. Jacob: 04 August 2009 - 03:17 AM



#5 User is offline   diablofan 

  • TheHotfix Addicted
  • Icon
Group:
Graphics Designer
Posts:
1874
Joined:
28-April 06
Gender:
Male
Location:
Ohio
Country:
Interests:
Building/Fixing Computers, Programming, Video Games, Camping, Anime, Manga

Posted 04 August 2009 - 03:41 AM

And I was hoping that nothing like this would show up. Damn, I guess were waiting...again.


#6 User is offline   redrumy3 

  • Hardcore Nerd
  • Icon
Group:
Basic Sponsor
Posts:
125
Joined:
11-August 07
Gender:
Male
Country:

Posted 04 August 2009 - 04:02 AM

they wont release a new rtm iso they will have hotfixes via windows update im guessing thats what those updates that were leaked by the person who leaked rtm :)

since those hotfixes he leaked did change build number


#7 User is offline   Jordan M. Jacob 

  • Hardcore Nerd
  • PipPipPipPipPip
Group:
Member
Posts:
140
Joined:
09-November 06
Gender:
Male
Location:
Ellerslie, GA
Country:
Interests:
Computers, Storm Chasing, and Video/TV Production.

Post icon  Posted 04 August 2009 - 04:12 AM

View Postredrumy3, on 04 August 2009 - 12:02 AM, said:

they wont release a new rtm iso they will have hotfixes via windows update im guessing thats what those updates that were leaked by the person who leaked rtm :)

since those hotfixes he leaked did change build number


If you read my post exactly as is redrumy3, this issue has been confirmed by other users running on the Hotfixed 7600.16399 Build and is still present.


#8 User is offline   redrumy3 

  • Hardcore Nerd
  • Icon
Group:
Basic Sponsor
Posts:
125
Joined:
11-August 07
Gender:
Male
Country:

Posted 04 August 2009 - 04:17 AM

View PostJordan M. Jacob, on 04 August 2009 - 12:12 AM, said:

If you read my post exactly as is redrumy3, this issue has been confirmed by other users running on the Hotfixed 7600.16399 Build and is still present.

yeah i messed up and didnt see that one part :X lol sorry


#9 User is offline   Franpa 

  • Geek of the Week
  • Icon
Group:
Basic Sponsor
Posts:
741
Joined:
08-March 08
Gender:
Male
Location:
QLD, Brisbane
Country:

Posted 04 August 2009 - 04:18 AM

7600.16399

Where is this? can't disable bold... I already have 8 hotfix/updates applied.

This post has been edited by Franpa: 04 August 2009 - 04:19 AM



#10 User is offline   Witt3439 

  • Geek of the Week
  • Icon
Group:
Premium Sponsor
Posts:
380
Joined:
18-July 06
Gender:
Male
Location:
West Virginia
Country:

Posted 04 August 2009 - 05:19 AM

If I'm not mistaken Franpa, the update KB972636 (included in the update package) is the one that installs the GDR update and changes the build number.

This post has been edited by Witt3439: 04 August 2009 - 05:19 AM



#11 User is offline   Scott 

  • Resident
  • Icon
Group:
Premium Sponsor
Posts:
447
Joined:
08-May 06
Gender:
Male
Location:
Louisville Ky
Country:
Interests:
Computers duh

Posted 04 August 2009 - 05:21 AM

any ome running the rc or beta to see if this is present in older builds
just wanna kow how longs its been in it
that one program that i might have to run once a year


#12 User is offline   Franpa 

  • Geek of the Week
  • Icon
Group:
Basic Sponsor
Posts:
741
Joined:
08-March 08
Gender:
Male
Location:
QLD, Brisbane
Country:

Posted 04 August 2009 - 05:40 AM

I have KB972636 installed and "slmgr -dlv" still says 16385. Can't figure out where to look in the registry, but I'm pretty sure the only change to the Windows version # the 8 updates did was change it from RTM to GDR.

This post has been edited by Franpa: 04 August 2009 - 05:41 AM



#13 User is offline   #13 D. Limes 

  • Daniel J. Limes
  • Icon
Group:
Exclusive Member
Posts:
1207
Joined:
31-May 06
Gender:
Male
Location:
Perrysburg, Ohio
Country:
Interests:
Sports, Girls, Computers, the usual

Posted 04 August 2009 - 05:41 AM

HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrent Version

displays 16399 GDR in there

7600.16399.amd64fre.win7_gdr.090722-1835 in BuildEx

This post has been edited by #13 D. Limes: 04 August 2009 - 05:42 AM



#14 User is offline   Franpa 

  • Geek of the Week
  • Icon
Group:
Basic Sponsor
Posts:
741
Joined:
08-March 08
Gender:
Male
Location:
QLD, Brisbane
Country:

Posted 04 August 2009 - 05:44 AM

7600.16399.amd64fre.win7_gdr.090722-1835

Ok then, maybe it did change :)


#15 User is offline   #13 D. Limes 

  • Daniel J. Limes
  • Icon
Group:
Exclusive Member
Posts:
1207
Joined:
31-May 06
Gender:
Male
Location:
Perrysburg, Ohio
Country:
Interests:
Sports, Girls, Computers, the usual

Posted 04 August 2009 - 05:48 AM

And the updates gave me a bit more of a performance boost :) I installed like all 7 updates or something like that in a zip package on here somewhere


#16 User is offline   Jordan M. Jacob 

  • Hardcore Nerd
  • PipPipPipPipPip
Group:
Member
Posts:
140
Joined:
09-November 06
Gender:
Male
Location:
Ellerslie, GA
Country:
Interests:
Computers, Storm Chasing, and Video/TV Production.

Post icon  Posted 04 August 2009 - 05:56 AM

View PostFranpa, on 04 August 2009 - 12:18 AM, said:

7600.16399

Where is this? can't disable bold... I already have 8 hotfix/updates applied.


If you check in your regedit under "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version" you will see the 7600.16399 build string.


#17 User is offline   shatrughan 

  • Peruser
  • PipPipPip
Group:
Member
Posts:
36
Joined:
24-July 07
Country:

Posted 04 August 2009 - 06:08 AM

great find

what will microsoft do now

will it re issue a new RTM build to all OEM or
will it patch the holes with a hot fix


#18 User is offline   Franpa 

  • Geek of the Week
  • Icon
Group:
Basic Sponsor
Posts:
741
Joined:
08-March 08
Gender:
Male
Location:
QLD, Brisbane
Country:

Posted 04 August 2009 - 06:09 AM

I already mentioned it did change... :blink:


#19 User is offline   #13 D. Limes 

  • Daniel J. Limes
  • Icon
Group:
Exclusive Member
Posts:
1207
Joined:
31-May 06
Gender:
Male
Location:
Perrysburg, Ohio
Country:
Interests:
Sports, Girls, Computers, the usual

Posted 04 August 2009 - 06:34 AM

It may be a bit of a hassle to recall all those OEMs but it's a huge bug that needs to be implemented into the "official" RTM. They need to fix that, and should have caught it before the release. A hotfix is nice, but it needs to be integrated.


#20 User is offline   Shayla 

  • 장미처럼 - 미스 너
  • Icon
Group:
Super Moderator
Posts:
3390
Joined:
28-August 06
Gender:
Female
Country:

Posted 04 August 2009 - 06:35 AM

so does it mean Microsoft will re-distribute RTM build for TechNET/MSDN on Aug 6th?I know RTM build still is still unchange (16385) but hope we can get the clean build without any critical bugs in it :)


  • (3 Pages)
  • +
  • 1
  • 2
  • 3
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users