ContributionsMost RecentMost LikesSolutionsRe: Blue Screen Caused by virtfile.sys Thank Mihty Mouse, uninstall of this hotfix is OK now. Uninstall doesn't work if CD BEWS12.5 is not in the box. I have put the install CD and uninstal of this hotfix works fine. And now i can run my backup jobs ok with GRT enable on Storage Group on Disk media. Thank you for all. But i'm little desapointed about Symantec Guys because i receive no help from Symantec people... Re: Blue Screen Caused by virtfile.sys Hi Mighty Mouse and thank you. But unfortunatly i try to uninstall hotfix 310648 but it doesn't work. I got: "Error 1325.Live Update is not a valid short file name" Re: Blue Screen Caused by virtfile.sys After i put back virtfile.sys V 1.0.114.125 in C:\Windows\System32\drivers...the system doesnt crash anymore, but i have still big problem during Storage group backup with GRT. Jobs failed because file VirtApi.dll is missing. But i check and the file is present in 2 folders: 1. D:\Program Files\Symantec\Backup Exec\VirtApi.dll (111 KB, V1.0.114.125) 2. D:\Program Files\Symantec\Backup Exec\x86\VirtApi.dll (91.8 KB, V1.0.114.125) I can also not browse the content of mailboxes in restore job wizrad.I got same error message (VirtApi.dll is missing...) If anyone as an idee because my backup are not running because i have put this 5 hotfix.....!? help... help... Re: Blue Screen Caused by virtfile.sys Hi, i have same problem on bews 12.5 w/SP1 after installing hotfix 317412, 317920, 317966, 310648, 318828 On liveUpdate 15.02.2009...! I have blue screenwhile running Backup-to-Disk jobs for Exchange 2007 w/SP1 from passive node of CCR cluster on Windows 2008 x64 nodes. But i dont know wich one is it causing the problem and i have at this time no solution. I ran BEWS 12.5 on Dell PE2950 with 16GB RAM I try to replace the virtfile.sys CASO communication stalledWhen the Central admin server submit a job to a media server the job start and run, during the running process we can see the job running, but when on the media server the job is completed the CASO server is waiting and after a timeout we have the error "communication stalled" and the job become on "hold" state on the CASO server. On the media server the job is completed 100%. The problem is that all the job become on hold state after a run. CASO server and media servers are W2K3 SP1 with BackupExec 10.