Windows 7 BSOD while doing anything associated with BF3 - HELP

[Taltal]

Hey guys, for a few days now I am trying to play BF3 but I keep getting crashes to blue screen saying Windows is shutting down to prevent damage.

ZA-G77-D3H by Gigabye
i5-3570K overclocked but back to original due to being the main suspect for the crash, which is not, at 3.4GHz
Gigabyte 7850 2GB
Can anyone please help me?
Downloading BF3 on origin - crash. Going to Battle Log - crash, playing BF3 crash.... All after only a couple of mins.
Anyone please help, I did everything people said on any forum possible.... Help me PLEASE!
Thanks so much in advance and have a nice day.

 

[Trouble]

Hello and welcome to the forums.
First make sure your machine is configured properly to facilitate the collection of .dmp files.

Go to Start and type in sysdm.cpl and press Enter

Click on the Advanced tab

Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Then:
Please read the first post in this sticky thread here Link Removed
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area Link Removed .
Good luck
Randy

 

[Taltal]

Working on it now Sorry, I just got home.

 

[Taltal]

I got this for now, CPU-Z is taking an un-normal ammount of time to download. Meanwhile, that's what I got for you Maybe there's no need for the CPU-Z

 

[Taltal]

Just got CPU-Z, pictures inside Please hurry I am REALLY sick of this...

 

[Trouble]

All four dump files are identical and blame
ta2usb.sys as the offending driver, which seems to be related to Native Instruments Traktor Audio 2 NATIVE INSTRUMENTS : HOME | HARDWARE AND SOFTWARE FOR MUSICIANS, PRODUCERS, DJS, GUITAR AND BASS PLAYERS
My suggestion would be to start there. Remove the device, uninstall any and all associated programs and check and confirm that the drivers is no longer loading.
Check with the device / software vendor and confirm that their product is Windows 7 64bit compatible and see if the have an update, hotfix or patch that may resolve the issue.
Confirm that the machine is not Blue Screening with the device and software removed.

BugCheck 10D, {6, 3, 57ff76896d8, fffffa80080887c0}
Unable to load image \SystemRoot\System32\Drivers\[COLOR=#ff0000][U][B]ta2usb.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for[COLOR=#ff0000][U][B] ta2usb.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for ta2usb.sys
[COLOR=#ff0000][U][B]Probably caused by : [/B][/U][/COLOR][COLOR=#FF0000][U][B]ta2usb.sys[/B][/U][/COLOR] ( [COLOR=#ff0000][U][B]ta2usb[/B][/U][/COLOR]+6e66 )
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000006, A fatal error was made in handling a WDF request. In this case,
    Parameter 2 further specifies the type of fatal error that has
    been made, as defined by the enumeration WDF_REQUEST_FATAL_ERROR.
Arg2: 0000000000000003, The driver attempted to send a framework request that has
    already been sent to an I/O target.
Arg3: 0000057ff76896d8, The WDF request handle value.
Arg4: fffffa80080887c0, Reserved.
BUGCHECK_STR:  0x10D_6
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  bf3.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff88000f0c589 to fffff80002e951c0
STACK_TEXT:  
fffff800`00ba2928 fffff880`00f0c589 : 00000000`0000010d 00000000`00000006 00000000`00000003 0000057f`f76896d8 : nt!KeBugCheckEx
fffff800`00ba2930 fffff880`00f0ce2b : 00000000`00000000 fffffa80`08955a00 00000000`00000000 fffffa80`08952e40 : Wdf01000!FxIoTarget::SubmitLocked+0xd5
fffff800`00ba29f0 fffff880`00f22767 : 00000000`00000000 00000000`00000000 00000000`00000004 fffffa80`08955a80 : Wdf01000!FxIoTarget::Submit+0x63
fffff800`00ba2a30 fffff880`0603ae66 : fffffa80`08088910 fffffa80`08976920 fffffa80`08952e40 fffffa80`08926a20 : Wdf01000!imp_WdfRequestSend+0x413
fffff800`00ba2a80 fffffa80`08088910 : fffffa80`08976920 fffffa80`08952e40 fffffa80`08926a20 00000000`00000004 : [COLOR=#ff0000][U][B]ta2usb[/B][/U][/COLOR]+0x6e66
fffff800`00ba2a88 fffffa80`08976920 : fffffa80`08952e40 fffffa80`08926a20 00000000`00000004 fffffa80`088e8840 : 0xfffffa80`08088910
fffff800`00ba2a90 fffffa80`08952e40 : fffffa80`08926a20 00000000`00000004 fffffa80`088e8840 00000000`00000000 : 0xfffffa80`08976920
fffff800`00ba2a98 fffffa80`08926a20 : 00000000`00000004 fffffa80`088e8840 00000000`00000000 00000000`00000000 : 0xfffffa80`08952e40
fffff800`00ba2aa0 00000000`00000004 : fffffa80`088e8840 00000000`00000000 00000000`00000000 fffffa80`08928c00 : 0xfffffa80`08926a20
fffff800`00ba2aa8 fffffa80`088e8840 : 00000000`00000000 00000000`00000000 fffffa80`08928c00 fffff880`0603b690 : 0x4
fffff800`00ba2ab0 00000000`00000000 : 00000000`00000000 fffffa80`08928c00 fffff880`0603b690 0000057f`f76af358 : 0xfffffa80`088e8840
STACK_COMMAND:  kb
FOLLOWUP_IP: 
[COLOR=#ff0000][U][B]ta2usb[/B][/U][/COLOR]+6e66
fffff880`0603ae66 ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  [COLOR=#ff0000][U][B]ta2usb[/B][/U][/COLOR]+6e66
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [COLOR=#ff0000][U][B]ta2usb[/B][/U][/COLOR]
IMAGE_NAME:  [COLOR=#ff0000][U][B]ta2usb.sys[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4f44e159
FAILURE_BUCKET_ID:  X64_0x10D_6_[U][B][COLOR=#ff0000]ta2usb[/COLOR][/B][/U]+6e66
BUCKET_ID:  X64_0x10D_6_[COLOR=#ff0000][U][B]ta2usb[/B][/U][/COLOR]+6e66

Additionally see if there is anything more recent for this driver
LGPBTDD.sys 7/1/2009 Logitech Game Panel here Link Removed

 

[Taltal]

Will do that. But right now I really wana sleep. Thank you so much!
Do you really think my DAC is the cause for BF3 BSOD? I would never have even consider it! And Ill see if they have any new driver for the logitech G19, but I think they don't since I recently installed it.
Oh, and thank you SO MUCH!

 

[Trouble]

All I can say is what the dump files are indicating at this time. All four which were all dated today, within about three hours of one another reported the same issue as indicated above.
But as a side note I might suggest that some people have found more success when running BF3 if they use their system's BIOS utility to turn off EIST and enable XMP mode for their memory. So you may want to give that a try.
Regards
Randy

 

[Taltal]

It's working just fine now!
THank you so much! Im gonna find a good, working version of the driver and use it.
Untill next time!
Thanks so much ones more!
/love