Initial reboot immediately black screens

[Guest]

I'm running a WD SATA 160GB HD and a Silicon Image on-board SATA Controller.
That's the setup that will run my Vista install. I have no other HDs on my
system. Anyways.

I've loaded the controller drivers onto a floppy. I pop the Vista DVD in
and it loads, no problem. I click the load drivers option and it finds the
controller driver on A:, again, no problem. I select, click format(it's a
new drive after all), and then commence with installation, still no problem.
It installs through the initial install process and then goes to reboot,
still no problem.

Once it reboots it then proceeds into this:

Windows Boot Manager:
Windows did not start correctly....blah blah blah...

File: \Windows\system32\drivers\si3112.sys

Stats: 0xc0000428

Info: The image hash cannot be found in the system catalogs. The image is
likely corrupt or the victim of tampering.

Enter = Continue

I click enter and it takes me to choose the O/S loading choices, ie: Safe
Mode, with Networking, so forth...

I have chosen both safe mode and start windows normally. Either way it just
goes back to the same black screen with the image hash error.

Any help would be GREATLY appreciated!

 

[Guest]

At what speed did you burn your DVD? Be sure to burn it a 2X, then reinstall.

 

[Guest]

I too have a very similar experience. I believe this to be because of the
new low level integrity checks on drivers. Your driver is not being verified
for such a signature during the installation and so it runs and gets copied
onto the drive. But once the system is now running Vista, these checks take
place, and your driver is not on the "official list" of drivers and so Vista
rejects it as unsigned and thus untrustworthy. I am hoping MS will either
add the driver to a "short list" when it copies it, or else replace it with
an approriate driver during install... otherwise there are going to be some
*really* unhappy first boot experiences when Vista comes on the market.

 

[Guest]

A follow-up to my previous post. I was trying to install Vista 64 on an AMD
64 X2 system. The driver SIS driver was copied into:
\windows\system32\drivers\si3114r5.sys

My curious question is why is a 64bit driver being copied into a directory
named system32? Shouldn't that be system64?

 

[Guest]

A follow-up to my previous post. I was trying to install Vista 64 on an AMD
64 X2 system. The driver SIS driver was copied into:
\windows\system32\drivers\si3114r5.sys

My curious question is why is a 64bit driver being copied into a directory
named system32? Shouldn't that be system64?

 

[Guest]

Just came across this page
http://www.microsoft.com/whdc/system/platform/64bit/kmsigning.mspx which has
a link to a file which describes how to temporarily disable driver signing in
Beta 2. I have yet to try this (the machine I need to test on is at home,
and I am not [yet]) but I will be trying this tonight. The trick is going to
be to find a way to get in. It looks like I might be able to use the F8
option to disable the signing once, long enough to get in and then make is
"psuedo temporary" as described in the doc.

 

[Guest]

Just boot using F8 key and use
'Disable Driver Signature Enforcement' tab
Should work

 

[Guest]

I'm having the exact same problem. The Windows logo screen never comes up,
so F8 is not an option. It seems that the ONLY option in this case is to use
a signed driver from the get-go, but that isn't possible either....MS really
needs to fix this issue or they're gonna be handing out a ton of refunds in
January. Driver signature verification needs to be an option duing
installation (and changeable after installation by administrators).