Yep, tried that, NFG, system wouldn't boot at all. Deleted the resultant
baseokfrf32.dll file & back to the previous problem at least (attempted to
boot, got to the Windows "Kit" screen, then failure & reboot to BSOD with
previously mentioned error message). Used Bart PE to boot up, ran RegEdit &
looked for reference to baseokfrf32 but couldn't find it (was RegEdit
editing the Bart registry or . . .?) then tried using a text editor to edit
the registry files in %windir%\system32\config couldn't read 'em.
Wound up just doing a Repair Install of the OS, which fixed the issue, but a
pain in the ass since I now have to do all the updates again.
Surely there must be some way to resolve this issue easier next time? This
is the 3rd time I've seen the same exact thing infection by
winantiviruspro, (at least partial) removal by combofix/virtumonde fix/vundo
fix, then this damn reference to base?????32 in the boot sequence . . .
"David H. Lipman" wrote in message
news:ewfFvIoxIHA.524@TK2MSFTNGP05.phx.gbl...
> From: "John Doe"
>
> | Following up on my earlier BSOD "base?????32" issue, I have created a
> Bart
> | boot CD & am ready to roll up the sleeves & dig in where do I locate
> the
> | original XP installation's Registry files so I can remove/edit the
> offending
> | reference?
> |
>
> I suggest the following first...
> "Boot into the Windows Recovery Console and logon as the Administrator and
> then go to
> %windir%system32
>
> Copy basesrv.dll to baseokfrf32.dll
>
> Then reboot the PC. See if that will allow the PC to load properly."
>
> --
> Dave
> http://www.claymania.com/removal-trojan-adware.html
> Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp
>
>