Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tunetyme]

I realize this is a problem with Microsoft and not J River or unRaid.

If I try to go on the server with Windows ExplorerI I can create a new folder.  When I try to give the folder a name it cause the system to reboot.  No error messages.  The same is true if I try to copy or move a folder.  I am hardwired connected to the server through a D-Link router.  I have check my system with Malware Bytes and Avast.  It is clear.  I have also
used Nirsoft Shellexview to identify all the addons to Windows Explorer.  I disabled all the non-Microsoft addons and I still have the problem.  Permissions are set to read write execute for all.

I would really appreciate any suggestions.

When I try to edit a field and update a file in MC 16.100 the system crashes.  I've tried for two days to log on to Microsoft to post a question but I can't seem to get to the login page...

This is why I am trying to get away from MicroCrap.  Another SNAFU.

Tunetyme

[tunetyme]

bump

[Matt]

This sounds like a hardware problem to me.  I wouldn't blame Microsoft (or JRiver).

Could you try a local hard drive, so unRaid is out of the loop?

Have you done a system memory test?  I've had good luck running four copies of this and splitting the memory between them.

[MrC]

Since all the crashes are reported as being related to only immediate disk write/flush activity, I'd work the following order:

1) force full file system checks on all disks in question
2) if raid, run full diagnostics on array
3) test each disk individually, start with SMART data and quick tests
4) ensure controller firmware / software is up to date and no issues are known for model/brand
5) ensure motherboard and associated hardware drives are up to date

Things that might be wrong?  Corrupt file system, faulty disk, faulty cable, faulty controller, faulty motherboard.

A memory test is an excellent idea too (yet I'd expect other odd, random problems appearing too if memory were the culprit).

[Mr ChriZ]

It's also worth taking a look in event viewer in admin tools, it's possible something will have been recorded before it restarted....

[tunetyme]

Thanks for your suggestions.  I decided to reload XP via the repair method.  It took all day with doing the all updates from Microsoft.  It solved the problem and everything works great now.

Tunetyme