another odd crash from 2.9.38

Hi guys,
I have this brand new box crashing on me,
after reboot this error will show up:

I’m using IDE to CF adpter with 512mb memory kingstone
intel cpu 2.8 celeron and 256 memory , asus p5pe mainboard
with gigabit network card.

I have four of the same setup installation since last week,
without these kind of odd problem, I had to reinstall the
mikrotik many times, even changing the memory card, but don’t
know what else to do and what could be the cause.
I can’t really keep changing all hardware without knowing
whats the problem first.

just one odd thing about it is that the box will shut down by itself
and have to manually turned up.
the cpu temperature is at 40 degree which looks good.

thanks

ok,
the box doesn’t allow winbox connection with this oddliest error:

mac-telnet stil works

send these pictures, along with a supout.rif file to support

I already did that.
but I cant connect to the board to make support.rif file

now I can ping, but now telnet, mac-telnet, ftp, winbox, ssh and all other does not work.

what shall I do?

Thanks

Have you replaced RAM? or Processor?

nope… I have not tried that. but I’ll give it a shot tomorrow…

I’ll have to wait hours for this error and not even sure whether it was fixed or not.

I’ve changed RAM/CPU/ Memory card to Sandisk
no luck yet

sometime Mac-Telnet works and sometimes it does not

however even if I make support.rif file I can’t ftp to box. how can I acquire that?

ftp result:

Status:	Waiting to retry... (1 retry left)
Status:	Connecting to 10.1.1.18 ...
Error:	Unable to connect!

ok,
ftp comes up with this now:

Status:	Connecting to 10.1.1.18 ...
Status:	Connected with 10.1.1.18. Waiting for welcome message...
Response:	220 Athen_A FTP server (MikroTik 2.9.38) ready
Command:	USER admin
Error:	Disconnected from server
Error:	Unable to connect!

telnet comes up with this:

C:\Documents and Settings\Administrator>telnet 10.1.1.18
Connecting To 10.1.1.18...Could not open connection to the host, on port 23: Con
nect failed

C:\Documents and Settings\Administrator>

Change the motherboard and solve the issue :laughing: .

I just unplugged the CF and plug into my own pc, the same TCP error happened,

it means some services are crashing or not starting in the boot. but the screen looks normal…

I changed the CF the TCP error didn’t happened.

but still getting this error with winbox:

Could not fetch index from 10.1.1.18, (port 80): Not found

I’ve sent the support rif file after that but no reply yet.