Freezes in stand-by mode after going on line.

It sounds like you have a device conflict.  Have you tried rebooting in SAFE MODE, checking Device Manager for any conflicts or unknown devices, or any duplicate/multiples?  Any errors found, or multiples in error, remove all related occurrences and reboot to get corrected.

Here are some helpful resource links, until we know more about your configuration.

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q308535
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q304811


Troubleshooting Device Conflicts with Device Manager (Q310126)

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q310126

Good luck,
":0) Asta

HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP (Q316434)
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q316434

System Standby Disconnects Modem Connections (Q305618)
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q305618

Thanks all. I shall investigate all the answers...

After running in safe mode I tried to do what you said regarding the control panel but couldn't see anything wrong. Anyway running in normal mode now the standby thingy works ok. You're an ace Asta. The only thing different in device manager is a cross on Sis 900 PCI Fast Ethernet Adapter whatever that is. I will leave it disabled or should I delete it? (I don't have a network if that is what it does).
Many thanks

Thanks, JimiHendrix.  That is an identifier for your Network card.  Is it correct?  Perhaps knowing more about your actual network card and settings will help; it may be one of the XP default.

 A red "X" indicates a disabled device. A disabled device is a device that is physically present in the computer and is consuming resources, but does not have a protected-mode driver loaded. .... More here, and I'll return after my meeting this morning to see about your progress:

 http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q310126

":0) Asta

If that is the correct Network Adapter card you have, check for your Manufacturer's web site for updated XP compatible drivers.

These links should provide you additional guidance.

http://www.sis.com/products/connectivity/900.htm

http://www.sis.com/support/driver/index.htm

In the link below, it shows that sis has the available driver and shows it to be compatible with Windows XP
http://www.sis.com/support/driver/drivermap.htm

Ok. I d/l a network driver which I shall try and install later. Usually it does not freeze any more but it did once earier on...

I'm off to meetings, feel free to comment here if additional roadblocks are encountered and I'll return when I can.  Be sure to check the links and information to eliminate any avoidable problems, though.
":0) Asta

I removed the ethernet addapter in device manager, but when I restarted it reinstalled itself again, but I don't think it is anything to do with the problem anyway. It was still freezing up like before.

Have you checked your BIOS manual, and turned off Power Management control in the BIOS so that it is handled within Windows?  Within Windows, have you tried different Power Management schemes to see if that helps from Control Panel?  It still sounds like you have a conflict, and the links I provided earlier address some of the troubleshooting processes.

Sorry, I have so little time this week; but will check back when I can.

Asta

When I said BIOS Manual, I meant the manual for your Motherboard.

yes, thanks. On this start up I disabled the bios power management so will see what that does.

Keeping my fingers crossed that that BIOS turn off has worked. Thanks again Asta. Is there anyway I can give you extra points? - not that you need them!

Oh dear, it just froze again. I don't seem to have any obvious conflict but will keep investigating...

A couple of thoughts on this, JimiHendrix:

You still appear to have a conflict, despite things we've done that "should have" helped resolve the problem.  You may want to try different Power Setting schemes within Windows to see if no longer using hibernate and/or existing power management schemes helps.  

If I were in your shoes, I would create a new question in this same Topic Area to bring it back into the open question queue (if the above don't help), include the link to this question so all can see the things done so far.  It may help get things resolve more quickly.  I am perfectly willing to continue working with you here and see if we can resolve this, however.

Try this --- start-run-msinfo32  .... from Tools check Automatic Skip Agent (ASD), to see what Windows reports.  Also, on the left panel, under hardware, problem devices, see what's shown there.  Is Device Manager still showing a redX?

What are your connections shown for your exisitng network and TCP/IP settings?

I'm really busy this week, but will check back as soon as I can to see what else has transpired for you.

":0) Asta

Change your stand-by mode, for sure; and let me know what happens.  Your system may be ACPI and some conflicts there.  Baffling we haven't yet resolved this, quite honestly, but always more to learn.
Asta

OOps, under msinfo32-tools, meant to check "net diagnostics"

I see that there are many problems in terms of other users who run WindowsXP and system freezes from stand-by, but many potential causes, as shown here:

http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=windows+xp+standby+freezes+when+online

Expanding all categories in msinfo32 on the left panel, may help us isolate some specific problems.

Microsoft MSDN library is a wealth of information to help us all.  These links are helpful about Windows XP and the Hibernate versus Standby functions:

http://www.microsoft.com/windowsxp/pro/using/howto/security/hibernate.asp

Another thought that comes to mind, is about your Motherboard.  At boot, jot down the BIOS version you have, and check for your Motherboard in terms of a possible BIOS update that "may" be needed with their web site.

Have you checked WindowsUpdate - Product Catalog lately, to see what fixes may be needed?

Also, from control panel, have you done cleanup and Defrag (just in case), and cleared your brower's cache (temporary internet files and history files)?

These XP "how to" links are great.
http://www.microsoft.com/windowsxp/pro/using/howto/default.asp

The points for me are fine, but for your information, any time you want to award experts for additional help given, you can always do so directly by creating a new question in the same topic area, entitle it .... Points for __expertname__ and in the comment field paste the link that covers where the help was given.

Asta

http://www.microsoft.com/windowsxp/pro/evaluation/overviews/fastresume.asp

If you swap a CardBus card after your computer resumes from suspend, your computer may stop responding (hang).

This problem occurs with any PC Card device that displays a Power Management tab in its properties. If the Allow this device to bring the computer out of standby check box in the device's properties is selected, your computer may hang when you swap PC Card devices after suspending and resuming your computer.
More here, and relates to problem in Pcmcia.sys.
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q318358

More about your system would help, is it an IBM Thinkpad?
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q317087

When you are using a notebook computer that employs the Intel 440MX chipset and an AC'97 soft modem, you may experience the following symptom with Windows XP:

When you use the internal modem on the notebook computer, Windows XP may seem to stop responding (hang).


This problem has been confirmed to occur only on computers using the Intel 440MX chipset and an AC'97 soft modem. These computers require an updated system BIOS and an updated driver file (P3.sys) so that Windows XP can fully support the Intel SpeedStep Technology power-saving functionality concurrent with modem operations. As of November 2001, this configuration is typically found on only a small range of sub-compact laptop computers using the Intel 440MX chipset in support of the Mobile Intel Pentium III processor-M CPU.
System May Become Unresponsive When Using a Modem (Q306580)
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q306580

Many more possibilities (sorry to say)
http://search.support.microsoft.com/search/nlsearch.aspx?Catalog=LCID%3d1033%26CDID%3dEN-US-KB%26PRODLISTSRC%3dON&Product=winxp&Query=lock%2520up%2520freeze%2520power%2520management&Queryc=lock+up+freeze+power+management&withinResults=false&srchstep=0&KeywordType=ALL&Titles=false&numDays=&maxResults=100

Devices May Not Power Up Properly When Resuming From Standby (Q311542)
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q311542

Off to work.
Asta

Wow. I don't know where you get your energy! It would take me a week to type all the stuff you have. I don't know where to start. First I will do as you suggest and start the question again - I hope I get it right. I have disabled the ethernet device in bios now and so now I dont have that in Device Manager any more.

;)

I thought you disabled Power Management in the BIOS; now I am confused.  Not the first time.  LOL.

The Network card is how you're getting on the Internet, no?

I think we need to methodically take it all from the top, and I'll check back either later this evening or in the morning; when I have a chance.  

Did you have a chance to check start-run-msinfo32 and look through all the items in the left panel to see if we can see any problems noted, such as (after expanding all the categories) any problem devices?

I am swamped.

":0) Asta

The ethernet card is just for a network I think. Anyway I seem to be able to get on the internet without it. I have posted the question again as you suggested, and now will try your msinfo thingy.
Many thanks

Everything passed in the network diagnostics

Great, thanks...  I'll check back later today or first thing in the morning.  I also posted in the follow-up question so I can keep tabs on your progress there.

At work,
Asta

What do you think of this?
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q311542

That was one of the links I sent you and thought had potential.... did you use the Search feature to see if this is on your sytem, and if/when found check Properties to get version info, etc.?

Asta

I'll say this, I'm learning right along with you; having only recently upgraded all our systems to XP...
":0)

Did you ever find Pci.sys on your system?  You'll need to search all folders, including the hidden ones.  Here's the one on my system, and the version I have.
5.1.2600.21
Asta

The same one here

That's not the problem then.
Hmmm back to the think tank.
":0) Asta

It's pretty consistant now, it goes to sleep the first time but freezes up on the second attempt even after waiting 5 or 10 minutes. Next I will try connecting again to see if it goes to sleep again after that.

Have you tried changing the time settings to a longer time to see if that changes anything?  Control Panel - Power Management.

Also, if you're using a screen saver, try to default to the standard Windows XP screen saver to see if that helps.  Stabbing at straws, but don't want to miss anything.

Up to now I have put into stand-by by pressing a button on the keyboard or going via the shutdown menu but after your last suggestion I changed the settings from never to 1 minute to try the timed stand-by. It did it ok after 1 min but froze the next time...
No screen saver
By the by, at BIOS start up it makes TWO beeps ( 3 or 4 sec seperation). Is that normal? The second beep is just before a table with information about the drives in the system.

Please advise your Motherboard make/model and BIOS.

Here's one example on error code/beeps for a specific type of MB/BIOS
http://www.sysopt.com/biosbmc.html

http://www.sysopt.com/biosbmc1.html

Not only is it important to note the number of beeps, but also if long, short, more here:
http://www.techadvice.com/tech/B/BeepCode.htm

P4S5A motherboard from Novatech:
BIOS reads:

"NIVIDIA GeForce2 MX-400 vER 3.11.01.30cb6
64.0 MB ram"

2 short beeps about 6 secs apart

No luck finding anything for this model under Novatech, but did find this
http://www.ecs.com.tw/download/p4s5a1x.htm

Was there not a date?

Asta

Thanks Asta. I 'spose I'll have to take it appart to find the date... I suppose Navatech (where I bought it) should know if the beeps are a problem.

They should have some idea, but perhaps you have a manual for the Motherboard that may also give some ideas.  Normally, when you boot you can see the Bios and version and date.  Holding PAUSE at boot long enough to read the on-screen info may help, then Pause again to resume boot.  My guess is that it is video card-related, but only guessing; since on some this pointed to improperly seated RAM chips, others had other causes.  

Yes the date comes up after the first screen.
02/18/2002
Looking at that link you gave...

I looked at it as well, and see many BIOS updates since that time, some if which may be pertinent.  Prior to flashing your BIOS, make sure to save existing settings and BIOS and follow all instructions carefully.  Flashing a BIOS if done incorrectly can create total chaos for you.

Again, if I were in your shoes, I'd contact the person from whom I got the Motherboard to check in on the issues we've defined first.

Do you know what this means Asta?
http://pro.kongju-e.ac.kr/~xrose/BIOS_AMI.htm

Hi, Jimi.

I assume you're asking about parity checks and errors, given the BIOS updates noted that regard that in the earlier link.

In computers, parity (from the Latin paritas: equal or equivalent) refers to a technique of checking whether data has been lost or written over when it's moved from one place in storage to another or when transmitted between computers.

More about that here:
http://searchstorage.techtarget.com/sDefinition/0,,sid5_gci212748,00.html

You'll find explanation there for the I/O Bus, Modem parity, and more.

Asta

What I am wondering is what the beeps mean. The link you gave me is interesting:
http://www.sysopt.com/biosbmc.html

but do you know if there is a kind of test of the beep at the beginning anyway. I get a single beep a few seconds after the first one. Does a single beep always mean something wrong with memory? If it does, I will try reseating it and/or if it's divisible see which bit works. I can't talk to Novatech until Monday.

What do you think? Thanks very much for all your help on this.

Make sure that you take all the standard precautions, turn everyone off completely, unplug, make sure you're grounded and remove any static buildup by touching the metal part of your computer case, etc., before ensuring the Memory Chips are properly seated.  Also, while you're in there, check if things are "hot" in there, or if the fan is doing a good enough job, you may also need to blow out any dust accummulation while there using standard specifically made air-pressure items sold for computer cleaning.  The beeps are specific to Motherboards/BIOS type; sorry to say I have zero time today but at the very least wanted to get back on this question of yours.

Hopefully I'll have a bit more time next week; up to my eyeballs in work (some weekend, huh?).

Check your manual for your Motherboard (system) and see if they say anything at all within it for troubleshooting and beep codes.

":0) Asta

If it is a memory problem how would it work perfectly OK the first time but not the second?

Perhaps different areas of Memory are being accessed.  I wish I knew the answer, Jimi, I'm as baffled as I can be.  I have not found any other similar problems to yours, despite extensive research.  It just doesn't make any sense.  The BIOS fixes noted above "may" address it, perhaps not.  You were planning to contact the vendor from whom you got the Motherboard, to ask, right?  I'm truly baffled.  

When I encounter problems, I go through the processes we've tried to apply and through the process of elimination, ultimately find my fix.

Have you contacted the MB site to ask about the beeps for your exact BIOS and version?  I would definitely do that, if not already done.  Beep codes are unique, not all the same in terms of warnings.

Did you check the manual for the Motherboard?  It's really much more productive for you to start with the source, check the manual for any troubleshooting help they give you and try different settings, etc. as recommended.

I hope to have a bit more time next Wednesday to check back on progress; I've been swamped with little time to do any family things at all, and need to spend a little time with them today.

Asta

Did DirectX diagnostics give you any results to validate your multimedia environment, and video card?

http://www.bioscentral.com/beepcodes/compaqbeep.htm  also good on beep codes, as are many others (but again, unique in terms of system type, MB and BIOS)

Based on the link I gave you above for the Model you gave me, the BIOS is AmiBIos, and this is what it says about the 2 short beeps you said you had:
2 short Memory parity error A memory parity error has occurred in the first 64K of RAM.  The RAM IC is probably bad
Per this:
http://www.bioscentral.com/beepcodes/amibeep.htm

It also said this:
2 short = POST Failure One of the hardware testa have failed

About BIOS basics, very informative, although your specific manual is needed for specifics to your setup, such as "default settings" and recommendations, "optimum settings" and recommendations, etc.

http://www.bioscentral.com/misc/biosbasics.htm

Asta: I have spent quite a lot of time playing with different settings in BIOS changing just about everything but no change in any way so it's back to the original settings.
I rang Novatech this morning. They said it probably wasn't a hardware problem (ie not their problem!) and, probably spinnning a yarn, said the singles beeps were normal. Also suggesting not to risk updating the BIOS unless there was a specific problem mentioned.
I guess there is no reason to go into standby anyway these days. It's not like the old days with white lettering against a black background: "READY:" sitting there for days on end, and it's probably better to keep a hard drive spinning rather than stop and start it. So if I feel like turning the screen off now and then I will change the times in power options. I would rather like to have an icon which runs a V.B or C++ program to turn off things straight away - a future project!
So I will click the thingy to give you the points - not that is the reason you are trying to solve the problem - and give up. Not worth wasting any more time.
Many thanks.

You're not wasting my time, Jimi, I'm happy to help you when and where I can, and more points are not needed.

I'll listen further.  Personally, I choose (though a very different MB, and environment), not to use hibernate or standby, since I'm active all day long on the system and have been a creature of habit, who simply turns off the system (normal shutdown) at the end of the day and let the entire system "rest".  Some feel this isn't wise, but since I've been a PC user since PCs first came out and have never had a downside to this process, keep this as my mode of operation and haven't yet been sorry.  

I'm also the personality type that stays on top of BIOS updates for my Motherboards (2 primary production systems), and if a BIOS update is specified that addresses a feature or function that applies to me, I back up the BIOS, jot down settings and apply the changes.

As with all things, it gets down to end-user preferences and what works best for whom.  For me, my choices have been helpful to keep my systems humming with minimal problems.  ;)

I've enjoyed working with you, learned in the process and feel it has been a win/win scenario for me as well.

":0) Asta

Asta:
The ROM burning software "aminfxxx.exe" link at http://www.ecs.com.tw/download/p4s5a1x.htm
doesn't work.
What do you use? Does it have BIOS backup?

My first computer was TRS 80 in '79 and, like most, knew nothing about anything, but in the end I knew every address in that massive(!) 64K and knew the ROM backwards. Now I don't even know how this machine starts. Any idea of the ROM address!

I use an external Plextor CD-RW, and use Roxio software, version 5.1 which is XP compatible.
This gives you some FAQs
http://www.roxio.com/en/support/roxio_support/roxio_xp_sup_notes.html

Thanks, I meant the ROM BIOS

I only use ASUS MBs, by choice, and they have very clear instructions on how to back up the CMOS (BIOS) in their information on how to flash/update their BIOS by MB type/model.  I always first jot down my existing settings and information, since I use a highly customized setup by choice and need;  then follow the instructions from their web site explicitly.  Yours, I believe was AMIBOS, and if you've been advised not to update it, don't want to encourage you to do otherwise.

This gives some general information, which may be helpful to you.

http://www.hardwarecentral.com/hardwarecentral/tutorials/12/1/

This may also help guide you further.

http://www.ecs.com.tw/download/manual_m.htm

Off to work, will check back when I can Wednesday or Thursday, swamped.

Asta