| Computing.Net: Over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to sign up now, it's free! |
PNP Device ID Error Code 22
|
Original Message
|
Name: Betty H
Date: November 15, 2000 at 08:35:43 Pacific
Subject: PNP Device ID Error Code 22
|
Comment: I have been following another thread on this board where someone else has this error code in winme. I actually have the error 3 times. ACPI IRQ Holder for PCI IRQ Steering ACPI\*PNP0C0F\00000001 22 ACPI IRQ Holder for PCI IRQ Steering ACPI\*PNP0C0F\00000002 22 ACPI IRQ Holder for PCI IRQ Steering ACPI\*PNP0C0F\00000003 22 This is not a winme bug. This same message has followed me from my win98 oem to win98se update and now to winme. I checked out the ms knowlege base articles and still can't figure out what plug and play devices are disabled. I don't think I have a problem but find it very annoying that I can't figure out what the error code refers to. I have an Aptiva 350 and am running winme. I have no conflicts in devise manager. How can I track down those devises? Does the address give me a clue and if so how do I find the devices. TIA Betty (remove no spam to reply)
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: fred6008
Date: November 15, 2000 at 19:01:07 Pacific
|
Reply: (edit) I am getting in too deep. What is a holder for PCI IRQ steering? I answered because I think I know why you get the message over and over. I have holders for PCI IRQ steering on 3 or 4 IRQs some of which are in use by something else also. Presumably, you have three such IRQs held. When all else fails guess. I would imagine you have three IRQs held by windows for intermittent use by PCI slots and that the pnp ID for the boards in those slots is wrong. Maybe jumpers, but I am guessing outrageously because there are no better answers posted yet.
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: Vidar
Date: November 15, 2000 at 23:00:50 Pacific
|
Reply: (edit)First of all I have no clue. Anyway, it's strange that the error messages have followed you through the upgrades, but ME is strange.... You say you have no conflicts in device manager, but have you checked with device manager running in safe mode? (Ctrl during startup) I've had some surprises doing so - some unknown devices that you may delete may show up.
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: trevor scrutton
Date: November 16, 2000 at 01:20:04 Pacific
|
Reply: (edit)this is a me bug if you look on the microsoft technet site those entries appear for the irq stearing but they are not relevent. i have the same problem. this is not an error as reported by problem devices
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: Betty H
Date: November 16, 2000 at 18:48:35 Pacific
|
Reply: (edit)Thanks you all for responding. I will check in safe mode to see if anything shows up. I don't think it is a real problem since it's been showing up from the time I got this puter. Just one of those things that bug you because you can't figure out what the heck is going on. If something shows up I will post back. I appreciate the input. Betty
Report Offensive Follow Up For Removal
|
|
Response Number 5
|
Name: wanderer
Date: November 20, 2000 at 13:45:42 Pacific
|
Reply: (edit)Short for Advanced Configuration and Power Interface http://webopedia.internet.com/TERM/A/ACPI.html pci irq steering is the irq that is shared out to pci pnp devices.. it sounds like one of your pci devices is having trouble w/ sleep mode.. if it has been following you thru the upgrades it is possible that you may have a cmos setting that is incorrect, or you may need to clear cmos to clear out the pnp nvram storage area.. i would try that first (clear cmos).. if fail, check your motherboard manufacturer for any relevant bios upgrades..
Report Offensive Follow Up For Removal
|
|
Response Number 6
|
Name: Lew
Date: December 18, 2000 at 23:35:39 Pacific
|
Reply: (edit)I too have the same error messages on at least two machines. One seems to work ok but the other is having problems recognizing the modem..may not be related..but I wonder. Does anyone know a source for error codes?
Report Offensive Follow Up For Removal
|
|
Response Number 7
|
Name: Jelico
Date: December 26, 2000 at 22:27:34 Pacific
|
Reply: (edit)http://www.microsoft.com/hwdev/download/respec/devids.txt - guess it doesn't explain what error code 22 is but it doesn explain what each pnp device id is. pnp0c0f is pci interrupt link device.
Report Offensive Follow Up For Removal
|
|
Response Number 8
|
Name: jelico
Date: December 27, 2000 at 21:17:13 Pacific
|
Reply: (edit)http://support.microsoft.com/support/kb/articles/Q125/1/74.asp?LN=EN-US&SD=gn&FR=0&qry=error%2022&rnk=1&src=DHCS_MSPSS_gn_SRCH&SPR=WINME - explains error codes .. 22 is disabled device
Report Offensive Follow Up For Removal
|
|
Response Number 9
|
Name: hamada samir
Date: January 16, 2001 at 19:43:14 Pacific
|
Reply: (edit)i found this error while i tried to install usrobotic fax modem then i changed the slot to solve this problem second i found this while i tried to install texas fax modem for notebook compaq and i restarted computer while pressing ctrl (save mode)and i got nothing except many hours wasted
Report Offensive Follow Up For Removal
|
|
Response Number 10
|
Name: Doug
Date: January 23, 2001 at 21:07:33 Pacific
|
Reply: (edit)Disabled device would explain it. I have drivers installed for an external modem which I no longer have attached. This wouldn't explain why new systems would have this error though. I also opened bootlog.txt and searched for "fail" and found that INITCOMPLETE for SIS620V failed. Anyone else see that?
Report Offensive Follow Up For Removal
|
|
Response Number 11
|
Name: Doug
Date: January 23, 2001 at 21:15:38 Pacific
|
Reply: (edit)I just checked jelico's link. It says that a PCI steering device is not in use. That shows up in SystemInfo even if it doesn't show up in device manager. MS says it's not a bug, it's a feature.
Report Offensive Follow Up For Removal
|
|
Response Number 12
|
Name: Steve Wolfe
Date: January 26, 2001 at 21:53:34 Pacific
|
Reply: (edit)I have seen info commenting that this is an error that is caused by devices that do not support hibernate mode. MOST all Creative labs sound cards have problems with the hibernation mode, as well as other hardware. Check your windows folder for a file created during the boot process that lists all devices with hibernate problems. The file is a text file called NOHIBER
Report Offensive Follow Up For Removal
|

Post Locked
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
Go to Windows Me Forum Home