Solved BSOD, System exception thread not handled when turning on

[chrism]

Hi!

Laptop: Toshiba Satellite P50-A, Windows 8.1

Lately, this week or so... I realized that my computer showed a BSOD with the "System Exception Not Handled", every time I turn on my computer for the first time in the day, then it restarted and apparently worked well for the rest of the day, I even turned-off the computer and started again (in the same day) and it didn't show the BSOD again, it only happens the first time I turn on it during the day. Kind of strange I think... so I'm getting worried about it. I've read that this problems are because some drivers are out of date, but I don't know what could be causing this... so I'd appreciate if you help me.


I have attached the requested files. Thanks for the help!


View attachment 54544
View attachment 54545

 

[blueelvis]

Hi Chrism & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

[B][SIZE=4]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
[/SIZE][/B]

This means that the system generated an exception or error which the Exception/Error catcher failed to catch which caused the system to bugcheck. Let's check the stack of the dump files which is almost same in every dump file -

3: kd> k
Child-SP          RetAddr           Call Site
ffffd000`208f31f0 fffff801`bf112039 Wdf01000!FxObjectHandleGetPtrQI+0x3b
ffffd000`208f3260 fffff801`c26b3033 Wdf01000!imp_WdfIoTargetStart+0x6a
ffffd000`208f32a0 00000000`00000000[COLOR=#FF0000][B][U] MijXfilt[/U][/B][/COLOR]+0x2033

The driver generating the exception is the "MijXfilt.sys" which is part of your Motion In Joy software for using the DS3 controller with the PC. Let's check it's date -

3: kd> lmvm mijxfilt
start             end                 module name
fffff801`c26b1000 fffff801`c26d3000   MijXfilt T (no symbols)           
    Loaded symbol image file: MijXfilt.sys
    Image path: \SystemRoot\System32\drivers\MijXfilt.sys
    Image name: MijXfilt.sys
    Timestamp:        Sat May 12 09:57:12[COLOR=#0000CD][B][U] 2012 [/U][/B][/COLOR](4FADE6A0)
    CheckSum:         00022009
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

And it is almost 2 years old.

I also see a Xbox Driver (xusb21.sys) dating 2009 which was known to cause issues. I would suggest you to update this driver as well along with the MotionInJoy software.

Let me know how it goes ^_^


-Pranav

 

[chrism]

Thanks for the quick reply Blueelvis and for the help!

I'll look for those drivers and see how it goes for the next couple of days, and I'll let you know.
Thanks (Y)

 

[blueelvis]

Thanks for the quick reply Blueelvis and for the help!

I'll look for those drivers and see how it goes for the next couple of days, and I'll let you know.
Thanks (Y)

Sure thing.

Let me know how it goes ^_^

-Pranav

 

[chrism]

So... I haven't got the BSOD again after updating the drivers, another thing that I did was to turn on the computer without the controller connected because before posting this, I never disconnected it.

Thanks Blueelvis, you're great (Y)

 

[blueelvis]

So... I haven't got the BSOD again after updating the drivers, another thing that I did was to turn on the computer without the controller connected because before posting this, I never disconnected it.

Thanks Blueelvis, you're great (Y)

Glad to hear that the issue has been solved ^_^

In case of any further problem, do not hesitate to post back ^_^