Tomorrow, on May 6 2009, 03:08 PM, said:
I have stumbled into a showstopper bug possibly.Lately(well starting from Beta) ive had issue where Windows 7 builds become completely unbootable.
Basicly i installed a build and used it for x amount of time.When i tryied booting it a few days later it showed only the Starting Windows text and no boot animation appeared.This has always been consistent with these.Same place-same symptoms.Nothing also helped.
Startup Repair only gave vague idea what might be the case.System files integrity check produced code 0xa(not 0x0 wich means no erors) and once SR said A recent driver installation or upgrade may be preventing the system from booting.Other time it gave more vague Unspecified changes to system configuration might have caused this problem.The F8 advanced options were useless too.Safe mode always got stuck after loading the first line:
C:\Windows\system32\system.Other options(as ntbtlog.txt,Last known good configuration etc seemed to not work at all).So now im(hopefully) close to figuring it out.I installed RC build.Only created one Restore point and then left it alone fow few days(that was monday).Today it booted fine.Ill wait for few more days to be sure.
The only differences with other install(that became non-boot) are(things i did back in that install that could account for this problem):
Installed Nvidia Display drivers(185.81).Installed Marvell Yukon NIC driver(Win7 includes older out-of-box) and installed ACPI ATK110 Utility(whatever it is) that Windows Update offered me.
Additionally on my dualboot system(Vista Ultimate x86 SP2) Diskeeper was allowed to defragment the Windows 7 partition.
In this install(that so far seems to be alive) i did not install any drivers and i completely disabled Diskeepers ability to defragment the Win7 partition.Lets see.Im suspecting either the ACPI utility or Diskeeper.If this install survives then im first gonna enable diskeeper and see if install boots after few days.if it does then im gonna install the ACPI utility and so on...
Ok i can confirm now that diskeeper is the culprit here.Heres the list of files Diskeeper defragmented on Windows 7 partition.I will ofcourse contact Diskeeper Support and let them know that such problem exists.Diskeeper version is
Diskeeper 2009 Pro Premier 13.0.835.0
Quote
\Windows\inf\oem1.PNF
\Windows\System32\Logfiles\Scm\SCM.EVM.4
\Programdata\Microsoft\Windows\DRM\drmstore.hds
\Windows\System32\DriverStore\FileRepository\volsnap.inf_x86_neutral_be8328e5ba4ba68c\volsnap.PNF
\Windows\ServiceProfiles\NetworkService\Appdata\Local\Microsoft...\index.dat
\Users\Raivo\AppData\Local\Microsoft\Windows\Temporary Internet Files\index.dat
\Users\Raivo\AppData\Roaming\Microsoft\Windows\Cookies\Low\index.dat
\Users\Raivo\AppData\Local\Microsoft\Windows\History\Low\History\index.dat
\ProgramData\Microsoft\Search\Data\Applications\Windpws\Projects\SystemIndex\Indexer\CiFiles
\Program Files\Common Files\microsoft shared\ink
\Windows\Prefecth\ReadyBoot\Trace2.fx
\Windows\inf\setupapi.ev1
\windows\inf\volume.PNF
\Windows\System32\DriverStore\FileRepository\cpu.inf_x86_neutral_6e86496ecf9ae196\cpu.PNF
\Windows\inf\msmouse.PNF
\Windows\System32\DriverStore\FileRepository\netmyk01.inf_x86_neutral_a3f8c82b61266bbe\netmyk01.PNF
\Windows\inf\cdrom.PNF
\Windows\inf\usb.PNF
\ProgramData\Microsoft\Windows\WER\ReportQueue
\Windows\inf\fdc.PNF
\Windows\inf\netmyk01.PNF
\Windows\System32\DriverStore\FileRepository\display.inf_x86_neutral_f21b65d8760fc507\display.PNF
\Windows\inf\nv_lh.PNF
\Windows\inf\disk.PNF
\Windows\Prefetch
\Windows\ServiceProfiles\NetworkService\Pictures\{0B7F109D-EA3F-41B6-9369-C41FC570F779}.jpg
\Windows\System32\DriverStore\FileRepository\wudfusbcciddriver.inf_x86_neutral_7187dd9e15b5dbac\wudfusbcciddriver.PNF
\Windows\System32\DriverStore\FileRepository\usbprint.inf_x86_neutral_1ce968aef36c87f4\usbprint.PNF
\Windows\inf\input.PNF
\Windows\System32\DriverStore\FileRepository\rdpbus.inf_x86_neutral_23dba0d65491c989\rdpbus.PNF
\Windows\WindowsUpdate.log
\Windows\inf\monitor.PNF
\Windows\inf\rdpbus.PNF
\Windows\SoftwareDistribution\DataStore\Logs\edb.log
\Windows\Temp\TS_FE52.tmp
\Windows\rescache\rc0001\ResCache.hit
\Windows\System32\Driverstore\INFCACHE.1
\ProgramData\Microsoft\Search\Data\Applications\Windows\GatherLogs\SystemIndex\SystemIndex.1.gthr
\Users\Raivo\Contacts\Raivo.contact
\Windows\System32\LogFiles\WUDF\WUDFTrace.etl
\Windows\Temp\TS_ECAA.tmp
\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat
\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb
\Users\Raivo\AppData\Local\Microsoft\Windows Mail\edb00001.log
\Users\Raivo\AppData\Local\Microsoft\Windows Mail\edbres00002.jrs
\Windows\SoftwareDistribution\Download\Install\2000UNIN.EXE
\Windows\Temp\TS_F4DB.tmp
\ProgramData\Microsoft\RAC\StateData\RacDatabase.sdf
\ProgramData\Microsoft\RAC\PublishedData\racWmiDatabase.sdf
FridgeTooFar, on May 9 2009, 03:52 PM, said:
Well Server 2008 R2 will be 64bit only so you do the math on whether windows 8 is 32/64bit considering 4 gb ram will be norm by the time it comes about. (32bit has trouble even reading 4gb, due to address space, etc the argument old as time....)
Servers are running RAM in exess of 12GB.It makes sense that Windows Server version goes x64 only.I dubt that much people will have 4GB when Windows 8 comes.I mean look.2GB was the norm a while ago but even today many still run barely 1GB.Not to mention netbooks where 4GB is really premium today(ASUS EEPC etch).Most still come with 1GB or 2GB conf.
I have 2GB so i see no benefit from going x86 to x64 currently.I will go x64 once i build a new PC(4-8GB RAM) but not before.