Sometimes the faulting app matters other times it's just another side effect.
I'm not certain which one it is here.
For example here's another one blaming the system kernel
Code:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffb50440, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002fb4f40, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b8100
ffffffffffb50440
FAULTING_IP:
nt!ExFreePoolWithTag+1b0
fffff800`02fb4f40 40f6c608 test sil,8
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: League of Lege
CURRENT_IRQL: 1
IRP_ADDRESS: ffffffffffffff88
TRAP_FRAME: fffff880088a86b0 -- (.trap 0xfffff880088a86b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffb50440 rbx=0000000000000000 rcx=00000000000008e8
rdx=fffff88002f70000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fb4f40 rsp=fffff880088a8840 rbp=0000000000000000
r8=0000000000004740 r9=0000000000000080 r10=fffff80002e09000
r11=00000000000001c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ExFreePoolWithTag+0x1b0:
fffff800`02fb4f40 40f6c608 test sil,8
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e303f0 to fffff80002e85c40
STACK_TEXT:
fffff880`088a8548 fffff800`02e303f0 : 00000000`00000050 ffffffff`ffb50440 00000000`00000001 fffff880`088a86b0 : nt!KeBugCheckEx
fffff880`088a8550 fffff800`02e83d6e : 00000000`00000001 ffffffff`ffb50440 00000000`00000000 fffffa80`028c7d20 : nt! ?? ::FNODOBFM::`string'+0x447c6
fffff880`088a86b0 fffff800`02fb4f40 : fffffa80`02bcf310 fffff800`02e91658 fffffa80`02bcf310 ffffffff`fffcf2c0 : nt!KiPageFault+0x16e
fffff880`088a8840 fffff800`02e9b09e : 00000000`00000001 fffff800`02e09000 00000000`20206f49 ffffffff`fffffffb : nt!ExFreePoolWithTag+0x1b0
fffff880`088a88f0 fffff800`02e792f7 : 00000000`00000000 00000000`00000000 fffffa80`06055400 fffff880`088a8c60 : nt!IopCompleteRequest+0x5ce
fffff880`088a89c0 fffff800`02e8b13d : fffff880`02f66580 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`088a8a40 fffff800`02e8d74f : 00000000`00000298 00000000`7ef98000 fffff880`00000080 00000000`0f75f118 : nt!KiCommitThreadWait+0x3dd
fffff880`088a8ad0 fffff800`0317c44e : fffff880`088a8c00 fffffa80`00000006 00000000`00000001 fffff880`088a8b01 : nt!KeWaitForSingleObject+0x19f
fffff880`088a8b70 fffff800`02e84ed3 : fffffa80`02836760 00000000`00000000 fffff880`088a8bb8 fffffa80`02dabfe0 : nt!NtWaitForSingleObject+0xde
fffff880`088a8be0 00000000`75102e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0f75f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75102e09
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExFreePoolWithTag+1b0
fffff800`02fb4f40 40f6c608 test sil,8
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!ExFreePoolWithTag+1b0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x50_nt!ExFreePoolWithTag+1b0
BUCKET_ID: X64_0x50_nt!ExFreePoolWithTag+1b0
Followup: MachineOwner
--------- It's just a side effect of the bad driver that is actually causing the problems.
Simplifying power management plan can also help reduce the chances of driver issues.
Windows 7 handles power management a little differently than xp or vista, this generally is what leads to crashes when older drivers are in use.
I also personally suggest doing this.
To Disable Selective Suspend:
open the control panel
go to power options (you may have to set view to small icons)
click change plan settings
in the window that opens:
click change plan settings
click change advanced power settings, expand usb and ensure usb selective suspend is disabled.