TIME OUT!!!
This is a discussion about TIME OUT!!! in the Windows Hardware category; A 2k Pro computer I'm working on boots normally to the point of loading all the sys tray crap, then usually before it gets to the last item or 2nd to last it quites responding for about 5 minutes, then works flawlessly after that.
A 2k Pro computer I'm working on boots normally to the point of loading all the sys tray crap, then usually before it gets to the last item or 2nd to last it quites responding for about 5 minutes, then works flawlessly after that...
After its time out period it generates the following errors in the Event Viewer:
perfctrs
Unable to read IO control information from NBT device.
Winmgmt
WMI ADAP was unable to load the winspool.drv performance library due to an unknown problem within the library: 0x0
-- Now ... just whaaaaaaaaat the faaaaaalk are WMI ADAP's, NBT's and Perctrs ... and why are they hastling me ???
heh .. help!
I know the timouts usually mean hardware and driver problems (NT4 days)...
After its time out period it generates the following errors in the Event Viewer:
perfctrs
Unable to read IO control information from NBT device.
Winmgmt
WMI ADAP was unable to load the winspool.drv performance library due to an unknown problem within the library: 0x0
-- Now ... just whaaaaaaaaat the faaaaaalk are WMI ADAP's, NBT's and Perctrs ... and why are they hastling me ???
heh .. help!
I know the timouts usually mean hardware and driver problems (NT4 days)...
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Mar 29
Mar 29
0
1 minute
Responses to this topic
Not to be a patronizing bastard but, check the microsoft knowledge base..
I had the same problem..
look for keywords winmgmt or WMI ADAP
you have to reinit the winmgmt database or something to that effect...
I had the same problem..
look for keywords winmgmt or WMI ADAP
you have to reinit the winmgmt database or something to that effect...
OP
Thanks...
I returned to the Knowledge Base and still got no hits on those key words, but since you did I, I opened the search to all products (instead of just Win2k) and WHAT DO YA KNOW - I got 2 hits under ADAP, which solved the problem just like ya said.
For anyone else: It's a known problem that sometimes happens from upgrading RC2 to Retail (with a fix - in the KB).
I returned to the Knowledge Base and still got no hits on those key words, but since you did I, I opened the search to all products (instead of just Win2k) and WHAT DO YA KNOW - I got 2 hits under ADAP, which solved the problem just like ya said.
For anyone else: It's a known problem that sometimes happens from upgrading RC2 to Retail (with a fix - in the KB).
