Vegas 12 makes windows 7 freeze??

marcel-vossen wrote on 8/24/2015, 1:57 PM
Today I have been experiencing very strange behavior with my windows 7 machine, with a specific Vegas 12 project. I just added 2 clips, when my machine started to freeze all the time (even the mouse would not move) and the eventviewer is full of errors like:

Reset to device, \Device\RaidPort0, was issued.
Request to physical disk 0 is timed out.
The device, \Device\Harddisk5\DR5, is not ready for access yet.

etc etc almost all drives are mentioned at some point

The only remedy when it happens is rebooting, but the strange thing is , nothing happens when I work in other programs in win 7, only when I start Vegas 12 and open this project again the errors occur. Even other Vegas 12 projects seem to work fine.

I even went out and bought a new SSD drive because at first I though my boot drive was dying, but after checking some thing, it looks like only Vegas causes this problem??

Is this even possible? That a program can cause windows drives to fail?

Did anybody have this before?




Comments

astar wrote on 8/24/2015, 2:54 PM
One of your drives is failing in the RAID set, or your controller is failing to maintain proper communication with one of the drives. That could be controller failure or cable. More than likely HDD failure, as HDD failure will pause the system as it attempts to wait for the data from the HDD.

If you have a raid controller that supports SMART, you could use a utility lke Speccy or others to see what SMART is reporting.

If it is not the above, I would make sure you have the latest chipset or drive controller drivers from your manufacturer.
marcel-vossen wrote on 8/24/2015, 3:49 PM
Thanks, do you know if the number of a physical drive that is mentioned in the eventlog is the same as in the drive manager in windows 7?

It just happened again, and when I go back to the very first warning in the system log, the point where it starts, it always says:

Request to physical disk 0 is timed out.
Reset to device, \Device\RaidPort0, was issued.

After that, hell breaks lose and all kinds of disk errors occur:

The device, \Device\Harddisk5\DR5, is not ready for access yet.
Physical disk 7 is plugged out.

Can I assume that physical disk 0 is my bootdisk, this is a Samsung EVO 840 SSD drive and it has the name disk 0 in the disk manager? Can an error on this disk trigger the rest of the errors? In the end, some of my data disks are not in the explorer anymore, I need to reboot the system to get them back.

Maybe I should try to replace the SSD bootdisk?

Marcel

astar wrote on 8/24/2015, 5:34 PM
No you can not assume Disk0 is your boot disk. Disk order has to do with where the drives were plugged in to the controller, and install selections. On my system SSD boot is disk1, and spinning storage that used to be a boot disk is disk0. I later upgraded to an SSD and reinstalled the OS.

Speccy can give you in sight in a simplistic fashion to the drive number. Under Storage > Partition ID - Disk# and partition#.

Opening an admin command prompt and running "Diskpart" > then "list disk" will show you a table as well. "List volume" will show you your partitions. This should all be the same as Disk Management.

With the power off on your system and unplugged, I would go in and reseat your cables, and raid cards (if any.) Then see if the problem persists, and then move to trying to replace cables, and then hardware. If the volume is storage and not boot, try moving the device to another controller interface. Moving the boot to another interface can be done, be will require expert boot configuration changes.

If you have a bunch of drives on your system, including like DVD or whatever. temporarily disconnection the extra drives and testing the system with no other devices for the errors. If you have RAID configured, do not test in this fashion. Note where disks are plugged in, so you can return them to the correct plugs. Sometime conflicts can occur with devices that are failing/acting badly on other interfaces.

If the device is a laptop, you can pretty much only reseat the HDD, and make sure the cooling fins/duct work are clean.

marcel-vossen wrote on 8/27/2015, 6:33 AM
Thank you very much Astar!

I checked with diskpart like you said, and it lists my disks in the same way that the disk manager does.

In the manager disk0 is not my boot disk, it is a new large 4Tb storage disk.

However what I meant to ask was, if physical disk 0 is mentioned in the eventlog, if this is the same disk0 ?
That would mean that the large storage drive is causing an error first?

I also did a check with Crysteldiskinfo, all disks seem to be fine.

To make sure my boot SSD was not the problem, I purchased a new SSD, made an image of the bootdisk on the new disk, exchanged the disks and worked with the new one for 3 days without any problems. So I THOUGHT I solved the issue....

Now today, trouble started again, so after all it was not the SSD ... :(

Since the troubles always seem to start with this error, I de-installed this Marvell driver that is mentioned here:

Source: mvs91xx
Request to physical disk 0 is timed out.

The system seems to work fine without it, so hopefully it will be stable now.