Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When I start up my computer I get

BAXOS is compressed

Press Ctrl+Alt+Del to restart.

What is this error?

Here are the necessary specifications of my machine:

BIOS: American Megatrends
Motherboard: ASUS M2N68-AM PLUS
CPU: AMD Athlon x4 640
GPU: ATI Radeon 5670
share|improve this question
I can't find anything anywhere regarding "BAXOS" or "BAX OS" could you give some details on what OS you actually have and details regarding when it started giving you this error? Had you just installed some new software or operating system? – Mokubai Feb 11 '12 at 14:21
The exact same message, only with "NTLDR" or "BOOTMGR", can be displayed by the Windows boot sector. It's very strange that yours says "BAXOS", though. – grawity Feb 11 '12 at 16:34

This is not your firmware. This is the bootstrap program in the Volume Boot Record of an NTFS volume. It is trying to read the BOOTMGR file (or the NTLDR file), but is unable to. The VBR bootstrap program is not a full filesystem driver, and so isn't capable of handling things such as compressed NTFS files.

Normally, this isn't a problem, since Microsoft's tools try to avoid compressing the BOOTMGR and NTLDR files. It is however possible to end up in a situation where those files are compressed. (Hewlett Packard indicates that one could restore these files from backup onto an NTFS volume that one has chosen to enable compression on, for example.) You simply need to decompress the files, in this case. One can do this by bootstrapping another installation of Windows NT, or the Windows Recovery Environment, and either turning off compression for the volume that those files are on, or decompressing the specific files.

The string "BAXOS" should actually be "NTLDR". Sometimes it isn't, though, and all sorts of five-letter combinations have been reported. When it isn't, this indicates that the reason that the bootstrap loader program thinks that the file is compressed is not that it actually is compressed, but that something has gone and scribbled random nonsense all over the volume, mucking up the MFT entry for the file as well as things in the first sector. (Volume corruption isn't the sole explanation. There's a possible way for a badly written rootkit malware to end up placing the system in this state. I've not seen it discussed in public, however.) In this case, chkdsk of the volume is called for, as the first stop.

Further reading

share|improve this answer
up vote 1 down vote accepted

I had recently used a tool to compress everything on my C: drive.

I had read up that booting from the Windows 7 Install DVD (yes this OS I had), going to Repair Your Computer> Load Drivers, and right-clicking the C: drive in the explorer window, going to properties, unselecting "Compress this drive" fixed the issue.

It did for me too, so the problem is solved now.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .