New
#520
I got that issue a couple of builds back, and nothing I tried sorted it. In the end, I bit the bullet, backed everything up (MRF), and did a clean install (first time in years) and it sorted the issue, plus another annoying issue where wifi would only automatically start after a proper shutdown and restart.
The old Acer T690 experiment didn't turn out as good as hoped. It's really pushing it with 10 at maxed 2GBs of mem. Although usable, it's a slow go. Here's my stats after letting it run and using it for 4 days so to work itself out. Had a few GSODs early on too. Vista, 7, and 8/8.1 ran pretty good on it. 8.1 used an average of approximately 35% mem.
Preliminary/New - Minutes:Seconds.
3:15/1:00 post to desktop
4:15/2:40 Fill out systray boot-up programs
0:445/0:20 for Task Manager to open and fill out
7:30/4:20 Disk/CPU thrashing stops to reach idle
70%/55% mem at idle
CU on the other partition runs a little better only using roughly 50% mem. I guess it's ok for testing Insider builds, but at snail's pace. LOL.
Yes. Pentium D duo @3GHz. Mem is the weakest point of course. Like I said, it's stretching it with 10. Too much going on at boot with sync, telemetry, and all. After the 4 minutes of thrashing it's ok, but slow.
Just looked. Purchased in May of 07. Old man by today's standards. Somewhat follows dogs' age.
The next project when the snow starts to fly is to get my Gateway 2000 P5-? out of mothballs. Been wanting to do that for quite awhile. I bought the Acer when the HD failed in it. Still have the monitor and keyboard too. It had 98SE and O97 installed. I'll have to pull the HD out of it and test in another machine. If it's trashed I'll either have to get either a set of floppies for it or burn an ISO to load 98SE on it again.
Attachment 157163
My old Acer laptop is also around 10 years old and started giving GSOD/BSODs with the FCU Insider Builds. It would do it at 75% during the version upgrade, but then would seem to work. However later on it would crash on shutdown/ hibernate.
It turned out that the Windows installer was grabbing a slightly older driver on the fax modem than the one I had, and using the newer* driver has hopefully fixed it.
* new is relative - they were probably both 10 years old but the one which was a few weeks newer seemed to make the difference.