3 BSODs in 1 day. Help.

  • Thread starter paskowitz
  • 7 comments
  • 1,131 views
3,239
United States
New York
thepatriots
I have done nothing to my computer except installing my bluetooth driver. All of a sudden today I have gotten 3 BSODs. I have saved my error reports and they are posted below. Considering I just did a clean install a couple of weeks ago... this is pretty maddening. :mad:

Crash 1:

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

Additional information about the problem:
BCCode: 10d
BCP1: 0000000000000005
BCP2: 0000000000000000
BCP3: 0000000000001202
BCP4: FFFFFA800E20A010
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Crash 2:

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

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800B418060
BCP3: FFFFF80000B9C518
BCP4: FFFFFA800C29BB80
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

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

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800B40B060
BCP3: FFFFF80004613748
BCP4: FFFFFA800C085A20
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1


I would greatly appreciate any advice on this matter. Thanks.
 
Usually there's a little bit more info than this.. Can you give us a little more info? Maybe try system restoring to a point when you didn't have the bluetooth driver?
 
System Information (local)
--------------------------------------------------------------------------------

computer name: AMP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8577916928 total
VM: 2147352576, free: 1887272960



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 9/15/2012 4:51:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-9703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800BDA0060, 0xFFFFF80000B9C518, 0xFFFFFA8007084390)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 9/15/2012 4:51:10 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800BDA0060, 0xFFFFF80000B9C518, 0xFFFFFA8007084390)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 9/15/2012 4:28:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-11731-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800B40B060, 0xFFFFF80004613748, 0xFFFFFA800C085A20)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 9/15/2012 1:28:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-12963-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800B418060, 0xFFFFF80000B9C518, 0xFFFFFA800C29BB80)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 9/14/2012 3:23:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091312-21668-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x13B77)
Bugcheck code: 0x10D (0x5, 0x0, 0x1202, 0xFFFFFA800E20A010)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
 
Did you use Windows Update to install/update the drivers?

When does it occur? During normal operation? Standby? Shutdown? Waking from hibernation?
 
Normal operation. I am usually not even using my computer. It just happens.

I got the driver (bluetooth) from Dell's website. I have a Dell Studio XPS 1647.
 
Uninstall the bluetooth driver and see what happens as it seems to be incapable of handling proper power state requests.

If you want to delve into things a bit further you can try this.
 
Bluescreens related to drivers = uninstall any and all drivers you installed since the last known stable boot.
 
Get a program called "bluescreen view"
This will show you what drivers are causing the crashes.
 
Back