Prev: Bad MBR
Next: Vadem ? (long shot)
From: kony on 11 Jan 2010 02:50
On Sun, 10 Jan 2010 10:19:05 +0000, TheDeadWolf
<thedeadwolfx(a)hotmail.com> wrote:


>Thank you for your suggestions. I will try these soon.
>Yes i do have a warranty, and yes it has been doing it almost as soon as
>i got it. However it is getting worse.

Since it has at least two memory modules, you might try
removing one, retesting the system, putting it back and
removing the other one. "IF" it is the memory it could be
just one module, or could be an incompatibility, or could be
one slot (try either/or modules in each slot).



>However i had already broken the seal a few days back to see if anything
>was wrong with the fans. I did not realize it could stop the warranty. I
>guess im screwed there.

Don't assume so yet, wait and see... but if I were you I'd
go ahead and contact Acer and see what they'll do, for
example how long they expect it to take, whether they cover
shipping cost. You could always get an RMA # and keep
looking for the problem in the interim till you decide to
send it in or not, at least until the point the RMA number
expires since many places these days don't leave a RMA
number indefinitely open they instead specify a time-window
you have to get it to them... but even then you may be able
to just get a new RMA number since the main issue is just
that the warranty period is still active.


>But while i did look i also took a few photographs.
>
>The computer/Where it is.
>http://i280.photobucket.com/albums/kk185/michaeljhull13wolf/P080110_1304_01.jpg
>http://i280.photobucket.com/albums/kk185/michaeljhull13wolf/P080110_1304.jpg
>http://i280.photobucket.com/albums/kk185/michaeljhull13wolf/P080110_1305_01.jpg
>The Monitor and what it looked like when it crashed.
>http://i280.photobucket.com/albums/kk185/michaeljhull13wolf/P080110_1305_02.jpg
>The inside of the pc.
>http://i280.photobucket.com/albums/kk185/michaeljhull13wolf/P080110_1308.jpg
>(Yes i know the wires are still plugged in but everything was turned off
>and the power cable was unplugged)
>http://i280.photobucket.com/albums/kk185/michaeljhull13wolf/P080110_1308_01.jpg
>http://i280.photobucket.com/albums/kk185/michaeljhull13wolf/P080110_1308_02.jpg
>On this pic you can just about see the ram underneath the Cd-drive.
>http://i280.photobucket.com/albums/kk185/michaeljhull13wolf/P080110_1309_02.jpg


If you say so... ;) Hard to make out much in the middle and
latter pictures.
From: TheDeadWolf on 11 Jan 2010 18:44
kony wrote:
> On Mon, 11 Jan 2010 07:59:15 +0100, Kyle
> <ThisIsPrivate(a)NoAddress.com> wrote:
>
>> On Sat, 09 Jan 2010 17:40:44 +0000, TheDeadWolf
>> <thedeadwolfx(a)hotmail.com> wrote:
>>
>>> Hey everyone.
>>> Firstly id like to say sorry for if i have posted in a wrong
>>> thread/newsboard.
>>> Secondly id like to thank anyone who reads and responds to this post as
>>> it is much appreciated.
>>>
>>> I got an Acer Aspire AX1300 for Christmas this year and it is a great
>>> computer, however i am experiencing some problems and it is getting
>>> annoying now.
>> I agree with all the others who replied, it's the memory.
>>
>> And yes, you can't use the warranty since you have broken the seal.
>
> Well... don't assume it for sure just yet, the seal could be
> to "discourage" owners from lurking inside, but particular
> technicians or CSRs may or may not care about the sticker
> being broken. I'd be sure to mention it was failing before
> it was opened the first time if they ask about the sticker,
> telling them something like you needed the data off the hard
> drive before sending it to them (which is what I recommend,
> get all your data off as you never know for sure if it's
> coming back with the drive wiped or even a different drive
> installed if not a different system... not to mention, I
> trust pimply faced kids in distant locations not much with
> data, even the honest and otherwise responsible ones may not
> leave the system in a secure locked area where others don't
> have access to it ).
>
>
>> Anyway, change the memory, it will solve the problem. If not, then you
>> have a BIG problem to deal with.
>
> I hope you're right, but generally memory problems would
> cause random glitches, bluescreen errors, failure to boot,
> etc, not just a repetitive video anomoly. Not that one
> cause is ok and the other isn't, it's just that plopping
> different memory in is one of the easiest fixes to do and
> the fault one of the easiest to find (if/when it is found).

Ok thanks to everyone who replied.
I have tested my CPU with the Memtest CD. It did two small tests then
one for an hour and half. No errors at all where found, all of them passed.
Someone else suggested to use a stress program (prime95) and use
SpeedFan to see if overheating was a problem. I have only an that for a
small amount of time and already the CPU temperature was 63C. However i
will carry with the full stress test tomorrow and report back here.
From: kony on 11 Jan 2010 19:22
On Mon, 11 Jan 2010 23:44:57 +0000, TheDeadWolf
<thedeadwolfx(a)hotmail.com> wrote:


>Ok thanks to everyone who replied.
>I have tested my CPU with the Memtest CD. It did two small tests then
>one for an hour and half. No errors at all where found, all of them passed.
>Someone else suggested to use a stress program (prime95) and use
>SpeedFan to see if overheating was a problem. I have only an that for a
>small amount of time and already the CPU temperature was 63C. However i
>will carry with the full stress test tomorrow and report back here.


63C is not too hot, if you were aggressively overclocking it
might limit your ceiling speed, but it should run all day
long for years at that temperature. However, a CPU
temperature that is elevated can be a sign of poor chassis
cooling that effects other components.

If speedfan doesn't list the chipset temperature, try some
other hardware monitoring programs to see which do.

Since you wrote it happens in everyday use not just full
load conditions, look more at the other temperatures
reported and voltages in such situations.

However, CPU processing or memory errors do not usually
manifest themselves with the symptoms you are seeing. Video
chipset or PSU are more likely culprits.
From: TheDeadWolf on 12 Jan 2010 19:41
kony wrote:
> On Mon, 11 Jan 2010 23:44:57 +0000, TheDeadWolf
> <thedeadwolfx(a)hotmail.com> wrote:
>
>
>> Ok thanks to everyone who replied.
>> I have tested my CPU with the Memtest CD. It did two small tests then
>> one for an hour and half. No errors at all where found, all of them passed.
>> Someone else suggested to use a stress program (prime95) and use
>> SpeedFan to see if overheating was a problem. I have only an that for a
>> small amount of time and already the CPU temperature was 63C. However i
>> will carry with the full stress test tomorrow and report back here.
>
>
> 63C is not too hot, if you were aggressively overclocking it
> might limit your ceiling speed, but it should run all day
> long for years at that temperature. However, a CPU
> temperature that is elevated can be a sign of poor chassis
> cooling that effects other components.
>
> If speedfan doesn't list the chipset temperature, try some
> other hardware monitoring programs to see which do.
>
> Since you wrote it happens in everyday use not just full
> load conditions, look more at the other temperatures
> reported and voltages in such situations.
>
> However, CPU processing or memory errors do not usually
> manifest themselves with the symptoms you are seeing. Video
> chipset or PSU are more likely culprits.

Okay i tested the Stress Tester (Prime95) to success. 4 hours and the
computer didn't crash. his was good because its about the longest the pc
has gone without crashing.
Here are the results.

Compare your results to other computers at
http://www.mersenne.org/report_benchmarks
AMD Athlon(tm) 7450 Dual-Core Processor
CPU speed: 2400.15 MHz, 2 cores
CPU features: RDTSC, CMOV, Prefetch, 3DNow!, MMX, SSE, SSE2
L1 cache size: 64 KB
L2 cache size: 512 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 48
L2 TLBS: 512
Prime95 64-bit version 25.8, RdtscTiming=1
Best time for 768K FFT length: 19.528 ms.
Best time for 896K FFT length: 23.247 ms.
Best time for 1024K FFT length: 26.122 ms.
Best time for 1280K FFT length: 32.578 ms.
Best time for 1536K FFT length: 40.104 ms.
Best time for 1792K FFT length: 47.905 ms.
Best time for 2048K FFT length: 54.404 ms.
Best time for 2560K FFT length: 71.952 ms.
Best time for 3072K FFT length: 90.870 ms.
Best time for 3584K FFT length: 104.394 ms.
Best time for 4096K FFT length: 117.842 ms.
Best time for 5120K FFT length: 156.914 ms.
Best time for 6144K FFT length: 192.167 ms.
Best time for 7168K FFT length: 235.338 ms.
Best time for 8192K FFT length: 269.045 ms.
Timing FFTs using 2 threads.
Best time for 768K FFT length: 13.402 ms.
Best time for 896K FFT length: 17.640 ms.
Best time for 1024K FFT length: 19.960 ms.
Best time for 1280K FFT length: 24.933 ms.
Best time for 1536K FFT length: 29.850 ms.
Best time for 1792K FFT length: 35.146 ms.
Best time for 2048K FFT length: 42.591 ms.
Best time for 2560K FFT length: 54.520 ms.
Best time for 3072K FFT length: 65.263 ms.
Best time for 3584K FFT length: 75.921 ms.
Best time for 4096K FFT length: 86.565 ms.
Best time for 5120K FFT length: 109.019 ms.
Best time for 6144K FFT length: 133.111 ms.
Best time for 7168K FFT length: 161.080 ms.
Best time for 8192K FFT length: 182.895 ms.
Best time for 58 bit trial factors: 3.260 ms.
Best time for 59 bit trial factors: 3.329 ms.
Best time for 60 bit trial factors: 3.328 ms.
Best time for 61 bit trial factors: 3.591 ms.
Best time for 62 bit trial factors: 3.657 ms.
Best time for 63 bit trial factors: 4.290 ms.
Best time for 64 bit trial factors: 4.878 ms.
Best time for 65 bit trial factors: 5.907 ms.
Best time for 66 bit trial factors: 6.943 ms.
Best time for 67 bit trial factors: 6.893 ms.
[Tue Jan 12 20:06:59 2010]
Self-test 1024K passed!
Self-test 1024K passed!
[Tue Jan 12 20:22:25 2010]
Self-test 8K passed!
Self-test 8K passed!
[Tue Jan 12 20:38:41 2010]
Self-test 10K passed!
Self-test 10K passed!
[Tue Jan 12 20:55:07 2010]
Self-test 896K passed!
Self-test 896K passed!
[Tue Jan 12 21:11:41 2010]
Self-test 768K passed!
Self-test 768K passed!
[Tue Jan 12 21:26:49 2010]
Self-test 12K passed!
Self-test 12K passed!
[Tue Jan 12 21:43:39 2010]
Self-test 14K passed!
Self-test 14K passed!
[Tue Jan 12 21:59:01 2010]
Self-test 640K passed!
Self-test 640K passed!
[Tue Jan 12 22:14:32 2010]
Self-test 512K passed!
Self-test 512K passed!
[Tue Jan 12 22:29:44 2010]
Self-test 16K passed!
Self-test 16K passed!
[Tue Jan 12 22:46:38 2010]
Self-test 20K passed!
Self-test 20K passed!
[Tue Jan 12 23:02:27 2010]
Self-test 448K passed!
Self-test 448K passed!
[Tue Jan 12 23:18:47 2010]
Self-test 384K passed!
Self-test 384K passed!
[Tue Jan 12 23:34:16 2010]
Self-test 24K passed!
Self-test 24K passed!
[Tue Jan 12 23:49:44 2010]
Self-test 28K passed!
Self-test 28K passed!
[Wed Jan 13 00:04:44 2010]
Self-test 320K passed!
Self-test 320K passed!
[Wed Jan 13 00:21:39 2010]
Self-test 256K passed!
Self-test 256K passed!

Anyway what i did before the test was in the windows 7 display options i
found something called powersave. This was turned on. I realized perhaps
this was a bit of a problem as to why the crashes were occurring. I
thought perhaps my pc wasn't getting enough power, or if it exceeded the
limit because that was switched on. So i switched to performance. I
think this has solved it. Im not sure yet but it hasn't crashed so far.
The overheating i don't think is a problem. When using the Stress Tester
it only reached 65C, and Core temperature was 51C. The fan speeds got to
2283, and the other fan was at 2647 (Not sure which fan was CPU fan or
which was the power pack fan)

If it crashes again though i will send it back as i have tried pretty
much everything.


Thank you all for your help in this matter. I will keep you updated as
to how it goes.
From: TheDeadWolf on 13 Jan 2010 11:48
TheDeadWolf wrote:
> kony wrote:
>> On Mon, 11 Jan 2010 23:44:57 +0000, TheDeadWolf
>> <thedeadwolfx(a)hotmail.com> wrote:
>>
>>
>>> Ok thanks to everyone who replied.
>>> I have tested my CPU with the Memtest CD. It did two small tests
>>> then one for an hour and half. No errors at all where found, all of
>>> them passed.
>>> Someone else suggested to use a stress program (prime95) and use
>>> SpeedFan to see if overheating was a problem. I have only an that for
>>> a small amount of time and already the CPU temperature was 63C.
>>> However i will carry with the full stress test tomorrow and report
>>> back here.
>>
>>
>> 63C is not too hot, if you were aggressively overclocking it
>> might limit your ceiling speed, but it should run all day
>> long for years at that temperature. However, a CPU
>> temperature that is elevated can be a sign of poor chassis
>> cooling that effects other components.
>> If speedfan doesn't list the chipset temperature, try some
>> other hardware monitoring programs to see which do.
>>
>> Since you wrote it happens in everyday use not just full
>> load conditions, look more at the other temperatures
>> reported and voltages in such situations.
>>
>> However, CPU processing or memory errors do not usually
>> manifest themselves with the symptoms you are seeing. Video
>> chipset or PSU are more likely culprits.
>
> Okay i tested the Stress Tester (Prime95) to success. 4 hours and the
> computer didn't crash. his was good because its about the longest the pc
> has gone without crashing.
> Here are the results.
>
> Compare your results to other computers at
> http://www.mersenne.org/report_benchmarks
> AMD Athlon(tm) 7450 Dual-Core Processor
> CPU speed: 2400.15 MHz, 2 cores
> CPU features: RDTSC, CMOV, Prefetch, 3DNow!, MMX, SSE, SSE2
> L1 cache size: 64 KB
> L2 cache size: 512 KB
> L1 cache line size: 64 bytes
> L2 cache line size: 64 bytes
> L1 TLBS: 48
> L2 TLBS: 512
> Prime95 64-bit version 25.8, RdtscTiming=1
> Best time for 768K FFT length: 19.528 ms.
> Best time for 896K FFT length: 23.247 ms.
> Best time for 1024K FFT length: 26.122 ms.
> Best time for 1280K FFT length: 32.578 ms.
> Best time for 1536K FFT length: 40.104 ms.
> Best time for 1792K FFT length: 47.905 ms.
> Best time for 2048K FFT length: 54.404 ms.
> Best time for 2560K FFT length: 71.952 ms.
> Best time for 3072K FFT length: 90.870 ms.
> Best time for 3584K FFT length: 104.394 ms.
> Best time for 4096K FFT length: 117.842 ms.
> Best time for 5120K FFT length: 156.914 ms.
> Best time for 6144K FFT length: 192.167 ms.
> Best time for 7168K FFT length: 235.338 ms.
> Best time for 8192K FFT length: 269.045 ms.
> Timing FFTs using 2 threads.
> Best time for 768K FFT length: 13.402 ms.
> Best time for 896K FFT length: 17.640 ms.
> Best time for 1024K FFT length: 19.960 ms.
> Best time for 1280K FFT length: 24.933 ms.
> Best time for 1536K FFT length: 29.850 ms.
> Best time for 1792K FFT length: 35.146 ms.
> Best time for 2048K FFT length: 42.591 ms.
> Best time for 2560K FFT length: 54.520 ms.
> Best time for 3072K FFT length: 65.263 ms.
> Best time for 3584K FFT length: 75.921 ms.
> Best time for 4096K FFT length: 86.565 ms.
> Best time for 5120K FFT length: 109.019 ms.
> Best time for 6144K FFT length: 133.111 ms.
> Best time for 7168K FFT length: 161.080 ms.
> Best time for 8192K FFT length: 182.895 ms.
> Best time for 58 bit trial factors: 3.260 ms.
> Best time for 59 bit trial factors: 3.329 ms.
> Best time for 60 bit trial factors: 3.328 ms.
> Best time for 61 bit trial factors: 3.591 ms.
> Best time for 62 bit trial factors: 3.657 ms.
> Best time for 63 bit trial factors: 4.290 ms.
> Best time for 64 bit trial factors: 4.878 ms.
> Best time for 65 bit trial factors: 5.907 ms.
> Best time for 66 bit trial factors: 6.943 ms.
> Best time for 67 bit trial factors: 6.893 ms.
> [Tue Jan 12 20:06:59 2010]
> Self-test 1024K passed!
> Self-test 1024K passed!
> [Tue Jan 12 20:22:25 2010]
> Self-test 8K passed!
> Self-test 8K passed!
> [Tue Jan 12 20:38:41 2010]
> Self-test 10K passed!
> Self-test 10K passed!
> [Tue Jan 12 20:55:07 2010]
> Self-test 896K passed!
> Self-test 896K passed!
> [Tue Jan 12 21:11:41 2010]
> Self-test 768K passed!
> Self-test 768K passed!
> [Tue Jan 12 21:26:49 2010]
> Self-test 12K passed!
> Self-test 12K passed!
> [Tue Jan 12 21:43:39 2010]
> Self-test 14K passed!
> Self-test 14K passed!
> [Tue Jan 12 21:59:01 2010]
> Self-test 640K passed!
> Self-test 640K passed!
> [Tue Jan 12 22:14:32 2010]
> Self-test 512K passed!
> Self-test 512K passed!
> [Tue Jan 12 22:29:44 2010]
> Self-test 16K passed!
> Self-test 16K passed!
> [Tue Jan 12 22:46:38 2010]
> Self-test 20K passed!
> Self-test 20K passed!
> [Tue Jan 12 23:02:27 2010]
> Self-test 448K passed!
> Self-test 448K passed!
> [Tue Jan 12 23:18:47 2010]
> Self-test 384K passed!
> Self-test 384K passed!
> [Tue Jan 12 23:34:16 2010]
> Self-test 24K passed!
> Self-test 24K passed!
> [Tue Jan 12 23:49:44 2010]
> Self-test 28K passed!
> Self-test 28K passed!
> [Wed Jan 13 00:04:44 2010]
> Self-test 320K passed!
> Self-test 320K passed!
> [Wed Jan 13 00:21:39 2010]
> Self-test 256K passed!
> Self-test 256K passed!
>
> Anyway what i did before the test was in the windows 7 display options i
> found something called powersave. This was turned on. I realized perhaps
> this was a bit of a problem as to why the crashes were occurring. I
> thought perhaps my pc wasn't getting enough power, or if it exceeded the
> limit because that was switched on. So i switched to performance. I
> think this has solved it. Im not sure yet but it hasn't crashed so far.
> The overheating i don't think is a problem. When using the Stress Tester
> it only reached 65C, and Core temperature was 51C. The fan speeds got to
> 2283, and the other fan was at 2647 (Not sure which fan was CPU fan or
> which was the power pack fan)
>
> If it crashes again though i will send it back as i have tried pretty
> much everything.
>
>
> Thank you all for your help in this matter. I will keep you updated as
> to how it goes.

Scrap that, nothing changed. Im sending it back i got no choice, ive
tried everything possible and it still crashes for no reason. I wouldn't
mind but my parents payed alot of money for that, and when i get it all
it does is crash.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Bad MBR
Next: Vadem ? (long shot)