HELP W2K SLEEP/ modem Driver preventing this on 2 comps

[AnMig]

I have been living with this problem past 3 months on a Compaq 12x325 laptop, Installed w2k pro not a hitch except. I cannot put the computer to sleep or hibernate.

everytime I try to automatically put my laptop to sleep in gives me a

"system stanbye failed"

The device driver Compaq 56k v.90 hsf mini pci modem device is preventing the machine from entering standbye. Please close all applications and try again. If the problem persists, you may need to update this driver.

This is the latest and the only driver available from compaq site (w2k approved)
This is not entirely a driver isssue since I AM ABLE to put my lap top to sleep using special hot keys (Fn + F4) so I know my system is cabable of going on standbye. I am not able to go on standbye or hibernate using (start---shutdown---stand bye or hibernate)
I was about to give up on this issue when all of a sudden my Home cpu (kk266 ) which was working well on w2k all of a sudden started to give me this sleep problem with modem driver preventing it to go on standbye. The only thing in common between the 2 system is W2k slipstreamed sp2/56k modem(conexant,askey)/norton utilities


I am really hoping somebody else has this problem since this standbye problem showed up on both of my systems.

No extra device on device manager when i boot in safe mode
tried a search in microsoft no help.
cant call compaq since they dont offer support once you change operating system (was mebefore.

 

[jaywallen]

Are you certain that there isn't an app trying to use the modem driver? That might prevent the driver from allowing W2K to go into standby or hibernation. Things that come to mind: fax, messaging or Trojan software. If the driver is WDM, it shouldn't be defeating ACPI functions on the laptop. I suppose it's possible that another driver might be interfering with the modem driver and making it to appear to be the cause of this issue.

Hope you find a solution.

Regards,
Jim

 

[DainBrammage]

Are you sure that your laptp is ACPI compliant if is no Win 2000 will not allow you to hibernate
Check and make sure your lappy isnt just APM compliant also flash your bios to the lateset available for your chipset

 

[AnMig]

Thanks for replies guys,
my lap top is aspci compliant and is I am able to manually go on standbye using special function key. SO at least I know it can go to standbye. Just cant seem to nail the problem down and now its happenning to my hom cpu.

How do I know if I have a trojan?

never had a virus before and always do norton virus scan.

any suggestions? its probably something simple with w2k.

 

[jaywallen]

What have you installed recently on both machines? The two machines are very different, hardware-wise. Correct? If both are behaving the same odd way, it's because of something that you installed on them, or some configuration change you made, whether intentionally or not. the only other likely candidate would be something like a Trojan. But let's take care of first things first. A Trojan might be detected by a virus scanner, but it might not. But you should be able to figure out what you've installed lately or whether or not you've set up something like FAX software that might be trying to keep the modem line open so that it can answer calls.

Something that might help is if you bring up your Task Manager and list for us the items showing on both the Applications and the Processes tabs. We might be able to spot something unusual in one of them.

Regards,
Jim

 

[AnMig]

jaywallen

Thanks for suggestion/ will try to list processes and applications running.

Procsesses:

system idle process
system
smss.exe
winlogon.exe
csrss.exe
services.exe
lsass.exe
svchost.exe
spoolsv.exe
svchost.exe
npssvc.exe
NPROTECT.EXE
regsvc.exe
MSTask.exe
Nopdb.exe
explorer.exe
winmgmt.exe
symtray.exe
iexplorer.exe
taskmgr.exe


Applications:

Reply-microsoft internet explorer

Anybody spot anything that shouldnt be there? This is all greek to me aside from the common ones (nprotect, winlogon ect)

 

[jaywallen]

Hi,

The only "unusual" items I see there are npssvc.exe, nprotect.exe, symtray, and nopdb.exe. Are all of those Norton/Symantec Utilities/Systemworks processes?

You said that you've updated your modem driver to the latest W2K-compliant version from the vendor, so that should be cool. I'm wondering if something in the complement of Norton utilities may be causing your systems' reluctance to go into standby.

In order to diagnose this you're going to have to change some things in your configuration to see if a given change will re-enable standby. I suggest opening the options dialogs for all of the Norton stuff and turning off EVERYTHING. After a reboot or two, then test the systems to see if they will successfully enter standby and then resume. If so, try re-enabling the Norton items ONE-AT-A-TIME with testing of the system after each item is re-enabled. When the system starts failing, you've found the culprit. NOTE: The one-at-a-time thing is very important if you really want to know what's going on and what you can and can't run on the system without causing failure of these power management features.

It would be very convenient if it were the Symantec software. That would neatly explain why standby just started failing three months ago. A live update could have done it, for instance, without you having attached any particular importance to the event, and therefore not having associated the update with the failure of the standby function.

If, however, Symantec isn't at fault, then you've got a harder job ahead of you. My first suggestion would be to reboot the system with minimal drivers to see if you can regain the standby function. If you do regain the function, then you're looking for a misbehaving driver. The driver could be badly written, or something could have happened to its configuration -- in which case, simply removing the device and its driver and then allowing the system to re-detect it (and installing the driver again, if it's not a W2K-native driver) may fix the problem.

Since you didn't specify yea or nay, I'll assume that you don't remember installing something new on both of the machines just before their power management features stopped working.

One other point: I'm assuming that standby always worked well on both of these systems. I think many (most?) desktop systems are a little iffy on this part of the ACPI spec. Also, a lot of cards and peripherals designed for desktops are simply not designed to strictly adhere to the standard. It appears that device vendors are assuming, correctly or incorrectly, that consumers don't care much about standby and hibernation on desktops. The notebook, however, should have the spec nailed regardless of any excuses by manufacturers. There's certainly no doubt that the average notebook purchaser expects to be able to use these features!

Please let us know what you learn. If this stuff was working for you before, it ought to work now. Or you should at least have a good explanation of why it won't, and thereby have the choice between having the power management features and whatever it is that's defeating them.

Regards,
Jim

 

[AnMig]

Thanks for suggestion will try to disable norton.
I do run live update every week.
It the error message always states that its my modem driver causing the sleep problem. What confuses me is that using the LAPTOP I can put it to sleep using special hot key provided by compaq but cannot put it to sleep by itself or by using the shutdown---standbye option. I would have accepted this quirk to compaq but suddenly my home pc that uses a entirely different modem and driver is doing the same thing.
I am pretty sure its norton or w2k. the only other common programs they have are NERO/iomega cdrw drivers/word 2000/power dvd

The lap top is a pentium 3 700 with 192 ram. It came with WIN ME but I formated and installed w2k. This lappy is pretty new about 6 months old too.

My home PC is kk266 1 ghz B TB/ crucial 256 x2/ Turtle beach santa cruz/
GE force 2 mxdetonator drivers 11/ conexant modem/

Thanks for suggestion will do as suggested when I go home.

I cant believe I am the only one having this problem since its happening to both my comps I thought somebody else might have this problem

Thanks again.

 

[jaywallen]

I have seen power management issues that were highly specific to Norton apps and the specific options they were using. Symantec / Norton programmers are very aggressive with the ways in which they implement features in their software. Sometimes they create more problems with their diagnostic / maintenance software than they solve. I doubt very much that this is an SP2 issue. But, even if turning off Norton appears to fix the issue, it doesn't necessarily mean that the issue is actually Norton's fault. It could always be that something they did legitimately causes the modem driver to cause this failure (or that it causes some other driver to fail in a way that makes it LOOK like the modem driver is causing ACPI function failure). This is about the only way in which I've seen user mode software cause much trouble in W2K. It grabs a kernel mode device driver and won't let go, or messes with it in other ways.

Please let us know how the testing goes.

Regards,
Jim

 

[AnMig]

jaywallen


Uninstalled norton (everything including live update/uninstalled windows notification also) still the problem persist in my home pc. Uninstalled the driver and reinstalled(modem driver) and work fine after reinstall no sleep problems but if I reboot my comp the problem re-appears.

I am at work now so after fiddling around with the lap top found out something. I am actually using the microsoft driver not the compaq driver. I believe this happened when i ran windows update and microsoft stated they had updated driver for my modem. I uninstalled the microsoft driver and forced w2k to acccept the compaq driver and violla the sleep problem is gone at least for my lap top.

I am pretty sure i ran and using updated modem driver from microsoft in my home PC so as soon as i get home I will uninstall them and use conexant provided driver (actually a gateway modem)
I hope this solves my home pc sleep problem.

Thanks for help, wont use microsoft drivers from windows update from now on

peace

 

[jaywallen]

Very interesting!

Yup, driver issues are the thorniest problem in W2K. Drivers that came with W2K were supposed to be ACPI-compliant, but I think a few ringers got through. Actually those drivers may have performed flawlessly under test conditions that did not anticipate a combination of devices (and possibly even software) that exists in the machines on which they fail to pass muster now. A lot of people are loathe to stray from the driver complement that comes with the OS lest they leap from the frying pan into the fire, but I think that staying right on top of the driver situation for my machines is the main reason I've had so little trouble with any of them. In the few cases where I couldn't find a fully W2K-compliant driver, I've simply removed the offending device and replaced it -- though that's tough to do if it's an intrinsic device on a notebook computer.

So, now that Norton has been vindicated on your machine. That at least saves you from having to do some shopping for anti-virus software. I hope things will go smoothly when you tackle the desktop's modem.

Regards,
Jim