Chassis intrusion fatal error

chassis intrusion fatal error

Either the BIOS settings have become corrupted which means you have some strange settings or the settings have been reset to the default. It is. If the problem persists, then check the Chassis Intrusion Jumper on the Mother Board. A jumper must be placed between Pin-2 and Pin-1. Now, this. If you are in the same situation — getting chassis intrusion messages when you boot, or clock errors, or any other symptom that seems to occur.

Chassis intrusion fatal error - you

TPM chassis intruded error message from an AMI BIOS

The image above shows an error message that an American Megatrends (AMI) BIOS has brought up at system startup. Until the user fixes the problem, the computer won’t boot. The message is at the end and says: Intel CPU uCode loading error – CMOS Checksum Bad – Chassis intruded! – Fatal error… System halted.

What TPM chassis intruded message means

The error message means that a feature in the BIOS – the Trusted Platform Module (TPM) – is enabled in the BIOS.

If you want to know more about the technical details of TPM technology, visit the following webpage.

Trusted Platform Module (TPM) – https://en.wikipedia.org/wiki/Trusted_Platform_Module

When enabled, this module produces that fatal error message from the BIOS if the case has been opened without valid authorisation. The TPM technology is meant for use in a business that runs large numbers of computers to protect computer cases from being opened and components being stolen. Currently, TPM is provided by almost all desktop PC and laptop PC manufacturers, but it is usually not enabled in the BIOS by default.

That said, home computer users should not enable TPM because it adds complications of the kind that produced the error message shown in the image above for someone who was messing around in the BIOS and enabled it. That person then opened the case without valid authorisation to make changes to the components and doing so blocked him from booting his own computer.

Active TPM 2.0 module is a requirement for Windows 11

Unfortunately, one of the stipulations of being able to upgrade  from Win 10 to Windows 11 is that the motherboard has an active TPM 2.0 module.

Why Does Windows 11 Need TPM 2.0? –

https://www.howtogeek.com/738163/why-does-windows-11-need-tpm-2.0/

Will Windows 11 run on your current Win10 computer?

Reset the BIOS to fix a TPM chassis intruded fatal error

A thief breaking into your house is highly unlikely to open the case of your computer in order to steal its components. He will steal entire devices. Moreover, it is easy to reset the BIOS and that disables TPM that prevents the TPM chassis intruded fatal error message presenting itself at startup.

The BIOS has to be reset to get rid of the message because you cannot enter the BIOS until you remove the reason for its appearance. The BIOS is reset if its battery is removed for five minutes and then replaced or there may be a jumper on the motherboard that is placed over a particular set of two pins to keep or to reset the BIOS settings.

Showing a cluster of jumpers across pins on a motherboard

The instructions from the user manual for a Gigabyte B550 AORUS MASTER (2020) motherboard appear below. The locations of the BIOS battery and jumper pins are shown in the motherboard’s user manual that you can download from its manufacturer’s website in PDF form.

With this motherboard, the instructions are just to turn the computer off and then use a screwdriver to short the two pins instead of doing so by placing a jumper on the pins.

Instructions to reset the BIOS by removing its battery
Instructions on how to reset the BIOS by using a jumper on the motherboard

The user manuals of several recent motherboards do not provide information on the individual BIOS settings

In 2020, Gigabyte was still  providing comprehensive user manuals for its motherboards, including information on the individual BIOS settings. However, I have noticed that in 2020 MSI and Asus have reduced their user manuals, providing minimal information on the BIOS – no information on the settings and only information on how to flash upgrade it. The Gigabyte B550 Aorus Master is a high-end board, so maybe that is only the case for its lower-end boards, so before buying a motherboard, visit the page of a particular model and download its user manual from the manufacturer’s website.

Hello everyone. Last night I finished a computer build (I’ll list my components below in case that is relevant to fixing this problem), and initially I had no problem accessing the ASUS BIOS. However, after I accessed the ASUS BIOS I turned the computer off and restarted it, and that’s when I experienced two problems:

Problems #1: After restarting the computer, I was greeted with a “American Megatrends” screen, as pressing the F2 and Delete buttons to access the BIOS did not work during the restart process. Initially I didn’t realize what the problem was, but, after repeating the restart process a few times I noticed that I was receiving a “Chassis Intrusion Fatal Error” message.

Now I know the Chassis Intrusion Fatal Error issue is related to the motherboard chassis intrusion switch (or something in the BIOS), but, I don’t have anything (wires / inputs) connected to motherboard chassis, “intruder or ground” inputs. Now here is the thing, it’s quite possible I enabled the chassis intrusion feature in BIOS when I first accessed it (again, initially everything was working fine), although I don’t remember doing that, as that would have been in inadvertent accident on my part.

Ultimately, I’m fairly certain I have to disable this feature in BIOS, but, therein lies the problem; because I can’t access the BIOS to do that. So at this point I am at loss on what to do, and as embarrassed as I am to admit it I spent several hours trying to troubleshoot the trouble, without actually fixing the issue.

Problem #2: To add insult to injury, after I restarted the computer multiple times (approximately 3-5), the computer is no longer sending inputs to my monitor. My monitor is on, and appears to be in working order (I tested it on another computer), but, I keep getting a “no signal” message on my screen. I have tried to plug (HDMI) the monitor into the motherboard directly, in addition to the graphics card - to no avail.

I don’t think the Chassis Intrusion Fatal Error and monitor issue are related, but it’s certainly hampering any potential fixes because I can’t see what my computer is displaying.

If there is anyone who may know of a fix for either one of these problems, I would really appreciate it if you could take the time to tell me what that might be.

Thanks,
Ryan

ASUS BIOS Version: Revision 0224

Components:
Intel I9 9900K
ASUS ROG Strix Z390-E Gaming
32GB G Skill Trident 3600 (F4-3600C17D-16GTZR
ASUS ROG Strix Gaming Geforce RTX 2070 OC 8GB Graphics Card
Samsung SSD 860 EVO 1TB
Samsung SSD 970 Evo 500GB
Thermaltake 1200-Watt Power Supply
Thermaltake RGB fans (X’s 7)
Thermaltake Floe AIO 360 TT Premium Edition

 

coconut_craig said:

Its my own pc, not prebuilt, ASUS z590-E. Was previously changing around fan headers when this happened. Checked that all the cables are plugged in tight and that the case is completely closed. Even if I have the case open this doesnt happen normally, so I dont know whats going on. As far as I’m aware there are no places on my NZXT H710 where there are sensors to see if the case is open.

Click to expand...

Such sensors are not built in the case but on the motherboard. Look at MB manual. https://dlcdnets.asus.com/pub/ASUS/mb/LGA1200/ROG_STRIX_Z590-E_GAMING_WIFI/E17988_ROG_STRIX_Z590-E_GAMING_UM_V2_WEB.pdf
Page 1-19. Front panel header. last 2 connectors are marked
Chassis intrusion header (CHASSIS)
The 2-pin header allows you to connect the chassis-mounted intrusion detection
sensor or switch. The chassis intrusion sensor or switch sends a high-level signal
to the header when a chassis component is removed or replaced, the signal is then
generated as a chassis intrusion event.

 

Got an ASUS motherboard?  Are you having problems booting sometimes?  Do messages regarding ‘chassis intrusion’ get displayed on your screen, and stop the boot process, even though no-one has opened the case?  There might be a simple solution.

Chassis Intruded!Fatal Error... System Halted.

The first time I got the above message I was a bit surprised.  I’m the only one that uses my computer, there are no kids in the house, and the case hadn’t been opened for months.  Pressing the Reset button resulted in a clean boot, so I wasn’t worried.  Computers do strange things sometimes and reboots make most of the problems go away.

But, it happened again a few weeks later, and again, and again…  Ultimately, a pattern emerged:  Whenever the power was cut to the computer for an extended period of time, the intrusion message would come up.

Sometimes I power off my computer from the wall for a few hours when a thunderstorm is rolling through.  Sometimes the LEDs on my stupid Steelseries keyboard will stay on even after the system has shut down, so I terminate power using the switch on the Power Supply Unit (PSU).  Sometimes I turn off power at the PSU when cleaning coolers and fans, installing solid state drives, and otherwise maintaining or tweaking the system.  Sometimes I go camping and power down the whole house (except the fridge) from the fuse box.

Opening the case wasn’t causing the error.  Physically cutting off power to the system was.

newsun-cr2032-replacement-lithium-battery

The only hunch I had was that it might have something to do with the battery.

Every motherboard has a small clock in it that keeps track of the time.  When the computer is connected to an AC outlet on a wall, the clock is powered by that.  When the power is physically cut (by turning it off at the wall or on the back of the PSU) then the clock is powered by a small battery on the motherboard instead.  If the battery is nearing the end of its life, and there isn’t enough power to keep the clock running, the clock will drift or reset, and when your computer starts up you are greeted with an operating system message telling you that your clock may be incorrect.  I’ve seen that happen many, many times over the years.

Even though I wasn’t seeing any clock symptoms here, I reasoned that something like a chassis intrusion system would need to monitor at least something while the power was disconnected, and if the battery was weak there may not be enough power for that circuit to operate properly.  Enough power for the clock, yes, but not enough for intrusion detection.  (Or it could be some obscure but related value stored in CMOS that was being wiped.)

So, whilst driving past Bunnings one day I popped in and picked up a pack of four CR2032 3V Lithium batteries for about $6.  When I got home I popped the case open, replaced the old battery with a new one, and closed it back up.  Only took a few minutes.  That night I shut down and terminated power to the system completely using the switch on the PSU.  The power was completely cut for over eight hours overnight.

In the morning I reconnected the power and booted the machine — everything worked perfectly.  No error message.  Nor has there been an error message for the years since (even though I’ve had to cut power countless times for various reasons).

Problem.  Solved.  🙂

If you are in the same situation — getting chassis intrusion messages when you boot, or clock errors, or any other symptom that seems to occur after cutting power to your system — then spend a couple of bucks and replace your motherboard battery before trying anything else.  It could be the fastest and cheapest hardware fix you ever get to perform.

Happy booting!

PS:  My motherboard is an ASUS Maximus IV Extreme-Z and was purchased in 2011.  Lots of other ASUS motherboards have the chassis intrusion feature, so I suspect will behave the same way when the battery starts to die.  Also, motherboards from other vendors like MSI, ASRock and Biostar probably have a similar feature on at least some of their boards.  I don’t consider this problem/fix to be motherboard-specific, or even vendor-specific.

PPS:  Motherboard batteries should last at least 3 years in a typical system that spends the vast majority of its time plugged into an AC outlet.  They will discharge faster in systems that are physically disconnected from external power frequently and/or for extended periods of time (e.g. because you use one of those ‘energy saving’ powerboards that cut power off completely when you press a button on a remote, or you’re in the habit of turning off your system at the PSU because it’s the only way you can get all of those motherboard LEDs to turn off at night so you can get to sleep, or the system is put into storage due to changing circumstances).  I’ve had batteries last over 8 years in servers that are continuously powered and running.

PPPS:  I tested the old battery with a multimeter.  The voltage of the cell was 2.26V.  This is well below the 3.0V ‘normal’ level, and getting quite close to the 2.0V threshold at which the performance of a CR2032 cell falls off a cliff.  It would seem that 2.26V is still enough for the clock circuitry to function normally, but not enough for the intrusion detection circuitry.

Like this:

LikeLoading...

Believe in

 

Join Date: Jul 2010

City & State: Bucharest

My Country: Romania

Line Voltage: 230VAC 50Hz

I'm a: Professional Tech

Posts: 5,563

DefaultRe: [HOWTO] Fix/Repair "Chassis Intruded Fatal Error System Halted" on Asus P5QL

Quote:

Originally Posted by shadowView Post

I assume the Chassis Intrusion 'feature' will not work anymore with the transistor gone. And I also assume that the real cause of the issue will be either that transistor which you desoldered or some part of the circuitry downstream of that.

Yes, it does not work anymore, but who cares about that again? A feature that was useless to begin with. At least the way Asus implemented it. I promised i'll get into more detail so here goes:

First of all, there is no other circuitry downstream. The gate of that transistor goes straight into pin 3 of the chassis intrusion connector and that's it. And the drain connects directly to pin 104 of the super IO controller, which would be the 3rd pin counting from the right side, where you see 102 printed.

And that transistor was just doing its job. It was fine, i checked. The way it was implemented was the problem.

Now with that settled, let's see just how many wrongs in a row could Asus get...
  1. On most other boards that support a chassis intrusion sensor (switch), there is an option in the BIOS to change the chassis intrusion sensor so that it merely reports that your case has been opened, rather than preventing you to boot up the damn computer. There is no such option with ASUS boards. The mere inclusion of this feature would have prevented all this trouble.

  2. The Super IO controller works with ridiculously low pull-up currents on those pins, i measured 3.3uA (microamps). Merely measuring with your multimeter, or even just TOUCHING them WILL pull the pins down, and make them report false information!

  3. The transistor doing the pull-down when the chassis intrusion switch is OPEN (or the jumper removed for whatever reason), is a MOSFET that conducts at very low gate voltages, and has no gate-source resistor. At 1.5v the transistor already conducts and pulls the pin down on the super IO. You can charge it up to that 1.5v by merely touching the pins of the connector.

  4. Given the very low currents the pins on the super IO controller, just the drain-to-source leakage current as that MOSFET gets old, or simply dust and dirt accumulating on the board, can create enough leakage current to make the IO pin appear as "low" and generate a chassis intrusion message which you can then never get rid of.

    And the icing on the cake...
  5. The chassis intrusion detection is a flag in NVRAM, and it can get set even if power is removed from the board. As long as the CMOS battery is there, the chassis intrusion "feature" will work. Or shall i say, prevent YOU from working?

Asus deserves a big and for this one.

Extra bit of fun info: The transistor right next to it will make the board report "New CPU installed!" every time until you clear CMOS, if you touch it or probe it. But at least it lets you boot the system.

Quote:

Originally Posted by kc8aduView Post

and nobody i know uses the feature anyway.good fix.

Thanks.


Last edited by Th3_uN1Qu3; 10-29-2013 at 04:54 PM..

Chassis intrusion fatal error - really. agree

chassis intruded fatal error system halted

Here we can see “chassis intruded fatal error system halted”

Facing Asus Motherboard Chassis Intruded Fatal Error?-Get Easy Solutions directly 

Despite its premium and convenient features, the Asus devices also tend to manifest specific technical errors. For example, almost like all technical devices, the Asus motherboard suffers from various quiet issues. One of the probable errors that arise is that the Asus motherboard chassis intruded on fatal errors. This chassis intrusion error may be a very frustrating problem, and it signifies specific problems within the BIOS setup. Also, it’d appear thanks to the hardware problem.

Hence, undergo the remaining article to understand the steps to resolve this issue from your Asus device. Then, head over to the successive section, which discusses the steps to repair it comprehensively.

Probable Causes of Asus Motherboard Chassis Intruded Fatal Error:

To overcome this error, you’ve got to understand the most reason behind it. Once you encounter this error message that says, ‘Chassis Intruded, Fatal Error … System Halted” on the monitor, you fail to use your Asus device further. Sometimes, you are doing not understand the precise reason behind this sort of error. Here, we declare multiple reasons thanks to which chassis intruded fatal error system halted occurs. Check the points below to know:

  • Invalid BIOS setup
  • Hardware issue
  • Outdated version of BIOS
  • Motherboard issue
  • Physical damage of the Motherboard

Quick Hacks to Resolve Chassis Intruded Fatal Error:

There are many solutions which will assist you bent resolve this trouble. Moreover, it helps to avoid all the possible motherboard problems efficiently. Take a glance at below.

Solution 1: Reset the CMOS

Since the matter tends to the CMOS, you would like to reset the CMOS. First, check whether all the items within the Motherboard are adequately seated or not. Then, unplug the sockets and take away the motherboard battery. Now, again plug the CMOS battery from the socket. At last, check if the chassis intruded fatal error still occurs or not.

Solution 2: BIOS Setup

To overcome this error, you’ll also verify the time and date of BIOS. Therefore, you’ll start the troubleshooting method from the BIOS. Undergo the steps one-by-one to try to do so:

  1. At first, pack up your computer and continuously press the F8 button.
  2. Then, from the BIOS option, attend the BIOS setup option with the assistance of the arrow keys.
  3. Now, hit the Enter key.

Solution 3: Disable the Chassis Intrusion

After completing the BIOS setup procedure, you would like to show off Chassis instructions to repair this issue. to try to do that, follow the rules instructed below:

  1. Firstly, press the F2 button on the keyboard to open the BIOS setup menu.
  2. Move down the cursor with the down Arrow key and click on the ‘System Security’ option.
  3. Hit the Enter key.
  4. When the System Security menu appears, click on the ‘Chassis Intrusion’ option.
  5. Now, hit the Enter button and choose the ‘Disabled’ option.
  6. Lastly, click on ‘Save’ to save lots of all the changes.
  7. Check if the difficulty remains fixed or not. If not, attend subsequent procedure.

Solution 4: Update the BIOS

BIOS is that the Basic Input Output System. BIOS identify and troubleshoot all the hardware issues of your device. But, if the BIOS isn’t updated, it causes the Asus motherboard chassis to be an intruded fatal error. To resolve this, you’ve got to vary the settings or update the BIOS. It’s easy to update the BIOS, but you’ve got to take care once you have updated this. Because if you commit any mistake or a mistake occurs, you’ll lose your valuable data. So, we have a suggestion that always backup your data first, then update it. Then, there’ll be no fear of losing critical data.

To update the BIOS, you’ve got to travel through the following steps:

  1. First, attend the Technical support website of Asus and search the Device name which you employ.
  2. Now, you’ll find the ‘Drivers and Softwares’ option by clicking thereon. Click on this to expand. After expanding this, you’ll see BIOS/UEFI.
  3. Tap the eyes-shaped key to look at the new update of the BIOS for the OS.
  4. Now, launch the newest version of the BIOS.
  5. After that, go to the .exe file and follow all the instructions to update the BIOS.
  6. Restart your laptop to see if the error message is resolved or not.

Solution 5: Clear the CMOS

Before starting this hack, cut the pc and unplug the facility cable. Next, perform the subsequent steps to clear the CMOS.

  1. First, open the pc and allocate the battery area on the Asus motherboard.
  2. Then, disconnect the battery from the most board.
  3. Now, short-circuit the positive and negative end portion of the battery holder for 1 minute. 
  4. After that, re-install the battery.
  5. Now, reconnect your device to the facility cable and turn on your computer. Then, enter the BIOS and put the right time and date. Now, the method is entirely completed.
  6. Check if the difficulty persists or not.

Solution 6:- Reset the Motherboard

The internal software of the Motherboard might cause this error code. There are three different paths to reset the Motherboard if you do not reach the BIOS. First, disconnect the CMOS battery of the Motherboard. Then, put on a jumper and wait a while. Then, do a deep reset with a jumper and disconnect the CMOS battery. Finally, take a glance at the detailed steps:

This is a simple hack. At first, pull the coin-sized battery and await a short time. This helps to reset the Motherboard to factory settings.

Before applying this process, you’ve got to get rid of the facility supply. Next, add a jumper to the two-pin connector with the Motherboard. Then, attach the jumper with the two pins and keep it for ten minutes.

Summing it Up

We hope this complete article contains the small print of the matter, and reading this may be pretty beneficial for you. So, troubleshoot it and resume the sooner seamless flow of operation on your system. Discard the annoying Asus motherboard chassis intruded fatal error successfully with this comprehensive guide. If you encounter any difficulties while applying the fixes or trouble understanding them, leave your feedback within the comment section below.

User Questions:

1. CHASSIS INTRUDED FATAL ERROR… SYSTEM HALTED

My PC show a mistake in startup “chassis intruded fatal error system halted”

would you please solve this error why this message is shown in the startup

My MotherBoard is ASUS P5P800-MX

2. “chassis intruded fatal error system halted”

I have some issues. Once I activate my PC, I buy this message: “chassis intruded fatal error system halted.”

My Motherboard is a: P8Z68-VPRO

Now I even have contacted the guy I bought the PC from, and he says to me its a jumper or something that went wrong. ( I even have never done any changes to my Bios or anything changed any parts in my PC)

Can anyone explain to me what a jumper is?

http://imgur.com/hznfe7Q

3. Chassis intruded! Fatal error, system halted

Chassis intruded! Fatal error, system halted from techsupport

4. “Chassis Intruded Fatal Error System Halted” and sometimes nothing shows abreast of the monitor

"Chassis Intruded Fatal Error System Halted" and sometimes nothing shows up on the monitor from techsupport

5. “Chassis Intruded! Fatal Error. System halted” on the fresh mobo! Help, please, you guys rock!

It’s worked maybe a complete of 5 days since that point. The first time I EVER booted it up (back in Feb), mobo said, “Chassis Intruded! Fatal Error. System halted.”

Back then (in Feb), I just restarted it a couple of times, and it soon began working. Then it started hanging about three days after (when I say hang, I mean total PC crash, mostly during games, video rendering, or Prime95).

RMA’d the memory. No help. RMA’d the PSU. No help. RMA’d the CPU. No help. The hanging still happened, but now it had been even worse: it’d also give me POST error beeps: 2 beeps, then an interruption, then five beeps. I could skip the beeping and obtain it else correctly by hitting the push button during the beeping. But, on the other hand, it’d still persevere games. Asus said the beeping code meant that the mobo was touching the case somewhere. But I knew it wasn’t, so I sent the mobo back. They “fixed” it and sent it back to me. Same problems.

Peter Johnson

Peter has been an ItechBrand reporter since July 2019. He previously covered tech Brand news in the United States from 2015 to 2017, before moving to San Francisco to write about cybersecurity. as well as over a decade of professional writing experience. He enjoys copious amounts of tea, board games, and football.

coconut_craig said:

Its my own pc, not prebuilt, ASUS z590-E. Was previously changing around fan headers when this happened. Checked that all the cables are plugged in tight and that the case is completely closed. Even if I have the case open this doesnt happen normally, so I dont know whats going on. As far as I’m aware there are no places on my NZXT H710 where there are sensors to see if the case is open.

Click to expand...

Such sensors are not built in the case but on the motherboard. Look at MB manual. https://dlcdnets.asus.com/pub/ASUS/mb/LGA1200/ROG_STRIX_Z590-E_GAMING_WIFI/E17988_ROG_STRIX_Z590-E_GAMING_UM_V2_WEB.pdf
Page 1-19. Front panel header. last 2 connectors are marked
Chassis intrusion header (CHASSIS)
The 2-pin header allows you to connect the chassis-mounted intrusion detection
sensor or switch. The chassis intrusion sensor or switch sends a high-level signal
to the header when a chassis component is removed or replaced, the signal is then
generated as a chassis intrusion event.

 

Hello everyone. Last night I finished a computer build (I’ll list my components below in case that is relevant to fixing this problem), and initially I had no problem accessing the ASUS BIOS. However, after I accessed the ASUS BIOS I turned the computer off and restarted it, and that’s when I experienced two problems:

Problems #1: After restarting the computer, I was greeted with a “American Megatrends” screen, as pressing the F2 and Delete buttons to access the BIOS did not work during the restart process. Initially I didn’t realize what the problem was, but, after repeating the restart process a few times I noticed that I was receiving a “Chassis Intrusion Fatal Error” message.

Now I know the Chassis Intrusion Fatal Error issue is related to the motherboard chassis intrusion switch (or something in the BIOS), but, I don’t have anything (wires / inputs) connected to motherboard chassis, “intruder or ground” inputs. Now here is the thing, it’s quite possible I enabled the chassis intrusion feature in BIOS when I first accessed it (again, initially everything was working fine), although I don’t remember doing that, as that would have been in inadvertent accident on my part.

Ultimately, I’m fairly certain I have to disable this feature in BIOS, but, therein lies the problem; because I can’t access the BIOS to do that. So at this point I am at loss on what to do, and as embarrassed as I am to admit it I spent several hours trying to troubleshoot the trouble, without actually fixing the issue.

Problem #2: To add insult to injury, after I restarted the computer multiple times (approximately 3-5), the computer is no longer sending inputs to my monitor. My monitor is on, and appears to be in working order (I tested it on another computer), but, I keep getting a “no signal” message on my screen. I have tried to plug (HDMI) the monitor into the motherboard directly, in addition to the graphics card - to no avail.

I don’t think the Chassis Intrusion Fatal Error and monitor issue are related, but it’s certainly hampering any potential fixes because I can’t see what my computer is displaying.

If there is anyone who may know of a fix for either one of these problems, I would really appreciate it if you could take the time to tell me what that might be.

Thanks,
Ryan

ASUS BIOS Version: Revision 0224

Components:
Intel I9 9900K
ASUS ROG Strix Z390-E Gaming
32GB G Skill Trident 3600 (F4-3600C17D-16GTZR
ASUS ROG Strix Gaming Geforce RTX 2070 OC 8GB Graphics Card
Samsung SSD 860 EVO 1TB
Samsung SSD 970 Evo 500GB
Thermaltake 1200-Watt Power Supply
Thermaltake RGB fans (X’s 7)
Thermaltake Floe AIO 360 TT Premium Edition

 

Believe in

 

Join Date: Jul 2010

City & State: Bucharest

My Country: Romania

Line Voltage: 230VAC 50Hz

I'm a: Professional Tech

Posts: 5,563

DefaultRe: [HOWTO] Fix/Repair "Chassis Intruded Fatal Error System Halted" on Asus P5QL

Quote:

Originally Posted by shadowView Post

I assume the Chassis Intrusion 'feature' will not work anymore with the transistor gone. And I also assume that the real cause of the issue will be either that transistor which you desoldered or some part of the circuitry downstream of that.

Yes, it does not work anymore, but who cares about that again? A feature that was useless to begin with. At least the way Asus implemented it. I promised i'll get into more detail so here goes:

First of all, there is no other circuitry downstream. The gate of that transistor goes straight into pin 3 of the chassis intrusion connector and that's it. And the drain connects directly to pin 104 of the super IO controller, which would be the 3rd pin counting from the right side, where you see 102 printed.

And that transistor was just doing its job. It was fine, i checked. The way it was implemented was the problem.

Now with that settled, let's see just how many wrongs in a row could Asus get...
  1. On most other boards that support a chassis intrusion sensor (switch), there is an option in the BIOS to change the chassis intrusion sensor so that it merely reports that your case has been opened, rather than preventing you to boot up the damn computer. There is no such option with ASUS boards. The mere inclusion of this feature would have prevented all this trouble.

  2. The Super IO controller works with ridiculously low pull-up currents on those pins, i measured 3.3uA (microamps). Merely measuring with your multimeter, or even just TOUCHING them WILL pull the pins down, and make them report false information!

  3. The transistor doing the pull-down when the chassis intrusion switch is OPEN (or the jumper removed for whatever reason), is a MOSFET that conducts at very low gate voltages, and has no gate-source resistor. At 1.5v the transistor already conducts and pulls the pin down on the super IO. You can charge it up to that 1.5v by merely touching the pins of the connector.

  4. Given the very low currents the pins on the super IO controller, just the drain-to-source leakage current as that MOSFET gets old, or simply dust and dirt accumulating on the board, can create enough leakage current to make the IO pin appear as "low" and generate a chassis intrusion message which you can then never get rid of.

    And the icing on the cake...
  5. The chassis intrusion detection is a flag in NVRAM, and it can get set even if power is removed from the board. As long as the CMOS battery is there, the chassis intrusion "feature" will work. Or shall i say, prevent YOU from working?

Asus deserves a big and for this one.

Extra bit of fun info: The transistor right next to it will make the board report "New CPU installed!" every time until you clear CMOS, if you touch it or probe it. But at least it lets you boot the system.

Quote:

Originally Posted by kc8aduView Post

and nobody i know uses the feature anyway.good fix.

Thanks.


Last edited by Th3_uN1Qu3; 10-29-2013 at 04:54 PM..

Got an ASUS motherboard?  Are you having problems booting sometimes?  Do messages regarding ‘chassis intrusion’ get displayed on your screen, and stop the boot process, even though no-one has opened the case?  There might be a simple solution.

Chassis Intruded!Fatal Error... System Halted.

The first time I got the above message I was a bit surprised.  I’m the only one that uses my computer, there are no kids in the house, and the case hadn’t been opened for months.  Pressing the Reset button resulted in a clean boot, so I wasn’t worried.  Computers do strange things sometimes and reboots make most of the problems go away.

But, it happened again a few weeks later, and again, and again…  Ultimately, a pattern emerged:  Whenever the power was cut to the computer for an extended period of time, the intrusion message would come up.

Sometimes I power off my computer from the wall for a few hours when a thunderstorm is rolling through.  Sometimes the LEDs on my stupid Steelseries keyboard will stay on even after the system has shut down, so I terminate power using the switch on the Power Supply Unit (PSU).  Sometimes I turn off power at the PSU when cleaning coolers and fans, installing solid state drives, and otherwise maintaining or tweaking the system.  Sometimes I go camping and power down the whole house (except the fridge) from the fuse box.

Opening the case wasn’t causing the error.  Physically cutting off power to the system was.

newsun-cr2032-replacement-lithium-battery

The only hunch I had was that it might have something to do with the battery.

Every motherboard has a small clock in it that keeps track of the time.  When the computer is connected to an AC outlet on a wall, the clock is powered by that.  When the power is physically cut (by turning it off at the wall or on the back of the PSU) then the clock is powered by a small battery on the motherboard instead.  If the battery is nearing the end of its life, and there isn’t enough power to keep the clock running, the clock will drift or reset, and when your computer starts up you are greeted with an operating system message telling you that your clock may be incorrect.  I’ve seen that happen many, many times over the years.

Even though I wasn’t seeing any clock symptoms here, I reasoned that something like a chassis intrusion system would need to monitor at least something while the power was disconnected, and if the battery was weak there may not be enough power for that circuit to operate properly.  Enough power for the clock, yes, but not enough for intrusion detection.  (Or it could be some obscure but related value stored in CMOS that was being wiped.)

So, whilst driving past Bunnings one day I popped in and picked up a pack of four CR2032 3V Lithium batteries for about $6.  When I got home I popped the case open, replaced the old battery with a new one, and closed it back up.  Only took a few minutes.  That night I shut down and terminated power to the system completely using the switch on the PSU.  The power was completely cut for over eight hours overnight.

In the morning I reconnected the power and booted the machine — everything worked perfectly.  No error message.  Nor has there been an error message for the years since (even though I’ve had to cut power countless times for various reasons).

Problem.  Solved.  🙂

If you are in the same situation — getting chassis intrusion messages when you boot, or clock errors, or any other symptom that seems to occur after cutting power to your system — then spend a couple of bucks and replace your motherboard battery before trying anything else.  It could be the fastest and cheapest hardware fix you ever get to perform.

Happy booting!

PS:  My motherboard is an ASUS Maximus IV Extreme-Z and was purchased in 2011.  Lots of other ASUS motherboards have the chassis intrusion feature, so I suspect will behave the same way when the battery starts to die.  Also, motherboards from other vendors like MSI, ASRock and Biostar probably have a similar feature on at least some of their boards.  I don’t consider this problem/fix to be motherboard-specific, or even vendor-specific.

PPS:  Motherboard batteries should last at least 3 years in a typical system that spends the vast majority of its time plugged into an AC outlet.  They will discharge faster in systems that are physically disconnected from external power frequently and/or for extended periods of time (e.g. because you use one of those ‘energy saving’ powerboards that cut power off completely when you press a button on a remote, or you’re in the habit of turning off your system at the PSU because it’s the only way you can get all of those motherboard LEDs to turn off at night so you can get to sleep, or the system is put into storage due to changing circumstances).  I’ve had batteries last over 8 years in servers that are continuously powered and running.

PPPS:  I tested the old battery with a multimeter.  The voltage of the cell was 2.26V.  This is well below the 3.0V ‘normal’ level, and getting quite close to the 2.0V threshold at which the performance of a CR2032 cell falls off a cliff.  It would seem that 2.26V is still enough for the clock circuitry to function normally, but not enough for the intrusion detection circuitry.

Like this:

LikeLoading...

Thematic video

FIX Chassis intrude error

0 Comments

Leave a Comment