canon lbp 1120 lasertulostimen asennus ei onnistu alkuperäisajureilla cdltä. (asennus on tehty prikulleen ohjeiden mukaan) .
voiko joku Xpn päitys "tappaa" ne kun asennuksen jälkeen zone alarm kysyy että käynnistetäänkö spooler sub system joka kerran xpn yhteydessä. kun tähön vastaa ei asennus epäonnistuu. xpn virheraportoinnin linkki johdattaa microsoftin sivulle
Follow these steps to solve the problem with The Windows Print Spooler Service
This problem was caused by The Windows Print Spooler Service.
This problem is often caused by printer drivers and other printer software, not the program using the printer.
What is a driver?
A driver is software that allows your computer to communicate with hardware or devices. Without drivers, the hardware you connect to your computer (for example, a video card or a webcam) will not work properly.
Troubleshooting
We've found that this problem is usually resolved by updating your computer with the latest printer drivers. To update your printer drivers, go online to your printer manufacturer's website and download the most recent drivers.
For your convenience, here are links to driver download websites for some printer manufacturers. If your manufacturer is not listed, check the documentation that came with your printer or visit their website.
* Brother International Corporation
* Canon U.S.A., Inc.
* Dell
* Hewlett-Packard Development Company, L.P.
* Lexmark International, Inc.
* Xerox Corporation
Additional technical information
This problem is the result of an issue known as heap corruption, which is often caused by a problem with a Dynamic Link Library (DLL) file. To try to solve this issue, you can update all printer drivers on the computer. However, if you are an advanced user interested in helping Microsoft determine the root cause for this issue, you can choose to enable a diagnostic tool in Windows called page heap and then, when this error occurs again, submit the diagnostic results to Microsoft. To turn on the page heap tool, follow these steps:
1.
Turn on the page heap tool
1. Go online to download and install Debugging Tools for Windows from the Microsoft Windows website.
2. Click Start, point to All Programs, point to Accessories, right-click Command Prompt, click Run as, and then choose an account with Administrator privileges (this account might be simply called Administrator).
3. In the administrator command prompt, type
cd /d "c:\Program Files\Debugging Tools for Windows"
4. To turn on the page heap tool, type
"Gflags.exe -p /enable spoolsv.exe /full /decommit"
5. Restart the spooler service by typing the following two commands into the command prompt:
net stop spooler
net start spooler
Note
Enabling the page heap tool might increase memory usage in the spoolsv.exe process. Typically, you won't experience a performance problem as a result of running the tool, even on the busiest print servers. However, if running this tool proves to be a performance problem, disable page heap by following the preceding steps, and then type
"Gflags.exe -p /disable spoolsv.exe"
Restart the spooler service or reboot your system and update your printer drivers as described earlier. For additional information on the page heap tool, go online to read the How to use Pageheap.exe Microsoft Support article.
2.
Recreate the error and submit to Microsoft
Once the page heap tool has been enabled and the spooler service restarted, attempt to recreate the error condition and submit the error report to Microsoft when prompted to do so. This will allow us to continue to investigate this error.
Note
If you are a system administrator and want to debug this problem, follow the steps in "Advanced debugging steps for system administrators" below before you send the error report to Microsoft.
Advanced debugging steps for system administrators
It is possible to perform basic debugging with the error reporting data before you send it to Microsoft.
1. Find the .mdmp file to debug this problem.
For Windows XP, you can access the .mdmp file from the Error Reporting dialog. In the dialog, you will see the sentence:
To see what data this error report contains,
With the dialog still open note the location of the .mdmp or .dmp file, and then leave the dialog open.
Note
If you do not see a path to the .mdmp or .dmp file but you do see a .txt file, note the path to the .txt file and do the following:
1. Press CTRL ALT DELETE, and then click Start Task Manager.
2. Click the Processes tab, click dwwin.exe, and then click End Process.
3. Open the location of the .txt file, which should also contain the .mdmp or .dmp file
2. Debug Steps
1. Click Start, click Programs, and then click Debugging Tools for Windows, WinDbg
2. In the Save Workspace dialog, click No.
3. Click File, click Open Crash Dump, and then type the path to the .mdmp file that you found in step 1 (make sure the error reporting dialog is still open because the file is deleted after the dialog is closed).
4. At the Windbg debugger prompt (at the bottom of the window) type these commands:
.symfix
.reload
!analyze -v
5. Scroll up to view the call stack. Note the DLL file(s) below ntdll and kernel32 in the call stack.
Here is an example of what the call stack might look like. Note that the first DLL below ntdll and kernel32 in this example uses bold font to highlight it. In an actual call stack, it will not appear with bold:
0012fc90 6d084ced 00000000 00000000 00000000 ntdll!DbgBreakPoint
0012fcb4 6d08a079 0000000f 6d074664 00151000 verifier!VerifierStopMessage 0x1fd
0012fd10 6d08a2c5 00151000 00000001 0019cff8 verifier!AVrfpDphReportCorruptedBlock 0x1b9
0012fd74 6d08871b 00151000 0019cff8 00000001 verifier!AVrfpDphCheckPageHeapBlock 0x125
0012fdc8 77b71c8f 00150000 01000002 0019cff8 verifier!AVrfDebugPageHeapFree 0x14b
0012fe10 77b3d9fa 00150000 01000002 0019cff8 ntdll!RtlDebugFreeHeap 0x2f
0012ff04 77b21c21 0019cff8 0019cff8 0019cff8 ntdll!RtlpFreeHeap 0x5f 0012ff20 765a7a7e 00150000 00000000 0019cff8 ntdll!RtlFreeHeap 0x14e
0012ff34 0040103e 00150000 00000000 0019cff8 kernel32!HeapFree 0x14
0012ff50 0040124c 00000001 0141efb8 01420f60 PrinterFile1!Function1 0x3e
0012ffa0 765a3833 7ffdb000 0012ffec 77afa9bd PrinterFile2!Function2 0x15f
6. After you have noted the first non-Microsoft DLLs in the call stack below .ntdll (in the example, PrinterFile1.dll and PrinterFile2.dll are below ntdll), in the Error Reporting dialog, click Send Error Report.
7. At this point, if the DLL provider is not clear from the file name, search for the DLL name using the file search in Windows. Once found, right-click the DLL, choose Properties, and then determine the provider in the Details tab.
The information on the Details tab should determine who to contact for an updated DLL to fix the issue or help you to further investigate the problem. Refer to the links above for the manufacturer’s support and driver downloads to identify any updated versions.
If the DLLs below ntdll are all from Microsoft Corporation, we ask that you first confirm that Pageheap is indeed enabled (using Gflags.exe -p) and, if so, go online to search the Microsoft support website for any updated versions or known issues for those DLLs.
8. After you have identified the DLLs to update, go to Step 3 to disable the page heap tool.
3.
Disable the page heap tool
josta ilmenee että ajurit pitäs päivittää. Heh no mistä kun ei ole uudempia?
mikähän tässä nyt on vikana?
eikai ajurit voi mennä toimintakelvottomiks noin. käytännössä printterini on nyt toimintokelvoton.
voiko joku Xpn päitys "tappaa" ne kun asennuksen jälkeen zone alarm kysyy että käynnistetäänkö spooler sub system joka kerran xpn yhteydessä. kun tähön vastaa ei asennus epäonnistuu. xpn virheraportoinnin linkki johdattaa microsoftin sivulle
Follow these steps to solve the problem with The Windows Print Spooler Service
This problem was caused by The Windows Print Spooler Service.
This problem is often caused by printer drivers and other printer software, not the program using the printer.
What is a driver?
A driver is software that allows your computer to communicate with hardware or devices. Without drivers, the hardware you connect to your computer (for example, a video card or a webcam) will not work properly.
Troubleshooting
We've found that this problem is usually resolved by updating your computer with the latest printer drivers. To update your printer drivers, go online to your printer manufacturer's website and download the most recent drivers.
For your convenience, here are links to driver download websites for some printer manufacturers. If your manufacturer is not listed, check the documentation that came with your printer or visit their website.
* Brother International Corporation
* Canon U.S.A., Inc.
* Dell
* Hewlett-Packard Development Company, L.P.
* Lexmark International, Inc.
* Xerox Corporation
Additional technical information
This problem is the result of an issue known as heap corruption, which is often caused by a problem with a Dynamic Link Library (DLL) file. To try to solve this issue, you can update all printer drivers on the computer. However, if you are an advanced user interested in helping Microsoft determine the root cause for this issue, you can choose to enable a diagnostic tool in Windows called page heap and then, when this error occurs again, submit the diagnostic results to Microsoft. To turn on the page heap tool, follow these steps:
1.
Turn on the page heap tool
1. Go online to download and install Debugging Tools for Windows from the Microsoft Windows website.
2. Click Start, point to All Programs, point to Accessories, right-click Command Prompt, click Run as, and then choose an account with Administrator privileges (this account might be simply called Administrator).
3. In the administrator command prompt, type
cd /d "c:\Program Files\Debugging Tools for Windows"
4. To turn on the page heap tool, type
"Gflags.exe -p /enable spoolsv.exe /full /decommit"
5. Restart the spooler service by typing the following two commands into the command prompt:
net stop spooler
net start spooler
Note
Enabling the page heap tool might increase memory usage in the spoolsv.exe process. Typically, you won't experience a performance problem as a result of running the tool, even on the busiest print servers. However, if running this tool proves to be a performance problem, disable page heap by following the preceding steps, and then type
"Gflags.exe -p /disable spoolsv.exe"
Restart the spooler service or reboot your system and update your printer drivers as described earlier. For additional information on the page heap tool, go online to read the How to use Pageheap.exe Microsoft Support article.
2.
Recreate the error and submit to Microsoft
Once the page heap tool has been enabled and the spooler service restarted, attempt to recreate the error condition and submit the error report to Microsoft when prompted to do so. This will allow us to continue to investigate this error.
Note
If you are a system administrator and want to debug this problem, follow the steps in "Advanced debugging steps for system administrators" below before you send the error report to Microsoft.
Advanced debugging steps for system administrators
It is possible to perform basic debugging with the error reporting data before you send it to Microsoft.
1. Find the .mdmp file to debug this problem.
For Windows XP, you can access the .mdmp file from the Error Reporting dialog. In the dialog, you will see the sentence:
To see what data this error report contains,
With the dialog still open note the location of the .mdmp or .dmp file, and then leave the dialog open.
Note
If you do not see a path to the .mdmp or .dmp file but you do see a .txt file, note the path to the .txt file and do the following:
1. Press CTRL ALT DELETE, and then click Start Task Manager.
2. Click the Processes tab, click dwwin.exe, and then click End Process.
3. Open the location of the .txt file, which should also contain the .mdmp or .dmp file
2. Debug Steps
1. Click Start, click Programs, and then click Debugging Tools for Windows, WinDbg
2. In the Save Workspace dialog, click No.
3. Click File, click Open Crash Dump, and then type the path to the .mdmp file that you found in step 1 (make sure the error reporting dialog is still open because the file is deleted after the dialog is closed).
4. At the Windbg debugger prompt (at the bottom of the window) type these commands:
.symfix
.reload
!analyze -v
5. Scroll up to view the call stack. Note the DLL file(s) below ntdll and kernel32 in the call stack.
Here is an example of what the call stack might look like. Note that the first DLL below ntdll and kernel32 in this example uses bold font to highlight it. In an actual call stack, it will not appear with bold:
0012fc90 6d084ced 00000000 00000000 00000000 ntdll!DbgBreakPoint
0012fcb4 6d08a079 0000000f 6d074664 00151000 verifier!VerifierStopMessage 0x1fd
0012fd10 6d08a2c5 00151000 00000001 0019cff8 verifier!AVrfpDphReportCorruptedBlock 0x1b9
0012fd74 6d08871b 00151000 0019cff8 00000001 verifier!AVrfpDphCheckPageHeapBlock 0x125
0012fdc8 77b71c8f 00150000 01000002 0019cff8 verifier!AVrfDebugPageHeapFree 0x14b
0012fe10 77b3d9fa 00150000 01000002 0019cff8 ntdll!RtlDebugFreeHeap 0x2f
0012ff04 77b21c21 0019cff8 0019cff8 0019cff8 ntdll!RtlpFreeHeap 0x5f 0012ff20 765a7a7e 00150000 00000000 0019cff8 ntdll!RtlFreeHeap 0x14e
0012ff34 0040103e 00150000 00000000 0019cff8 kernel32!HeapFree 0x14
0012ff50 0040124c 00000001 0141efb8 01420f60 PrinterFile1!Function1 0x3e
0012ffa0 765a3833 7ffdb000 0012ffec 77afa9bd PrinterFile2!Function2 0x15f
6. After you have noted the first non-Microsoft DLLs in the call stack below .ntdll (in the example, PrinterFile1.dll and PrinterFile2.dll are below ntdll), in the Error Reporting dialog, click Send Error Report.
7. At this point, if the DLL provider is not clear from the file name, search for the DLL name using the file search in Windows. Once found, right-click the DLL, choose Properties, and then determine the provider in the Details tab.
The information on the Details tab should determine who to contact for an updated DLL to fix the issue or help you to further investigate the problem. Refer to the links above for the manufacturer’s support and driver downloads to identify any updated versions.
If the DLLs below ntdll are all from Microsoft Corporation, we ask that you first confirm that Pageheap is indeed enabled (using Gflags.exe -p) and, if so, go online to search the Microsoft support website for any updated versions or known issues for those DLLs.
8. After you have identified the DLLs to update, go to Step 3 to disable the page heap tool.
3.
Disable the page heap tool
josta ilmenee että ajurit pitäs päivittää. Heh no mistä kun ei ole uudempia?
mikähän tässä nyt on vikana?
eikai ajurit voi mennä toimintakelvottomiks noin. käytännössä printterini on nyt toimintokelvoton.
Vastaukset 3
Vanhimmat
Onko se Spooler päällä palveluissa? Eihän taustatulostus toimi ilman sitä. Miksi vastaisit kieltävästi palomuurin kysymykseen pitäisikö Spoolerin käynnistys sallia?
tein ton microsoftin sivun ohjeen mukaan eli poistin kansiosta ja reksiteristä kaikki ylimääriset. ASENNUS ONNISTUI ok. mutta kun otan testisivun tulostuksen niin tulee " tietokoneesi suojaamiseksi windows on sulkenut tämän ohjelman"
explorer.exe on havainut ongelma ja ...on suljettava"
minkä takia noin testisivun kohdalla??
kuitenkin netistä tulostin sivun niin toimi.
jihaa ei sittenkään tullut viisaammaksi.
hmmm näyttää netistä tulostus onnistuvan mutta ei kovalevyltä MIKÄÄN:.
eli missä nyt on vika?