| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 105970 | 2009-12-20 20:46:00 | Can't boot past isapnp.sys | nofam (9009) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 841514 | 2009-12-20 20:46:00 | Hi All, Removed w32.downadup plus a few other nasties from a PC (XP Pro) using trojan remover in safe mode, and now the PC in question won't boot past isapnp.sys in safe mode, and just freezes on a black screen if I boot normally. Any ideas? :thumbs: |
nofam (9009) | ||
| 841515 | 2009-12-20 20:51:00 | Try this (support.microsoft.com) | Speedy Gonzales (78) | ||
| 841516 | 2009-12-20 21:30:00 | Thanks Speedy - tried that, and it's replaced the file from the install CD, but I still get the same issue on boot. :illogical | nofam (9009) | ||
| 841517 | 2009-12-20 21:53:00 | Remove the hdd put it in a working system then do a full scan with an AV program | Speedy Gonzales (78) | ||
| 841518 | 2009-12-21 01:40:00 | Try booting from the XP CD, load up the recovery console, type in chkdsk /r See if it repairs the system files - Have a PC here was completely unbootable - even the drive wouldn't show, ran chkdsk and whalla, bootable drive. Other wise a repair install my also fix it. |
wainuitech (129) | ||
| 841519 | 2009-12-21 02:51:00 | Try booting from the XP CD, load up the recovery console, type in chkdsk /r See if it repairs the system files - Have a PC here was completely unbootable - even the drive wouldn't show, ran chkdsk and whalla, bootable drive. Other wise a repair install my also fix it. Yea-possible its a file system error. If that fails then a repair install would be the next option. KSODs are the worst to troubleshoot:x |
Blam (54) | ||
| 841520 | 2009-12-21 22:56:00 | I'm having the exact same issue. I did not notice any trojan/viruses on my computer. Yesterday it okay, today it goes blank screen and safemode haults at isapnp.sys My first speculation was there was a windows update that installed in the background that has caused it to be non-bootable. Seems like the timing of your incident and mine may not be a co-incidence? Let me know if you found a solution.. :stare: |
Sadbuttrue (15520) | ||
| 841521 | 2009-12-21 23:15:00 | Hi Sadbuttrue, I ended up doing a full rebuild; I found evidence of a Virut infection, which is pretty much the kiss of death for a Windows install, as it writes itself to every .exe on the system partition. Try booting into the recovery console and rename/replace isapnp.sys from the install CD as Speedy says in his post. The most practical option is to remove the drive and slave it to another clean system, and run a full scan with NOD32. Good luck!! |
nofam (9009) | ||
| 841522 | 2009-12-22 01:50:00 | I would do a repair install. Chances are, its infected more than just that system file... Do it after you do a full virus scan |
Blam (54) | ||
| 841523 | 2009-12-22 05:31:00 | If as nofam said its variant of the Virut infection - you will be a lot better off doing a complete reinstall of windows / programs the lot. That virus, if it gets in is basically impossible to remove, as it does affect every exe and scr file on your PC. As soon as you remove it, another takes its place, even on a repair install. |
wainuitech (129) | ||
| 1 2 | |||||