A7N8X-X causing to reboot

[amusedfrog]

ive recently made a new system with a A7N8X-X mobo, AMD K7 Athlon XP 2600+ and 512 DDR 400Mhz, but whenever i start up the system it seems to immediatly reboot as windows starts to load or reboots without warning within a few minutes of using windows. any help or suggestions as to why this might be would be appreciated.

N.B ive tried numerous different bios configurations but nothing seems to prevent it.

[richt]

Hey I've got similar problems Random reboots on an A7N8X-X with Athlon 2500+ and 2x512MB Valueram.

Seems to happen at all clock frequencies. Last time around, the machine wouldn't even post. I had to reset the cmos. Now it will hang at IDE detection.

On XP, I get blown from windows to POST quite often.

Any ideas. I'm now thinking maybe it is bad ram, or my overclocking hurt it somehow. I have a GeForce 5900SE from evga and a promise raid controller.

I've also noticed that ever so often I do get nwix.exe failing for no particular reason, so I'm thinking bad memory.

[garnet_abx]

Run Memtest to check for memory errors.

[vernon]

Hello, I have the same problem but my motherboard is an Asus K8S-MX running an AMD 64 3000+. Today I got kicked out 3 times while trying to update my antivirus. I dont think it is related because it was able to update later. What should I do? Is there a fault with Asus AMD motherboards in general?...please help!!!

[Bofinn]

I think you might get better answers by posting this question in the A64 zones instead of this thread...

[noorman]

Originally Posted by amusedfrog

ive recently made a new system with a A7N8X-X mobo, AMD K7 Athlon XP 2600+ and 512 DDR 400Mhz, but whenever i start up the system it seems to immediatly reboot as windows starts to load or reboots without warning within a few minutes of using windows. any help or suggestions as to why this might be would be appreciated.

N.B ive tried numerous different bios configurations but nothing seems to prevent it.

check your PSU voltages, check temps, check seating of CPU and CPU-heatsink.

run MemTest and try more relaxed memory timings ...

come back with Voltages and Temps and some more on your HW

[noorman]

BUMP

[noorman]

BUMP

[Zafiro]

Hi, this is my first post.

im having the same problem. all was working ok for 1 year, no overclocking.

my pc:
asus a7n8x-d rev 2.0, bios up to date ver. 1008 (audio 5.1, 2 nic's, 1 modem, 2 firewire, 6 usb, sata raid controller)
512mb (1dimm) pc4000
athlon xp2000@1.6ghz (133mhz x 12.5)

30gb ide quantum fireball
160gb SATA western digital

16x dvd-rw burner
10x dvd reader

sound blaster 5.1, tv card.......... nothing else.

the bios status:

mobo temp: 21C / 69F
cpu temp: 50C / 122F

vcore: 1.60v
+3.3: 3.32v
+5: 4.83v
+12: 11.77v


i think it could be a power supply issue, what do you think? i will try to measure the +5 and +12v while running.

thanks
Jorge.

[noorman]

Originally Posted by Zafiro

Hi, this is my first post.

im having the same problem. all was working ok for 1 year, no overclocking.

my pc:
asus a7n8x-d rev 2.0, bios up to date ver. 1008 (audio 5.1, 2 nic's, 1 modem, 2 firewire, 6 usb, sata raid controller)
512mb (1dimm) pc4000
athlon xp2000@1.6ghz (133mhz x 12.5)

30gb ide quantum fireball
160gb SATA western digital

16x dvd-rw burner
10x dvd reader

sound blaster 5.1, tv card.......... nothing else.

the bios status:

mobo temp: 21C / 69F
cpu temp: 50C / 122F

vcore: 1.60v
+3.3: 3.32v
+5: 4.83v
+12: 11.77v


i think it could be a power supply issue, what do you think? i will try to measure the +5 and +12v while running.

thanks
Jorge.

You are running WindowsXP or Windows2000 ...

There 's a setting in these Windows versions that is set [default] to reboot when there is a BSOD (blue screen of death) event.
You can switch this off by going in the Properties of My Computer and then to the Advanced TAB and at the bottom 'Startup and Recovery'.
There you need to remove the tick before "Automatically reboot".


This will give you the chance to see what happens next time; the BSOD will stay up, the computer will NOT reboot and you have the chance to make notes of the message that the BSOD contains; you have to make note of the number sequence and of the text that appears beneath it.

Together they can give you a good clue to what is going wrong.

It could well be possible that your system got unstable through a new but unstable driver [it still happens]


If you can give us such an error message (or more than 1) we will be able to help you (in most cases) ...

[Zafiro]

Originally Posted by noorman

You are running WindowsXP or Windows2000 ...

There 's a setting in these Windows versions that is set [default] to reboot when there is a BSOD (blue screen of death) event.
You can switch this off by going in the Properties of My Computer and then to the Advanced TAB and at the bottom 'Startup and Recovery'.
There you need to remove the tick before "Automatically reboot".


This will give you the chance to see what happens next time; the BSOD will stay up, the computer will NOT reboot and you have the chance to make notes of the message that the BSOD contains; you have to make note of the number sequence and of the text that appears beneath it.

Together they can give you a good clue to what is going wrong.

It could well be possible that your system got unstable through a new but unstable driver [it still happens]


If you can give us such an error message (or more than 1) we will be able to help you (in most cases) ...

I'm using winXP sp2.

i cant turn off auto-boot after BSOD because the BOSD is before login.

the first error was that when i was using windows normally, windows rebooted w/o any errors, then, when loading SO after boot, the error was "ntfs.sys is damaged or corrupted".
after a few reboots, that message disapeared but windows hangs just before/after login (randomly).

i changed the power supply and nothing changed, BUT, i used another old-ide drive to reinstall windows and installation was succesfull. im at work now, later i will post again.

thanks!!
Jorge.

[noorman]

Originally Posted by Zafiro

I'm using winXP sp2.

i cant turn off auto-boot after BSOD because the BOSD is before login.

the first error was that when i was using windows normally, windows rebooted w/o any errors, then, when loading SO after boot, the error was "ntfs.sys is damaged or corrupted".
after a few reboots, that message disapeared but windows hangs just before/after login (randomly).

i changed the power supply and nothing changed, BUT, i used another old-ide drive to reinstall windows and installation was succesfull. im at work now, later i will post again.

thanks!!
Jorge.

You can boot from your CDROM (WinXP) and go into the Recovery Console.
Log in.
Then you 'll get a prompt (like in a DOS-box/Command-box).
type there chkdsk :c /r
this will do a diskcheck, repair files and track and deal with BAD clusters on that disk ...
Maybe this will do the trick.

Can you still get into the BIOS/Setup ?

[Zafiro]

Originally Posted by noorman

You can boot from your CDROM (WinXP) and go into the Recovery Console.
Log in.
Then you 'll get a prompt (like in a DOS-box/Command-box).
type there chkdsk :c /r
this will do a diskcheck, repair files and track and deal with BAD clusters on that disk ...
Maybe this will do the trick.

Can you still get into the BIOS/Setup ?

yes i can get into bios. i updated to rev 1008.

thanks for the "chkdsk c: /r" , i will try it. thanks!!!

[Kage]

I had the same problem with my A7V333-X and my A7N8X-E DLX an Athlon XP 2700+ and a 512MB DIMM of Samsung DDR400. In the case of the A7V333 I had to knock the clock to 1.6GHz at a FSB of 266MHz. For the A7N I merely had to make sure that the memory was set to 400MHz.

[noorman]

Originally Posted by Zafiro

yes i can get into bios. i updated to rev 1008.

thanks for the "chkdsk c: /r" , i will try it. thanks!!!

You can run chkdsk :c /r also in a DOS-box (command line [black] window) in Windows ...

If the partition is in use by any program, you 'll be asked if it can be checked after the next (re)boot; answer yes (Y)

Reboot ...