BSOD while playing battlefield 3 multiplayer

#1
I recently installed battlefield 3, and I've been playing the campaign without much trouble, but when I'm playing multiplayer I'll get a blue screen about 5-10 minutes into a match. I've attached the SF diagnostic details and the screenshots of CPU-Z. Thanks for any help in advance.
 


Attachments

#2
Sorry, I've attached another ZIP because I didn't include the other SPD slots in CPU-Z. I only added slot #3. Slot #2 and #4 were both blank.
 


Attachments

Trouble

Noob Whisperer
#3
Start with this driver
L6TPortB.sys 12/11/2008 Guitar Port Line 6. Update, uninstall or as a last resort search for and rename to L6TPortB.OLD (probably here C:\Windows\System32\Drivers but may be elsewhere)
All eight of your dump files are identical
Code:
Unable to load image \SystemRoot\System32\Drivers\L6TPortB.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for L6TPortB.sys
*** ERROR: Module load completed but symbols could not be loaded for L6TPortB.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 92b2eed1, 89ddebc8, 89dde7a0}
[COLOR=#ff0000][U][B]Probably caused by : L6TPortB.sys ( L6TPortB+10ed1 )[/B][/U][/COLOR]
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 92b2eed1, The address that the exception occurred at
Arg3: 89ddebc8, Exception Record Address
Arg4: 89dde7a0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
L6TPortB+10ed1
92b2eed1 804b0720        or      byte ptr [ebx+7],20h
EXCEPTION_RECORD:  89ddebc8 -- (.exr 0xffffffff89ddebc8)
ExceptionAddress: 92b2eed1 [COLOR=#ff0000][U][B](L6TPortB[/B][/U][/COLOR]+0x00010ed1)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 00000007
Attempt to write to address 00000007
CONTEXT:  89dde7a0 -- (.cxr 0xffffffff89dde7a0)
eax=84aa09f0 ebx=00000000 ecx=86903300 edx=00000000 esi=86903158 edi=868a7280
eip=92b2eed1 esp=89ddec90 ebp=89dded38 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
[COLOR=#ff0000][U][B]L6TPortB[/B][/U][/COLOR]+0x10ed1:
92b2eed1 804b0720        or      byte ptr [ebx+7],20h       ds:0023:00000007=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  00000001
EXCEPTION_PARAMETER2:  00000007
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82ba7718
Unable to read MiSystemVaType memory at 82b87160
 00000007 
FOLLOWUP_IP: 
[COLOR=#ff0000][U][B]L6TPortB[/B][/U][/COLOR]+10ed1
92b2eed1 804b0720        or      byte ptr [ebx+7],20h
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER:  from 92b20b2e to 92b2eed1
STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
89dded38 92b20b2e 00000000 875bc980 00000000[COLOR=#ff0000][U][B] L6TPortB[/B][/U][/COLOR]+0x10ed1
89dded50 82c4d66d 871493d0 ac63ac05 00000000   [B] [COLOR=#ff0000]L6TPortB[/COLOR][/B]   +0x2b2e
89dded90 82aff0d9 92b20d0e 871493d0 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME: [COLOR=#ff0000]    [B]L6TPortB[/B][/COLOR]   +10ed1   
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME:[COLOR=#ff0000][U][B] L6TPortB[/B][/U][/COLOR]
IMAGE_NAME:  [COLOR=#ff0000][U][B]L6TPortB.[/B][/U][/COLOR]sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4941a086
STACK_COMMAND:  .cxr 0xffffffff89dde7a0 ; kb
FAILURE_BUCKET_ID:  0x7E_[COLOR=#ff0000][U][B]L6TPortB[/B][/U][/COLOR]+10ed1
BUCKET_ID:  0x7E_[COLOR=#ff0000][U][B]L6TPortB[/B][/U][/COLOR]+10ed1
Followup: MachineOwner
If Blue Screens persist update these older drivers as well
LHidFilt.Sys 9/26/2008, LMouFilt.Sys 9/26/2008, L8042Kbd.sys 9/26/2008 from here Logitech - Support & Software Downloads
Rt86win7.sys 2/26/2009 from here Realtek
Keep us posted
Regards
Randy
 


#4
Thanks a lot mate, will give it a go and report back with any progress.
 


#5
Well that seems to have done the trick, been playing flawlessly since I updated the tone port drivers. It makes sense now that the line 6 drivers were causing the problem, because I had just installed windows 7 from windows XP and I was in a hurry to install drivers for everything, so I installed the XP version of the tone port drivers I had on my hdd. I feel a little stupid for that, but at least its all good now. Thanks for the help!
 


Trouble

Noob Whisperer
#6
Good to hear that you were able to resolve your problem and thanks for posting back and updating your thread with that information.
Thanks for joining our community and we hope to continue to see you around the forum.
Any further issues just let us know.
Regards
Randy
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.