Hi, I just bought a new system in January. These are the specs:
HARDWARE:
- Antec 300 case with four 120mm fans (two in, two out) - bought in Jan. 2009
- Asus P5Q motherboard - bought in Jan. 2009
- Intel E2200 Core 2 Duo processor - bought in Dec. 2008
- Arctic Cooling Freezer 7 CPU Cooler - bought in Jan. 2009
- Kingston Value RAM (2x2GB) - bought in Dec. 2008
- Sapphire Toxic HD4850 512MB DDR3 - bought in Dec. 2008
- Sound Blaster Audigy OEM (last revision before Audigy 2) - a couple years old now
- OCZ X Stream Stealth power supply (500watt) - bought in Jan. 2009
- Seagate SATA 1 Terabyte hard drive - bought in Jan. 2009
- Seagate SATA 250GB hard drive - a couple years old now
- LG SuperMulti DVDRAM drive - a couple years old now
SOFTWARE:
- Windows XP Pro SP3 (fully updated)
- Latest mother board drivers (bios was updated last night Feb. 13 2009)
- Latest ATI Catalyst Driver Suite 9.1 (updated Feb.12 2009)
- Sound Blaster is OEM thus only the included CD can be used for driver installation due to lack of
support from creative
- This motherboard comes with EPU 6 Engine which is disabled through the BIOS as well as Driver Xpert
which is also disabled
Now I have been working on my own systems since 2000 but I am stumped here. Between Jan.14 2009 and Feb.
9 2009 I have had 3 BSOD. When the BSOD occurs it has always been under normal operation, eg. viewing a
web page or changing system fonts. What happens is the system immediately goes to BSOD then it reboots on
its own. Upon reboot I see a message telling me that the system is not detecting my terabyte drive. No
boot drive detected. OK, I know a system can get flutters so from here I cold shutdown holding the power
button down. Upon reboot the drive is still not detected. One more cold shutdown and this time I went to
the BIOS and my terabyte drive plugged into SATA channel 1 is showing "not detected" while at the same
time my 250GB SATA (Seagate also) is detected fine on SATA channel 3. I do not run any kind of RAID setup
what so ever. Anyway I ctrl+alt+delete from the BIOS to reboot and still no detection. I must have tried
it in this fashion about 2 or 3 more times with no luck. I then had the idea to try my terabyte drive on
SATA channel 2 instead and it worked, it booted up properly no problem. I am very particular about my
setup and I believe I should be running on channel 1. With this in mind I shutdown and plug my terabyte
drive back into SATA channel 1 and it booted up properly no problem. This first instance occurred within
the first two weeks of running this rig. The second time it occurred I believe was on Feb. 8 2009. This
occurred while changing the right click menu font through Windows. The exact same thing played out only
this time when I shutdown I immediately switched channels from SATA 1 to 2 with the exact same
results...booted and loaded Windows no problem. The following morning it did it again, so again I perform
the same routine only this time while booting in SATA channel 2 I get the message that no boot drive is
detected. Oh oh. So I reboot from BIOS (ctrl+alt+delete) and it loaded on the second attempt. I shutdown
and plug the terabyte drive back into SATA channel 1 and it worked no problem. At this point I started
asking people I know that know much more then I do about computers. Responses include: (a)power supply
not giving enough power or failing (b)bad SATA cable (c)bad motherboard or SATA port (d) bad chipset on
PCB of hard drive
Power Supply: I have yet to get the power supply tested but I am a gamer and have had no problems while
gaming which is what would make the power supply work its hardest I figure.
SATA cable: I am currently running the same cable on my 250GB drive as it has now become my system/boot
drive. AS of Feb. 11 2009 I have had no issues yet.
Motherboard: I know so much about computers now that I realize I really know nothing. However if a
motherboard SATA port had issues would it go from working to not working? I have yet to get this
motherboard tested.
Terabyte drive: This is what I think the culprit is! Everything else seems to work as it should and right
now my system has been very stable for three days. This drive has been sent to the store from whence it
came for testing. Yesterday (Feb. 13 2009) the store called me and said the drive checks out OK.
I want to use that drive because of its size and speed but I cannot justify putting data from work or
taxes back on this drive until I can resolve this issue. This is the first time I have ever written to
any forum for tech support problems. I apologize for any mistakes and am very open to constructive
criticism. I have always found my solutions simply by searching and reading. This problem is upsetting
the flow of my day to day activities and work. I have searched vigorously and have found this problem
only once on a site that I can't seem to recall but I know must be bookmarked (somewhere). The problem
was that no one responded to it. If I am asking something that I have failed to find on this site I am
sorry. However I am running out of time and must find a solution. On Tuesday, Feb. 17 2009, unless I
figure this out, this entire rig will be taken to the store for a complete test. I hope the problem is
found but I have little faith in people who work for a minimum wage to find the answer. I don't mean to
offend anyone by that comment it is just a simple truth I have come to find as accurate. Though there are
many people who do take pride in their work regardless of wage. I hope one of them finds there way to my
computer.
Thank you for any time spent considering my dilemma.
Popyacap
HARDWARE:
- Antec 300 case with four 120mm fans (two in, two out) - bought in Jan. 2009
- Asus P5Q motherboard - bought in Jan. 2009
- Intel E2200 Core 2 Duo processor - bought in Dec. 2008
- Arctic Cooling Freezer 7 CPU Cooler - bought in Jan. 2009
- Kingston Value RAM (2x2GB) - bought in Dec. 2008
- Sapphire Toxic HD4850 512MB DDR3 - bought in Dec. 2008
- Sound Blaster Audigy OEM (last revision before Audigy 2) - a couple years old now
- OCZ X Stream Stealth power supply (500watt) - bought in Jan. 2009
- Seagate SATA 1 Terabyte hard drive - bought in Jan. 2009
- Seagate SATA 250GB hard drive - a couple years old now
- LG SuperMulti DVDRAM drive - a couple years old now
SOFTWARE:
- Windows XP Pro SP3 (fully updated)
- Latest mother board drivers (bios was updated last night Feb. 13 2009)
- Latest ATI Catalyst Driver Suite 9.1 (updated Feb.12 2009)
- Sound Blaster is OEM thus only the included CD can be used for driver installation due to lack of
support from creative
- This motherboard comes with EPU 6 Engine which is disabled through the BIOS as well as Driver Xpert
which is also disabled
Now I have been working on my own systems since 2000 but I am stumped here. Between Jan.14 2009 and Feb.
9 2009 I have had 3 BSOD. When the BSOD occurs it has always been under normal operation, eg. viewing a
web page or changing system fonts. What happens is the system immediately goes to BSOD then it reboots on
its own. Upon reboot I see a message telling me that the system is not detecting my terabyte drive. No
boot drive detected. OK, I know a system can get flutters so from here I cold shutdown holding the power
button down. Upon reboot the drive is still not detected. One more cold shutdown and this time I went to
the BIOS and my terabyte drive plugged into SATA channel 1 is showing "not detected" while at the same
time my 250GB SATA (Seagate also) is detected fine on SATA channel 3. I do not run any kind of RAID setup
what so ever. Anyway I ctrl+alt+delete from the BIOS to reboot and still no detection. I must have tried
it in this fashion about 2 or 3 more times with no luck. I then had the idea to try my terabyte drive on
SATA channel 2 instead and it worked, it booted up properly no problem. I am very particular about my
setup and I believe I should be running on channel 1. With this in mind I shutdown and plug my terabyte
drive back into SATA channel 1 and it booted up properly no problem. This first instance occurred within
the first two weeks of running this rig. The second time it occurred I believe was on Feb. 8 2009. This
occurred while changing the right click menu font through Windows. The exact same thing played out only
this time when I shutdown I immediately switched channels from SATA 1 to 2 with the exact same
results...booted and loaded Windows no problem. The following morning it did it again, so again I perform
the same routine only this time while booting in SATA channel 2 I get the message that no boot drive is
detected. Oh oh. So I reboot from BIOS (ctrl+alt+delete) and it loaded on the second attempt. I shutdown
and plug the terabyte drive back into SATA channel 1 and it worked no problem. At this point I started
asking people I know that know much more then I do about computers. Responses include: (a)power supply
not giving enough power or failing (b)bad SATA cable (c)bad motherboard or SATA port (d) bad chipset on
PCB of hard drive
Power Supply: I have yet to get the power supply tested but I am a gamer and have had no problems while
gaming which is what would make the power supply work its hardest I figure.
SATA cable: I am currently running the same cable on my 250GB drive as it has now become my system/boot
drive. AS of Feb. 11 2009 I have had no issues yet.
Motherboard: I know so much about computers now that I realize I really know nothing. However if a
motherboard SATA port had issues would it go from working to not working? I have yet to get this
motherboard tested.
Terabyte drive: This is what I think the culprit is! Everything else seems to work as it should and right
now my system has been very stable for three days. This drive has been sent to the store from whence it
came for testing. Yesterday (Feb. 13 2009) the store called me and said the drive checks out OK.
I want to use that drive because of its size and speed but I cannot justify putting data from work or
taxes back on this drive until I can resolve this issue. This is the first time I have ever written to
any forum for tech support problems. I apologize for any mistakes and am very open to constructive
criticism. I have always found my solutions simply by searching and reading. This problem is upsetting
the flow of my day to day activities and work. I have searched vigorously and have found this problem
only once on a site that I can't seem to recall but I know must be bookmarked (somewhere). The problem
was that no one responded to it. If I am asking something that I have failed to find on this site I am
sorry. However I am running out of time and must find a solution. On Tuesday, Feb. 17 2009, unless I
figure this out, this entire rig will be taken to the store for a complete test. I hope the problem is
found but I have little faith in people who work for a minimum wage to find the answer. I don't mean to
offend anyone by that comment it is just a simple truth I have come to find as accurate. Though there are
many people who do take pride in their work regardless of wage. I hope one of them finds there way to my
computer.
Thank you for any time spent considering my dilemma.
Popyacap