win2k bugcheck with epia m933

[graybeard2025]

win2k bugcheck with epia m933

[graybeard2025]

My epia m works great except for win2k bugcheck error, event id 1001, which causes an immediate reboot. This bugcheck occurs anytime I try to backup the c drive to either a usb2 drive, a firewire drive, or a networked drive on another local networked win2k PC. I have tried 3 different backup programs, Stomp BackupMyPC, Novabackup version 7, and the backup program provided with win2k. All give the same bugcheck error and reboot.  Yet, all three backup programs work fine when the backup target is a second IDE disk instead of an external disk. Any ideas anyone?

My system is stock Epia M933 with win2k sp3 with all current upgrades, 256MB Crucial memory, 300watt ATX power supply, new Via bios. Both external drives have their own power.

[Connor]

It could be that to access that device it needs to use an instruction not supported by the C3 chip
like CMOV and that if you could have an identical board with a Celeron processor it could work fine.

Could you just do it to the IDE drive and copy it across afterwords?

[Gamer]

I ran a couple of tests for you. I tested MS Backup on 2K server and workstation without a problem. I backed up to a Windows share on another machine. I used both an EPIA 800 and a 9000. If you can be more specific on what you are doing, I'll try to replicate your problem.  

[graybeard2025]

I quess I wasn't clear enough. MSBackup to a normal IDE disk file works fine. But when I try to select a file location on either a usb2 harddrive or a firewire harddrive attached to the apprpriate Epia M port for the backup to be stored on, the backup programs will backup several hundred megabytes, then crash with a  reboot. I currently do my backup to my second ide drive, then use normal copy to move it to the external devices successfully, but my real objective is to determine any limitations of my Epia M as a small file server for the rest of my home network. About CMOV I don't know enough to comment except to observe several hundred megabytes are copied before the reboot occurs.

[graybeard2025]

Gamer is right. I was mistaken about backup to a network drive. It does work when you use a win2k workstation instead of a win98se. But my main issue remains: I can't backup to the EPIA M firewire port or to the USB port. Furthermore, if the firewire drive is moved to the win2k networked PC, I can backup up to that drive attached there successfully using it as a network share. It still looks like some problem with the EPIA USB2 and Firewire ports.

[graybeard2025]

Latest test is disappointing. I repeated the msbackup to a usb2 drive, and it failed after about 350 MB. I then repeated the test holding a 10 inch room electric fan above the Epia M board which is simply mounted on a board with standoffs, no case. The room temperature is about 70F.  This backup completed perfectly. So I seem to a a heat-related problem on a board that I understood was inherently cool and quiet. Is anyone out there in a position to repeat this test with either a firewire or usb2 external drive? The backup is only about 1.2 gig and the USB is heavily used for about 15 minutees or so. Without the external cooling, the USB2 drive backup crashed in about 3-5 minutes.