Mayflash Dolphin Bar BSOD usbochi.sys

[Harkon]

OS Windows 10
Dolphin Build 4.0.7777

So I just got myself a Mayflash Dolphin Bar off ebay so I can hook up my Wii remotes a lot easier. As it was kinda annoying to use the wii's sensor bar. However after maybe 5-10 minutes of playing I get a blue screen of death saying something has gone wrong with usbochi.sys. I'm honestly not quite sure what is going on and wondered whether anyone else has ever had anything similar and know of a way to potentially solve this?

Note: This did not happen to me before using the Dolphin Bar, thus I am sure that it must be the culprit somehow! Could it potentially be faulty?

I did have a brief google search but so far no luck. The previous post that I found that seems to be the same issue is https://forums.dolphin-emu.org/Thread-bsod-while-playing-dolphin. This person also had issues with OHCI USB Miniport Driver.

I have posted my Who Crashed summary below

Quote:On Mon 21/09/2015 7:31:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092115-17593-01.dmp
This was probably caused by the following module: usbohci.sys (usbohci+0x2D83)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8013FB12D83, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\usbohci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: OHCI USB Miniport Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

[taloon]

Hey man, I had this problem really badly too at one point... funnily enough I thought I solved the problem but sadly, I was still getting it.

One thing I've noticed when using the DolphinBar for any sort of extended period of time, is that at the ends of the bar (where the IR lights are located) I noticed it getting quite hot...

It would work for a little while after a clean reboot and after not being plugged in for a bit, but after some extended use, would start disconnecting the remotes and then eventually BSODing on me.

I'm not sure if the heat thing is causing it to BSOD, but I'm pretty sure that may be SOMEHOW related.

Do a test, next time you get a BSOD, touch the ends and see how hot they are, unplug it, let it cool down, then try again and see how long it goes for before it does it again. Will be a good test!

[Harkon]

(09-23-2015, 02:20 PM)taloon Wrote: Hey man, I had this problem really badly too at one point... funnily enough I thought I solved the problem but sadly, I was still getting it.

One thing I've noticed when using the DolphinBar for any sort of extended period of time, is that at the ends of the bar (where the IR lights are located) I noticed it getting quite hot...

It would work for a little while after a clean reboot and after not being plugged in for a bit, but after some extended use, would start disconnecting the remotes and then eventually BSODing on me.

I'm not sure if the heat thing is causing it to BSOD, but I'm pretty sure that may be SOMEHOW related.

Do a test, next time you get a BSOD, touch the ends and see how hot they are, unplug it, let it cool down, then try again and see how long it goes for before it does it again. Will be a good test!

I don't think it could be possible to be an overheating problem, as the shortest time I had it on was less than a minute before a crash. That being said I will definitely check how hot the bar is, just to be on the safe side!

[DakuShinobi]

(09-25-2015, 12:57 PM)Harkon Wrote:

(09-23-2015, 02:20 PM)taloon Wrote: Hey man, I had this problem really badly too at one point... funnily enough I thought I solved the problem but sadly, I was still getting it.

One thing I've noticed when using the DolphinBar for any sort of extended period of time, is that at the ends of the bar (where the IR lights are located) I noticed it getting quite hot...

It would work for a little while after a clean reboot and after not being plugged in for a bit, but after some extended use, would start disconnecting the remotes and then eventually BSODing on me.

I'm not sure if the heat thing is causing it to BSOD, but I'm pretty sure that may be SOMEHOW related.

Do a test, next time you get a BSOD, touch the ends and see how hot they are, unplug it, let it cool down, then try again and see how long it goes for before it does it again. Will be a good test!

I don't think it could be possible to be an overheating problem, as the shortest time I had it on was less than a minute before a crash. That being said I will definitely check how hot the bar is, just to be on the safe side!

I hate to revive an old thread, but I've been fighting this issue for a couple of months now. It worked fine when I got it but started going out of whack a little while ago. I'll too test its overheating tonight but I was wondering if you ever found this to be the issue or if you got a fix for it.

I've only ever seen the issue mentioned a couple times and none had a viable fix that worked.

[Harkon]

(10-23-2015, 11:55 PM)DakuShinobi Wrote: I hate to revive an old thread, but I've been fighting this issue for a couple of months now. It worked fine when I got it but started going out of whack a little while ago. I'll too test its overheating tonight but I was wondering if you ever found this to be the issue or if you got a fix for it.

I've only ever seen the issue mentioned a couple times and none had a viable fix that worked.

I never managed to figure out what was causing the problem, that being said I did give up pretty quickly. I am going to be building a new computer in the next week, so I will test the bar then to see if it also crashes the new computer. I'll put up my results here after that.

My guess is that it may be an issue with my current computer, but if it also crashed the new desktop it may be a faulty dolphin bar.

[Amazeballz]

I also receive these BSOD's.

kmode_exception_not_handled (usbohci.sys)

I've literally been losing sleep trying to get to the bottom of this. The ONLY time I've ever gotten this is with the Mayflash Dolphin Bar plugged in and set to mode 4. It's clear to me based on other examples and my own findings, that this bar is at least partially responsible. I might suggest Dolphin Emu may be equally as responsible, however, I remember at least one occasion where my PC BSOD'd while not running the program. Though, I can't confirm with certainty that I hadn't recently started the emulator in the same session.

There are a lack of complaints about it, which leads me to believe that either a lot of you are not using the bar in mode 4, are not reporting the issue, or it's specific to the Firmware version. I currently have "Ver05" (the 9/2/2015 update) installed, which I updated to from Ver04. I'd like to roll back to see if it's faulty firmware, however, the only other version I can find anywhere is Ver02. I was hoping to find 3.

If anyone still has Ver03, please upload it!

Meanwhile, I'll test Ver02, but judging by other posts I've read, TR wasn't supported until Ver03? Guess I'm about to find out.

[KHg8m3r]

Did you try the latest firmware that was released on September 2? http://www.mayflash.com/Support/Download/

[Amazeballz]

Grr. Just realized I can't roll back unless I edit the versions with hex... which I haven't done before. Should be fun.

Yes, that is the update I have. So I guess one could say I have "Ver05", though it's not labeled as such. I'll edit my previous post if possible to reflect that.

[mbc07]

About firmware, you're right, you can't downgrade it, just upgrade, but don't waste your time, downgrading your DolphinBar won't fix this. This problem is often related to USB ports, if you're connecting it to an USB 3.0 port, try changing to an USB 2.0 or vice versa, if you're using extension cords, try plugging the bar directly...

[Amazeballz]

(11-04-2015, 05:39 AM)Jhonn Wrote: About firmware, you're right, you can't downgrade it, just upgrade, but don't waste your time, downgrading your DolphinBar won't fix this. This problem is often related to USB ports, if you're connecting it to an USB 3.0 port, try changing to an USB 2.0 or vice versa, if you're using extension cords, try plugging the bar directly...

USB 3.0 ports are blue correct? If so, I don't have any. As far as I know, I just have the black USB 2.0s and the red ones that have a higher power output, which I've tried in both.

Side note: I sure wish Mayflash had better customer support beyond an email system. Some technical support F.A.Q. would be cool.

btw, my motherboard is the ASUS M4A79XTD EVO