kronoSX
Honorary Master
anty you think it could be a driver issue?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
anty you think it could be a driver issue?
Its sounds to me like its more than likely blown, if it does not read it at bios startup.
Only SATA Drives are "hot swappable" so if it was and IDE Drive and he unplugged while it was on then i dont think there is much hope?
Its sounds to me like its more than likely blown, if it does not read it at bios startup.
Only SATA Drives are "hot swappable" so if it was and IDE Drive and he unplugged while it was on then i dont think there is much hope?
(0x000000011, Parameter2, Parameter3, Parameter4):
The system could not enter ACPI mode. There are many reasons for this, including:
It could not initialize the AML interpreter.
It could not find the Root System Description table.
It could not allocate a critical driver.
It could not load the Root System Description table.
The system could not load device descriptor blocks.
The system could not connect an interrupt vector.
The SCI_EN (system control interrupt enable request) cannot be set (see 0x00000001 earlier in this article).
The ACPI Table checksum is incorrect.
ACPI consists of a hierarchical arrangement of tables, each one building upon the next to define the complete capabilities of the system and every device in it. It starts by looking for the Root System Description table, which points to the next table, which points to the next and so on. This error occurs for the most part because these tables are bad or missing.
Free, portable system utility BlueScreenView displays your last Blue Screen of Death, so you can more easily see the error message—while you use Google to figure out the problem.
If you've been a Windows user for a while, you've likely been the recipient of a BSOD at some point, but there's no way to easily take a screenshot of the screen—you have to either whip out a digital camera, or try and frantically scribble the error down on some paper. BlueScreenView parses the minidump files generated during a blue screen, and then displays the same error just as you saw it before—and all you have to do is launch the no-installation-required application to do so.