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

Discussion in 'Windows 7' started by pilot76103, Aug 4, 2009.

Thread Status:
Not open for further replies.
  1. jkh334

    jkh334 MDL Junior Member

    Jul 31, 2009
    53
    0
    0
    Whats the big deal about chkdsk /r Ive never used it. Its asked me at start up before if I wanna run checkdisk and I usually just skip it anyway,
     
  2. PrEzi

    PrEzi MDL Addicted

    Aug 23, 2007
    534
    3
    30
    Well it seems that for some people it's more important than a stable and secure kernel :D

    P.S. You shouldn't skip those checks since your hdd is marked 'dirty' - it can be the reason of bad shutdown/ bad sectors / MFT errors etc.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. jkh334

    jkh334 MDL Junior Member

    Jul 31, 2009
    53
    0
    0
    hmm maybe that could be why i always have to hit the power button to finish shutting down vista.

    Edt-but I would assume that with this bug i should do it from within vista not 7?
     
  4. Stormcrow

    Stormcrow MDL Junior Member

    Jul 30, 2009
    76
    1
    0
    I've been at Microsoft whan an OS ( XP ) was moving towards RTM.

    They have very strict categorisation of bugs, in particular 'showstoppers'.
    At the run-up to RTM, 'showstoppers' had a definition which was something like 'actual data corruption under normal use'. I can't remember the actual wording.

    This is necassary, otherwise no software would ever actually ship.

    I don't see this bug falling into that category.

    --
    SC
     
  5. PrEzi

    PrEzi MDL Addicted

    Aug 23, 2007
    534
    3
    30
    Nah, just proceed as usual.
    Did run chkdsk /r on a few of my drives and I didn't get any BSODs nor data corruption. Mem usage was high, yes, but anyway - what would you expect ? It goes down after the scan/repairs ;)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. ZoeyZoey

    ZoeyZoey MDL Novice

    Jul 29, 2009
    11
    0
    0
    so there is no bug was a chipset controller issue, so everyone update chipset drivers etc, i dont have this bug on 4 of my pc's so can we close this thread?
     
  7. bertmace

    bertmace MDL Member

    Jul 14, 2009
    143
    0
    10
    Dos 5.0 was best win 3.0
     
  8. atifsh

    atifsh MDL Junior Member

    Jun 4, 2008
    73
    1
    0
    yes and iv heard crysis works like a charm on 6.22 :p.... u dont even need graphic card, everything is done by OS :p
     
  9. delweine

    delweine MDL Member

    May 1, 2007
    164
    0
    10

    ya man, pees me off for several reasons. i ran the test 3 times now, no memory leaks, no issues at all except the standard mem usage when running chkdsk /r on a non root drive.

    as far as these update packs. they could be just for internal usage. ive never seen update packs from ms change a build number before. that does not mean they have not, ive just never seen it.

    id be a bit weary about installing any update packs not currently offered via WU, MSDN, Connect, and Technet. in other words, my install is fine, perhaps a few minor bugs. but nothing to get into a chits about.
     
  10. pilot76103

    pilot76103 MDL Member

    Jul 30, 2009
    190
    33
    10
    Build 7600.16399 has already been made and leaked! It was a set of 8 Hotfix updates that does not include the "chkdsk" memory leak issue/fix.
     
  11. pilot76103

    pilot76103 MDL Member

    Jul 30, 2009
    190
    33
    10
    #52 pilot76103, Aug 4, 2009
    Last edited by a moderator: May 23, 2017
    (OP)
  12. ZoeyZoey

    ZoeyZoey MDL Novice

    Jul 29, 2009
    11
    0
    0
    its not a windows problem but chipset driver. everyone needs to update chipset drivers or wait for who ever makes your chipset drivers to update them for windows 7, im using lastest intel chipset drivers and it fix the problem.
     
  13. pilot76103

    pilot76103 MDL Member

    Jul 30, 2009
    190
    33
    10
    It does this on ATI, nVidia, and Intel chipsets... WTF are people who don't have chipset updates like me to do on my 5 year old XP unit, 2 year old Vista Laptop, and 2 year old MacBook. This needs to be fixed where it isn't a chipset issue since it is also present when booting from the DVD in the WinPE system.

    Updated main post with screenshots of issue being present in WinPE when booting from Windows 7 RTM 7600.16385 DVD.
     
  14. PrEzi

    PrEzi MDL Addicted

    Aug 23, 2007
    534
    3
    30
    Guys - just relax.
    Build 7600.16399 is nothing more than 16385 + hotfixes integrated.
    I don't see a point for this thread to exist any more except flaming...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. pilot76103

    pilot76103 MDL Member

    Jul 30, 2009
    190
    33
    10
    The topic needs to be open since the issue is present on Server 2008 R2 and when booting from the DVD as well.
     
  16. HotCarl

    HotCarl MDL Addicted

    Jul 21, 2009
    831
    16
    30
    #57 HotCarl, Aug 4, 2009
    Last edited: Aug 4, 2009
    ROFL! Great... Man, I still have flashbacks and night-terrors from those days, back in the good 'old early to mid 90's... Has it been that long? I remember running DOS 6.22 on an old PackardBell 60 Mhz Pent. 1 with 4MB of RAM (it could run Windows for Workgroups 3.11 too!)...and before that I had a 386 and a 486 runnin DOS... I think (if I recall correctly) that the 486 was running at something like 33 MHz and the 386 was running at like in the 20 to 25MHz range (when you pushed in the "Turbo" button...lol)... They both had less than 2MB RAM... Ohhhh, those were the days...
     
  17. delweine

    delweine MDL Member

    May 1, 2007
    164
    0
    10
    #58 delweine, Aug 4, 2009
    Last edited by a moderator: May 23, 2017
  18. pilot76103

    pilot76103 MDL Member

    Jul 30, 2009
    190
    33
    10
    If someone chooses to panic because I consider that this is a "Show Stopper" bug then so be it, that is on them. To me this is still a show stopper considering that it is present in the un-Patched and Patched RTM builds, x86 and x64, on Windows Server 2008 R2, and is also doing it when you boot from DVD. As far as all hardware configs, I consider VMWare, MacBook, HP Laptop, and Compaq Desktop to cover quiet a few Hardware configs to consider this a critical enough bug that it needs to be built into any Official ISO/DVD Microsoft releases to anyone! I appologize for creating panic, the topic title was to create attention and show concern regarding this matter.

    P.S. I accept your appology, next time please don't jump the gun without having proof or legitimate reason to do so.
     
  19. atifsh

    atifsh MDL Junior Member

    Jun 4, 2008
    73
    1
    0