Ok so, I was on my computer (self built) a week or two ago, and it froze up completely. I restarted and got some error messages as windows tried to start up(the one where it says there was an error with windows restarting in 30..29..28 etc etc. I let the timer run down and it wouldn't start. I kept restarting a few times, occaisonally getting windows to load and the computer to function normally, a few times this message, a few times jsut a blank screen after all the BIOS screens went by. I took it to geek squad, and they said it looked as if an IDE port was not working correctly. So i switch the cable from ide port 2 to ide port 1(IC7-G mother board btw) and it worked great for a few days. Now it's back to the same thing, and when playing World of Warcraft, it'll randomely freeze up looping sounds, sometimes will return to normal after 20 seconds or so sometimes won't. Any sugestions? I ran a disk defrag, and many spywbot programs(all found nothing except temporary files).

EDIT: system speccs: Intel pentium 4 prescott 800MHz 478 socket @ 3.00ghz (box settings)

XTASY Radeon 9800pro (agp)

500w rosewill PSU

A raidmax case with 6 case fans(all 80mm) 1 on side 1 on top 2 in front 2 in back

1gig corsair XMS DDR400 ram

western digital 160gig 7200rpm serial ATA150 harddrive

Im pretty newb at this stuff as well, so be easy on me. BTW all parts are still under 3 year manufacture warranty, so if need be, I can replace.



EDIT: also, sometimes all sound dies, and I use on board audio, so this makes me think maybe the audio on the mobo is faulty also?


-----------------------------------------------------------------

Someone suggested my PSU, but I really doubted that one. heres the response I gave when they blamed the PSU:

I highly highly doubt it is the PSU after today, long loading times for windows, no sound, freeze and haev to reset via power button hold down... all signs of my mobo it seems(I use onboard audio) I would say harddrive but how's that affect my audio? The drivers are all up to date to the best of my knowledge..

--------------------------------------------------------------------------

After this I got no responses, and I thought maybe I needed to give more info so i posted my error log:


ednesday, December 01, 2004 atapi A parity error was detected on \Device\Ide\IdePort1.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 atapi A parity error was detected on \Device\Ide\IdePort1.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 atapi The device, \Device\Ide\IdePort1, did not respond within the timeout period.
Wednesday, December 01, 2004 atapi The device, \Device\Ide\IdePort1, did not respond within the timeout period.
Wednesday, December 01, 2004 atapi A parity error was detected on \Device\Ide\IdePort1.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 atapi A parity error was detected on \Device\Ide\IdePort1.
Wednesday, December 01, 2004 Disk The driver detected a controller error on \Device\Harddisk0\D.
Wednesday, December 01, 2004 atapi The device, \Device\Ide\IdePort1, did not respond within the timeout period.
Wednesday, December 01, 2004 atapi The device, \Device\Ide\IdePort1, did not respond within the timeout period.
Wednesday, December 01, 2004 atapi The driver detected a controller error on \Device\Ide\IdePort1.

----------------------------------------------------------------------------------


Still no response, then i thought about it, and why would ABIT claim it's there mobo on their own forums???? Wouldn't they avoid it like the devil??? So I came here, where my responses will be un biased ^^ (and hopefully much faster lol >_< )


Heres a link to the original thread:

http://forum.abit-usa.com/showthread.php?p=643783#post643783

Sounds like a bad harddrive.But it could be a very flawed windows install.Go to the run box and type this or copy and paste this chkdsk c: /f .And it will check your Hd. IF you can get it to windows again.I would take that HD and test it another PC even though you might have to reformat it and loose your stored info. But some times thats all you can do..Here what i would do.

Frist id try to reinstall windows.If that wont work id rma that HD.When you do the install what file system are you choosen?Fat or NTFS? and are you using the quick fromat option.I always use the quick format and NTFS files because the normal format takes hours sometimes.Any way if you cant get that far Rma that thing but i would frist buy a second one that way when the rma comes back you can run a nice Raid array.Then if that dont work RMA the board.

Edit: I just thought of something do you have the chipset drivers installed?That could be a driver issue also.And i had a 500 watt rosewill psu and it was fine for the system you see in my sig so i know it would run your's(not that mines so great but im sure my system needs a little more power than your's but i could be wrong)

NTFS, thanks a ton, CHK DSK ran once on it before, and found some stuff(this was from start up I didn''t initialize it myself) I'll try it tonight, because I have school in 10 minutes, and CHKDSK takes a while doesn't it? (PS keep replying ^^ I can read in school via study hall and computer apps class )

O, btw my harddrive is split into C(20gigs) and E(120gigs).. Will that change the run box entry at all?

Initial thoughts were a driver error too.

But to me, it sounds more like the board than the HD.

if ya have another HD try installing that and see if you still get the errors.

I would just RMA the board though. The error log pointed to a controller error, not the drive itself. So either your drivers are really messed up, or the boards IDE controllers are ruined.

You should get an SATA drive anyway. Does your CD/DVD drive still work ok?

Good point DUBBLIN GUNNER. thats was a great observation.Im still half asleep..lol ive only had 1 coffee so far

Yeah, CD/DVD drives work fine. When I do get on it works basically fine, except sometimes the sound wont work, but the only time i consistently notice freezes is when playing heavy load games. Stuff like WC3 and counterstrike wont freeze, but other s**t will, like world of warcraft in busy areas or large 40 man fights. I was thinking board from this too, not being able to handle all the info coming in?

Ok, well if your CD/DVD drives work, I would say that the IDE controller is fine.

So, now were back to either the drivers, or the HD itself.

Also, maybe a ram problem, as it only happens when loaded (mostly) its possibly a ram issue. Do you overclock? What ram do you have installed? Do you have any spare DIMMs lying around to test?

Dodgy ram can corrupt data. hence when loaded, it could be easily corrupting data flowing through it, also, this is where the driver may get corrupt, while loading into memory.

Can you test the HD in another computer? Or test another one in that computer?


lol @ Mothow, I know how ya feel!!

I can't test the harddrive unfortanatly, the ram is 1gig of corsair XMS, seems pretty reliable though. Im not overclocking. I'm about to test the chkdsk..

edit: the reason im leaning towards IDE is because of this error:

Wednesday, December 01, 2004 atapi A parity error was detected on \Device\Ide\IdePort1.


it appears several times.

spare DIMMS? whats that? I ran chkdsk but it finished in like 20 seconds o_O just said it was verifying some stuff.. doesn't seem right to me. The ram I can probably test in another computer. under computer properties it displays all of it, and my virtal paging size reflects how much RAM i have as well..

edit: so most likely drivers? I tried DLing all the newest drivers, but for somereason I have trouble finding them.. what was the thing about disabling audio wiht 5.1?

Ok, with that error its definitely either the IDE controller or the HD.

And paired with the poor performance of my audio im still leaning towards board... now even if it is board do you think I should RMA them both to be safe? I hear it's good to start totally fresh with a new mobo anyways, sooo.

Put it this way, if you RMA either one, you'll be without the PC for a time anyway. So you may aas well RMA them both, and as you said, start with new parts.

To resolve this issue, change the transfer mode for the controller:

1. Right-click My Computer, and then click Manage.
2. Double-click System Tools in the right pane, and then double-click Device Manager.
3. Double-click IDE ATA/ATAPI Controller in the right pane, and then double-click the appropriate controller.
4. On the Advanced Settings tab, click PIO Only in the Transfer Mode box.
5. Click OK, close the Computer Management window, and then reboot the computer.

I'm leaning toward mobo since you are having problem with on-board sound as well. But I would still try a different stick of RAM first.