A7N8X Deluxe R2....booting sometimes stops at ide detection

  • Thread starter Thread starter Archer
  • Start date Start date
A

Archer

My computer works properly and there are no stability issues when it is
running. However, when it starts up, sometimes it stops on the ide
detection and sits there. I can Control-alt-delete or reset and it will
boot up properly with no issues. Sometimes it will do this twice in a row.
I had a revision 1.04 of this same board and it would do the same thing. Is
this a known issue with this line of asus board? Is there a setting in the
bios that will allow the drives to be recognized on every boot? Thanks
 
Yea, I have been on with asus tech support (UK) and he tells me that I am
the first one that has reported this type of problem. It's locking up after
the primary ide detection, I can tell because the 2nd ide channel isnt ever
query'd.. after many many emails with both the Tiwan tech support and His
tech support he's told me this..

" it could be down to the controllers not releasing the information
resulting in the BIOS looking for drives that are not connected. If the
motherboard is less than a year old, you can return your motherboard to your
reseller for a replacement. If over the year, we can help you with the
warranty repair/exchange how-ever this procedure normally takes around 2 - 3
weeks."

I guess I will be returning my board to overclockers and asking for a new
one to be sent out, but I hate the idea of being without this pc for over a
week..

JL
 
To me this is just an annoyance. Since this has happened to me on two
different A7N8X Boards (Rev 1.04 and 2.0), I don't believe it is a defect
and If I replace my board, I wouldn't be surprised to still have the
problem. I have tried changing bios settings and I've replaced my ata133
ide cable with a new one. Good luck with your return.
 
To me this is just an annoyance. Since this has happened to me on two
different A7N8X Boards (Rev 1.04 and 2.0), I don't believe it is a defect
and If I replace my board, I wouldn't be surprised to still have the
problem. I have tried changing bios settings and I've replaced my ata133
ide cable with a new one. Good luck with your return.
Click to expand...

Yea, I still havent decided if I "want" to return it yet. It's damn near
impossible to get "True" tech support these days, and they dont seem to have
a quality system in place to show them about "common" faults with the
boards. So if I return it and my next one is just like it then I am out of
a board for no real bonus..

I have "Requsted" a contact at their Holland Repair Centre so I can
"inquire" as to this being a main fault or not.. I'll post the reply back
"if" they choose to work with me..
 
If it's their board then it's their issue.. Dont let them say otherwise
it MIGHT be the controller chip, if so it's still their issue as they buy
the controllers.. Does that mean that user pressure will get it fixed, nope,
but it still doesnt hurt to push them to fixing it.. Asus has a quality rep
(to me at least) and them just sitting by on the sidelines with this is not
someting that I find acceptable, the boards they release to company's like
DELL (and like) would be cured of this problem pre-release.. so they can do
it for us too
 
Hi, sounds like same problem being discussed here....
Nvidia users experience Nforce IDE problems

Those with IDE problems please post full details!
http://www.nforcershq.com/forum/viewtopic.php?t=19484
Click to expand...

I think that the problem there is different than the one we are describing,
the one we are describing seems to be a failure by AWARD during the primary
slave detection test phase (during POST). That doesnt mean that the problem
isnt related (Faulty I/O Controller). But that page doesnt seem to have any
"Request" near what I am describing, all the faults there are software
faults (More of a pain in the ass IMHO)..
 
Back
Top