| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 134573 | 2013-07-15 22:30:00 | BSOD | Renegade (16270) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1348950 | 2013-07-15 22:30:00 | I'm a bit stuck with this one. Toshiba laptop Win 7 Home Premium 32 bit. BSOD STOP 0x000000F4 (0x00000003, next lot seem to change with no google hits) Startup repair doesn't repair: Prob sig 5 Autofailover / prob sig 7 badpatch Last Known... blue screens Safe Mode blue screens Memtest clear HD Sentinel drive health 100% Chkdsk /f and /r didn't help Minidump folder nothing logged since 2012 MEMORY.DMP 15/07/2013 4:23:34 p.m. CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x888afd40 0x888afeac 0x83256eb0 ^ that seems to point to possible HD error, just about to try the Seagate tool, but not too hopeful on that picking up any problems. ... and that's a negative, mouse locks after clicking accept, and then the programs craps itself out to the command prompt. Factory recovery next? |
Renegade (16270) | ||
| 1348951 | 2013-07-15 23:03:00 | Get something like HDAT2 and verify the drive health in SMART. If you find any big errors that's a good clue the drive is screwed. Could be a virus. Try AVG bootable scan CD or something? |
Agent_24 (57) | ||
| 1348952 | 2013-07-16 06:07:00 | Looks like that stop error may mean its got bad sectors on it. Try removing it then put it in a desktop then scan it for errors | Speedy Gonzales (78) | ||
| 1348953 | 2013-07-16 09:11:00 | ^Will do. It's beginning to look like something weird with the drive. HDAT2 continually giving drive not ready messages, and the bootable AVG CD had disk error 04, ax = 4235, drive fe and wouldn't load. |
Renegade (16270) | ||
| 1348954 | 2013-07-16 10:10:00 | Take the drive out and try in another machine if you can, check for loose connections. Maybe even the SATA controller is buggered... | Agent_24 (57) | ||
| 1348955 | 2013-07-17 05:47:00 | Take the drive out and try in another machine if you can, check for loose connections. Maybe even the SATA controller is buggered... I'll go with buggered SATA controller, put another drive in and HDAT2 has the same errors. The drive worked fine in another PC, and no malware or bad sectors. |
Renegade (16270) | ||
| 1348956 | 2013-07-17 11:34:00 | It's not one of those Intel chipsets that had a known problem with the SATA controller failing? | Agent_24 (57) | ||
| 1 | |||||