BSOD playing games, 0x50, 0xA, 0xD1

Arc · 01 Nov 2012

Well, what I first checked , if the sata controller is properly updated or not.

Code:

lmvm jraid
start             end                 module name
fffffa60`00772000 fffffa60`00793000   jraid      (deferred)             
    Image path: \SystemRoot\system32\drivers\jraid.sys
    Image name: jraid.sys
    Timestamp:        Thu May 19 13:25:18 2011 (4DD4CCE6)
    CheckSum:         00029667
    ImageSize:        00021000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

And it is done. So, well done, and the cause is in some different place this time, for sure.

A deeper look at the latest dump gives this result, repeatedly.

Code:

fffff800`08b98888  fffffa60`03b159b6 USBPORT!GetHcFdoExt+0x1a
fffff800`08b988e8  fffffa60`03b1b593 USBPORT!USBPORT_Core_DecIoRequestCount+0xb7

So, we may conclude that, it is something related to USB devices, or the ports itself.

For the port, first, uninstall and reinstall the USB ports drivers.

Right click on Computer icon > manage. It will open the computer management window.
Click on "Device Manager" in the left pane, it will list all installed devices up.
Expand "USB Serial Bus Controllers" by clicking on the triangle in front of it.
Click on one item to select, then right click and uninstall.
Do the same for all.
Restart the computer.
At restart, windows will auto configure the appropriate drivers.

And, Disable USB Selective Suspense too.
USB Selective Suspend - Turn On or Off

For the devices, first, detach all the USB devices other than the keyboard and mouse.
Then, Update the drivers for them all, including the keyboard and mouse, if any third party drivers are installed for them.

+* If you use any USB network adapter, take care of it, first. Then Keyboard and mouse, then all, one by one.

Let us know the results.

Thumbless Joe · 01 Nov 2012

Alright I uninstalled everything under the USB controllers, however I was wondering if I should be concerned that it doesn't look like Intel(R) ICH10 family USB universal host controller 3A35 and a couple others that were similar to that except the ends were something like 3A36, 3A37 and so on don't appear to be there anymore as well as a RealTek something, I don't remember what it was exactly. Also I don't really know anything about the USB devices I have plugged in, I no longer have any boxes or anything to tell me more about them, is there a way for me to figure out what they are so I can look for their drivers and update them?

Arc · 02 Nov 2012

Sorry that is not possible for me ...... I can do debug for you, cannot check the brands and builds of your USB devices, other than the data I get in your crash dump.

I hope you can understand it.

Thumbless Joe · 02 Nov 2012

Yeah it's ok, I'll look into them when I have time this weekend, on the plus side I didn't any BSOD yesterday after I uninstalled the USB controllers, which is promising but I don't want to get my hopes up just yet.

Thumbless Joe · 04 Nov 2012

Well I got another BSOD after a couple days, I'm still trying to find drivers for some of my USB devices, but here are the dump files for this one

Arc · 04 Nov 2012

Joe, it is not providing sufficient information.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80266174e8, c, 1, fffff800078bc1df}

Probably caused by : win32k.sys ( win32k!WakeRIT+37 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa80266174e8, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800078bc1df, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80007a85080
GetUlongFromAddress: unable to read from fffff80007a85160
 fffffa80266174e8 Nonpaged pool

CURRENT_IRQL:  c

FAULTING_IP: 
nt!KeSetEvent+14f
fffff800`078bc1df 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  csrss.exe

TRAP_FRAME:  fffffa6008774630 -- (.trap 0xfffffa6008774630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80266174e8 rbx=0000000000000000 rcx=fffffa80066174e8
rdx=fffffa800afa80e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800078bc1df rsp=fffffa60087747c0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffffa800b0c2060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeSetEvent+0x14f:
fffff800`078bc1df 488908          mov     qword ptr [rax],rcx ds:fffffa80`266174e8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800078b586e to fffff800078b5ad0

STACK_TEXT:  
fffffa60`087744e8 fffff800`078b586e : 00000000`0000000a fffffa80`266174e8 00000000`0000000c 00000000`00000001 : nt!KeBugCheckEx
fffffa60`087744f0 fffff800`078b474b : 00000000`00000001 fffffa60`08774710 00000000`0000049f fffffa80`0af871d0 : nt!KiBugCheckDispatch+0x6e
fffffa60`08774630 fffff800`078bc1df : 00000000`00000001 00000000`00000000 00000000`0001004b 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`087747c0 fffff960`001056af : 00000000`00000000 00000000`00000000 fffffa80`0a874c10 00000000`00000000 : nt!KeSetEvent+0x14f
fffffa60`08774830 fffff960`001c570f : 00000000`00000000 000000db`000004a2 fffffa80`0a874c10 00000000`00000000 : win32k!WakeRIT+0x37
fffffa60`08774860 fffff960`001c5ded : fffff900`c00ea09c 00000000`00503534 fffff900`c00ea010 fffff900`c00ea010 : win32k!QueueMouseEvent+0x150
fffffa60`08774890 fffff960`001c5b85 : fffff900`c00ea010 000000db`000004a2 fffffa80`07b69cd8 00000000`00000246 : win32k!ProcessMouseInput+0x24d
fffffa60`08774900 fffff800`078d7307 : fffffa80`0b0c2060 fffffa80`0b0c2060 00000000`00000000 00000000`00000000 : win32k!InputApc+0xd5
fffffa60`08774930 fffff800`078b7faf : 00000000`00000000 00000000`00000000 fffff960`001c5ab0 00000000`00000000 : nt!KiDeliverApc+0x2d7
fffffa60`087749d0 fffff800`078bd5eb : 00000000`00000000 00000000`00000008 fffff960`00000000 fffff960`00000002 : nt!KiSwapThread+0x3ef
fffffa60`08774a40 fffff960`0015dcee : fffff900`00000002 fffff900`c0133990 00000000`00000001 fffffa60`0000000d : nt!KeWaitForMultipleObjects+0x2eb
fffffa60`08774ac0 fffff960`0015e03f : 00000000`00000000 fffff900`c0133990 00000000`00000004 fffff960`00363c20 : win32k!xxxMsgWaitForMultipleObjects+0x102
fffffa60`08774b40 fffff960`00118c03 : fffffa80`00000001 fffffa80`0000000c fffffa80`0b0c2060 fffffa80`0a874c10 : win32k!xxxDesktopThread+0x26f
fffffa60`08774bc0 fffff960`0019eeea : fffffa80`00000001 fffff960`00363c20 00000000`00000000 00000000`00000000 : win32k!xxxCreateSystemThreads+0x73
fffffa60`08774bf0 fffff800`078b5573 : fffffa80`0b0c2060 00000000`00000004 000007fe`fdb28b60 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffffa60`08774c20 000007fe`fda7c43a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`022bfe78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fda7c43a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!WakeRIT+37
fffff960`001056af 4883c428        add     rsp,28h

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!WakeRIT+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ff45412

FAILURE_BUCKET_ID:  X64_0xA_win32k!WakeRIT+37

BUCKET_ID:  X64_0xA_win32k!WakeRIT+37

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

In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

Also, test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Let us know the results.

Thumbless Joe · 08 Nov 2012

Sorry, I have been a little busy and haven't had time to mess with my computer. As far as I know I already ran a full memtest before I posted this thread and it didn't find any problems, I'm running driver verifier again and will post the results whenever something happens.