Vista build and release dates

[Guest]

I can't install vista 64 bit on my pc due to a bsod error I get during the
last stage of installation. I'm hoping if I buy a current copy of vista with
a more recent release date I'll have better luck. Would later versions have
some bug fixes and more drivers or will all versions have the same version
number till a service pack is released? I tried to install vista 64 oem
build date date 2/15/07 and version number 6.0.6000.16386.

 

[Andrew McLaren]

I can't install vista 64 bit on my pc due to a bsod error I get during the
last stage of installation. I'm hoping if I buy a current copy of vista
with
a more recent release date I'll have better luck. Would later versions
have
some bug fixes and more drivers or will all versions have the same version
number till a service pack is released? I tried to install vista 64 oem
build date date 2/15/07 and version number 6.0.6000.16386.

No. The retail packs are *never* updated with interim fixes. If you buy a
copy of Vista today, it will be exactly the same as when Vista was first
released.

The exception is when Microsoft very clearly and publically released a
slipstreamed Service Pack release - as they did for XP Service Pack 2. You
could get a complete new copy of Windows XP to install, which already had
SP2 built-in. But that was a bit unusual; Microsoft didn't release an update
for XP SP1 for example.

There has been a bit of back-and-forth debate about this; but the decision
was based on providing customers with a known baseline. Otherwise, it would
be hard to tell exactly what revision level you were starting with. Some
might disagree with this decision, but ... there you have it.

You can roll hotfixes into a Vista setup, by using the Windows Automated
Installation Kit (WAIK). This involves a bit of work to set up, but it's the
"official" solution to getting hotfixes into an initial installation.
https://www.microsoft.com/downloads...7d-f12c-4676-917f-05d9de73ada4&displaylang=en

Probably not the answer you wanted, but I hope it helps a bit.

Which specific STOP error are you seeing, that prevents installation? There
may be other workarounds ...

 

[Guest]

Thanks for the reply Andrew, I'll try the link and see if that information
helps me. Unfortunately I didn't make a note of the last stop error I was
getting and wouldn't know what it was unless I try to reinstall vista but I
do remember loading vista in safe mode watching the list of loading drivers
suddenly stop. The folder path was windows/system32/drivers/crcdisk.sys. I
ran chkdsk, it found an error, fixed it but now the list of drivers stops at
windows/system32/drivers/disk.sys. I loaded all the new 64 bit drivers from
web sites and manufacturer discs. Vista accepted a bus driver and a network
driver. However it would not accept a video card driver ("installation
failed" message appeared) an IDE driver and a SATA driver. The bsod appears
shortly after the windows load screen begins with the bar under the windows
logo. The bsod has displayed an "IRQ_NOT_LESS_OR_EQUAL" error, a "0x000007E"
error (before I ran chkdsk) and another "0x000000" type error that I can't
remember. This may be more info than you expected, however I'm hoping more
info could improve my chances for a fix. If you think the last stop error
can help you figure out a work around or what the problem is I'll reinstall
vista and let you know tomorrow possibly.

 

[Andrew McLaren]

suddenly stop. The folder path was windows/system32/drivers/crcdisk.sys.
I

It's a bit misleading, actually ... crcdisk.sys is the last driver to get
loaded, during that phase of the boot process. So it's the just last driver
which gets displayed, even when the system boots normally. Folks sometimes
conclude (erroneously) it must be a really buggy driver

windows/system32/drivers/disk.sys. I loaded all the new 64 bit drivers
from
web sites and manufacturer discs. Vista accepted a bus driver and a
network
driver. However it would not accept a video card driver ("installation

Are you installing the 3rd party drivers during the setup process? Or
afterwards, when Vista is all installed and you've logged in for the first
time?

While it's usually good to use the vendor-supplied drivers, for performance
and features, for maximum stability the default Microsoft drivers are often
the best. You should normally be able to install Vista without any 3rd party
drivers at all - unless the boot drive is on a RAID controller which needs
special drivers.

But apart from that, you should be able to get Vista installed with just
what's on the Vista DVD. If you are seeing problems with STOP errors, I'd
recommed you start with a clean installation of Vista, as vanilla as
possible, with no 3rd party drivers. Get that installed, and make sure the
machine is running okay. Then, you can go back and add hardware-specific
vendor-supplied drivers for IDE, SATA, graphics etc. To isolate the cause of
STOP errors, you'd probably want to do this one driver at a time: ie,
install the graphics driver. Then use the machine for a while and satisfy
yourself it's running okay (maybe slow, but not crashing). Then and only
then, install the vendor SATA drivers. Again, use the machine for a while
and satisfy yourself it's running okay. Then install the IDE drivers. Use
the machine for a while and satisfy yourself it's running okay. And do on.
If you start to get blue screens, you can axiomatically suspect the last
driver you installed, is the culprit.

logo. The bsod has displayed an "IRQ_NOT_LESS_OR_EQUAL" error, a
"0x000007E"
error (before I ran chkdsk) and another "0x000000" type error that I can't

STOP 0x7E is nearly always caused by a buggy driver.

But if you actually *must* install 3rd party drivers, even just to get Vista
installed and running on the machine, then you must have somewhat unusual
hardware. In which case it's help if we know more about what the hardware
is, exactly.

 

[Guest]

The upgrade advisor lists two things that vista might have compatibility
issues with on my motherboard (according to gigabyte and microsoft its vista
certified). The nvidia network controller and the onboard sound which is
disabled anyway. Only my modem is displayed as "will not work with windows
vista". Modems are cheap so no worries there. I was careful to buy vista
certified components. Here are my specs:

Intel Core 2 Duo E6700 Conroe 2.66GHz LGA 775 Processor

GIGABYTE GA-N650SLI-DS4 LGA 775 NVIDIA nForce 650i SLI ATX Intel Motherboard

Patriot Extreme Performance 4GB(2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2
6400) Dual Channel Kit Desktop Memory

PNY GeForce 8600GTS 256MB 128-bit GDDR3 PCI Express x16 HDCP Ready SLI
Supported Video Card (2)

Creative Sound Blaster X-Fi XtremeGamer 7.1 Channels PCI Interface Sound Card

ASUS Black SATA DVD-ROM Drive Model DVD

ASUS 18X DVD±R DVD Burner with LightScribe and 14X DVD-RAM Write Black SATA
Model DRW

Seagate Barracuda 7200.10 (Perpendicular Recording) ST3250620AS 250GB 7200
RPM SATA 3.0Gb/s Hard Drive - OEM

I'm installing drivers during the setup process. I'm not able to log into
vista. Nvidia has recently released 64 bit chipset and video drivers.
Creative labs has released 64 bit x-fi drivers with limited functinality.
The modem is the only item listed out of my whole setup that will not work.
Your help is greatly appreciated.

 

[Jane C]

Hi me too,

There is a known issue with certain configurations using over 3GB RAM. Can
you install with just 2GB, then apply the fix here:

http://support.microsoft.com/kb/929777

Does this then work?

 

[Guest]

Thanks Jane....I'll definately try what you've suggested and let you know if
it worked for me.

 

[Guest]

I've noticed the fix has a .msu extension. Vista will recognize this as an
exectuable? I'm guessing the double click rule still applies to open
exectuable files in vista.

 

[Andrew McLaren]

I've noticed the fix has a .msu extension. Vista will recognize this as
an
exectuable? I'm guessing the double click rule still applies to open
exectuable files in vista

Yes. The *.msu extension is associated with Windows Update
(system32\wusa.exe). If you double click on the msu file, Windows Update
will automatically run and install the file. Likewise you could just run the
msu file, at a command like.



(Hey Jane ... sorry for pushing in

 

[Guest]

Thanks very much for the help Jane and Andrew. I removed 2 gigs of memory,
installed vista without a hitch, downloaded the 929777 update, reinstalled
the same 2 gigs (after a reboot of course) and vista is now performing
flawlessly. I'm sure that patch could help alot of others if only more
people were aware of its availability. Thanks again

 

[Andrew McLaren]

Thanks very much for the help Jane and Andrew. I removed 2 gigs of
memory,
installed vista without a hitch, downloaded the 929777 update, reinstalled
the same 2 gigs (after a reboot of course) and vista is now performing
flawlessly. I'm sure that patch could help alot of others if only more

Outstanding! Thanks for letting us know it worked.

(And thanks Jane for remembering the crucual 929777 fix, which I'd neglected
in my first reply!)

 

[Jane C]

Hi me too,

Glad that got the problem solved for you. Thanks for posting back and
letting us know