Save this settings. Odpri menu. Windows Spooler fails to start with the faulting module name ldaNLM Go to Processes tab. Make sure the option Show processes from all users is enabled. Locate the process spoolsv.
If you can find it, the Windows Spooler is running. If you do not find the process in the list, manually run it. Locate the service Print Spooler. Run it. If you still cannot see the process spoolsv. See the error events and their descriptions. You might find the information such as: Faulting application name: spoolsv.
Solution The module ldaNLM Sort the files by time of creation in ascending order, so the older files are on top. Each print job submitted from the printing application is represented by two files. Faulting application name: spoolsv. Could you please help to provide the event log as below? We would like to know the Event ID and the error message general information.
It has done this 1 time s. The following corrective action will be taken in milliseconds: Restart the service. Windows will notify you if a solution is available. DoneStage1 State[0]. You might need to capture some dumps or traces to further investigate the issue, which I suggest to contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.
The first error you posted show a import error from a citizen's driver. It's not the root cause of the spooler crash you have IMO. You need to update a drivers, the question is, which's one? To find it disable the printer monitor on your printqueue to find the bad monitor, you will have to disable biderectional support on each print queue to test out. Disabling that remove the advanced monitor from the driver. Important; If you can get a crash dump it would help, as it will more pin-point to the bad print monitor directly.
We had similar issues with Vista early last year, when trying to install printers from a windows print server. One work around was to print direct to the network printer, other was to use at least a Windows print server. Don't know if this would help in your case, though, the thesting I did earlier this year on Windows 7 RC seemed to work fine against the printers on our Win2K3 print server.
I have drivers for an HP Laserjet I would suggest to remove any print drivers first from add remove programs and from the local print server on the win7 machine. Then install drivers for win7 from hp and connect to the printer directly.
There seems to be issue's with the drivers from a printserver This is what I do most of the time on small firms. Yes, delete the printer map. It wont let me delete the drivers once I restart the service, saying they re in use. I tried booting in safe mode, no luck ther either, i am starting to see the end of a tunnel, however, no light in sight :.
How is the AV on the machine - I vaguely remember having a similar problem last year and it turned out there was eith a virus or some malware. Ran combo fix and it seemed to clear up the problem. Actually this was one of the very first things I disabled, the "on Access Protection on Mcaffee". I also checked the logs to see if i spotted anything and there was nothing there that i could see as a cause of this issue. What I am doing now is running a regirtry repair tool I found dont know if its any good, but its free if you want to take a look :.
Open the registry and remove the print drivers and and printers from the system. On the Windows server you can install the Windows 7 drivers and when you connect the printer on the workstation from the print server it will get the Windows 7 Drivers and not try to use the Windows drivers. I havent noticed anyone mentioning this so here goes. We get this from time to time when a print job crashes. Have a look in there for anything of the date that these problems began most likely it will be in printers folder.
First of all let me thank you all for the help.
0コメント