Bios Issue after boot virus

Acer / Aspire as3216a
April 25, 2011 at 00:30:53
Specs: Windows XP home, 4 GB
I Have a Acer Aspire intel Dual core (motherboard Type N1996-002185CEOC6E)with a BIOS problem.
I had a boot sector virus on the HD, with partitioned Magic I zero-ed the complete HD to be sure the virus was gone. By trying to reinstall windows XP, a question was asked boot on virus <Yes/No> so logically I say NO ..
But the Virus was still on there.
So I cleared the BIOS with the jumper next to the battery.
And now my BIOS is gone, PC doesn't boot anymore ???

Can I still do something or ... new motherboard ?


See More: Bios Issue after boot virus

Report •


#1
April 25, 2011 at 01:41:53
Are u sure the cmos jumper is in correct place?

We can not fight new wars with old weapons, let he who desires peace prepare for war - PROPHET.


Report •

#2
April 25, 2011 at 02:05:01
yes ... The strange thing is that some times the hard drive or CDrom spins up, the HD is recognized in the BIOS, and sometimes it just doesn't even starts the BIOS cycle ??

Sorry MB type M1641 Aspire Acer.

The problem started with a Boot virus. --> blue screen error code 0x0000007B (0xF78D2524)
First time I encountered this type of Virus.
Destroys the Boot sector of the HD, so formatting / partitioning no use. It comes back
Then resetting the BIOS (but if I got it right it's just the config settings that will be resetted)
Tried to reinstall Windows XP ... virus is back --> blue screen again
Tried to install UBUNTU --> same problem blue screen
Booting from CD (Partinioned Magic)--> works
Formatting and ZERO-ing the complete disk
install windows again --> Blue screen ??!!

restet the BIOS, switch jumper, boot + wait 10 sec
Take out battery , boot + wait 10 sec

And now the system is not really stable no more.
Some times it boots, then nothing ...

Can I do a Flash update into the BOOT ?
Or is there a way to flush all what is programmable ?


Report •

#3
April 25, 2011 at 10:46:26
I'd run memtest.

1/3 of highway deaths are caused by drunks. The rest are by people who can't drive any better than a drunk.


Report •

Related Solutions

#4
April 25, 2011 at 11:48:57
"blue screen error code 0x0000007B"

STOP: 0x0000007B (parameter1, parameter2, parameter3, parameter4)
INACCESSIBLE_BOOT_DEVICE

There are MANY different things that can cause that error.

A boot Sector virus is one of the LEAST likely things that would have caused your error.

Boot Sector viruses are NOT common theses days - I have NOT encountered one for many years - if you were using any anti-malware software at all that has a resident module - a part that runs in the background all the time looking for suspicious activity - then it's extremely unlikely you have a boot sector virus, because the anti-malware software would have probably found it before it could do any damage .

The 0x0000007B error is generated by Windows, NOT the bios.

The fact that you were getting that error indicates your computer itself booted fine, the bios was working fine, the bios found the hard drive has a bootable partition, but when the Windows operating system attempted to load from the hard drive it encountered something that caused the 0x0000007B error.

There is lots of info on the web about troubleshooting the 0x0000007B error.

E.g. Here's a good third party one...

STOP 0x0000007B Error Resolution
Steps to Resolve the STOP 0x0000007B Blue Screen Error
http://pcsupport.about.com/od/findb...

Two things that I have found that often get rid of this error

- See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:
http://www.computing.net/hardware/w...


(Too late for you do this now since you zero filled the drive)
- run CHKDSK /R C: in the Recovery Console

For more info,
see response 11 in this:
http://www.computing.net/answers/wi...


starting at, scroll down to "If that won't work....."
..........

"I Have a Acer Aspire intel Dual core (motherboard Type N1996-002185CEOC6E)"

That may all be useless info.
N1996 merely indicates the mboard meets the N1996 standard - that has nothing to do with the mboards's model number.
-002185CEOC6E may also be useless.


"with partitioned Magic I zero-ed the complete HD to be sure the virus was gone. "

If you zero filled the entire hard drive, then there CANNOT be any malware on the hard drive .

"By trying to reinstall windows XP, a question was asked boot on virus <Yes/No> so logically I say NO .."

Clear as mud. That's useless info, unless you can quote the exact message you got.

You don't normally get any such message while installing XP from an XP CD.

"But the Virus was still on there."

If you still got the STOP 0x0000007B while trying to install XP from the CD on a hard drive that has been zero filled, then that error CANNOT be caused by any data on the hard drive because it doesn't have any significant data on it yet - that has to be caused by a hardware problem.

"So I cleared the BIOS with the jumper next to the battery.
And now my BIOS is gone, PC doesn't boot anymore ???"

Did you move the Clear Cmos jumper back to it's "normal" position after you did that ? If you didn't the computer may not boot.

Assuming you moved the Clear Cmos jumper back to it's "normal" position after you did that, clearing the Cmos DOES NOT cause the mboard itself to not boot.

You WILL get a "CMOS CHECKSUM ERROR" or similar message after you have cleared the Cmos, because all Cmos settings in the bios have been set to defaults including the current Date and Time - you must go into the bios and set at least the current Date and Time, Save bios settings, then you won't get that message again while booting

You get the same message when you remove the mboard battery then install it again

NOTE that is NOT the same thing as booting - loading - the operating system from the hard drive. Your hard drive will NOT be found to be bootable by the bios until you have installed XP on it again.


"The strange thing is that some times the hard drive or CDrom spins up, the HD is recognized in the BIOS, and sometimes it just doesn't even starts the BIOS cycle ??"

See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:
http://www.computing.net/hardware/w...

Your no boot at all problem can also be caused by a failing power supply if it's a desktop computer.

Failing power supplies are common and can cause your symptoms.
Check your PS.
They often partially work, fans and hard drives may spin, leds may come on, yet you may get no video and the mboard will not boot all the way.
See response 4 in this:
http://www.computing.net/hardware/w...

If you can borrow a power supply from another working computer, try connecting that.

If it is failing, you can usually replace it with any decent quality standard sized standard ATX PS with the same capacity or greater.

Standard (PS/2) power supply size - 86mm high, 150mm wide, 140mm deep, or 3 3/8" h x 5 7/8" w x 5 1/2" d , or very close to that, though the depth can be more or less for some PSs.


Report •

#5
April 25, 2011 at 12:22:44
Thanx Tubesanwire.

I know it's very strange. First time in my life I can not get this damn PC back working ??? ALso first time i'm posting for help :) I have some more info , but I will follow your directions tomorrow , I might have forgotten something or .. I don't know

BIOS seems OK ...
Has nothing to do with XP, 'cos Ubuntu same problem (blue screen, with the same error code return)

Partion Magic (RAM uploaded OS BSD look alike I think) Works without the blue screen crash. Maybe because it's is uploaded into the RAM. Not HD or Secondary PCI BUS.

CHKDSK was the first thing I did from another PC under UBUNTU
Checked = no change
Erased the boot sector
Erased the partitions
Then Zero-ed the Disk
Changed memory

Installed XP again , no change
UBUNTU no change
But very strange with an HD with Windows installed on it from another PC it works .. NO blue screen ??? !!!
I don't get it ...

If it's not on the HD, Hard ware works fine (tested all components on other PC's)

BIOS has been refreshed. Where does this problem comes from.(Oh yes... before the PC was working fine... until my mom surfed for 10 min the net :) )

So the only place I see there could be some issues is some where in the Stack ware(Firmware)

I've been working on a project for a bank on StuxNet, a walware that uses PC OS to get into the PLC hardware memory allocations ??? Pretty evolved stuff, could this type problem or virus do the same ... change Stack ware ??

Anyway ... Tomorrow will follow your instructions (thanx for that man) and hope I missed something ....


Report •

#6
April 25, 2011 at 15:14:17
Side notes - this is probably your mboard:

Acer Aspire M1640 M1641 Motherboard N1996 MBSAK09007
http://cgi.ebay.com/ws/eBayISAPI.dl...

ACER MCP73 MBSAK09007 desktop motherboards
http://www.aliexpress.com/product-g...

ACER MCP73 MBSAK09007 desktop motherboards
http://www.aliexpress.com/store/301...

It has many labels on it - it's probable model is MBSAK09007 - that should be on one of the labels, or possibly printed on the mboard.

The MBSAK09007 is also used in some Gateway models, probably has a Gateway bios version rather than an Acer one

The Acer Group of companies includes Acer, Gateway, and eMachines computers.
.......

There are many things you could have tried to fix this error BEFORE you zero filled the drive with Partition Magic that you can't do now because you did that.

NOTE that some programs DO NOT zero fill the entire drive - they just zero fill the data in the partition table.The zero filling should take a LONG TIME if it is zero filling the entire drive - at least as long as it takes / took to FULL format all the partitions on the drive. If that took only a short time, it did NOT zero fill the entire drive.
..........

I have searched regarding this same error before many times, and as far as I have seen, it's a Windows ONLY error.
You either get it with an existing Windows installation, or you get it while you're trying to install Windows (2000 and up).

Causes I haven't mentioned yet.

With SOME main chipsets on the mboard, if the hard drive is SATA, and if the bios Setup has the SATA controllers set to SATA or AHCI mode, you MAY get the 0x0000007B error while trying to install Windows from the CD.

(With MOST main chipsets on the mboard, if the hard drive is SATA, and if the bios Setup has the SATA controllers set to SATA or AHCI mode, 2000's and XP's Setup simply doesn't find any SATA drives, because the CD has no SATA controller drivers built into it.)

If you change the bios setting so that the SATA controller mode is set to an IDE compatible mode, Save settings, then the files loaded by the 2000 or XP CD WILL detect SATA drives, as IDE compatible drives, and Setup will install Windows fine.

I / we usually cannot find details of what you see in a brand name system bios version, but whatever it is, it's presently set to SATA or AHCI, it's changable, and at least one other choice is an IDE compatible mode of some sort, Save bios settings.

After Setup has finished and you have loaded the main chipset drivers for the mboard and other drivers you need for the system that were not built into Windows including the SATA controller drivers, then you can go into the bios Setup and set the SATA controllers SATA or AHCI mode, Save bios settings, if you wish to.
.....

It's possible you zero filling the drive did not erase the MBR - Master Boot Record - which has the Boot Sector in it. If the MBR or the Boot Sector is corrupted, you may still the 0x0000007B error even when you DO change the SATA controller mode to an IDE compatible mode in the bios Setup.
Re-writing the MBR should fix that problem.
That can be done with SOME hard drive manufacturer's diagnostics or drive prepartion utiliies.
What is the brand of the hard drive ?
......

If you install UBUNTU (or another flavor of Linux) on the system before you install XP, you MAY get the 0x0000007B error when you try to install XP.
You MAY get the error even when you DO change the SATA controller mode to an IDE compatible mode in the bios Setup.

The Ultimate Boot Cd for Windows (UBCD4Win) has something called “Fix_hdc” that will probably fix the drivers issue.

Ultimate Boot Cd for Windows
http://www.ubcd4win.com/

More info.

Fix_hdc vs. Fix_IDE
http://ubcd4win.com/forum/index.php...

Fix_hdc is newer
.....

http://forum.driverpacks.net/viewto...

Excerpt:

The next operation is to run the plugin FIX_hdc.
Select Start->Programs->Registry Tools->FIX_hdc->fix hard disk controller.
Select <M> Update MassStorage drivers.
Hit any key to continue and reboot into Window 2000.
(Similar applies to XP)


Report •


Ask Question