I have a V515w configured to run wireless on the network, and there are two Dell laptops on the network that, occasionally, will awake from hibernating and have a runaway dleacoms.exe process taking up all of one CPU core's cycles. There does not seem to be a definite pattern to the problem, but occasionally happens, and the only way to address it is to bring up the task manager and show processes from all users, then kill off the process. My print driver is up to date on both laptops, and the firmware is up to date on the printer as well.
Try this tweak, first and see if it helps.
Start, control panel, device manager. Click on Network and then right click on your wireless adapter, left click properties, power management. Uncheck the box, allow computer to turn off this device to save power.
What is a Dell Service Tag and how do I locate it?
Original poster, If you have solved your problem, can you please mark the correct thread(s) with your solution. Thanks
Welcome to Dell Community!
Microsoft MVP - Windows Expert-Consumer April 1, 2012 to March 31, 2015
Well, I tried this and it failed three times - actually more often than without making the change! I did let it go awhile to make sure I didn't make a judgment after one failure.
Printer is on your wireless network, correct?
Try using these Recommended Wireless Router Settings I use channel 11. I would make a new SSID to make connecting easier.
Run Delete Print Jobs to remove any stuck print jobs from the queue.
Disconnect the printer.
Start, control panel, programs and features(add/remove programs) Dell V515 Printer, uninstall.
Restart your computer. Make sure the printer was removed. Manual Printer Driver Removal
With the computer online, insert the Dell V515w Printer disk and choose new installation. It will walk you through the process to install the printer. At some point, it will ask you to connect the printer to the computer, then find your network and ask for your password.
Remember virus programs and firewalls will block communications.
I have put up with this problem a long time, and I'm a bit surprised it has not been duplicated. I cannot tell you all of the circumstances under which it occurs (there are several permutations of it), but one that I have discovered has a pretty reliable reproduction rate is the following:
1) take the laptop, work with it at home on the wireless network
2) hibernate the computer
3) go to another location that has another wireless network for which the network is already known, thereby having the computer automatically connect there
4) work a bit, then hibernate the computer
5) return home, start back up
My son attends tutoring at a location where I work for an hour in their break room while waiting, and I almost always return home to the dleacoms process spinning away, and I sometimes get the problem there at the tutoring location (though this is not near as common). I just went to look at a problem on the network at my ex-wife's house, and was going to use my laptop as a test case. As soon as I brought the laptop up, I found dleacoms was spinning away. It's easy to know it's happened: this laptop fires up the fan non-stop within a few seconds of a process running one of the cores at 100% usage, so it doesn't take long for me to start looking around as to why an otherwise idle laptop is trying to reheat my hot cocoa.
While I can't read the code, and I can't attach to the process, my hunch is that some part of the code that comes to life after hibernation can't cope with a "no such thing" response when looking for the printer on the now-attached network, and just gets stuck at that point. Too bad we can't just do a kill -9 and get a stack trace from the core dump. As I said in my earlier reports, this problem will happen just from putting the laptop into hibernation and restarting it later on without leaving the house, and the problem still happens with my previous laptop as well. It does not happen every time at home, though it is becoming more frequent, but it seems to be far more consistent when I change locations and then return home.
Start, control panel, power options. I would select high performance.
Choose what closes the lid does. I hasve it do nothing, so the children don't walk around the house carrying an open laptop..
Click on change when the computer sleeps, then advanced power settings. Power lid and buttons there will allow you to change when the computer hibernates, if memory serves me correctly.
The dlee is from the printer and I would reinstall the printer using the instructions below.
First run Delete Print Jobs to remove any stuck print jobs from the queue.
Make sure the printer is not usb connected to this computer.
Start, control panel, programs and features, Dell V515w Printer, uninstall.
Restart yourt computer. Make sure the printer was removed. Manual Printer Driver Removal
With the computer online, insert the printer disk, choose additional computer, network and follow the instructions.
Also try these tweaks...
Start, control panel, device manager.
Go to the USB Controller section and click the + sign.
Go to each USB Root Hub and right click on it, left click properties, left click power management. Uncheck the box, allow computer to turn off this device to save power.
Restart your computer.
Try the following steps:
1) scroll up
2) note where you've suggested this before
3) note where I said it had no effect
4) think about submitting the problem to the developers rather than giving knee jerk responses that were not correct the first time around, have been tried, haven't done the job.
A rock star can do more than just cut and paste.
The software has a real problem, it has a real cause, it has to do with the developers, doesn't have to do with re-installing the print drivers. As long as you keep doing things to bump your post count that have no real relationship to the problem at hand, the longer you will keep the information away from the developers to fix.
"Real rock stars use their minds, not just drink stuff that comes from a can."
-- Me, 2012
Just wanted to tell you, I have a printer from the same serie, which is NOT wireless and I have similar issues.
When the printer and computer has been on for a while, without using the printer, then it's very rare that I can get it to work.Neither scanning nor printing works. The suggestion from the errorbox is always: "restart your computer".
I have sometimes tried to switch the printer off and turn it back on before I started to print. And it happens to work most of the time (unless the printer already had a seizure that day).All the time the computer was turned on as usual, just the printer was turned off/on.
My point is - the printer dlls cannot cope with errors and needs restarting, when something hits them.I wonder what happens to your laptop, if you shut down the printer and then restart it later?
Hope this helps - Heidi
P.s. Looove your last bullet list John :)
just edited the above text !!
I'm also having this issue with same printer on Win7 laptop. Causes rapid battery drain. Seems to only happen after hibernation.
I find that it's easy to figure out when this is happening: after coming out of hibernation, when the system settles and no longer has anything of note actually doing anything, my 1702 laptop is now a fire breathing dragon. Eventually, it dawns on me that something is running full tilt boogie for no apparent purpose.
It's a shame they won't look into this. I've considered using one of my pricey tech team problems on this, but I suspect I'll just find myself as frustrated doing that as I am with the rock star non-attempts to look into it.
It's so frustrating of late - it's gotten to be more frequent, not less over time - that I've considered buying another non-Dell printer to get this frustration out of my life. Most every return from hibernation requires me to kill off the dleacoms process, then forget three days later when I go to print and find it won't work. Heaven help me if I need to print something in a hurry - hurry won't be in the reboot's vocabulary!
I have observed the same kind of thing on my daughter's recent inspiron and V313 printer....
I am thing about just junking this printer before even buying its first set of cartridges...
So have I.. I just killed a dleacoms.exe process that was taking 97% max CPU. It seems to be related to handling wake from sleep situations. I have a Dell V515w that is connected to the network wirelessly. The printer is usually sleeping too. I think someone should try and get a trace like a ptrace or some other kind of process dump to see what this thing is doing at the time it is happening.. Has Dell opened a bug ticket on this yet?
I have Win7, Dell Inspiron and Dell v313w printer (connected to wireless net) and see same issue. It appears to happen after the PC comes out of hibernation. It happens periodically and my Norton software detects it and pops up an excessive CPU warning. I start task manager and this process is indeed eating CPU. I do a Win restart and the process returns to normal for a period of time, and then the issue is repeated. I tried re-installing and other suggestions to no avail. Appears to me to be a software bug .... pass it on to developers.
This is not a suggested answer, just a potential work around (I am on Windows 7 64 bit)
Open task manager go to Processes and find dleacoms.exe (Sort by name or CPU)
Right click on dleacoms.exe and select "Go to service(s)" - should take you to "dlea_device" in Task Manager / Services
Right click on dlea_device and stop the service
Right click on dlea_device and start the service
Seems to work for me.
Having said that these V313(w) and V515(w) printers are ... weak
Heidi, I am having same issue ...only now I restart, and then print something ....then go to print another document ...have to restart computer AGAIN. I have installed, uninstalled at least 6 times, can not figure out what I am missing!!!! I was never able to connect to wireless, so I use USB port. READY to toss the damn printer out the window!!!