11-26-2008 08:03 AM
Lenovo is making our company look very unprofessional. I am embarrassed to admit that something "approved" by IBM would be sold with so many different bugs. It is not all Lenovo's fault, as we are all aware of the horrible Vista incompatibilities.
As of 11/24/2008 - Intel offered a driver update for their wireless card that would cause the DHCP NACK renewal operation
to fail and leave the system in a stale state without network connectivity. At first the BSOD was caused by NETw5v32.sys which has been resolved by the latest Intel driver for the Wireless unit, 5100 AGN adapter. Now NETIO.SYS and ntkrnlpa.exe
have been causing the BSOD especially after going into Hibernation, and then going back into the OS.
I am exhausted, and have exhausted my resources to resolve this issue that no one seems to want to discuss.
Is there any professionals out there who have also experienced this issue and found a solution?
Thanks in advanced - and for allowing me to vent...
Solved! Go to Solution.
11-26-2008 08:54 AM
Please tell us:
GFX Driver versions, are also important.
Follow @LenovoForums on Twitter! Try the forum search, before first posting: Forum Search Option
Please insert your type, model (not S/N) number and used OS in your posts.
I´m a volunteer here using Yoga 11s, Yoga 13, T510, X220t, T61.
TIP: If your computer runs satisfactorily now, it may not be necessary to update the system.
12-07-2008 01:26 PM
12-08-2008 07:39 AM
I was getting the same DHCP issue with the Intel 5100 Wireless card. After updating the device drivers, the events went away.
Today we tried to reinstall to the default software base, and the system was having multiple errors after this was performed.
Try the Intel drivers for your DHCP issue, and if you like, I would also un register the Hibernation feature.
Run the Command Prompt as Administrator > this must be done even if you have local admin rights <
and type "powercfg.exe /hibernate off". Even after doing this, the Sleep function did some very strange stuff.
One of the strangest things was when the system was coming out of Sleep mode, the Hard Drive indicator was on almost 100% of the time. To trouble shoot, we disabled the "Speed Step" processor throttling. The sleep function worked much better after disabling that thing. Things seemed to be going well, and then in telling the system to Shut Down (BAM) BSOD
Hope there are some others out there experiencing this issue - share the knowledge ...
12-08-2008 07:46 AM
here's my update so far:
* got one DHCP failure after reboot (not after suspend or hibernate)
* got my first BSOD on this laptop ever, after updating to the Intel drivers
12-31-2008 11:01 AM
I am shocked that Lenovo hasn't addressed this problem yet! I have spent time on the phone with them and they clearly do not have a handle on it. My network connection will drop after several minutes of working fine after waking up from the sleep state.
I was advised to disable "computer can turn of radio" in the device manager (did nothing). Uninstalling Access Connection eliminated the most difficult to recover from situations but the problem of smoothly getting back on the air after sleep is still there. Most of the time turning off radio with Fn+F5 and then turning it back on will fix the problem untill the next sleep state. This whole thing makes it very hard to use a laptop when you have to fiddle with it when you try to wake it up!
12-31-2008 11:15 AM
I actually have an update for this. We sent the Lenovo back to the Depot. They diagnosed the Wireless card as bad.
That would explain the DHCP errors, and the Stand By / Sleep issues.
After it was returned (obviously scrubbed) I beat the hell out of it. Surprisingly, after all the headache, and driver updates,
the device was actually at fault. Here are the specs that we have that currently work, otherwise your card could be
at fault also.
Intel Wireless - 10418086 Intel 3945ABG Wireless LAN controller - aka 5100
Intel Driver version 184.108.40.206
Good luck, and remember to test all of your products thoroughly before giving them to your end client.
It would be better for you to not give it to them, find the problem, get it solved and keep the headache's to a minimum!
01-18-2009 09:40 AM - edited 01-18-2009 09:42 AM