BSOD-Gaming-SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

[Truther]

I have a semi new system build and get random blue screens when gaming i think its Logitech software and maybe something else any help would be awesome thanks!


On Sat 4/6/2013 10:04:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040613-19359-01.dmp
This was probably caused by the following module: ladfgscamd64.sys (ladfGSCamd64+0x7352)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF880040CC352, 0xFFFFF88003BA1168, 0xFFFFF88003BA09C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ladfgscamd64.sys
product: Logitech GSeries Headset
company: Logitech
description: Capture Filter Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ladfgscamd64.sys (Capture Filter Driver, Logitech).
Google query: Logitech SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sat 4/6/2013 10:04:41 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ladfgscamd64.sys (ladfGSCamd64!SBLMShutDownEngine+0x690A)
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF880040CC352, 0xFFFFF88003BA1168, 0xFFFFF88003BA09C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ladfgscamd64.sys
product: Logitech GSeries Headset
company: Logitech
description: Capture Filter Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ladfgscamd64.sys (Capture Filter Driver, Logitech).
Google query: Logitech SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

 

[koolkat77]

Seems to be caused by Driver for the Logitech GSeries Headset. Update to the latest version available and see if that stops the BSOD's. :ar: Driver Reference Table - ladfgscamd64.sys

[FONT="Lucida Console"]*** WARNING: Unable to verify timestamp for ladfGSCamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSCamd64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff880040cc352, fffff88003ba1168, fffff88003ba09c0}

Probably caused by : hardware ( ladfGSCamd64+7352 )

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

2: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff880040cc352, The address that the exception occurred at
Arg3: fffff88003ba1168, Exception Record Address
Arg4: fffff88003ba09c0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
ladfGSCamd64+7352
fffff880`040cc352 f00f8c0bfcffff  lock jl ladfGSCamd64+0x6f64 (fffff880`040cbf64)

EXCEPTION_RECORD:  fffff88003ba1168 -- (.exr 0xfffff88003ba1168)
ExceptionAddress: fffff880040cc352 (ladfGSCamd64+0x0000000000007352)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff88003ba09c0 -- (.cxr 0xfffff88003ba09c0)
rax=0000000000000200 rbx=fffffa800e8c3000 rcx=0000000000000000
rdx=404f60eb01485c01 rsi=000000000000015f rdi=0000000000000001
rip=fffff880040cc352 rsp=fffff88003ba13a0 rbp=0000000000000017
 r8=fffffa8012b43010  r9=fffffa8012b33010 r10=0000000000000156
r11=fffff88003ba1480 r12=fffffa8012b43b10 r13=fffffa800d2e4c9c
r14=000000000000015f r15=fffffa800d2e4000
iopl=0         nv up ei pl nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010203
ladfGSCamd64+0x7352:
fffff880`040cc352 f00f8c0bfcffff  lock jl ladfGSCamd64+0x6f64 (fffff880`040cbf64) [br=0]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

MISALIGNED_IP: 
ladfGSCamd64+7352
fffff880`040cc352 f00f8c0bfcffff  lock jl ladfGSCamd64+0x6f64 (fffff880`040cbf64)

LAST_CONTROL_TRANSFER:  from fffffa800e8c3000 to fffff880040cc352

FAILED_INSTRUCTION_ADDRESS: 
ladfGSCamd64+7352
fffff880`040cc352 f00f8c0bfcffff  lock jl ladfGSCamd64+0x6f64 (fffff880`040cbf64)

STACK_TEXT:  
fffff880`03ba13a0 fffffa80`0e8c3000 : fffff800`0000015c 00000000`0000015c 00000000`00000000 3fb99999`a0000000 : ladfGSCamd64+0x7352
fffff880`03ba13a8 fffff800`0000015c : 00000000`0000015c 00000000`00000000 3fb99999`a0000000 00000000`00000000 : 0xfffffa80`0e8c3000
fffff880`03ba13b0 00000000`0000015c : 00000000`00000000 3fb99999`a0000000 00000000`00000000 40800000`0000005b : 0xfffff800`0000015c
fffff880`03ba13b8 00000000`00000000 : 3fb99999`a0000000 00000000`00000000 40800000`0000005b 00000000`00000200 : 0x15c


FOLLOWUP_IP: 
ladfGSCamd64+7352
fffff880`040cc352 f00f8c0bfcffff  lock jl ladfGSCamd64+0x6f64 (fffff880`040cbf64)

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ladfGSCamd64+7352

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff88003ba09c0 ; kb

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_ladfGSCamd64.sys

BUCKET_ID:  X64_IP_MISALIGNED_ladfGSCamd64.sys

Followup: MachineOwner
---------
2: kd> lmvm ladfGSCamd64
start             end                 module name
fffff880`040c5000 fffff880`04127800   ladfGSCamd64 T (no symbols)           
    Loaded symbol image file: ladfGSCamd64.sys
    Image path: \SystemRoot\system32\DRIVERS\ladfGSCamd64.sys
    Image name: ladfGSCamd64.sys
    Timestamp:        Tue Apr 12 00:41:01 2011 (4DA34B3D)
    CheckSum:         00068224
    ImageSize:        00062800
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4[/FONT]

Please uninstall DAEMON Tools and any Alcohol % software. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run :ar:
sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

dtsoftbus01.sys             Fri Jan 13 19:45:46 2012 (4F10358A)

Daemon Tools driver Possible BSOD issues in Win7

Kaspersky has also been contributing to your crashes, as a test please remove it using its removal tool from here:

Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials is recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows
Malwarebytes Anti-Malware Free
Good and Free system security combination

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Check a drive for errors:
1. Check a drive for errors
2. Check your hard disk for errors in Windows 7
3. http://www.sevenforums.com/tutorials/433-disk-check.html

Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file.

To do this, follow these steps:

• Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7
  
• At the command prompt, type the following command, and then press ENTER: sfc /scannow
• The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions. http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

1. http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
2. http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Let us know the results.

Debug session time: Sun Apr  7 04:04:41.484 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\040613-19359-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 1:58:12.234
*** WARNING: Unable to verify timestamp for ladfGSCamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSCamd64.sys
Probably caused by : hardware ( ladfGSCamd64+7352 )
BugCheck 1000007E, {ffffffffc000001d, fffff880040cc352, fffff88003ba1168, fffff88003ba09c0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff880040cc352, The address that the exception occurred at
Arg3: fffff88003ba1168, Exception Record Address
Arg4: fffff88003ba09c0, Context Record Address
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_ladfGSCamd64.sys
MaxSpeed:     3500
CurrentSpeed: 3492
BiosVersion = 4.6.5
BiosReleaseDate = 01/29/2013
SystemManufacturer = EVGA INTERNATIONAL CO.,LTD
SystemProductName = E699 0.0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``