New Posts  All Forums:Forum Nav:

5720 Dead

post #1 of 9
1/17/06 at 1:22pm
Thread Starter 
so heres the deal:

after about 3 weeks of faithful service, it decided to not boot on me. Ironically, it stopped working last night, my first day of class that also happened to be my birthday. Instead of being able to be ultra-thankful for the wonderful 5720, the unit failed to start right before i wanted to sleep.

the problem: when i power it, the dvd drive whirs up, but there is not enough clicking on the hd. The hd-busy light on the display comes up but then dissapears and the unit is silent except for the really quite cpu fan ... other than that NO ACTIVITY. ive tried a bunch of things and i cant figure it out because it was working perfectly before i turned it off [prior to failure]

what i need is a quick rundown of the procedure to invoke the 30day return policy. From my take, the unit was shipped 12-20-05, and today is 1-17-06.... which would make the THIRTIETH day tomorrow. Hopefully its from ship date and not order date, which would make my time to check the unit only about 2 weeks. Can someone quickly corrent me if im wrong???

I simply want to return this unit, and be done with it. PLEASE HELP ME OUT GUYS!!!
Reply
Reply
post #2 of 9
1/17/06 at 3:59pm
Don't know about Sager, but for Dell, the 21 days period starts from the order date.
Reply
Reply
post #3 of 9
1/17/06 at 4:36pm
Thread Starter 
I just confirmed, its 30 days from the shipdate, so i just have to do it by tomorrow. To bad my faith in sager has been severly shaken .. but im thankful that it at least failed within the 30 day window.
Reply
Reply
post #4 of 9
1/17/06 at 7:15pm
Sorry to hear that you got a bad unit. At least you're within the 30-day window. I'd be calling them up immediately.
Reply
Reply
post #5 of 9
1/18/06 at 5:35pm
Thread Starter 
Yup, got the RMA# and sent it back.

Anyone else that gets into a similar bind, i HIGHLY recommend you call them up instead of using the online request form ... it takes forever. With calling, you'll play a little phone tag, but eventually the RMA department will contact you and get things squared away fast.
Reply
Reply
post #6 of 9
1/27/06 at 6:42am
i had this happen with a bad 1g ram after stable overclock suddenly quit on me, i just removed the cmos battery and shorted the two pins for the cmos battery connection. voila, works perfect.
Reply
Reply
post #7 of 9
1/27/06 at 12:04pm

oh man...

dang. This just happened to me last night. I was thinking...did i set it down too hard on the bed when I got back to my room? NAH....it's just a piece.

But I'm kinda in the middle of a TDY, and getting ready to deploy to Afghanistan on Sunday...maybe I'll be able to get this thing shipped back by then? But I don't have the ability to phone tag with a payphone.

Dammit Dammit Dammit.
Reply
Reply
post #8 of 9
3/5/06 at 8:22pm
mine does that about 3 times a month... ill turn it on bios clears and then nothing...
i just turn it off and back on and within one or two tries it works fine. i dont think its too big of a deal... atleast for my case anyway.. good luck
Reply
Reply
post #9 of 9
3/6/06 at 4:19am
Quote:
Originally Posted by avery155
mine does that about 3 times a month... ill turn it on bios clears and then nothing...
i just turn it off and back on and within one or two tries it works fine. i dont think its too big of a deal... atleast for my case anyway.. good luck
Interesting.

Mine did that two times since I bought it in January.

random error?? Maybe...
Hopefully, nothing really serious.
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home