I get this error in my Event Viewer. I can't find anything on Microsoft Knowledge Base nor any web searches. Does anyone know what file this error message is referring to? Any help is appreciated. Thanks, Sun W.

This error does not come from Win2K. I guess you tried to install Live!Ware from Creative Labs (and you probably didn't succeed). Try to uninstall your Sound card (remove all the drivers) and re-install it using the Win2K drivers. Until now I didn't succeed to install Live!Ware but the problem seems to be erratic. Hope this helps.

I have the same problem and I haven't installed Live!Ware at all. Any hints as to what this service is and how the problem can be resolved? The error occurs upon every start up....

Problem still excist after using cleensweep method from Sondblaster. Is there anybody that knows a solution.

I found somthing i think it will help,, under device manger take "display hiden devices" then you will find the "PfModNT" under "drivers without Plug and Play" try to disable it I hope that will help

I've been tormented by this problem for weeks! (And other soundblaster related problems, but that's another story.) I had to actually go into the registry and delete the PfModNT entry (run regedt32, then go to local machine, current control set, services, then look for the PfModNT entry and delete it.) That took care of the problem and I don't get the error anymore. Now if I could just get the card to work....

I will post this message to this thread as well just for good luck: I can shed a bit of light on this issue but not much more. If you do a bit of looking around in the registry you will find that PFModNT.sys one of a set of 4 files that form a driver by Creative which is installed by SoundBlaster driver packages. Look at the following several keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PfModNT and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_PFMODNT\0000 and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{8ECC055D-047F-11D1-A537-0000F8753ED1} and HKEY_CLASSES_ROOT\CLSID\{6410C3A0-A732-11D3-9CFD-00A0C95949D5} The registry seems to refer to these files in general as either "Creative Platform Detector" or "SysSetup.Dll,LegacyDriverPropPageProvider". In any event, you should also notice that there are several files in your "C:\Program Files\Creative\Sharedll\" directory: PfMod.dll Pfmod16.dll PfModIntl.dll also PfModNT.sys may be there as well as in your "C:\WINNT\System32\" directory. (or equivilant depending on which OS you are running. The important part of all this is that if you have a copy of "Dependancy Viewer" (a development tool) and you try to open _any_ of these files dependancy viewer will notify you that these dll's (and the .sys driver) are all "Not a valid Win32 Module". Interesting to note is that if you take "valid" copies of these files from another machine with a working copy of Live!Ware 3 and overwrite the ones on your machine, you will be able to reboot once withour the "PFModNT.sys" error. More interesting to note is that if you reboot again, these old "bad" files will be replaced, and you will again begin getting these errors. While your system is in this state, the Live!Ware 3 install (and older versions as well) will fail to run (lock up) during init. I have run the liveware install in a debugger and it seems to fail imediatly after trying to load "pfmodnt.dll" (suprise, suprise). I am almost certain that the problem is comming from the corrupt driver dlls. but since they keep getting replaced after reboot I am at a complete loss as to how to get rid of them. I have tried _everything_ including the following: 1) deleting the files from "safe mode with command prompt" mode. 2) deleting the files from the "dllcache" system folder 3) searching every file on my system for the text "pfmodnt" to try and find a "hidden" copy of the files that some program might be using to restore them. 4) scouring the registry (the only place they really show up is under the driver key and the "shareddlls" key. 5) stopping the install program for Live!Ware 3 with a debugger before it loads the dlls, and grabbing a fresh copy the the dlls from the install's temporary directoy and using those to overwrite the old ones. no luck. I'm hoping someone technically minded (or even better someone at creative) will read this and email me with another clue. Sorry folks but that's the best I can do.