The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Ok so here's the deal. I have two Western Digital Harddrives, one is a 120g, the other a terabyte. The 120 is my boot drive, with Windows XP Pro installed on it.
Everything works perfectly except that for whatever reason my computer will randomly (playing L4D2, surfing Facebook, sitting idle) reboot itself and get stuck on the "Checking DMC Pool Data...." screen attempting to boot from my terabyte harddrive. I then have to restart it, go into my Bios, and reset the 120 as my primary boot drive.
Why does my computer think it can change this around? Why can't it just listen to me?
Thanks,
Will
Edit: I realize I didn't put much information in this post. The harddrives are both SATA, the terabyte one is the WD Caviar Black model. I'm not sure of the 120g.
First, you need to figure out why it's randomly rebooting. Turn off "automatic reboot on system failure ( here), then write down what appears on the BSOD.
First, you need to figure out why it's randomly rebooting. Turn off "automatic reboot on system failure ([url= here[/url]), then write down what appears on the BSOD.
Will do, I'll let you know the message the next time it happens.
Ok so since turning off automatic restart my computer hasn't done much, until now. BSOD and here's the Stop message: 0x000000F4 (0x00000003 0x8A9BCF0 0x805C77D0)
How do I perform a memtest? Thanks for your help guys.
No it doesnt pop up any info on the DCMI pool and I'll check my power supply tonight, sorry for the late response but there's been no activity from the machine in awhile.
Question, do you have an IDE hard drive by any chance?
Chances are you either have an IDE hard drive that is set to slave when it's meant to be a master (or it should be and it's jumpered as slave and is on the master connector, or, there is nothing on the master connector) or your SATA drive isn't on the channel0 connector on your raid card/mobo.
0x000000F4 (0x00000003) is a HDD issue, though 0x000000F4 can also refer to memory (but the 03 makes it point to a drive issue).
Oh yeah, disabling standby mode/hibernate in your power saving features will probably fix this.
bowen on
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
Question, do you have an IDE hard drive by any chance?
Chances are you either have an IDE hard drive that is set to slave when it's meant to be a master (or it should be and it's jumpered as slave and is on the master connector, or, there is nothing on the master connector) or your SATA drive isn't on the channel0 connector on your raid card/mobo.
0x000000F4 (0x00000003) is a HDD issue, though 0x000000F4 can also refer to memory (but the 03 makes it point to a drive issue).
Oh yeah, disabling standby mode/hibernate in your power saving features will probably fix this.
They're both SATA drives. Should my boot drive be on Channel0 and my storage be on Channel1?
I also recently formatted my computer and was updating the whole thing. I installed SP3 and it failed during the installation. I'm not sure if this could have anything to do with it or not? Would it be worth it just to formst again? That usually gets rid of the BSOD.
Posts
Will do, I'll let you know the message the next time it happens.
Do a memtest to rule out memory and maybe a scandisk (though I think the hard disks will post a SMART error even before getting to the DMI section).
What kind of power supply do you have?
How do I perform a memtest? Thanks for your help guys.
No it doesnt pop up any info on the DCMI pool and I'll check my power supply tonight, sorry for the late response but there's been no activity from the machine in awhile.
Chances are you either have an IDE hard drive that is set to slave when it's meant to be a master (or it should be and it's jumpered as slave and is on the master connector, or, there is nothing on the master connector) or your SATA drive isn't on the channel0 connector on your raid card/mobo.
0x000000F4 (0x00000003) is a HDD issue, though 0x000000F4 can also refer to memory (but the 03 makes it point to a drive issue).
Oh yeah, disabling standby mode/hibernate in your power saving features will probably fix this.
They're both SATA drives. Should my boot drive be on Channel0 and my storage be on Channel1?
I also recently formatted my computer and was updating the whole thing. I installed SP3 and it failed during the installation. I'm not sure if this could have anything to do with it or not? Would it be worth it just to formst again? That usually gets rid of the BSOD.