| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 119001 | 2011-06-30 08:28:00 | Anyone ever come across this XP startup error? | Speedy Gonzales (78) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1213580 | 2011-06-30 08:28:00 | I've got a desktop here (not mine), and its started to bring up this error recently, once it boots into windows . One of the files containing the system's Registry data had to be recovered by use of a log or alternate copy . The recovery was successful . I've scanned it for errors, malware, defragged it . Thats fine . I've checked a few sites, via Google, and some say its a memory prob . So, I'm testing the ram now with memtest . And some sites, say it maybe a corrupt profile . Or a driver (AFAIK, noone has installed anything else (driver or hardware) . Since it was here last time . And to do a sfc / scannow on it ( havent done this yet) . According to one site, this hdd is / or was also affected by a firmware bug (ST3160815AS) . I'm trying to find out WHAT firmware was affected now . Earlier , I managed to get it back online (no sites would load at all) . So any ideas, WHAT the prob maybe ?? |
Speedy Gonzales (78) | ||
| 1213581 | 2011-06-30 09:51:00 | I'd guess firmware bug. Just a guess though :p :pf1mobmini: |
jareemon (5207) | ||
| 1213582 | 2011-06-30 09:54:00 | Possible. Just have to find out where the update is ! | Speedy Gonzales (78) | ||
| 1213583 | 2011-06-30 11:31:00 | One of the files containing the system's Registry data had to be recovered ----- Seen that part a few times, cant remember the complete rest apart from the fact it did say it had used a backup, and it was successful. Normally to do with some sort of reg corruption. Not any hardware/firmware upgrades. Generally though there are other problems as well. |
wainuitech (129) | ||
| 1213584 | 2011-06-30 11:35:00 | I'd try a system restore but you don't do them! | linw (53) | ||
| 1213585 | 2011-06-30 19:45:00 | That drive code is somewhat reminiscent of the self bricking Seagates from a couple of years ago. If it is that model it shouldn't have any bearing on the existing problem, coz there'd be no data visible at all. | Paul.Cov (425) | ||
| 1213586 | 2011-06-30 21:03:00 | A List of the drives affected by the 7200.11 firmware bug is Listed here (news.cnet.com). | wainuitech (129) | ||
| 1213587 | 2011-06-30 21:33:00 | Registry recovery is probably due to ungraceful shutdown and last known good config files would of been used...This would lead to believe there was a power cut, or the system didnt write completely to disk on last shutdown. I guess it could be a firmware bug or Memory or Disk error. |
SolMiester (139) | ||
| 1213588 | 2011-06-30 23:52:00 | I think something is borked. Went to use Javara (to remove old versions of Java) last night. It crashed with a 0x0000008E stop error. Which according to some sites, maybe caused by a damaged hdd. And after I rebooted I ran bluescreenview, and saw some strange filenames (one was called 2 that was it), and about 10 files with strange characters (mostly boxes) with nothing else (no date / or anything else) So, I may try another hdd. Told the person the PSU may need replacing too (a 350W). I also noticed the Nvidia videocard (256 mb) I think it is. Its got a fan but its dead (doesnt spin). Probably have to replace that too. Sooner or later. Uninstalled Itunes, (because it said it was missing registry entries - something to do with the burning / ripping I think). Then reinstalled it, it said the same thing. So, I gave up.. |
Speedy Gonzales (78) | ||
| 1213589 | 2011-07-01 04:30:00 | I reinstalled Windows 98 on a friend's PC once, and after installation I kept getting that error message and a truckload of problems. Turned out one of the memory sticks was faulty. |
Agent_24 (57) | ||
| 1 2 3 | |||||