ntoskrnl.exe BSOD randomly

moieu said:

Well I just split the two. My phone is now charging on a separate cable and my headset is using it's own too. And I haven't had any bsods.

That's good to know :)

Just for the sake of debugging, here's my analysis:

Code:

BugCheck 1000008E, {c0000005, 82a87189, a16d6ca4, 0}

Probably caused by : invalid_control_transfer

Code:

a16d6ca4 -- (.trap 0xffffffffa16d6ca4)
ErrCode = 00000002
eax=855b2400 ebx=97cf4a1c ecx=00000000 edx=00000000 esi=00000008 edi=00000028
eip=82a87189 esp=a16d6d18 ebp=a16d6d24 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!ExReleaseResourceAndLeavePriorityRegion+0xc:
82a87189 888b0200008d    mov     byte ptr [ebx-72FFFFFEh],cl ds:0023:24cf4a1e=??

The exception being introduced here is a NMI (or Non-Maskable Interrupt), and is a very high priority interrupt used for crashes.

The nt!ExReleaseResourceAndLeavePriorityRegion (undocumented) is used to release a executive resource, and leave a priority region. The priority region in this case, may have been a critical section.

Code:

1: kd> u win32k!NtUserCallOneParam+0x43
win32k!NtUserCallOneParam+0x43:
97cf4a5f e8a3ecfeff      call    win32k!UserSessionSwitchLeaveCrit (97ce3707) <-- Problem here
97cf4a64 8bc7            mov     eax,edi
97cf4a66 5f              pop     edi
97cf4a67 5e              pop     esi
97cf4a68 5d              pop     ebp
97cf4a69 c20800          ret     8
97cf4a6c 90              nop
97cf4a6d 90              nop

The problem happens when attempting to call a certain function, and this call fails.

Alright, still getting bsods... I've tried everything. Its still usbfilter.sys, I ran driver verifier to check. But even after updating it it's still the cause. I'm also not able to do anything past boot now cause it says winload.exe is missing or corrupt. It did this earlier and then after awhile went away. I need serious help because I'm going to get kicked out of my classes if I can't submit work... also, I was trying to fix it by myself and found a thread were a program had fixed the issue, it disabled the USB filter system file, but now my keyboard and mouse won't work at all.

Ok so I reset my computere to factory settings again. It's couldn't find another way to use my keyboard and mouse after boot, and I finally got the winload.exe error to go away. It just went away, after awhile. After resetting my computer I installed all the updates, and I didn't get a blue screen, but I got that thing where my computer tower stays on, but everything connected to it shuts off. My monitor went to standby mode. I guess that's kind of like a blue screen, although I got no dmp file for it. If I get any blue screens I will be posting the dmp files for them as they come.

Alright for some reason I can't edit my previous posts, but I had a bsod and there was no dump file, then I decided to use driver verifier to see which one it was, it was usbfilter.sys I'm attaching the two bsods I got from driver verifier in hopes that you have a fix. Keep in mind the last time I installed the amd update from my computer's website it didn't fix the usbfilter.sys bsods I was getting.

Code:

3: kd> lmvm usbfilter
start             end                 module name
fffff880`043c9000 fffff880`043d6000   usbfilter T (no symbols)           
    Loaded symbol image file: usbfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\usbfilter.sys
    Image name: usbfilter.sys
    Timestamp:        Tue Dec 22 08:26:22 2009 (4B3082AE)
    CheckSum:         0000DFD8
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Where did you update the driver last time? Try the AMD website, since this driver usually belongs to your chipset. Do you have a non-USB keyboard and mouse?

Support & Drivers

Code:

BugCheck D5, {fffff98008d84df0, 0, fffff880043cd1aa, 0}

Could not read faulting driver name
Probably caused by : usbfilter.sys ( usbfilter+41aa )

The driver caused a invalid page fault, since the pool page was no longer allocated to the driver's own address space. It was freed.

Did you use the AMD automatic driver installation?