Windows Vista SMB.SYS Blue Screen

I'm going to try out the Driver Verifier next.

As for the chipset and processor, the processor is a Xeon 5150.

The chipset identification utility fails to identify the chipset. I tried on several machines.

 

How about SIW or Everest?

 

I was reading this article:
"STOP 0x27 in mrxsmb.sys" error when trying to copy files to a NAS device

It got me wondering - could this be an error with the server rather than the workstations?
I'd check the server logs for errors around the time that you get the BSOD's on the workstations.

 

Another update:

I ran Intel's Chipset update utility and while it did blue screen on trying to update something in the process, I did successfully update my smbus driver. So we'll see what happens from here.

 

Update again:

So the driver update utility only worked on the machines that I did not run Dell's chipset update program on. It updated my smbus driver to version 8.6.0.1002, but would not touch the machines I used Dell's on. Any thoughts on this?

In the mean time, I (think) I found the inf file for the smbus controller for version 8.6.0.1002 and I loaded it into one of the machines that I ran dell's on and it seems to update. So my question is, did it actually do anything since it was just an inf file? I'm a little concerned now.

 

More Information

http://www.intel.com/support/chipsets/inf/sb/CS-009272.htm


"The Intel® Chipset Software Installation Utility does have a setup program; however, the setup program will prevent you from upgrading the utility if it has been installed already. "

So apparently if one version of an update utility is on a system, another version cannot be used, so the "have disk" option must be used.

What this seems to mean: If you download an outdated chipset utility from Dell, and then intel releases a newer version, you're pretty much up the creek unless you know how to manally install drivers, which isn't difficult, but for most people, it would be. Good game.

I'll let you all know if I get blue screens with this new driver.

 

I'm not aware of the functions of this particular .inf file - but you can check to see if it does anything by opening it up (to edit) and seeing what it contains.

I'm not a big fan of the Intel Installation utility - it seems kludged together from bits and pieces. I fought with one on an HP laptop today until I got "p***ed" and did it manually also.