BSOD playing SWTOR, many different error codes

[manoble522]

Just replaced my old failed SSD. Fresh copy of Win7Pro-x64. MSE with default settings installed. Nvidia drivers version 285.62 installed. I get BSOD when playing SWTOR. Attached files.

Any assistance would be greatly appreciated.

Thanks,
Matt

 

[manoble522]

Anyone have any ideas on this? Any help would be greatly appreciated. Thanks.

 

[writhziden]

[list=1]
[*]

Loading Dump File [F:\BSODDmpFiles\manoble522\Jan_2012\Windows_NT6_BSOD_jcgriff2\011912-12168-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03062000 PsLoadedModuleList = 0xfffff800`032a7670
Debug session time: Wed Jan 18 23:29:49.444 2012 (GMT-7)
System Uptime: 0 days 0:41:31.615
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800030de03b, fffff88007812240, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+160 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800030de03b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007812240, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiSystemServiceExit+160
fffff800`030de03b 488b8de8000000  mov     rcx,qword ptr [rbp+0E8h]

CONTEXT:  fffff88007812240 -- (.cxr 0xfffff88007812240)
rax=0000000000000000 rbx=000000000ffbf7bc rcx=fffffa800d5fd140
rdx=0000000000000000 rsi=00000000fffa4000 rdi=00000000fffa6000
rip=fffff800030de03b rsp=fffff88007812c20 rbp=fffff88007812ca0
 r8=000000000febe0b8  r9=000000000ffbf7d8 r10=0000000000000000
r11=fffffa800d5fd140 r12=0000000074a57e68 r13=000000000febfd20
r14=000000000febea20 r15=0000000074a22450
iopl=0         nv up di pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010046
nt!KiSystemServiceExit+0x160:
fffff800`030de03b 488b8de8000000  mov     rcx,qword ptr [rbp+0E8h] ss:0018:fffff880`07812d88=0000000074a716ba
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  swtor.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000074a716ba to fffff800030de03b

STACK_TEXT:  
fffff880`07812c20 00000000`74a716ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x160
00000000`0febe0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a716ba


FOLLOWUP_IP: 
nt!KiSystemServiceExit+160
fffff800`030de03b 488b8de8000000  mov     rcx,qword ptr [rbp+0E8h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiSystemServiceExit+160

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff88007812240 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceExit+160

BUCKET_ID:  X64_0x3B_nt!KiSystemServiceExit+160

Followup: MachineOwner
---------
[*]
Loading Dump File [F:\BSODDmpFiles\manoble522\Jan_2012\Windows_NT6_BSOD_jcgriff2\011812-12480-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03060000 PsLoadedModuleList = 0xfffff800`032a5670
Debug session time: Wed Jan 18 22:46:59.212 2012 (GMT-7)
System Uptime: 0 days 22:57:12.383
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {4, 2, 0, fffff800030be3f0}

Probably caused by : kbdclass.sys ( kbdclass!KeyboardClassServiceCallback+47e )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030be3f0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330f100
 0000000000000004 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeInsertQueueApc+8c
fffff800`030be3f0 33d2            xor     edx,edx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffd310 -- (.trap 0xfffff88002ffd310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800a4dbc00
rdx=fffffa800a4dbbb0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030be3f0 rsp=fffff88002ffd4a0 rbp=0000000000000002
 r8=0000000000000000  r9=fffffa800a4dbbb0 r10=0000000000000000
r11=fffff88002ffd502 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeInsertQueueApc+0x8c:
fffff800`030be3f0 33d2            xor     edx,edx
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030dc1e9 to fffff800030dcc40

STACK_TEXT:  
fffff880`02ffd1c8 fffff800`030dc1e9 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ffd1d0 fffff800`030dae60 : fffffa80`0940ad40 fffff880`1306d500 fffffa80`08df3550 fffffa80`0a4dbb60 : nt!KiBugCheckDispatch+0x69
fffff880`02ffd310 fffff800`030be3f0 : fffffa80`0a4dbb60 00000000`00000002 00000000`00000000 fffffa80`08e99b28 : nt!KiPageFault+0x260
fffff880`02ffd4a0 fffff800`030e0843 : fffffa80`09a2a070 00000000`a000000c 00000000`00000000 fffffa80`0a335000 : nt!KeInsertQueueApc+0x8c
fffff880`02ffd500 fffff880`0401ce0e : 00000000`00000004 fffffa80`0aa24e06 fffffa80`0aa24e30 00000000`00000000 : nt!IopfCompleteRequest+0xb63
fffff880`02ffd5f0 fffff880`047f3978 : 00000000`00000002 fffff880`02ffd700 00000000`0000000e fffff880`13157df1 : kbdclass!KeyboardClassServiceCallback+0x47e
fffff880`02ffd670 fffff880`07451629 : fffffa80`0a9fdf58 fffffa80`0aa237f0 fffffa80`00000001 00000000`0000000e : kbdhid!KbdHid_InsertCodesIntoQueue+0x118
fffff880`02ffd6d0 fffff880`07451894 : fffffa80`00000023 00000000`00000000 00000000`00000000 00000000`00000001 : HIDPARSE!HidP_KbdPutKey+0x3d
fffff880`02ffd700 fffff880`074517d2 : 00000000`00000000 fffff880`0744f9d6 00000000`00000007 00000000`00000000 : HIDPARSE!HidP_TranslateUsage+0x84
fffff880`02ffd740 fffff880`047f3672 : 00000000`00000000 fffffa80`0a9fdeec fffffa80`0a9fde10 00000000`00000000 : HIDPARSE!HidP_TranslateUsageAndPagesToI8042ScanCodes+0xde
fffff880`02ffd7a0 fffff800`030e0021 : fffffa80`0908148b fffff880`00000001 fffffa80`00000000 fffff880`077ecb2b : kbdhid!KbdHid_ReadComplete+0x276
fffff880`02ffd820 fffff880`077e59c4 : fffffa80`09a788f0 fffffa80`09a78806 fffffa80`0aa2ac00 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02ffd910 fffff880`077e5c2d : fffffa80`09a94f02 fffffa80`09a94f20 fffffa80`0aa2aca0 00000000`00000008 : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff880`02ffd9a0 fffff800`030e0021 : fffffa80`0aa28fbb 00000000`00000000 fffffa80`0aa2ab01 fffffa80`0aa28bd0 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff880`02ffda30 fffff880`0456c631 : fffffa80`08d4b050 fffffa80`082e3500 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02ffdb20 fffff880`0456cb0f : fffffa80`0ac4c402 fffffa80`0aa28bd0 00000000`ffffffff fffffa80`08d4beb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02ffdc00 fffff880`0456a66f : fffffa80`08d4beb0 fffffa80`08d4b1a0 fffffa80`08d4c050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02ffdc60 fffff880`0455bf89 : fffffa80`08d4b050 00000000`00000000 fffffa80`08d4be02 fffffa80`08d4beb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02ffdca0 fffff800`030e80ac : fffff880`02fd5180 fffffa80`08d4beb0 fffffa80`08d4bec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffdcd0 fffff800`030d496a : fffff880`02fd5180 fffff880`02fe0040 00000000`00000000 fffff880`0455bdb0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
kbdclass!KeyboardClassServiceCallback+47e
fffff880`0401ce0e 488d4e20        lea     rcx,[rsi+20h]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  kbdclass!KeyboardClassServiceCallback+47e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kbdclass

IMAGE_NAME:  kbdclass.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc116

FAILURE_BUCKET_ID:  X64_0xA_kbdclass!KeyboardClassServiceCallback+47e

BUCKET_ID:  X64_0xA_kbdclass!KeyboardClassServiceCallback+47e

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

[*]
Loading Dump File [F:\BSODDmpFiles\manoble522\Jan_2012\Windows_NT6_BSOD_jcgriff2\011812-11653-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03299670
Debug session time: Tue Jan 17 23:48:28.863 2012 (GMT-7)
System Uptime: 0 days 1:36:52.034
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800030dfce0, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiCheckAging+50 )

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

3: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800030dfce0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiCheckAging+50
fffff800`030dfce0 48c1e80c        shr     rax,0Ch

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003303100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  swtor.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000311c588 to fffff800030d0c40

STACK_TEXT:  
fffff880`0b705048 fffff800`0311c588 : 00000000`0000001e ffffffff`c0000005 fffff800`030dfce0 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b705050 fffff800`030d02c2 : fffff880`0b705828 00000000`001ff623 fffff880`0b7058d0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`0b7056f0 fffff800`030cebca : fffff880`02fd5180 00001f80`00000001 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0b7058d0 fffff800`030dfce0 : 00000000`00000000 00000000`00000002 00000000`00060001 00000580`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`0b705a60 fffff800`030ddf98 : fffff880`0b705b40 00000000`ff8d9020 fffff880`0b705c20 fffff680`007fc6c8 : nt!MiCheckAging+0x50
fffff880`0b705ac0 fffff800`030ced6e : 00000000`00000001 00000000`ff8d9020 00000000`0051e301 00000000`3b52a3f9 : nt!MmAccessFault+0x3d8
fffff880`0b705c20 00000000`77d879dd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0c3624d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77d879dd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCheckAging+50
fffff800`030dfce0 48c1e80c        shr     rax,0Ch

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiCheckAging+50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!MiCheckAging+50

BUCKET_ID:  X64_0x1E_nt!MiCheckAging+50

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


[/list]

1. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
2. Fault due to your keyboard. Are you using a gaming keyboard, by chance? Other possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
3. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking any hardware, please stop.
  
  
  
• I also note that your latest dump files are from January 19th, and today is February 7th. If your clock is not set correctly, the system can be unstable.
  
  
  
• Obtain updated drivers for your keyboard.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  

 

[manoble522]

Thank you writhziden, JMH, and Dave76 for your collective response! I appreciate it!

1. Possible causes are Memory problems…
- See memory comment below.

Corrupted hard disk file system…
- Just replaced faulty SSD and installed fresh copy of Win 7 Pro x64. Ran SDD and HDD utilities to check drive status. All came back clean. Also ran check disk on all drives with success on each.

Corrupted System Files…
- Ran sfc /scannow and it completed without error or fixing anything.

Graphics Driver…
- Uninstalled graphics driver until default windows vga driver was being used. Performed a clean reinstall of latest drivers (285.62 for x64), performed a clean install of latest beta drivers(290.53 for x64), both having the same results, BSODs no matter which version. Maybe I should try an older version that might be more stable? What would you suggest?

Drivers…
- I believe all my drivers are up to date, including chipset.


2. Fault due to your keyboard. Are you using a gaming keyboard, by chance?
- Yes. I am using the Logitech G110 gaming keyboard. Reinstalled latest drivers for the keyboard.

Other possible causes are Memory problems…
- See memory comment below.

Corrupted hard disk file system…
Corrupted System Files…
- Same comments as above.

BIOS…
- I have not done any sort of BIOS updates. Would you suggest performing this action?

Lack of Windows updates…
- Windows updates are enabled. Latest updates are installed.

Antivirus Software…
- Per previous advice from you guys I switched to MSE and it is up to date and enabled. Default settings used. Full Scan came back clean.

Backup…
- No backup running, scheduled, or ever performed.

Hardware…
- Not too sure how to respond to this. Maybe I just have the perfect storm of hardware. Last resort I might try a new motherboard. Would do you think?


3. Possible causes are Memory problems…
- See memory comment below.

Viruses…
- MSE Full Scan return with nothing found. Is there any other program I should run to check for viruses besides MSE?

Corrupted hard disk file system…
Corrupted System Files…
Lack of Windows updates…
Drivers…
- Same comments as above.


If you are overclocking any hardware, please stop.
- Stopped overclocking CPU. Set everything to Auto in BIOS. CPU at default clock.

I also note that your latest dump files are from January 19th, and today is February 7th. If your clock is not set correctly, the system can be unstable.
- The dates are correct. They are from that date. My original post was 2 weeks ago.

Obtain updated drivers for your keyboard.
- Reinstalled latest drivers from Logitech.

Run the boot version of Memtest86+
- Ran Memtest86+ as suggested in a previous post. Ran both sticks in slots I normally use them in, 20+ passes overnight and workday without errors. Ran each stick seperatly in multiple slots. Each 20+ passes overnight and workday without errors. Reinstalled sticks as specified in MB manual for dual channel.

 

[writhziden]

Thank you writhziden, JMH, and Dave76 for your collective response! I appreciate it!


Corrupted hard disk file system…
- Just replaced faulty SSD and installed fresh copy of Win 7 Pro x64. Ran SDD and HDD utilities to check drive status. All came back clean. Also ran check disk on all drives with success on each.

BIOS…
- I have not done any sort of BIOS updates. Would you suggest performing this action?

You're welcome.

Glad your drives came up clean.

One of the first steps when system failure results in a system with new technology, such as an SSD, is to update the BIOS. You should check your BIOS updates and see if any are known to provide better support for SSDs.

Corrupted System Files…
- Ran sfc /scannow and it completed without error or fixing anything.

Graphics Driver…
- Uninstalled graphics driver until default windows vga driver was being used. Performed a clean reinstall of latest drivers (285.62 for x64), performed a clean install of latest beta drivers(290.53 for x64), both having the same results, BSODs no matter which version. Maybe I should try an older version that might be more stable? What would you suggest?

Drivers…
- I believe all my drivers are up to date, including chipset.

Good news that your Windows files are clean.

Sometimes an older graphics card driver can help in these situations.

Did you update your drivers via the SSD manufacturer, as well? See post#2 by usasma and the quote about SSDs.

2. Fault due to your keyboard. Are you using a gaming keyboard, by chance?
- Yes. I am using the Logitech G110 gaming keyboard. Reinstalled latest drivers for the keyboard.

Antivirus Software… [/B]
- Per previous advice from you guys I switched to MSE and it is up to date and enabled. Default settings used. Full Scan came back clean.

Viruses…
- MSE Full Scan return with nothing found. Is there any other program I should run to check for viruses besides MSE?

Backup…
- No backup running, scheduled, or ever performed.

Any change after updating the keyboard drivers?

MSE is a good antivirus for stability. For security, though, we recommend supplementing it with Malwarebytes the free version (we do not suggest starting the trial) and running full scans at least weekly. Also, see the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 by panais.

We can rule out a backup program causing the problem, but we do recommend backing up your data from time to time. I use http://www.sevenforums.com/tutorials/73828-imaging-free-macrium.html myself, but http://www.sevenforums.com/tutorials/663-backup-complete-computer-create-image-backup.html?ltr=B works, as well.

Hardware…
- Not too sure how to respond to this. Maybe I just have the perfect storm of hardware. Last resort I might try a new motherboard. Would do you think?

If you are overclocking any hardware, please stop.
- Stopped overclocking CPU. Set everything to Auto in BIOS. CPU at default clock.

I also note that your latest dump files are from January 19th, and today is February 7th. If your clock is not set correctly, the system can be unstable.
- The dates are correct. They are from that date. My original post was 2 weeks ago.

Run the boot version of Memtest86+
- Ran Memtest86+ as suggested in a previous post. Ran both sticks in slots I normally use them in, 20+ passes overnight and workday without errors. Ran each stick seperatly in multiple slots. Each 20+ passes overnight and workday without errors. Reinstalled sticks as specified in MB manual for dual channel.

I would try the BIOS update and making sure your SSD has all drivers up to date and see if the system is more stable. If it is not, then start replacing hardware.

Overclocking can cause instability, so we usually recommend turning it off while trying to determine how to make the system more stable. Has it helped to turn it off at all?

Okay, just making sure the clocks are all set properly on the computer.

Most likely, the memory is good if you let it run that long without any errors.