Computer reboots instead of returning from standby.

how are you putting it into standby?  i mean to ask, are you sure it's not hibernation, or actually turning off?  could it be as easy as a misconfigured power-button action?

Either selecting standby in the turn off computer dialog or pressing the power button which is configured to go to standby. The computer states going into standby and the lights indicates it is in standby. Exactly the same as before upgrading to the SSD. The problem occurs when coming out of standby.

Change the system recovery options from Restart to Dump and you will get BSOD each time you try to return the machine from standby. You need to reinstall Intel driver for HDD (if AHCI os ised).
If this does not help let it dump amd upload here minidump file.

noxcho,
I am confused. I am not getting the BSOD. Where do or did I "Change the system recovery options from Restart to Dump"? I do not have an Intel driver for HDD. Attached in an image from my device manager:
Screen-Capture.gif

is it at all likely that the battery is dying while in standby mode?

you can tell it to NOT automatically reboot upon bluescreen like this:
right-click 'my computer'
properties
advanced
click the button under 'startup' and put a checkmark for 'do not automatically reboot'

"is it at all likely that the battery is dying while in standby mode?"
It is plugged in and the battery is at 100%.

I unchecked "Automatically restart" under "System Failure" on the startup and recovery settings as you suggested. Now the computer locks up when returning from standby. Ctl Alt delete doesn't even work. No bluescreen - the computer returns to where it left as it should after retuning from standby but everything  is locked up.

wow that's ... unique...

what are your previous event viewer log entries for system/application when it rebooted before?  

can you run a scan at www.driveragent.com, and post the url of your results?  i'll get you all the drivers you need, it's most likely a driver at this point.

The error log displays:
The lxdvCATSCustConnectService service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Attached in the error log image.
Screen-Capture.gif

could you post a screenshot of your system and app logs, after you do this in them:
view > filter > uncheck informational and success

also the driveragent url would be a benefit

I went to computer management, services, lxdvCATSCustConnectService and tryed starting the service and got the same error (see images).
Screen-Capture.gif
Screen-Capture.gif

that service reports back to lexmark how much you print, how much ink you use, etc...  

http://driveragent.com/b/driveragent_results?hwid=7e6c835edf6991b1830f6704825ec7ea&PHPSESSID=emru4th5kbnumkdqr5r8eqam72

ok so it's not a driver issue...

would you be able to post a shot of the error/warning/failure's from the application and system logs?  or upload a save of them?

Actually the fact your system did reboot automatically indicates that it was trying to recover from failure. I had recently the problem with come backup from standby and my PC did always BSOD.
When the PC locks how long does it remain in locked state? Did you let it run till it unlocks?

"would you be able to post a shot of the error/warning/failure's from the application and system logs?  or upload a save of them?"
I thought I did in my response http:#28890540.  If that is not what you are referring to, then could you explain how to get the application and system logs?

"When the PC locks how long does it remain in locked state? Did you let it run till it unlocks?"
I waited a couple of minutes. I'll try longer.

your screenshot of the event viewer was just one event, i was hoping to see all the errors/warnings/failures from around the time it locks up/reboots

Here are screen shots of the system and application error logs.
Screen-Capture.gif
Screen-Capture.gif

ok so all of those errors are at least one service not starting up properly, which is good - and i think you've nailed it down to the lexmark service.  there are some logon issues in there, is the machine set to go to the welcome screen when resuming from standby?

are you inclined to uninstall all things lexmark, test, and then reinstall them if needed?

I will uninstall the Lexmark drivers and utilities and reinstall.

well test before you reinstall them - i've seen lexmark stuff working perfectly fine in and of itself, while irritating other windows processes

I uninstalled the Lexmark drivers and utilities but returning from standby still locks up. However, not getting errors in the system log now.

wow.  

is it set to go to the welcome screen, or some other login prompt, upon wakeup?  there's a tab by the power settings that has a checkmark for 'show the welcome screen when resuming...'

i ask because there were a few entries for errors when logging in

can we set that setting to the opposite of whatever it's at now?

Did not see a "tab by the power settings that has a checkmark for 'show the welcome screen when resuming...' I checked "Prompt for password when computer resumes from standby." No change.

I'm thinking the main error is
FTDisk Error Event ID 57
http://eventid.net/display.asp?eventid=57&eventno=2197&source=Ftdisk&phase=1
Experts exchange has found a solution and that it was related to
unsafe USB removal problem.
https://www.experts-exchange.com/questions/22041819/FTDisk-Error-Event-ID-57.html

"it was related to unsafe USB removal problem"

I am not removing any USB devices when I get this problem. The FTDisk Event ID 57 warnings in my error logs refer to "The system failed to flush data to the transaction log. Corruption may occur." (see image). The solutions listed on the link on eventid.net require a subscription and I am not interested in subscribing at this time since I am not sure the reference is applicable to this problem.
Screen-Capture.gif

I did see a device in my safely remove hardware utility: O2 Micro SD SCSI Disk device (see image). I did stop and remove (it is not an USB device) then went to standby and returned. No Change.

You response did give me the idea to search through the MS KB for "The system failed to flush data to the transaction log." and "The lxdvCATSCustConnectService service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion." I will let you know if I find anything useful. Thanks.
Screen-Capture.gif

Good idea. I'll research too

You dont have to sub scribe to the site to see the
FTDisk Error Event ID 57 posts and suggestions.
http://eventid.net/display.asp?eventid=57&eventno=2197&source=Ftdisk&phase=1

I just thinking. You say>>I cloned my hard drive to the solid state drive.
Cloned maybe the key.
A clone is an image from a previous hard drive , an image or mirror?
intact with all the same settings? or just windows components?
Something missing?? does your windows recognise the new hard drive?
and in the bios?
is it set to boot to HDO first boot?
Rom drive second boot?
Sleep mode switches off the hard drive as well the monitor?
What other power savers do you have on there?
Check the network card, it has a setting to allow it to turn your windows off
just throwing ideas


 

>A clone is an image from a previous hard drive , an image or mirror?
I used Acronis True Image Home Clone disk

>intact with all the same settings? or just windows components?
>Something missing??
Don't think so. Both dives show the same data size

>does your windows recognise the new hard drive?
yes

>and in the bios?
yes

>is it set to boot to HDO first boot?
>Rom drive second boot?
Not sure what you mean. Hard drive - first priority CD - second priority

>Sleep mode switches off the hard drive as well the monitor?
Not sure where to check or set that.

>What other power savers do you have on there?
What do you mean?
 
>Check the network card, it has a setting to allow it to turn your windows off
The network card is disabled (I'm not connected to wired network).

control panel power options.<< to check the power options for the monitor and hard drive
Other power savers like a screen saver with a password setting to logon after it awakes.
only offering ideas..
Just feels like there is an inconsistancy in the motherboard and the windows could be the drive
Looking at all the errors you have.
Service control manager is related to (controller) being the keyword here I believe...
sourced>>
The Service Control Manager maintains a database of installed services in the registry. The database is used by the SCM and programs that add, modify, or configure services.
The HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services registry key is used for storing this database.
>>>An initial copy of the database is created when the system is installed.<<< This a clone.
The database contains entries for the device drivers required during system boot.
The database includes the service type, startup type, error control level, fully qualified path of the service executable, optional dependency information and optional account name and password about each installed service and driver service.
http://en.wikipedia.org/wiki/Service_Control_Manager

As I see it using a clone, usually 100% reliable but when they go wrong it has to be in the regestry and what it sees with the regestered windows and the bios.
What hard drive did you have prior?
I believe it's posible you brought problems over to the new solid state drive.
I'm not familiar with SSD  but a little lookup
Solid State Drive is this usable as a standrad Windows storage drive especialy since this is a Windows XP Tablet Version Sp3 Toshiba Stylistic 2112 . OEM sensative?

A solid-state drive (SSD) is a data storage device that uses solid-state memory to store persistent data. An SSD emulates a hard disk drive interface, thus easily replacing it in most applications. An SSD using SRAM or DRAM (instead of flash memory) is often called a RAM-drive, not to be confused with a RAM disk.
http://en.wikipedia.org/wiki/Solid-state_drive

Windows XP Tablet Version Sp3 Toshiba Stylistic 2112
Tablet PC brings to mind the pen tool. Or Touch screen in W7 is that right?
Did you flash the bios prior?
Or need to when cloning?

Your problem is rooted in Windows XP still treating the drive as though it were not an SSD device which is causing problems in, most notably, cached writing.  Here is an article on making XP be "SSD friendly"
http://www.ocztechnologyforum.com/forum/showthread.php?43460-Making-XP-pro-SSD-friendly 

Check the C:\Windows\minidump folder and see if there are any recent minidump (.dmp) files --- date is in file name. If so, attach the 3 most recent ones to a comment.

I found one recent minidump (.dmp) files.
Mini032910-01.dmp

thenelson,
I read through here pretty quickly, but didn't notice,

Do you have ANYTHING plugged in to your system by USB when this thing goes to standby?

Have you tried disconnecting all USB items and then testing?

"Do you have ANYTHING plugged in to your system by USB when this thing goes to standby?"
No.

Minidump analysis wasn't helpful. The faulting module was csrss.exe -- Client/Server Runtime which is responsible for a number of functions and probably has nothing to do with problem.

And maybe the second time is a charm.....
Your problem is rooted in Windows XP still treating the drive as though it were not an SSD device which is causing problems in, most notably, cached writing.  Here is an article on making XP be "SSD friendly"
http://www.ocztechnologyforum.com/forum/showthread.php?43460-Making-XP-pro-SSD-friendly 

"Your problem is rooted in Windows XP still treating the drive as though it were not an SSD device"
Yep, I saw that with your first post. Took me a while to respond because the link had a lot of suggestions to try. I tried all of them with no change to the problem. Didn't see much other improvement either. Perhaps my SSD (PQi SSD Laptop Drive S525 128GB) doesn't have the random writes filling up the write buffer problem described in the link.
 

I'm sorry; I thought that article also included turning off the write caching; but, on rerreading it, it didn't.
Your event 57's (and probably others) are due to the system's failure to write cached data out to the SSD and are probably due to the timing differences in wake up times.
Open My Computer
Right Click on C: and select Properties Click on Hardware Select the first disk (assuming that is where the system is booting from) and click on Properties Click on Policies and uncheck the enrty for Enable write caching on this disk. Then, OK and OK.
That should fix it.
SSD's; though, still don't like having cloned images from non-SSD's dropped onto them as it causes a misalignment between the blocks internal to the SSD and those defined in the partition table.
Read this: http://msftmvp.com/Documents/BestPrac_SSD.pdf

Everything was grayed out on the policies tab to for the SSD drive.

Is write caching still checked?

I'd consider running a repair reinstall using the Toshiba Stylistic 2112  xp setup disc.
May fix the core components.

> Is write caching still checked?
Yes, see image

> I'd consider running a repair reinstall using the Toshiba Stylistic 2112  xp setup disc.
I may need to byte the bullet. (Pun intended).

Oops - here's the image:
Screen-Capture.gif

Your system thinks the drive is a removable device which is a known bug with some NVidia chipsets.  Resuming from standby on a removable boot device is fraught with potential problems and is, I believe, the root cause of your problem. To go further, I need the model number of your Toshiba (I.E. P500D-ST5805) from the bottom of the system.
You may have some real rock-and-a-hard-place problems, too.
SSD's are organized internally into blocks and normal XP hard disk partitions are not aligned with those boundaries.  What this causes is a severe performance degradation and a shortened life; because, every time you write, the device has to do a read-modify-write so it doesn't trash the contents of the rest of that block.  SSD's can only write to each block a fixed number of times before they stop working.
Since all you have is a recovery disc that will restore an image of the misaligned block structure, this whole idea may not be such a good one.
So, we may be able to fix the resume problem; but, you need to understand that the SSD will not perform as fast as it could and will have a shorter life.

Did not see a model number on the back. Here an all the numbers on the back:
P/N: CP373052-1
S/N: R8118148
MODEL: ST5112  (in the original question, there was a typo that incorrectly stated 2112)
Product No: FPC353DATK
REG NO: ST5111

"this whole idea may not be such a good one."
One of the options on buying a ST5112 computer was a 64 gb SSD so I would think the computer should be able to be set up to work with a SSD. I guess we can deal with that in a new question after this one is resolved.

Yeas; but, its also a Fujitsu Stylistic ST 5112, not a Toshiba, at all, which changes everything......
I have to go, for a while; but, the key to your issue is that XP is reporting the SSD as a removable device and is not managing it (especially powerwise) correctly.

"Run a repair reinstall"
I will do that in the next day or two.

"did you perchance, uninstall the Shock Sensor Utility?"
Yes

"if you were to repartitiion the drive using the instructions I posted earlier"
Which instructions are those?

Read this: http://msftmvp.com/Documents/BestPrac_SSD.pdf

It may have fixed the resume from standby problem temporarilly; but, unless you fix the issue of Windoze thinking it is a removable device so you can turn off the write caching, it will be back and, sooner or later, won't be fixable using CHKDSK.
Additionally, I don't know what the number of writes limitation is on that SSD; but, unless you do something about the misalignment issue, the drive will die long before its time.

How would I fix the issue the issue of Windoze thinking it is a removable device so I can turn off the write caching?

Davis,
I finally heard back from PQI.  I believe they are saying the settings are fine for the SSD:

There is a wear leveling function of the SSD firmware that could control a great deal of read and write when SSD operate. Therefore, it attaches great importance to flash memory life-time. Using proper flash memory management tool, it can extend the flash memory lifetime.

Don’t worry about that it does not affect the read and write limit.