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-bs...ng-dolphin. This person also had issues with OHCI USB Miniport Driver.
I have posted my Who Crashed summary below
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-bs...ng-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.