Now, if the bugcheck information is like 0x0000007a (0xfffff6fb800083f8, 0xffffffffc0000185, 0x0000000056040880, 0xfffff7000107fff8) you should do a complete harddisk check of the drive you were running the scan on. Look for bad clusters. My experience is that support will only perform a simple check of the disk, check your current network drivers and re-install the app and tell you to call back if the problem exists. OVER AND OVER AND OVER.
STOP Error 0x0000007A: KERNEL_DATA_INPAGE_ERROR
STOP error 0x7A means that the requested page of kernel data from the paging file could not be read into memory. STOP code 0x0000007A may also display "KERNEL_DATA_INPAGE_ERROR" on the same STOP message.
This could be a driver or disk controller problem. If there is no strong evidence to link it to a McAfee program I suggest you post to http://answers.microsoft.com/en-us/windows/forum/windows_7 and have the minidump from the BSOD zipped and ready for uploading when they ask for it.
To clearify the post. The issue was resolved and information only posted to give folks that search here, something to start with.
The bugcheck indicates an issue with the:
ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
DISK_HARDWARE_ERROR: There was error with disk hardware
Yes. It could be related to anything to do with the flow of information from the disk to the memory page. I am suggesting that people first do a FULL check of the disk to eliminate the common occurance of bad clusters before they go off in other areas. If the only issue you have is the system crashing when Mcafee is full scanning then a file issue would likely be the cause. Hours on the support line, running low level checks and re-installing and calling back only to explain and do this again and again will be avoided.
Thanks for your comments.