IBM 621410U Hardware Maintenance Manual - Page 29

Error code, Description, Explanation, Action, Start, Control Panel, Networks, Adapters, Properties

Page 29 highlights

Table 4. NDIS (Windows 2000 or Windows XP) Event Viewer messages for the Ethernet controller (continued) Error code (hex) Description 0x0E Explanation: Could not allocate enough memory for receive queue. 0x0F Action: v If you have Windows 2000, do the following: 1. From the Windows 2000 desktop, click Start"Control Panel"Networks"Adapters. 2. Select your IBM Ethernet adapter from the list. 3. Click Properties"Advanced. 4. Lower the resource values that apply to the transmit queue. v If you have Windows XP Professional, do the following: 1. Click Start"Control Panel"Network Connections"Local Area Connection. 2. Select your IBM Ethernet adapter from the list. 3. Click Properties"Advanced. 4. Lower the resource values that apply to the transmit queue. Explanation: Could not allocate enough memory for other structures. 0x10 Action: v If you have Windows 2000, do the following: 1. From the Windows 2000 desktop, click Start"Control Panel"Networks"Adapters. 2. Select your IBM Ethernet adapter from the list. 3. Click Properties"Advanced. 4. Lower the resource values that apply to the transmit queue. v If you have Windows XP Professional, do the following: 1. Click Start"Control Panel"Network Connections"Local Area Connection. 2. Select your IBM Ethernet adapter from the list. 3. Click Properties"Advanced. 4. Lower the resource values that apply to the transmit queue. Explanation: Did not find any Ethernet controllers. Action: Contact the network administrator. The driver may need to be reinstalled. If the problem persists, run diagnostics to determine if the hardware has failed. 0x11 Explanation: Multiple Ethernet controllers found, but none matched the required ID. 0x13 Action: Contact the network administrator. The driver may need to be reinstalled. If the problem persists, run diagnostics to determine if the hardware has failed. Explanation: Did not find any Ethernet controllers that matched the required subven/subdev. 0x16 Action: Contact the network administrator. The driver may need to be reinstalled. If the problem persists, run diagnostics to determine if the hardware has failed. Explanation: Single adapter found, but multiple instances tried to load. 0x17 Action: Contact the network administrator. The driver may need to be reinstalled. If the problem persists, run diagnostics to determine if the hardware has failed. Explanation: Slot parameter not specified in the registry. Action: Contact the network administrator. The driver may need to be reinstalled. If the problem persists, run diagnostics to determine if the hardware has failed. Diagnostics 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176

Table 4. NDIS (Windows 2000 or Windows XP) Event Viewer messages for the Ethernet controller (continued)
Error code
(hex)
Description
0x0E
Explanation:
Could not allocate enough memory for receive queue.
Action:
v
If you have Windows 2000, do the following:
1.
From the Windows 2000 desktop, click
Start
Control Panel
Networks
Adapters
.
2.
Select your IBM Ethernet adapter from the list.
3.
Click
Properties
Advanced
.
4.
Lower the resource values that apply to the transmit queue.
v
If you have Windows XP Professional, do the following:
1.
Click
Start
Control Panel
Network Connections
Local Area Connection
.
2.
Select your IBM Ethernet adapter from the list.
3.
Click
Properties
Advanced
.
4.
Lower the resource values that apply to the transmit queue.
0x0F
Explanation:
Could not allocate enough memory for other structures.
Action:
v
If you have Windows 2000, do the following:
1.
From the Windows 2000 desktop, click
Start
Control Panel
Networks
Adapters
.
2.
Select your IBM Ethernet adapter from the list.
3.
Click
Properties
Advanced
.
4.
Lower the resource values that apply to the transmit queue.
v
If you have Windows XP Professional, do the following:
1.
Click
Start
Control Panel
Network Connections
Local Area Connection
.
2.
Select your IBM Ethernet adapter from the list.
3.
Click
Properties
Advanced
.
4.
Lower the resource values that apply to the transmit queue.
0x10
Explanation:
Did not find any Ethernet controllers.
Action:
Contact the network administrator. The driver may need to be reinstalled. If the problem
persists, run diagnostics to determine if the hardware has failed.
0x11
Explanation:
Multiple Ethernet controllers found, but none matched the required ID.
Action:
Contact the network administrator. The driver may need to be reinstalled. If the problem
persists, run diagnostics to determine if the hardware has failed.
0x13
Explanation:
Did not find any Ethernet controllers that matched the required subven/subdev.
Action:
Contact the network administrator. The driver may need to be reinstalled. If the problem
persists, run diagnostics to determine if the hardware has failed.
0x16
Explanation:
Single adapter found, but multiple instances tried to load.
Action:
Contact the network administrator. The driver may need to be reinstalled. If the problem
persists, run diagnostics to determine if the hardware has failed.
0x17
Explanation:
Slot parameter not specified in the registry.
Action:
Contact the network administrator. The driver may need to be reinstalled. If the problem
persists, run diagnostics to determine if the hardware has failed.
Diagnostics
21