# Computer help - ASPI blue screen, hard drive

**URL:** https://boards.straightdope.com/t/computer-help-aspi-blue-screen-hard-drive/445992
**Category:** Factual Questions
**Created:** [April 19, 2008, 11:44am UTC](https://boards.straightdope.com/t/computer-help-aspi-blue-screen-hard-drive/445992 "2008-04-19T11:44:13Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Athena](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@Athena](https://boards.straightdope.com/u/Athena)
#### Post date: [April 19, 2008, 11:44am UTC](https://boards.straightdope.com/t/computer-help-aspi-blue-screen-hard-drive/445992/1 "2008-04-19T11:44:13Z")

</div>

My computer won’t boot. I get the blue screen of death on startup. [This](http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314830) is the error I get, although I am not installing anything - I’m just booting. The specific parameter I get is 0x00000002, that is:

> [@](#):
>
> 0x00000002, Parameter2, Parameter3, Parameter4):
> 
> This error is defined as ACPI root PCI resource failure. To discover what current resources are being used by PCI devices, ACPI must be able to query the CRS descriptor in the ACPI namespace. This error occurs if the BIOS lacks a pointer to the list, or if the list is empty, or if the list contains errors or conflicts.

It appears to have something to do with my second hard drive, which is about 3 months old. If I disable it by detaching the power from it, the computer boots, although XP wants to do a chkdsk on my main drive.

I’ve checked all the cables, they’re tight.

I’ve tried disabling ASPI in the BIOS. When I do that, it hangs on startup (it gets to the point where it tells me windows shut down badly, and do I want to run in safe mode. I say no, just boot, and it just sits there forever.)

So what’s going on? Anyone?

---

<div class="post-metadata">

### Author: ![Quartz](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/quartz/32/267_2.png) [@Quartz](https://boards.straightdope.com/u/Quartz)
#### Post date: [April 19, 2008, 12:26pm UTC](https://boards.straightdope.com/t/computer-help-aspi-blue-screen-hard-drive/445992/2 "2008-04-19T12:26:36Z")

</div>

Are we talking A **S** PI or A **C** PI? Both are valid acronyms and are very different.

I’m going to assume ACPI as it’s more likely.

Is your second drive PATA / IDE or SATA? (Big ribbon cable or slim plastic cable) If the former, are both drives jumpered correctly (master / slave / cable select)? If the latter, try plugging it in to a different SATA socket; also try a different SATA cable.

If you’ve done all that, try resetting the ESCD (?) in your BIOS. This will reinitialise the data area Windows is trying to read.

---

<div class="post-metadata">

### Author: ![Athena](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@Athena](https://boards.straightdope.com/u/Athena)
#### Post date: [April 19, 2008, 12:43pm UTC](https://boards.straightdope.com/t/computer-help-aspi-blue-screen-hard-drive/445992/3 "2008-04-19T12:43:36Z")

</div>

Yup, it’s ACPI, not ASPI. I’m posting pre-coffee 😃

Second drive is SATA. I finally did get it to boot by swapping what I assume are the drive controller cables - I pulled them both out of the motherboard and switched 'em around.

I think I still get the chkdsk on startup - I’m doing a full backup of my second drive at the moment, so I can’t double check that. But I was getting it every time. How do I make that go away?

---

<div class="post-metadata">

### Author: ![Quartz](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/quartz/32/267_2.png) [@Quartz](https://boards.straightdope.com/u/Quartz)
#### Post date: [April 19, 2008, 1:01pm UTC](https://boards.straightdope.com/t/computer-help-aspi-blue-screen-hard-drive/445992/4 "2008-04-19T13:01:21Z")

</div>

It sounds like you’ve got Windows installed on both and it’s getting confused.

A quick check: do you have a c:\windows and a d:\windows directory?

---

<div class="post-metadata">

### Author: ![Athena](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@Athena](https://boards.straightdope.com/u/Athena)
#### Post date: [April 19, 2008, 1:07pm UTC](https://boards.straightdope.com/t/computer-help-aspi-blue-screen-hard-drive/445992/5 "2008-04-19T13:07:34Z")

</div>

No, Windows is not installed on both drives.

It’s actually only checking the data partition on my primary drive. I have it partitioned into 3 partitions - C: is the OS, D: is a data partition, and E: is the pagefile. It only wants to check D:

I did reboot, and it wants to check D: again. I’ll go ahead and let it, but boy, it’s going to get old if it wants to do this every time I reboot.

---

<div class="post-metadata">

### Author: ![Quartz](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/quartz/32/267_2.png) [@Quartz](https://boards.straightdope.com/u/Quartz)
#### Post date: [April 19, 2008, 1:14pm UTC](https://boards.straightdope.com/t/computer-help-aspi-blue-screen-hard-drive/445992/6 "2008-04-19T13:14:05Z")

</div>

Aha! What you’ve probably got here is a partition relabelling issue. Each of your drives has a primary partition. Your first hard drive also has an extended partition. Windows assigns drive letters first to primary partitions, and then to extended partitions. So when you only had the first drive in, you happily had C: and D:, but when you put the second drive in, that became the new D:, and the old D: became E:!

---

<div class="post-metadata">

### Author: ![Athena](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@Athena](https://boards.straightdope.com/u/Athena)
#### Post date: [April 19, 2008, 2:02pm UTC](https://boards.straightdope.com/t/computer-help-aspi-blue-screen-hard-drive/445992/7 "2008-04-19T14:02:36Z")

</div>

Ummm… I don’t think that’s the issue. It’s been working fine with the disks for about 3 months. C/D/E are the first drive, F is the second drive.

Disk manager tells me all the drives and all the partitions are just fine & healthy.

It still wants to run chkdsk on startup though.
