As this happens on your ESX infrastructure, it more or less must be an issue with the alongside installed software.
Could you please post a list of ALL installed applications?
And if you have some special hardware to the VM attached, also list that.
I can only relate my experience of around 350 clients in several geographical locations. Our desktops and notebooks (all various Dell hardware) initially went from 8.7 -> 8.8 while running XP w/ no impact to USB keyboards or other hardware. All of our desktop PCs are deployed with USB or USB/bluetooth wireless keyboards & mice.
We later migrated our client PCs to Windows 7, again installing 8.8 with no hardware issues
Prior to this, I upgraded my last environment of around 700 PCs running XP sp3 on mixed source hardware from 8.7 -> 8.8 with no impact to hardware.Message was edited by: erase*.* on 6/5/12 1:30:31 PM CDT
The problem seems to be getting worse (also is now affecting vmware machines and laptops which are using the PS/2 keyboard driver). So far all indications are problems/conflcts with the mfehidk.sys driver and "something" on our systems.
Given that Robster and Bread Murder also had the issue with VSE 8.8, I'm wondering if possibly we can narrow down which file(s) are conflicting with mfehidk.sys.
Unfortunately all attempts to get a dump from Windows have not worked. The machine is locked up to the point that it won't respond to any input at all.
So it'll be an interesting troubleshooting operation.
You can take a memory dump from the vmware machine even if it's crashed. At least on vmware workstation that works for troubleshooting problems like this. Maybe that's a variant to get the memory dump.
it may be worth going through a series of selective startups with everything but McAfee and MS services and startup items disabled. If that boots w/o issue, enable things 1 at a time until you find the problem.
We've gone through all the troubleshooting with McAfee so far and the problem is definitely with their mfehidk.sys driver and "something" else on the machines. IF you disable all McAfee services, but leave the mfehidk.sys driver present the problem still occurs.
Sorry been off work for a few days. At the time we only had windows XP so cant say if it will happen on windows 7. BUT we do have Novell Client 4.91, do you think mfehidk.sys is clashing with this client?
At this point it's just a theory. Although I know people with 10,000 machines and VSE and Novell Client without any problems, so I could be all wet. We're trying on Windows 7 to see if we can run into the problem.
Based upon the ntblog.txt, the mfehidk.sys loads fairly early on and then some networking drivers and Novell Client drivers.
Assuming that the log stopped recording at the time it hosed the machine:
Service Pack 3 6 11 2012 09:04:46.375
Loaded driver \WINDOWS\system32\ntoskrnl.exe
Loaded driver \WINDOWS\system32\hal.dll
Loaded driver \WINDOWS\system32\KDCOM.DLL
Loaded driver \WINDOWS\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS
Loaded driver pci.sys
Loaded driver isapnp.sys
Loaded driver pciide.sys
Loaded driver \WINDOWS\system32\DRIVERS\PCIIDEX.SYS
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver dmload.sys
Loaded driver dmio.sys
Loaded driver PartMgr.sys
Loaded driver ACPIEC.sys
Loaded driver \WINDOWS\system32\DRIVERS\OPRGHDLR.SYS
Loaded driver VolSnap.sys
Loaded driver atapi.sys
Loaded driver ahcix86.sys
Loaded driver \WINDOWS\System32\Drivers\SCSIPORT.SYS
Loaded driver atiide.sys
Loaded driver iaStor.sys
Loaded driver nvgts.sys
Loaded driver disk.sys
Loaded driver \WINDOWS\system32\DRIVERS\CLASSPNP.SYS
Loaded driver fltmgr.sys
Loaded driver NCRecognizer.sys
Loaded driver NCFilter.sys
Loaded driver NCUncFilter.sys
Loaded driver mfehidk.sys
Loaded driver PxHelp20.sys
Loaded driver KSecDD.sys
Loaded driver Ntfs.sys
Loaded driver NDIS.sys
Loaded driver csacentr.sys
Loaded driver csafile.sys
Loaded driver csareg.sys
Loaded driver csanet.sys
Loaded driver nicm.sys
Loaded driver Mup.sys