New
#1
Specific actions.
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.
Last edited by Arc; 28 May 2014 at 01:38.
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.
Last edited by Arc; 28 May 2014 at 01:38.
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: iMac 27' 2014 BSOD Win7 Wdf01000.sys
Here is a thread: BSOD DRIVER_POWER_STATE_FAILURE ntoskrnl.exe+75bc0
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.
fffffa800654e010 , the fourth argument is the blocked IRP. Do !irp on it .....Code:BugCheck 9F, {3, fffffa8005803620, fffff80004108518, fffffa800654e010} Probably caused by : usbccgp.sys Followup: MachineOwner ---------
Code:0: kd> !irp fffffa800654e010 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 pending \Driver\usbvideo 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
(Well, it is a cross posting actually, to keep things under a same roof.)
Thread: BSOD New custom build (0x0000010d) possibly DS3 Tool driver
Issue: playstation controller
Let us see the driver's timestamp:Code: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 Probably caused by : MijXfilt.sys ( MijXfilt+363a ) Followup: MachineOwner ---------
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.Code:Image path: \SystemRoot\system32\DRIVERS\MijXfilt.sys Image name: MijXfilt.sys Timestamp: Sat May 12 09:57:12 2012 (4FADE6A0)
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.
Last edited by Arc; 14 May 2015 at 13:05.
Here is a thread: BSOD playing Left 4 Dead 2
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.
Was looking at Steves post here: BSOD 5 minutes after startup from sleep or shutdown every day. And thought about it. What I do to suggest the intel display driver update.
Look at dxdiag.txt.
The chip type is the point. In physical verification, it is this place:Code:--------------- Display Devices --------------- Card name: Mobile Intel(R) 4 Series Express Chipset Family Manufacturer: Intel Corporation Chip type: Mobile Intel(R) 4 Series Express Chipset Family
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. :)
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.
I learned it from Layback Bear.
If it BSODs with a probable cause igdpmd64.sys, it is to uninstall windows update KB2670838.______________________________________________________
I have dealt with three of such issues.
- Sudden BSoD While Playing an Online Game, Error 0x50
- BSOD web browsing, not sure which error (see description.)
- BSOD and computer shutdown unexpectedly
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.
Generally, this comes with bugcheck 10D, or 10E.
The failing xusb21.sys is of August 2009, as said in Carrona.org.
In the crash dumps ....Driver Description: XBox USB wireless controller
BSOD issues in Win7 with 2009 driver (found in mid-2012)
But there is no possibility of an update, till date. Because ....Code:Image name: xusb21.sys Timestamp: Fri Aug 14 03:40:17 2009 (4A848F49)
Xbox 360 Wireless Controller for Windows includes .....
And, Xbox 360 Controller for Windows includes ....Code:CatalogFile=xusb21.cat DriverVer=08/13/2009,2.1.0.1349
What I have noticed that uninstallation of XBox controller and reinstallation sometimes solves the issue.Code:CatalogFile=xusb21.cat DriverVer=08/13/2009,2.1.0.1349
=============================================================================
BTW, the Xbox one controller for PC (a different device and different driver, though) has a newer driver.
Code:DriverVer=05/26/2014,6.2.11059.0 CatalogFile=xb1usb.cat