It seems the problem might have been with the new version of the fingerprint software Toshiba supply with the win 7 upgrade. I removed the 'application' part - (I suspect the drivers are still there) - and the system is reasonably perky now.Sounds like it had an issue with the upgrade then. What about trying a reinstall? Sorry if I am harping on about stuff you may already have done, but for instance SPTD (the hardware access layer used by, for instance, Daemon-tools) doesn't support upgrading from Vista to 7.
Interesting, thanks.It seems the problem might have been with the new version of the fingerprint software Toshiba supply with the win 7 upgrade. I removed the 'application' part - (I suspect the drivers are still there) - and the system is reasonably perky now.
I would never ever use MS's OS "upgrade" feature, I've heard so many horror stories of things going terribly wrong with upgrades. Just clean out all the old, then in with the new. It means (a lot) less bother and less work trying to fix stuff that gets borked in the long run.
I would never ever use MS's OS "upgrade" feature, I've heard so many horror stories of things going terribly wrong with upgrades. Just clean out all the old, then in with the new. It means (a lot) less bother and less work trying to fix stuff that gets borked in the long run.
I get a stall about every few days with W7-64: when I don't reboot for that long, it will freeze, and give me an error that there aren't enough system resources to do whatever I want. I even had to give a hard reboot (press the button) once because of that, it didn't have the system resources for a reboot. And I always have to tell it to kill all active processes, because there are no system resources available for them to quit gracefully.
I get a stall about every few days with W7-64: when I don't reboot for that long, it will freeze, and give me an error that there aren't enough system resources to do whatever I want. I even had to give a hard reboot (press the button) once because of that, it didn't have the system resources for a reboot. And I always have to tell it to kill all active processes, because there are no system resources available for them to quit gracefully.
I get a stall about every few days with W7-64: when I don't reboot for that long, it will freeze, and give me an error that there aren't enough system resources to do whatever I want. I even had to give a hard reboot (press the button) once because of that, it didn't have the system resources for a reboot. And I always have to tell it to kill all active processes, because there are no system resources available for them to quit gracefully.
There are no events logged in the event viewer, but try google and look at the amount of hits. Very many people have the same problem.
I'm going to try all the suggestions, starting with increasing the size of the registry, if applicable.
I get a stall about every few days with W7-64: when I don't reboot for that long, it will freeze, and give me an error that there aren't enough system resources to do whatever I want. I even had to give a hard reboot (press the button) once because of that, it didn't have the system resources for a reboot. And I always have to tell it to kill all active processes, because there are no system resources available for them to quit gracefully.
This happened from the start, and I had to download and install some W7-64 drivers because some of the automatically installed ones turned out to be broken.Again, even if there are lots of google hits for it, I dont' think this is an operating system issue. I firmly believe you'd be incredibly hard pressed to duplicate this scenario on a clean OS with the base drivers loaded. There's some other 3rd party app somewhere causing you this grief.
Thanks. But yes, I checked. And yes, there are many people who had the same problem and posted a solution that worked for them. A lot of different solutions, that don't work for others.Of course, I also realize that this really doesn't help your situation either , but even the performance event log had no details? Or the memory leak diagnostic event log? Those two aren't stored in the same place as the "big three" that you're used to, they're buried a bit deeper.