Specific actions.

[Arc]

I am planning to showcase specific issues, which are sort of rare and requires specific actions; as I get a chance to deal with those.

 

[Arc]

1394ohci.sys

For issues related to 1394ohci.sys, it is better to get the driver reverted to the legacy driver. Here is a guide on how to do it: How to Revert the Win7 1394ohci.sys to the Legacy Driver

Thread: http://www.sevenforums.com/bsod-hel...-2014-bsod-win7-wdf01000-sys.html#post2787377

 

[Arc]

usbvideo.sys

Here is a thread: http://www.sevenforums.com/bsod-hel...e_failure-ntoskrnl-exe-75bc0.html#post2786343

My suggestion here was to disable webcam.

Apparently it may seem to be an abrupt suggestion, but if you find usbvideo.sys error, the action should be taken on the webcam.

[COLOR=Red][B]BugCheck 9F[/B][/COLOR], {3, fffffa8005803620, fffff80004108518, [COLOR=SeaGreen][B]fffffa800654e010[/B][/COLOR]}

Probably caused by : usbccgp.sys

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

fffffa800654e010 , the fourth argument is the blocked IRP. Do !irp on it .....

0: kd> [COLOR=Blue][B]!irp[/B][/COLOR] [COLOR=SeaGreen][B]fffffa800654e010[/B][/COLOR]
Irp is active with 15 stacks 12 is current (= 0xfffffa800654e3f8)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

......
......
......

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e0 fffffa8005803620 00000000 fffff88003e97fd4-fffffa80057f7010 Success Error Cancel 
           \Driver\usbccgp    ks!CKsDevice::CompleteDevicePowerIrp
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0  1 fffffa80057fde10 00000000 00000000-00000000    [COLOR=Red][B]pending
           \Driver\usbvideo[/B][/COLOR]
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 fffffa8005ae1e30 00000000 00000000-00000000    pending
           \Driver\ksthunk
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8005a04010    

            Args: 00000000 00000000 00000000 00000000

 

[Arc]

MijXfilt.sys

(Well, it is a cross posting actually, to keep things under a same roof.)

Thread: http://www.sevenforums.com/bsod-hel...10d-possibly-ds3-tool-driver.html#post2785883
Issue: playstation controller

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

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

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

Let us see the driver's timestamp:

    Image path: \SystemRoot\system32\DRIVERS\MijXfilt.sys
    Image name: MijXfilt.sys
    Timestamp:        Sat [COLOR=Red][B]May[/B][/COLOR] [COLOR=Red][B]12[/B][/COLOR] 09:57:12 [COLOR=Red][B]2012[/B][/COLOR] (4FADE6A0)

The latest driver available in Playstation 3 controller(Dualshcok 3 or Sixaxis) driver for windows | MotioninJoy is Version 0.7.1001. Which is this driver under issue.

Over two years till date, thee is no driver update. And the latest version is crash prone.

The suggestion would be, uninstall the installed driver of playstation controller and then install an earlier version.

 

[Arc]

Stop 0xA0000001

Here is a thread: http://www.sevenforums.com/bsod-help-support/332329-bsod-playing-left-4-dead-2-a.html#post2782963

Stop 0xA0000001 is inherent with ATI/AMD display. It may be the display driver, or even the GPU.

First apply any other version (better a known good WHQL) of the display driver.

If the display issue continues with multiple version of the driver, unfortunately there is no other way but changing the GPU.

 

[Golden]

You're a fookin champion Arc!

 

[Arc]

igdkmd32.sys or igdmkd64.sys: specific driver suggestion.

Was looking at Steves post here: http://www.sevenforums.com/bsod-hel...tup-sleep-shutdown-every-day.html#post2789576. And thought about it. What I do to suggest the intel display driver update.

Look at dxdiag.txt.

---------------
Display Devices
---------------
          Card name: Mobile Intel(R) 4 Series Express Chipset Family
       Manufacturer: Intel Corporation
          [COLOR=Red]Chip type: Mobile Intel(R) [B]4 Series Express Chipset[/B][/COLOR] Family

The chip type is the point. In physical verification, it is this place:



Now, go to Intel Download Center. Search for it:



The search result is here:



So, the specific driver upload suggestion would be: Intel® Graphics Media Accelerator Driver, Windows 7.

Sorry for it, Steve. I did not mean any disrespect or anything. Please dont take it otherwise?

And, Thank you Colin.

 

[essenbe]

Arc, how dare you think I would make a mistake! I am the Jedi Master and Jedi Masters never make mistakes. You should know that by now. :roflmao:

 

[Arc]

igdpmd64.sys

I learned it from Layback Bear.

If it BSODs with a probable cause igdpmd64.sys, it is to uninstall windows update KB2670838.

Windows Update - Uninstall an Update

​

______________________________________________________
I have dealt with three of such issues.

• http://www.sevenforums.com/bsod-hel...aying-online-game-error-0x50.html#post2718571
• http://www.sevenforums.com/bsod-hel...t-sure-error-see-description.html#post2767755
• http://www.sevenforums.com/bsod-hel...mputer-shutdown-unexpectedly.html#post2830833

None of them came back to mark their threads as solved. So it is not a certain event. But at least none of them came back which is a good basis of assumption that it worked for them.

 

[Arc]

xusb21.sys

Generally, this comes with bugcheck 10D, or 10E.

The failing xusb21.sys is of August 2009, as said in Carrona.org.

Driver Description: XBox USB wireless controller
BSOD issues in Win7 with 2009 driver (found in mid-2012)

In the crash dumps ....

    Image name: xusb21.sys
    Timestamp:        Fri [COLOR=Red]Aug 14[/COLOR] 03:40:17 [COLOR=Red]2009[/COLOR] (4A848F49)

But there is no possibility of an update, till date. Because ....
Xbox 360 Wireless Controller for Windows includes .....

CatalogFile=xusb21.cat
DriverVer=[COLOR=Red]08/13/2009[/COLOR],2.1.0.1349

And, Xbox 360 Controller for Windows includes ....

CatalogFile=xusb21.cat
DriverVer=[COLOR=Red]08/13/2009[/COLOR],2.1.0.1349

What I have noticed that uninstallation of XBox controller and reinstallation sometimes solves the issue.


=============================================================================
BTW, the Xbox one controller for PC (a different device and different driver, though) has a newer driver.

DriverVer=[COLOR=Red]05/26/2014[/COLOR],6.2.11059.0
CatalogFile=xb1usb.cat

 

[Boozad]

I had one of those yesterday or the day before, I managed to solve one last year but couldn't remember the fix. Top stuff Arc.

 

[Arc]

Thank you mate.

 

[Boozad]

I'd be interested to hear back from the guy with the NetGear Wireless USB Adaptor to see if that fix worked for him yesterday.

 

[Arc]

Me too. I found that thread very interesting!!

 

[Arc]

NFC_Driver

From MSINFO32.nfo, it is nothing helpful....

nfc_driver    NFC_Driver    c:\windows\system32\drivers\nfc_driver.sys    Kernel Driver    Yes    System    Running    OK    Normal    No    Yes

In Carrona.org, no information.
In SystemExplorer, nothing helpful.

I learned that it is an ASUS Bloatware. ROG Game First III

Start Menu\Programs\ASUS\[COLOR=Red]ROG Game First III[/COLOR]    Public:Start Menu\Programs\ASUS\ROG Game First III    Public

Apparently a NETIO.sys BSOD involving NFC_Driver.sys as an unloaded module gets solved by uninstalling ROG Game First III.

​