Saturday, January 17
Need Help With A Laptop Issue
Ok, last month I got hit by the Microsoft Internet Explorer Zero Day bug. It might just be a coincidence, it might be the root cause of many of my problems.
Last week my Alienware 51M laptop started having the Wireless NIC fail when it would come out of Hibernate or Sleep mode. The NIC connects, shows the network. If I go to the Command Prompt and run IPCONFIG, everything looks good. But if I try to ping the gateway, I get HARDWARE FAILURE. This happens if I try to ping anything but 127.0.0.1.
Very odd indeed.
The only way to get the NIC back is to reboot. When I reboot, I get the following error in the System Log:
Event Type: Error
Event Source: PSched
Event Category: None
Event ID: 14103
Date: 1/17/2009
Time: 9:22:37 AM
User: N/A
Computer: ALIEN2008
Description:
QoS [Adapter {F4518C6A-2EAD-44DE-9289-0B3C62A42D6F}]:
The netcard driver failed the query for OID_GEN_LINK_SPEED.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 04 00 02 00 56 00 ......V.
0008: 00 00 00 00 17 37 00 c0 .....7.À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 0d 00 01 c0 ...À
If I follow the link to Microsoft support for this error I get this:
Details
Product: Windows Operating System
ID: 14103
Source: PSched
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_PS_QUERY_OID_GEN_LINK_SPEED
Message: QoS [Adapter %2]:
The netcard driver failed the query for OID_GEN_LINK_SPEED.
Explanation
This event record indicates a serious problem.
User Action
Contact your technical support group or the Microsoft Product Support Services.
Yeah, go Microsoft, this is a serious problem, but we don't have a solutoin.
So I called Microsoft support and got a far as I could with free support. They told me that they were aware of the problem, and that I should just continue to reboot my machine as a work around.
WTF? It is a laptop, rebooting it over and over kind of defeats the purpose of having a laptop.
I've disabled all power management on the NIC, still no change. I've tried manually turning off the NIC before shutting down, no change. I looked in System Restore, but I don't have a restore point before 1/2009. This is all very infurating.
Anyone else out there have a similar problem, know a solution?
Last week my Alienware 51M laptop started having the Wireless NIC fail when it would come out of Hibernate or Sleep mode. The NIC connects, shows the network. If I go to the Command Prompt and run IPCONFIG, everything looks good. But if I try to ping the gateway, I get HARDWARE FAILURE. This happens if I try to ping anything but 127.0.0.1.
Very odd indeed.
The only way to get the NIC back is to reboot. When I reboot, I get the following error in the System Log:
Event Type: Error
Event Source: PSched
Event Category: None
Event ID: 14103
Date: 1/17/2009
Time: 9:22:37 AM
User: N/A
Computer: ALIEN2008
Description:
QoS [Adapter {F4518C6A-2EAD-44DE-9289-0B3C62A42D6F}]:
The netcard driver failed the query for OID_GEN_LINK_SPEED.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 04 00 02 00 56 00 ......V.
0008: 00 00 00 00 17 37 00 c0 .....7.À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 0d 00 01 c0 ...À
If I follow the link to Microsoft support for this error I get this:
Details
Product: Windows Operating System
ID: 14103
Source: PSched
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_PS_QUERY_OID_GEN_LINK_SPEED
Message: QoS [Adapter %2]:
The netcard driver failed the query for OID_GEN_LINK_SPEED.
Explanation
This event record indicates a serious problem.
User Action
Contact your technical support group or the Microsoft Product Support Services.
Yeah, go Microsoft, this is a serious problem, but we don't have a solutoin.
So I called Microsoft support and got a far as I could with free support. They told me that they were aware of the problem, and that I should just continue to reboot my machine as a work around.
WTF? It is a laptop, rebooting it over and over kind of defeats the purpose of having a laptop.
I've disabled all power management on the NIC, still no change. I've tried manually turning off the NIC before shutting down, no change. I looked in System Restore, but I don't have a restore point before 1/2009. This is all very infurating.
Anyone else out there have a similar problem, know a solution?
Labels: bad support, microsoft, wireless, zero day
Comments:
<< Home
I have the same problem since last wednesday. I can even reach my router config page (@192.168.1.1), but when I ping my cable modem (192.168.100.1) or any other host on the internet, I get a "Hardware Failure". Disabling and enabling the network card does not work, only restarting my laptop works.
This happens a few minutes after my laptop wakes up from hibernation. I get the same PSched error message in the event log as you. A few seconds after that event, a warning event from DHCP says
"Your computer has automatically configured the IP address for the Network Card with network address [MAC]. The IP address being used is 192.168.0.1."
with the MAC address of my unconnected, WIRED interface.
I suspect that update KB958687 is causing this problem. This update was installed just before the problem started. Maybe uninstalling this update will help resolve this, I will try it later this week
This happens a few minutes after my laptop wakes up from hibernation. I get the same PSched error message in the event log as you. A few seconds after that event, a warning event from DHCP says
"Your computer has automatically configured the IP address for the Network Card with network address [MAC]. The IP address being used is 192.168.0.1."
with the MAC address of my unconnected, WIRED interface.
I suspect that update KB958687 is causing this problem. This update was installed just before the problem started. Maybe uninstalling this update will help resolve this, I will try it later this week
Update KB958687 is NOT causing this problem. Uninstalling did not help.
Working solution:
I restored my system to the point of the last update cycle, and the problem was gone. I re-installed all of the windows updates, except the driver update 'Realtec RTL8169/8110 Family Gigabyte Ethernet NIC' for my LAN NIC I installed manually via microsoft update. The WLAN conncection now stays alive after hibernate. Very strange, a driver update for my LAN causes problems on my WLAN interface...
Working solution:
I restored my system to the point of the last update cycle, and the problem was gone. I re-installed all of the windows updates, except the driver update 'Realtec RTL8169/8110 Family Gigabyte Ethernet NIC' for my LAN NIC I installed manually via microsoft update. The WLAN conncection now stays alive after hibernate. Very strange, a driver update for my LAN causes problems on my WLAN interface...
Thanks for the heads up. I'll try my Wireless driver this weekend, it is Intel though. I've downloaded and reinstalled the latest, but somewhere I have the old version that came with the laptop. Will try that one.
I'm also curious if something that Norton, Malware Bytes, Ad Aware or Windows Defender removed when I got Zero Dayed is causing the problem.
I'm also curious if something that Norton, Malware Bytes, Ad Aware or Windows Defender removed when I got Zero Dayed is causing the problem.
Ok, I just performed a Driver Rollback on my wireless adapter, and things seem to be working now.
I'm going to bed.
I'm going to bed.
Got up this morning and the laptop would not resume properly from Hibernating overnight.
Back to square one, I might just reload XP from scratch.
Back to square one, I might just reload XP from scratch.
Hmmm... Ok, if I disable, then enable the wireless NIC, the connection works. Now I just need to figure out how to do this from the command line and write a script.
Ok, I disabled the wired NIC, and it just came ouf of four hours of Hibernate and worked. The wired is a RealTek, like yours, will work on it's driver next.
If you find it's a hardware problem, I do have a working Intel A/B/G MiniPCI card I'll send ya if you want to experiment (assuming that 51M takes MiniPCI and not MiniPCIe). You know how to get ahold of me :-)
Post a Comment
<< Home
Number of people who will never get their time back from reading this page:
