BSOD while playing BF3---Windows 7

[Tbutter]

Okay IVe been running Driver Verify all morning and nothing happened. Then I play Crysis 2 while running that and after about 45 minutes I got a BSOD. 0x00000109. Which I guess is maybe memory related. So now Im going to run memtest to see what happens.

 

[writhziden]

Okay IVe been running Driver Verify all morning and nothing happened. Then I play Crysis 2 while running that and after about 45 minutes I got a BSOD. 0x00000109. Which I guess is maybe memory related. So now Im going to run memtest to see what happens.

If you upload the dmp file, it may not be memory and may point to a device driver.

 

[Tbutter]

Here are the two dump files from today. Again I recieved no BSOD's while doing normal tasks. Just after playing 45 minutes of Crysis 2. So this seems to happen with all games now....

 

[writhziden]

It doesn't look like Verifier is turned on. These were memory_corruption and then DirectX related.

Check Verifier to see if your settings were enabled: Start Menu->type Verifier into Search programs and files (do not hit enter)->Right Click Verifier->Run as administrator->Display exisiting settings->Next

You should have a bunch of drivers listed in the table on the right. If not, go through the steps to enable Verifier again.

 

[Tbutter]

Haha I did what the turtorial said! I'll try again later. I'm also going to run the memtest tonight.

I'll keep yah updated. Thanks for being so patient.

 

[Tbutter]

Okay so I ran the Memtest over night. 12 Passes and zero errors for both sticks of memory.

 

[writhziden]

Okay so I ran the Memtest over night. 12 Passes and zero errors for both sticks of memory.

Sounds good. Doubtful you have memory issues then, but just to be safe, run the http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html in extended mode for five passes tonight. See 5. To Change the Memory Diagnostic Tool Options in that tutorial.

 

[Tbutter]

Okay so no more errors with the other tests. I'm sure my Memory is out of the question now as that seems okay.

I received a BSOD while playing again today after about 10 minutes. It was a USB.sys stop error of some sort. Im beginning to wonder if this TP-Link Wireless adapter has something to do with it.

 

[writhziden]

Okay so no more errors with the other tests. I'm sure my Memory is out of the question now as that seems okay.

I received a BSOD while playing again today after about 10 minutes. It was a USB.sys stop error of some sort. Im beginning to wonder if this TP-Link Wireless adapter has something to do with it.

Look through http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html and see if it applies.

 

[Tbutter]

Hey,

So the USB thing didn't work. I had a USBEHCI.SYS error earlier before I did the USB thing. Then after that I just installed the Adapters Driver and that was all and after about 25 minutes which is decent compared to other times, I got a 0x0000004E error.

So memory is not bad, I know my NiVidia Drivers are all up-to-date.....what can this be??

 

[Tbutter]

Okay so another crash of BF3 but this time it said that NiVidia Drivers had stopped working.....

I have uploaded my newest dump files for yah!! Im going back to school this weekend so I will no longer be using the USB Adapter so maybe it will change soon.

 

[writhziden]

[list=1]
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tbutter\Windows_NT6_BSOD_jcgriff2\010112-14523-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03001000 PsLoadedModuleList = 0xfffff800`03246670
Debug session time: Sun Jan  1 19:07:54.103 2012 (UTC - 7:00)
System Uptime: 0 days 0:15:30.915
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( USBSTOR!PortAvioSchedulerTransferBatch+5d )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6236333665353838
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff800048b08c8 -- (.exr 0xfffff800048b08c8)
ExceptionAddress: fffff88006d731ad (USBSTOR!PortAvioSchedulerTransferBatch+0x000000000000005d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff800048b0970 -- (.trap 0xfffff800048b0970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800048b0b48 rbx=0000000000000000 rcx=fffff88006d761e0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006d731ad rsp=fffff800048b0b08 rbp=fffff88006d76110
 r8=fffff800048b0ba0  r9=fffffa800b411b70 r10=fffff800031f4880
r11=0000000000010000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
USBSTOR!PortAvioSchedulerTransferBatch+0x5d:
fffff880`06d731ad cf              iretd
Resetting default scope

MISALIGNED_IP: 
USBSTOR!PortAvioSchedulerTransferBatch+5d
fffff880`06d731ad cf              iretd

LAST_CONTROL_TRANSFER:  from fffff800030755fe to fffff8000307dc10

STACK_TEXT:  
fffff800`048af9a8 fffff800`030755fe : 00000000`00000000 fffff880`0416e3f1 fffff800`048b0120 fffff800`030a9830 : nt!KeBugCheck
fffff800`048af9b0 fffff800`030a94fd : fffff800`0328771c fffff800`031c4c30 fffff800`03001000 fffff800`048b08c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`048af9e0 fffff800`030a82d5 : fffff800`031c8028 fffff800`048afa58 fffff800`048b08c8 fffff800`03001000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`048afa10 fffff800`030b9361 : fffff800`048b08c8 fffff800`048b0120 fffff800`00000000 fffffa80`0b411ce0 : nt!RtlDispatchException+0x415
fffff800`048b00f0 fffff800`0307d2c2 : fffff800`048b08c8 fffffa80`0b411d00 fffff800`048b0970 fffffa80`0b411ce0 : nt!KiDispatchException+0x135
fffff800`048b0790 fffff800`0307bbca : fffffa80`42554855 fffffa80`0b3a5060 fffffa80`0b3a5000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`048b0970 fffff880`06d731ad : fffff880`06d76110 fffffa80`00000000 fffffa80`00000000 00000000`00000002 : nt!KiGeneralProtectionFault+0x10a
fffff800`048b0b08 fffff880`06d76110 : fffff880`06d72222 fffffa80`0b411d00 fffff880`06d76110 fffffa80`0b411ce0 : USBSTOR!PortAvioSchedulerTransferBatch+0x5d
fffff800`048b0b48 fffff880`06d72222 : fffffa80`0b411d00 fffff880`06d76110 fffffa80`0b411ce0 00000000`00000000 : USBSTOR!WPP_GLOBAL_Control
fffff800`048b0b50 fffff880`06d71e64 : fffffa80`0b411ce0 00000000`00000000 fffffa80`0b411a20 fffff880`06d6dd1f : USBSTOR!UsbDequeueIrp+0x6a
fffff800`048b0b80 fffff880`06d70e9a : 00000000`00000000 fffffa80`0b411b70 fffffa80`0b411b70 fffffa80`0dec1c60 : USBSTOR!UsbQueueRemove+0x6c
fffff800`048b0bd0 fffff880`06d703da : fffffa80`06fe9b60 fffffa80`0b411a20 fffffa80`0e6bb230 fffffa80`0e6bb230 : USBSTOR!UsbStorPumpNextRequest+0x6a
fffff800`048b0c00 fffff800`03081021 : 00000000`00000013 fffffa80`0dec1f73 00000000`00000000 00000000`00000050 : USBSTOR!USBSTOR_CswCompletion+0x226
fffff800`048b0c60 fffff880`10178631 : fffffa80`0abe5050 fffffa80`06fe9c00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`048b0d50 fffff880`10178b0f : fffffa80`0d1cc002 fffffa80`0dec1c60 00000000`ffffffff fffffa80`0abe5eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`048b0e30 fffff880`1017666f : fffffa80`0abe5eb0 fffffa80`0abe51a0 fffffa80`0abe6050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`048b0e90 fffff880`10167f89 : fffffa80`0abe5050 00000000`00000000 fffffa80`0abe5e02 fffffa80`0abe5eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`048b0ed0 fffff800`030890ac : fffff800`031f3e80 fffffa80`0abe5eb0 fffffa80`0abe5ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`048b0f00 fffff800`03080765 : 00000000`00000000 fffffa80`0717ab60 00000000`00000000 fffff880`10167db0 : nt!KiRetireDpcList+0x1bc
fffff800`048b0fb0 fffff800`0308057c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0a6d4aa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBSTOR!PortAvioSchedulerTransferBatch+5d
fffff880`06d731ad cf              iretd

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  USBSTOR!PortAvioSchedulerTransferBatch+5d

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_USBSTOR.SYS

BUCKET_ID:  X64_IP_MISALIGNED_USBSTOR.SYS

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tbutter\Windows_NT6_BSOD_jcgriff2\010212-14539-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03068000 PsLoadedModuleList = 0xfffff800`032ad670
Debug session time: Mon Jan  2 12:44:09.795 2012 (UTC - 7:00)
System Uptime: 0 days 2:51:11.607
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {e000, 2, 1, fffffa800b61cc48}

Probably caused by : usbehci.sys ( usbehci!EHCI_EnableAsyncList+1b )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000000000e000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffa800b61cc48, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003317100
 000000000000e000 

CURRENT_IRQL:  2

FAULTING_IP: 
+6236333665353838
fffffa80`0b61cc48 0000            add     byte ptr [rax],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c720 -- (.trap 0xfffff80000b9c720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000e000 rbx=0000000000000000 rcx=fffffa800b0736a0
rdx=0000000010000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa800b61cc48 rsp=fffff80000b9c8b8 rbp=fffffa800b0736a0
 r8=000000005841655f  r9=0000000000011031 r10=0000000000000004
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffffa80`0b61cc48 0000            add     byte ptr [rax],al ds:e000:00000000`0000e000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030e41e9 to fffff800030e4c40

STACK_TEXT:  
fffff800`00b9c5d8 fffff800`030e41e9 : 00000000`0000000a 00000000`0000e000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c5e0 fffff800`030e2e60 : fffffa80`0bf87a90 fffff800`030e8ca6 fffffa80`0bf87410 fffff880`058bae87 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c720 fffffa80`0b61cc48 : fffff880`058bae87 fffffa80`0b0736a0 fffffa80`0b0736a0 fffffa80`0e3c4ba0 : nt!KiPageFault+0x260
fffff800`00b9c8b8 fffff880`058bae87 : fffffa80`0b0736a0 fffffa80`0b0736a0 fffffa80`0e3c4ba0 fffffa80`0e3c4ba0 : 0xfffffa80`0b61cc48
fffff800`00b9c8c0 fffff880`058bd98b : fffffa80`0b61cd02 fffffa80`0e3c4ba0 fffffa80`0d997a90 00000000`00000000 : usbehci!EHCI_EnableAsyncList+0x1b
fffff800`00b9c8f0 fffff880`058c2144 : fffffa80`0e3c4ba0 00000000`00004000 fffff800`00000001 fffffa80`000003ed : usbehci!EHCI_sMode_Transfer+0x377
fffff800`00b9c980 fffff880`058c9f3c : 00000000`00000002 fffffa80`0b61ca00 00000000`00000005 fffffa80`0b072050 : usbehci!EHCI_SubmitTransfer+0xbc
fffff800`00b9c9c0 fffff880`058cea18 : 00000000`00000060 00000000`00000004 fffffa80`0b61ca00 fffff880`058d7b28 : USBPORT!MPf_SubmitTransfer+0x84
fffff800`00b9ca10 fffff880`058dca96 : fffffa80`0b0721a0 00000000`00000060 fffff800`00000010 fffffa80`0e3c47c0 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x808
fffff800`00b9ca70 fffff880`058d9d59 : fffffa80`0b072050 fffffa80`0b072050 fffffa80`0b61ca00 fffffa80`0e3c47c0 : USBPORT!USBPORT_Core_iSubmitTransferToMiniport+0x236
fffff800`00b9cb00 fffff880`058caf89 : fffffa80`0b072050 00000000`00000000 fffffa80`0b072d02 fffffa80`0b072d28 : USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x149
fffff800`00b9cb60 fffff800`030f00ac : fffff800`0325ae80 fffffa80`0b072d28 fffffa80`0b072d40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9cb90 fffff800`030dc96a : fffff800`0325ae80 fffff800`03268cc0 00000000`00000000 fffff880`058cadb0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_EnableAsyncList+1b
fffff880`058bae87 8a542430        mov     dl,byte ptr [rsp+30h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  usbehci!EHCI_EnableAsyncList+1b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c00

FAILURE_BUCKET_ID:  X64_0xD1_usbehci!EHCI_EnableAsyncList+1b

BUCKET_ID:  X64_0xD1_usbehci!EHCI_EnableAsyncList+1b

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tbutter\Windows_NT6_BSOD_jcgriff2\010212-14570-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03051000 PsLoadedModuleList = 0xfffff800`03296670
Debug session time: Mon Jan  2 13:45:58.089 2012 (UTC - 7:00)
System Uptime: 0 days 0:29:44.901
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff8800591c60e}

Probably caused by : usbehci.sys ( usbehci!EHCI_PrefetchControl+1a )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800591c60e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003300100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
usbehci!EHCI_PrefetchControl+1a
fffff880`0591c60e 8b00            mov     eax,dword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c5b0 -- (.trap 0xfffff80000b9c5b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800af8fc80
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800591c60e rsp=fffff80000b9c740 rbp=fffffa800718db20
 r8=000000004f444648  r9=0000000000010011 r10=0000000000000001
r11=fffff80000b9c778 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbehci!EHCI_PrefetchControl+0x1a:
fffff880`0591c60e 8b00            mov     eax,dword ptr [rax] ds:db20:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030cd1e9 to fffff800030cdc40

STACK_TEXT:  
fffff800`00b9c468 fffff800`030cd1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c470 fffff800`030cbe60 : fffffa80`0b4e9c00 00000000`00000000 00000000`00000000 fffffa80`0718dd88 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c5b0 fffff880`0591c60e : 00000000`ffffffff 00000000`00000000 fffffa80`0718d9f0 fffffa80`0ad336a0 : nt!KiPageFault+0x260
fffff800`00b9c740 fffff880`05924122 : fffffa80`0718dd88 fffffa80`0b4e35e8 00000000`00000001 00000000`00000005 : usbehci!EHCI_PrefetchControl+0x1a
fffff800`00b9c780 fffff880`0592bf3c : 00000000`00000002 fffffa80`0b4e33a0 00000000`00000005 fffffa80`0ad32050 : usbehci!EHCI_SubmitTransfer+0x9a
fffff800`00b9c7c0 fffff880`05930a18 : 00000000`00000060 00000000`00000004 fffffa80`0b4e33a0 fffffa80`0b482ae0 : USBPORT!MPf_SubmitTransfer+0x84
fffff800`00b9c810 fffff880`0593ea96 : fffffa80`0ad321a0 00000000`00000060 fffff880`00000010 fffffa80`0718d9f0 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x808
fffff800`00b9c870 fffff880`0593e0e6 : fffffa80`0dd25490 fffffa80`0718d9f0 00000000`00000000 fffffa80`0ad32050 : USBPORT!USBPORT_Core_iSubmitTransferToMiniport+0x236
fffff800`00b9c900 fffff800`0300c62f : 00000000`00000000 00000000`00000008 fffffa80`0ad32002 00000002`3ae0e528 : USBPORT!USBPORT_Core_ProcessScatterGatherList+0x5b2
fffff800`00b9c9b0 fffff800`0300c420 : fffffa80`0ad32050 00000000`00000008 fffffa80`00000028 fffff880`0593fe6b : hal!HalBuildScatterGatherList+0x203
fffff800`00b9ca20 fffff880`0593e586 : fffffa80`0ad32050 00000000`00000000 fffffa80`0ad32d28 fffffa80`0718d9f0 : hal!HalGetScatterGatherList+0x44
fffff800`00b9ca80 fffff880`0593bea6 : fffffa80`07302ca0 fffffa80`0ad32050 fffff800`0300c3dc fffffa80`0ad321a0 : USBPORT!USBPORT_Core_iMapTransfer+0x24a
fffff800`00b9cb00 fffff880`0592cf89 : fffffa80`0ad32050 00000000`00000000 fffffa80`0ad32d02 fffffa80`0ad32d28 : USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x296
fffff800`00b9cb60 fffff800`030d90ac : fffff800`03243e80 fffffa80`0ad32d28 fffffa80`0ad32d40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9cb90 fffff800`030c596a : fffff800`03243e80 fffff800`03251cc0 00000000`00000000 fffff880`0592cdb0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_PrefetchControl+1a
fffff880`0591c60e 8b00            mov     eax,dword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbehci!EHCI_PrefetchControl+1a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c00

FAILURE_BUCKET_ID:  X64_0xD1_usbehci!EHCI_PrefetchControl+1a

BUCKET_ID:  X64_0xD1_usbehci!EHCI_PrefetchControl+1a

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tbutter\Windows_NT6_BSOD_jcgriff2\010212-12994-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03260670
Debug session time: Mon Jan  2 17:08:11.790 2012 (UTC - 7:00)
System Uptime: 0 days 0:13:38.602
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 82bb2, 2, 81731}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000082bb2, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000081731, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  bf3.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003120d7c to fffff80003097c40

STACK_TEXT:  
fffff880`067ece18 fffff800`03120d7c : 00000000`0000004e 00000000`00000099 00000000`00082bb2 00000000`00000002 : nt!KeBugCheckEx
fffff880`067ece20 fffff800`0303f6d0 : 00000000`00000000 fffff680`0060e1c0 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`067ece60 fffff800`030684b3 : fffffa80`0c920100 fffff700`0005e438 0000007f`fffffff8 fffff8a0`152f1a30 : nt! ?? ::FNODOBFM::`string'+0x333b8
fffff880`067ecef0 fffff800`03069596 : fffffa80`0c920100 fffffa80`00000008 fffff880`0005b0c9 fffff800`0000000e : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`067ed7a0 fffff800`0336db1a : fffff8a0`1515a060 fffff880`067edae0 00000000`00000000 fffffa80`0dc6a250 : nt!MmCleanProcessAddressSpace+0x96
fffff880`067ed7f0 fffff800`0335109d : 00000000`c0000005 00000000`c0000001 00000000`c1fad000 fffffa80`0d7027c0 : nt!PspExitThread+0x56a
fffff880`067ed8f0 fffff800`0308b3fa : 00000000`00000100 fffffa80`0dc6a310 00000000`00000001 fffff800`0309d13d : nt!PsExitSpecialApc+0x1d
fffff880`067ed920 fffff800`0308b740 : 00000000`00000246 fffff880`067ed9a0 fffff800`03351010 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`067ed9a0 fffff800`03096f77 : fffffa80`0dc6a250 00000000`00000890 00000000`00000000 fffffa80`0de10310 : nt!KiInitiateUserApc+0x70
fffff880`067edae0 00000000`74502e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`070af0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74502e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`03120d7c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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


[/list]

lmimirr	fffff880`103ed000	fffff880`103f4000	Tue Apr 10 16:32:45 2007 (461c108d)	0000a04c		lmimirr.sys
RaInfo	fffff880`0bbf3000	fffff880`0bbfa000	Fri Jan 04 11:57:14 2008 (477e818a)	0000d903		RaInfo.sys
LMIRfsDriver	fffff880`0ba00000	fffff880`0ba13000	Mon Jul 14 10:26:56 2008 (487b7e50)	0001e26d		LMIRfsDriver.sys

You should uninstall LogMeIn and install the latest version as the above drivers are all from the program and are outdated.


BF3 causing crashes is very common from the experiences I've had over the past few weeks. The memory_corruption is likely due to BF3 and not due to hardware. Your other blue screen errors are USB related. Could you please list the devices plugged into your USB ports?


Edit: I also still see AVG on your computer. Please uninstall AVG using the AVG remover and install Microsoft Security Essentials in its place to run with Windows Firewall. Do this at least for testing purposes and until we can find a solution to your computer problems.

 

[Tbutter]

Okay so here is what I just did-----

I went into my BIOS and unclocked my system. Back to the original 3.4 GHz and a 4.3 GHz Turbo boost. I was around 4.5 GHz before. And also took the voltages down to stock. I am on my fourth game of BF3 with absolutly no problems besides lag.

USB: Logitech Mouse, TP-Link USG Adapter, 500 GB External Harddrive, Thermaltake Ultimate Keyboard, amd a Turtle Beach Headset.

This is a paid version of AVG not the free version and when im playing these games im turning it off.

 

[writhziden]

Okay so here is what I just did-----

I went into my BIOS and unclocked my system. Back to the original 3.4 GHz and a 4.3 GHz Turbo boost. I was around 4.5 GHz before. And also took the voltages down to stock. I am on my fourth game of BF3 with absolutly no problems besides lag.

USB: Logitech Mouse, TP-Link USG Adapter, 500 GB External Harddrive, Thermaltake Ultimate Keyboard, amd a Turtle Beach Headset.

This is a paid version of AVG not the free version and when im playing these games im turning it off.

I should probably start adding zigzag3143's "If you are overclocking, stop" to my blue screen help posts... Glad you found a possible solution. Keep us updated as to whether it keeps your system more stable.

 

[Tbutter]

Well I figured it would be worth a try.

I put my CPU Overclock Setting on Auto in AI Tweaker, and changed my Voltage down to 1.35V from 1.42V. It is still overclock to a 4.3 GHz freq. but the bus speed is down from 103.0 to 100.3 and a multiplier of 43. And it is running at 4.3 GHz in game.

Does this sound stable to you?? Its been good for 6 games now. and my CPU temps are 50-55 and GPU are 40-50 C.

 

[writhziden]

Well I figured it would be worth a try.

I put my CPU Overclock Setting on Auto in AI Tweaker, and changed my Voltage down to 1.35V from 1.42V. It is still overclock to a 4.3 GHz freq. but the bus speed is down from 103.0 to 100.3 and a multiplier of 43. And it is running at 4.3 GHz in game.

Does this sound stable to you?? Its been good for 6 games now. and my CPU temps are 50-55 and GPU are 40-50 C.

Sounds like a solid method, and the impression is more stability. Whether it means almost complete stability is hard to judge for a short duration. Typically, to determine a very stable machine, the machine must run normally (meaning you do your normal routine) for ~1 week without crashes.

 

[writhziden]

Did your overclocking changes provide stability in the long run? Let us know if you need anything.