Articles

Solved Win XP kernell32.dll getcurrentprocessornumber error

February 5, 2012 at 11:40:57
Specs: Windows XP

the procedure entry point getcurrentprocessornumber could not be located in the dynamic link library kernell32.dll.

See More: Win XP kernell32.dll getcurrentprocessornumber error

Report •


#1
February 5, 2012 at 12:35:21
✔ Best Answer

The function "Getcurrentprocessornumber" requires Vista or higher, and the error you got seems to happen when people try to run games that require DirectX 10 on an XP machine.

What did you do when it happened?

Nigel

Wind slow


Report •
Related Solutions


Ask Question