BSOD while idle

Dragsooth · 26 Feb 2014

Received three BSOD this past week. Two were when the computer was idle and one was while I was installing a driver to activate my PS3 controller on the PC. I don't think it was the driver.

Random long codes: 0x0000010D (0x0000000000000005, 0x0000000000000000, 0x00000000000D1202, 0xFFFFFA8007BA91E0)

Dunno if those are necessary, but meh. Might be worth noting that my graphics card is overclocked, but it's completely stable and done with AMD's software.

Attachments include the real info.

(Also, the "D" in the 0x00000D1202 code 'could' be a "0". I have bad handwriting and it was dark)

Arc · 26 Feb 2014

Hi Dragsooth,

There are two different BSODs there.

One is stop 0x10D, caused by MotioninJoy simulate Xbox 360 controller (virtual Xinput device).

Code:

BugCheck 10D, {5, 0, 1202, fffffa8007ba91e0}

*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )

Followup: MachineOwner
---------

And it is very common with the driver version that you have installed. Uninstall it, and install an earlier one. Hopefully this particular issue will be over by this action.

The other issue is stop 0x116, a display/graphics related issue.

Code:

BugCheck 116, {fffffa800a8c9010, fffff88003a0bdbc, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+bdbc )

Followup: MachineOwner
---------

Uninstall your installed version of the display driver.

How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

Drivers - Clean Left over Files after Uninstalling

Then install version 13.9 WHQL only.

Previous AMD Catalyst? Display Drivers

Lately we have seen that the 13.9 WHQL is most stable itself.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.

Dragsooth · 26 Feb 2014

I uninstalled the drivers and made sure there were no leftovers with that tool. I don't feel comfortable downgrading my driver, but luckily there was a new update!

I couldn't really figure out the Power Supply Calculator, it looks quite intimidating for a layman. I figured if I passed the Fur Mark while overclocked, then it has enough power... dunno if that's true though.

Didn't really see any files to post for the Fur Mark and the link you sent said nothing of the sort, but the temperature finally leveled out at 73c. There was a minor artifact, looked like a windows XP mouse drag line on a desktop. That means something's up, perhaps decrease the power? I'm overclocked to max with AMD CCC, but power is up 10%. I didn't really think the BSOD had to do with my overclock, especially since the temp is fine, the fan is fine, and nothing is freezing.

Arc · 26 Feb 2014

The system is really cool. WoW!

Overclocking causes hardware instabilities sometimes. If the stop 0x116 BSOD continues to occur even after altering the display driver, then you may need to test the system with the stock hardware settings.

Dragsooth · 27 Feb 2014

Alright, so we've troubleshot it down to that. If it does BSOD again, it's my overclock. If it does do that, what should I decrease in the overclocking settings?

Dragsooth · 27 Feb 2014

Arc said:

The system is really cool. WoW!

Overclocking causes hardware instabilities sometimes. If the stop 0x116 BSOD continues to occur even after altering the display driver, then you may need to test the system with the stock hardware settings.

So I got another BSoD, this one happened after I was fiddling with CPU overclocking xD

Arc · 27 Feb 2014

Code:

BugCheck 101, {31, 0, fffff88002f65180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

Overclocking can be blamed for it.

Set all the hardware components viz. RAM, CPU and GPU to default/stock settings.

Dragsooth · 05 Mar 2014

Seems I've blue screened again and I've disabled my OC before it too. I've started another thread on another issue, but now I think they're related, I'll post a link. Display driver AMD has stopped responding and has recovered

Arc · 06 Mar 2014

I guess you are using the 13.9 WHQL as suggested earlier?

If so, try any other version of display driver, and see if the situation is the same or not.

If it happens with multiple versions of the driver, the only way is to change the GPU.

Many solutions to the "display driver stopped working and now received" are available over the internet, but none of them will work for long.

Dragsooth · 06 Mar 2014

Well the blue screen is my main concern here, since I can't even leave my computer idle without it blue screening.