[bengerszewski]

I have Windows 7 Ultimate x86 RTM.

Yesterday, i got the bsod, did not manage to write down the info, but got this info when i rebooted:
BCCode: 10d
BCP1: 0000000D
BCP2: 8526D498
BCP3: 87086220
BCP4: 850E71F0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Today, i got the bsod again, but with this info when i booted up:
BCCode: 10d
BCP1: 0000000D
BCP2: 851EEA20
BCP3: 8571D008
BCP4: 866AFF08
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Can someone please help?

[Rollin' Rog]

I've never seen that BCCode before and can't find any documentation of it, I suspect it's a hardware error of some kind, but maybe a look at it in the debugger will shed more light.

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to c:\windows\minidump and copy the last few minidump files to that folder. *this assumes 'c' is your boot drive, if it is not, subsitute accordingly
3 > close the folder and right click on it and select Send to Compressed (zipped) Folder.
4 > use the "manage attachments" in the "advanced" reply window to upload that zip file here as an attachment.

If you do not see any minidumps, be sure you are not using any cache cleaner such as CCleaner. Also run sysdm.cpl and select Advanced > Startup and Recovery. Make sure "small memory dump" is the one chosen under "write debugging information" and the location should be %systemroot%\minidump


>> Also, can you get any more information out of the Control Panel > Performance and Information Tools > Advanced > Reliability Monitor?

[bengerszewski]

Here is the zip file containing the information you requested.

[Rollin' Rog]

They are both nominally identical to this >>

Debug session time: Tue Oct 27 18:06:38.822 2009 (GMT-7)


WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000d, A power irp was received for the device but the irp was not
requested by the device (the power policy owner). Possibly there
are multiple power policy owners. Only one driver in the stack can
be the power policy owner. A KMDF driver can change power policy
ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
Arg2: 8526d498, Device object pointer.
Arg3: 87086220, Power Irp.
Arg4: 850e71f0, Reserved.

Making some sense of it is a challenge since I have never seen that particular bugcheck before.

My feeling is that it is related to a plugnplay or USB device.

I see two in the back traces and trap frames, with one which would be of particular concern.

*** ERROR: Module load completed but symbols could not be loaded for usbaapl.sys
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys

The blue highlighted one appears related to an Ipod or Iphone app and was probably designed for what it is doing.

The Red highligted one I have seen cause problems on at-least two other machines.

It appears to be a non-standard USB controller possibly used to implement an PS3 Controller on a Windows machine.

http://www.google.com/search?hl=en&s...&aq=f&oq=&aqi=

http://forums.techguy.org/windows-vi...-shutdown.html

Does this ring any bells for you?

Anyway, I would test by removing this device and its USB controller. Look for it in Programs and Features

-------------------------------------

For those Reliability Index errors, it appears you began having problems on the 23rd

What are the informational events for the 2 or 3 days previous to that? Are they installs, updates, or something else? You can expand those to read additional information for them.

[Leeter]

I read somewhere that certain USB-devices can mess with how Win7 starts up. My suggestion is to remove all USB devices and start up, see if the problem remains.

[bengerszewski]

None of my USB devices were connected during the time in which the errors occurred. Also, i installed libusb so that i could properly use some jailbreaking utilities. Is there a way to reinstall or reconfigure it so that it will not cause any problems?

[Rollin' Rog]

"jailbreaking" utilities? Are you referring to something for the Iphone?

That is something else you should remove or uninstall for test purposes.

I don't think it is going to be compatible, reinstalled or not -- and I can only suggest that you uninstall it while trying to work out this problem.

It's probably going to be a process of elimination.

[bengerszewski]

I'll give it a try, and yes, this is for jailbreaking iPod touches and iPhones. I installed it under compatibility mode for windows vista though, because if i did a normal install, the usb ports wouldnt recognize anything. Also, my computer has not crashed since i posted this thread.

[bengerszewski]

Lol, nevermind, it just happened again.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 10d
BCP1: 0000000D
BCP2: 85CCA7C8
BCP3: 85DD39F0
BCP4: 86D40760
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102909-17160-01.dmp
C:\Users\USERNAME\AppData\Local\Temp\WER-33618-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

[Rollin' Rog]

Well that of course is going to be the same error as previous -- and none of those specifically identifies a driver or device.

But from what I can glean from the error message a "device" is being sent a power request (sleep or wake up) in a manner not properly "authorized".

So you have to figure out what device that is. To do that I think you have to remove any non-standard device AND the drivers for it. It could be that Windows thinks the device is present from its driver profile even when it is not.

Paying attention to when these faults occur is also important -- as you may be doing something to trigger them.

If you have uninstalled libusb0.sys and any associated Iphone apps and get another BSOD -- upload the minidump for that.