Yellow Bangs (!) on Wireless NIC and Ethernet NIC

[Throttle]

We're having a random/intermittent issue where one or both NICs are offline when a T60 boots. The offline NICs are accompanied by the UAA Bus Driver (High Definition Audio) and/or 945GM integrated Display Adapter.

Of the 80 or so T60's we have rolled out, a small number of the population have this boot issue on a daily basis. It ranges from 2 to around 4 per day. Sometimes we can have the user power down and boot, and that fixes the issue for an unspecified amount of time. Other times it takes an admin to log in and disable/enable devices to get them going again. One odd thing is that if you disable/enable the UAA Bus Driver (when it is the device that goes offline with the NICs), then shutdown and boot, the NICs come up and work. Didn't do anything to the NICs, just the UAA Bus Driver. They do share IRQs.

We've tried everything from 1.02 BIOS thru 1.06, variations of the drivers, etc. I'm currently running the latest of everything from IBM/Lenovo, the latest Matrix Driver, Chipset, and video drivers from Intel, and the latest High Definition audio driver from Microsoft.

I would really appreciate some assistance if anyone has any ideas.

Thanks,

ajh

[87325is]

try to disable access connections. since i stated using the xp wifi program i have not had a problem. for wifi that is. i dont have a wired connecton most of the time but i have never had issues with that

[Throttle]

I tried that early on, but have since upgraded to a different version of Access Connections and the NIC drivers. I'll remove Access Connections and see if that helps. Maybe my testing wasn't clean enough to come to a good conclusion.

Thanks for the idea.

More info on the issue:

We have a small group of machines that we initially rolled out (15-20) where we used Sidgen during the imaging process to create the unique SID. Those machines have not given us a single problem.

Between that time and the rollout the following week, I believe MSFT released their monthly patches and one of them broke our ability to use Sidgen effectively (the machines all came up with duplicate computer name on the network).

We moved over to MSFT Sysprep to get around the issue, and I knew that there would be issues with it because of the way it recreates the NICs during the configuration process after imaging.

Any thoughts will be appreciated.

Thanks,

ajh