Intermittent BSODs with no obvious commonality

cluberti said:

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.

Several: a Logitech G15, a Microsoft Intellimouse, a Madcatz TE, and a pair of cheap Gear Head speakers that I think I got at best buy whose purchase actually seems to coincide with these problems starting now that I am thinking about it specifically.

Here's another crash with Chrome not even running though at this point the speakers seem the obvious culprit (I don't have another option so I can't really swap them out right now) though I am not sure how much you can narrow down the device from these.

https://dl.dropboxusercontent.com/u/8816545/MEMORY.7z (still uploading so give it a few minutes)

It was not the TE or the speakers as it turns out, with both completely removed I still got this BSOD:

https://dl.dropboxusercontent.com/u/8816545/MEMORY3.7z

I found an old ps/2 keyboard I am using to eliminate that option but I don't know if I have any old mice. I am not actually sure if it is a USB device that is causing these crashes I am just trying to proactively troubleshoot.

and shortly after posting that I get another crash, so if it is a USB device it would theoretically be the mouse but I am not positive that it is in fact that

https://dl.dropboxusercontent.com/u/8816545/MEMORY4.7z

Another BSOD with no USB devices aside from the mouse, IRQL_NOT_LESS_OR_EQUAL

https://dl.dropboxusercontent.com/u/8816545/MEMORY5.7z

and another, MEMORY_MANAGEMENT

https://dl.dropboxusercontent.com/u/8816545/MEMORY6.7z

What does a memory management error indicate if my memory passed memtest cleanly? These messages still seem really disparate

cluberti said:

I took a look at the last one, and it was yet again in Chrome, but a 1a with a non-documented error code. I hate to say it, but I'm starting to think there's some hardware issue here.

I'd be fine with a hardware issue if I could actually figure out which piece of hardware it is

Golden said:

We have seen 0x124's caused recently by running a beta version of Chrome. I wonder if this is similar? What version of Chrome is being run?

40.0.2214.91, latest stable (which is what I always run)