New
#41
and a second.
https://dl.dropboxusercontent.com/u/8816545/MEMORY1.7z
and a second.
https://dl.dropboxusercontent.com/u/8816545/MEMORY1.7z
a third and the second in a row with BUGCODE_USB_DRIVER as the stop error on USBPORT.sys
https://dl.dropboxusercontent.com/u/8816545/MEMORY3.7z
here's one with SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION, there were a few of these but I did not manage to save those dumps
https://dl.dropboxusercontent.com/u/8816545/MEMORY4.7z
Does anyone have any ideas as to what might be causing this or any additional diagnostics I could perform that might help me figure it out? I have no clue how to proceed without replacing my entire computer which is not a particularly appealing option.
In this case, the thread crash was trying to complete an IRP (I/O Request Packet), but the IRP had been corrupted, causing the crash. It is *again* in Chrome, so either Chrome itself is doing something screwy, or it could be the display driver (Chrome, like IE, is directx-accelerated on systems that support it). An easy way to check is to disable hardware acceleration in Chrome.
Kernel memory structure corruption can affect anything - the fact that the majority of the crashes contain Chrome as the crashing process, to me, means that either you only use a browser on your machine and do nothing else, or something to do with how Chrome interacts with the system is involved.
I've gotten two crashes since disabling hardware acceleration:
https://dl.dropboxusercontent.com/u/8816545/MEMORY5.7z
https://dl.dropboxusercontent.com/u/8816545/MEMORY6.7z
Both of these claim USBEHCI as the cause of the crash. EHCI is the controller for USB 2.0 devices, so... do you happen to have a USB device attached to a USB2 or USB3 port? They're at least consistent with each other in callstack and bugcheck codes right now.