XP Home : Unable to go into Hibernation or Standby Mode

M

Mr. Low

Dear Sir,

I have upgraded by PC with SP3 two days ago.

Now I am unable to enter into hibernation or standby mode.

The error message is: “ The device driver for the ‘Communication Port (COM1)
devices is preventing the machine from hibernation. Please close all
application and try again. If problem persist, you may need to update the
driver.â€

I have checked and confirmed that all the desktop application inclusive of
the internet connection are off, but this error message keep coming when I
want to go into hibernation.

May I know how to overcome this problem?

If I am going to update the driver, I do not know where to get it,
appreciate very much if someone knowledgeable could help me on this.

Thanks

Low
 
M

MowGreen [MVP]

Mr. Low,

The possible cause might be that the Communications Port needs to be
either uninstalled/reinstalled, or the driver needs to be updated.
If the system is on broadband the issue may stem from the ethernet card
[Network adapter]. If it's on dialup, it may be the modem.

First thing to try would be to uninstall Communications Port [COM1] via
Device Manager and then click Action, Scan for hardware changes, and
allow DM to reinstall the drivers.
If the result is the same then check see if there is a more recent
driver for Communications Port [COM1].

Open Device Manager by going to Start > Run > type in or copy&paste the
below into the Open: line and then click OK or press Enter

devmgmt.msc

Click the plus sign next to Ports, then click on Communications Port
[COM1].

*Right* click on Communications Port [COM1] and then 'Uninstall' to
remove it.
Do the same to update the driver except choose 'Update Driver'.
IF reinstalling/updating the driver for Communications Port [COM1]
doesn't resolve the issue, try the same steps for the Network adapter
and then the modem, depending on how the system connects to the internet.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============
 
M

Mr. Low

Hello MowGreen,

Many thanks for your professional advice, the problem is now fully resolved.

Best Regards

Low

--
A36B58K641


MowGreen said:
Mr. Low,

The possible cause might be that the Communications Port needs to be
either uninstalled/reinstalled, or the driver needs to be updated.
If the system is on broadband the issue may stem from the ethernet card
[Network adapter]. If it's on dialup, it may be the modem.

First thing to try would be to uninstall Communications Port [COM1] via
Device Manager and then click Action, Scan for hardware changes, and
allow DM to reinstall the drivers.
If the result is the same then check see if there is a more recent
driver for Communications Port [COM1].

Open Device Manager by going to Start > Run > type in or copy&paste the
below into the Open: line and then click OK or press Enter

devmgmt.msc

Click the plus sign next to Ports, then click on Communications Port
[COM1].

*Right* click on Communications Port [COM1] and then 'Uninstall' to
remove it.
Do the same to update the driver except choose 'Update Driver'.
IF reinstalling/updating the driver for Communications Port [COM1]
doesn't resolve the issue, try the same steps for the Network adapter
and then the modem, depending on how the system connects to the internet.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============



Mr. Low said:
Dear Sir,

I have upgraded by PC with SP3 two days ago.

Now I am unable to enter into hibernation or standby mode.

The error message is: “ The device driver for the ‘Communication Port (COM1)
devices is preventing the machine from hibernation. Please close all
application and try again. If problem persist, you may need to update the
driver.â€

I have checked and confirmed that all the desktop application inclusive of
the internet connection are off, but this error message keep coming when I
want to go into hibernation.

May I know how to overcome this problem?

If I am going to update the driver, I do not know where to get it,
appreciate very much if someone knowledgeable could help me on this.

Thanks

Low
 
M

MowGreen [MVP]

Mr. Low said:
Hello MowGreen,

Many thanks for your professional advice, the problem is now fully resolved.

Best Regards

Low

You're mowst welcome. Glad to hear that the issue is resolved.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============
 
M

Mr. Low

Hello MowGreen,

Although the problem has been fixed earlier, but when I check my disk for
error
the same problem recur, is there any other way to fix it completely.

My Event Logs are are follows:

====================================================
Event Type: Error
Event Source: serenum
Event Category: None
Event ID: 43
Date: 5/19/2008
Time: 6:21:03 PM
User: N/A
Computer: LOWSK
Description:
The description for Event ID ( 43 ) in Source ( serenum ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: .
Data:
0000: 16 00 00 00 01 00 c0 00 ......À.
0008: 00 00 00 00 2b 00 04 c0 ....+..À
0010: 05 00 03 00 56 00 00 c0 ....V..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

=====================================================
Event Type: Error
Event Source: Serial
Event Category: None
Event ID: 36
Date: 5/19/2008
Time: 6:21:56 PM
User: N/A
Computer: LOWSK
Description:
While validating that \Device\Serial0 was really a serial port, the contents
of the divisor latch register was identical to the interrupt enable and the
receive registers. The device is assumed not to be a serial port and will be
deleted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 08 00 02 00 56 00 ......V.
0008: 00 00 00 00 24 00 06 c0 ....$..À
0010: 3e 00 00 00 00 00 00 00 >.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: f8 03 00 00 00 00 00 00 ø.......

===================================================

Thanks

Low



--
A36B58K641


MowGreen said:
Mr. Low said:
Hello MowGreen,

Many thanks for your professional advice, the problem is now fully resolved.

Best Regards

Low

You're mowst welcome. Glad to hear that the issue is resolved.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============
 
K

kt404u

Still cannot initiate stand by mode, doesn' give me that option???
Tied above steps to no avail.Tried to adjust in perf and maint. also. nada???
any help would be appreciated.

Mr. Low said:
Hello MowGreen,

Although the problem has been fixed earlier, but when I check my disk for
error
the same problem recur, is there any other way to fix it completely.

My Event Logs are are follows:

====================================================
Event Type: Error
Event Source: serenum
Event Category: None
Event ID: 43
Date: 5/19/2008
Time: 6:21:03 PM
User: N/A
Computer: LOWSK
Description:
The description for Event ID ( 43 ) in Source ( serenum ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: .
Data:
0000: 16 00 00 00 01 00 c0 00 ......À.
0008: 00 00 00 00 2b 00 04 c0 ....+..À
0010: 05 00 03 00 56 00 00 c0 ....V..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

=====================================================
Event Type: Error
Event Source: Serial
Event Category: None
Event ID: 36
Date: 5/19/2008
Time: 6:21:56 PM
User: N/A
Computer: LOWSK
Description:
While validating that \Device\Serial0 was really a serial port, the contents
of the divisor latch register was identical to the interrupt enable and the
receive registers. The device is assumed not to be a serial port and will be
deleted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 08 00 02 00 56 00 ......V.
0008: 00 00 00 00 24 00 06 c0 ....$..À
0010: 3e 00 00 00 00 00 00 00 >.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: f8 03 00 00 00 00 00 00 ø.......

===================================================

Thanks

Low



--
A36B58K641


MowGreen said:
Mr. Low said:
Hello MowGreen,

Many thanks for your professional advice, the problem is now fully resolved.

Best Regards

Low

You're mowst welcome. Glad to hear that the issue is resolved.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============
 
K

kt404u

oh yea thanks, kt404u...

Mr. Low said:
Hello MowGreen,

Although the problem has been fixed earlier, but when I check my disk for
error
the same problem recur, is there any other way to fix it completely.

My Event Logs are are follows:

====================================================
Event Type: Error
Event Source: serenum
Event Category: None
Event ID: 43
Date: 5/19/2008
Time: 6:21:03 PM
User: N/A
Computer: LOWSK
Description:
The description for Event ID ( 43 ) in Source ( serenum ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: .
Data:
0000: 16 00 00 00 01 00 c0 00 ......À.
0008: 00 00 00 00 2b 00 04 c0 ....+..À
0010: 05 00 03 00 56 00 00 c0 ....V..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

=====================================================
Event Type: Error
Event Source: Serial
Event Category: None
Event ID: 36
Date: 5/19/2008
Time: 6:21:56 PM
User: N/A
Computer: LOWSK
Description:
While validating that \Device\Serial0 was really a serial port, the contents
of the divisor latch register was identical to the interrupt enable and the
receive registers. The device is assumed not to be a serial port and will be
deleted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 08 00 02 00 56 00 ......V.
0008: 00 00 00 00 24 00 06 c0 ....$..À
0010: 3e 00 00 00 00 00 00 00 >.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: f8 03 00 00 00 00 00 00 ø.......

===================================================

Thanks

Low



--
A36B58K641


MowGreen said:
Mr. Low said:
Hello MowGreen,

Many thanks for your professional advice, the problem is now fully resolved.

Best Regards

Low

You're mowst welcome. Glad to hear that the issue is resolved.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top