Description of problem:
Booted a viostor win2012 guest with 82576 VFs assigned. Downloaded driver from intel mainpage:
https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21694&lang=eng&OSVersion=Windows%20Server%202012*&DownloadType=Drivers
and placed driver to a ftp server. Win2012 crashed after running PROWinx64.exe by clicking the driver file at ftp server. Sometimes before crash, windows complaint not enough disk space. but actually, there were 17G free space.

Version-Release number of selected component (if applicable):
qemu-kvm-1.4.0-1.el7.x86_64
3.9.0-0.rc5.46.el7.x86_64
virtio-win-prewhql-58

How reproducible:
100%

Steps to Reproduce:
1. install win2012 to ide disk while with a virtio disk attached
2. install -58 viostor driver and shutdown guest
3. boot win2012 with virtio interface as well as with VFs assigned
4. install VF driver by running driver stored at ftp.

  
Actual results:
win2012 crashed.

Expected results:


Additional info:
1. IDE doesn't trigger this issue
2. Downgrading to virtio-win-prewhql-55 doesn't reproduce this issue, marking Regression

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: srv*c:\mss*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
Machine Name:
Kernel base = 0xfffff800`d506e000 PsLoadedModuleList = 0xfffff800`d5338a60
Debug session time: Tue Apr  2 18:53:38.110 2013 (UTC - 7:00)
System Uptime: 0 days 0:02:33.000
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
...............
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EF, {fffffa8003f85980, 0, 0, 0}

Probably caused by : csrss.exe

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: fffffa8003f85980, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000