Vista Tutorial - NETIO.SYS Failure Upon Reboot/Restart

Whenever I cold/warm boot Vista Home Premium SP1, it fails due to netio.sys.
Always! Windbg reports:

Bugcheck: 1000007E, C0000005
Bucket ID: 0x7E_NETIO!nsipReadBootFirmwareTableData+77
File Type: 3.6 Driver
FileVersion: 6.0.6001.18000 *longhorn_rtm.080118-1840)

I did a search of netio.sys and the results showed I had 7 instances with
the following dates:

1/18/2008 c:\websymbols\netio.sys\479191033a000
1/19/2008 c:\windows\system32\drivers
1/19/2008 c:\windows\winsxs\x86_microsoft-windows-netio-infrastructure...
(1 instance)
4/1/2008 c:\windows\winsxs\x86_microsoft-windows-netio-infrastructure...
(2 instances)
4/10/2008 c:\websymbols\ (directory)
11/2/2006 c:\windows\winsxs\x86_microsoft-windows-netio-infrastructure...

1. I'm concerned that there may be conflicts between the different versions
of netio.sys
2. I know that c0000005 refers to an access violation but I have no idea
how to get rid of it, e.g. get my system to boot cleanly.
3. Dell tech support told me to run hotfix Windows6.0-kb937168-x86.exe;
however, I'm not having an ICS issue so don't want to install this if it
isn't going to fix my problem plus the date is older than my current (most)
netio.sys.

I'm running a Dell XPS H2C with:
QX-6850 OC to 3.66 (factory)
4GB Dominator memory OC 1066 (factory)
2 nVidia 8800 Ultra (SLI through nVidia software and BIOS)

Any help will be greatly appreciated!
Thanks,

Nick.

Hi,

a) File version conflicts were a problem in Win9x systems, they haven't been
in the NT line. I would serioulsy doubt this to be the source of the
problem.

b) Factory set or not, undo the overclocking. The access violation can
easily be due to a timing mismatch of a driver file.

c) Set a restore point, install the recommended patch. Sometimes installing
an older version of a file will resolve a conflict.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"nshaw" <nshaw@xxxxxx> wrote in message
news:9C5FB477-982C-4F9B-A34C-04A2D0164DB4@xxxxxx