Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
BSOD using PCSX2
#1
It blue screens whenever I try to run a game, or get near the plugins/config.
I'm attaching the dump file.


Attached Files
.zip   081612-24601-01.zip (Size: 29,99 KB / Downloads: 104)
Reply

Sponsored links

#2
it's a problem with one of your Hardware , Driver or OS

PCSX2 is NOT the cause !!
Reply
#3
Is there anyway I can trace it to what the problem is?
Reply
#4
Specs? Or maybe you need to update your DirectX drivers?
CPU: Intel Core i5-3470 Quad Core @ 3.6GHz
RAM: 8GB
GPU: Nvidia GeForce GTX 660 Ti
OS: Windows 7 Ultimate x64
Reply
#5
Download the program whocrased.
Reply
#6
attach the mini dumps to a post or upload them to a file locker
Reply
#7
the bsod is in the usb wifi driver

In my own experience, this can often be a result of a faulty memory stick, though only if the driver is failing IRQ comparison

The error in this case is caused by the driver itself

Quote:Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081612-24601-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols\win7_64*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0341a000 PsLoadedModuleList = 0xfffff800`0365e670
Debug session time: Thu Aug 16 16:08:44.152 2012 (UTC + 10:00)
System Uptime: 0 days 10:26:58.089
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {d, fffffa8009c10e20, fffffa800e111010, fffffa8009bece70}

Unable to load image \SystemRoot\System32\Drivers\bpusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bpusb.sys
*** ERROR: Module load completed but symbols could not be loaded for bpusb.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : bpusb.sys ( bpusb+1745 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 000000000000000d, 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: fffffa8009c10e20, Device object pointer.
Arg3: fffffa800e111010, Power Irp.
Arg4: fffffa8009bece70, Reserved.

Debugging Details:
------------------


BUGCHECK_STR: 0x10D_d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff88000f6b01b to fffff800034991c0

STACK_TEXT:
fffff880`009e77f8 fffff880`00f6b01b : 00000000`0000010d 00000000`0000000d fffffa80`09c10e20 fffffa80`0e111010 : nt!KeBugCheckEx
fffff880`009e7800 fffff880`00f6ac91 : 00000000`00000002 fffff880`009e78c8 00000000`00000004 00000000`00000000 : Wdf01000!FxPkgFdo:LaughispatchDeviceSetPower+0xb3
fffff880`009e7850 fffff880`00f59f38 : fffffa80`09bece70 00000000`00000000 00000000`00000000 00000000`000000ff : Wdf01000!FxPkgFdo::_DispatchSetPower+0x21
fffff880`009e7880 fffff880`00f187fa : fffffa80`0e111010 fffffa80`0e111010 00000000`00000000 fffffa80`0e111478 : Wdf01000!FxPkgPnp:Laughispatch+0x314
fffff880`009e78f0 fffff880`0a821745 : fffffa80`0b814020 00000000`00000016 fffffa80`0e111402 fffffa80`0e111478 : Wdf01000!imp_WdfDeviceWdmDispatchPreprocessedIrp+0x196
fffff880`009e7930 fffffa80`0b814020 : 00000000`00000016 fffffa80`0e111402 fffffa80`0e111478 00000000`00000000 : bpusb+0x1745
fffff880`009e7938 00000000`00000016 : fffffa80`0e111402 fffffa80`0e111478 00000000`00000000 fffff880`0a824ed8 : 0xfffffa80`0b814020
fffff880`009e7940 fffffa80`0e111402 : fffffa80`0e111478 00000000`00000000 fffff880`0a824ed8 0000057f`f47ebfd8 : 0x16
fffff880`009e7948 fffffa80`0e111478 : 00000000`00000000 fffff880`0a824ed8 0000057f`f47ebfd8 fffffa80`0e111010 : 0xfffffa80`0e111402
fffff880`009e7950 00000000`00000000 : fffff880`0a824ed8 0000057f`f47ebfd8 fffffa80`0e111010 fffffa80`0b814390 : 0xfffffa80`0e111478


STACK_COMMAND: kb

FOLLOWUP_IP:
bpusb+1745
fffff880`0a821745 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: bpusb+1745

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bpusb

IMAGE_NAME: bpusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dd4effe

FAILURE_BUCKET_ID: X64_0x10D_d_bpusb+1745

BUCKET_ID: X64_0x10D_d_bpusb+1745

Followup: MachineOwner
---------
Reply
#8
wifi Driver and PCSX2 ??? Huh
Reply
#9
its conflicting with another driver on the system that can adjust system power states
Reply
#10
well good to know Smile
Reply




Users browsing this thread: 1 Guest(s)