Hello Tony, welcome to SF!
Quite a setup you've got there, looks good!
If this setup has been working fine for a longer period of time, we would suspect a change of some sort to have occurred for you to get these problems. However, looking at the dump, there is something wrong somewhere and for now it points to hardware...
HTML Code:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff88001002562, Address of the instruction which caused the bugcheck
Arg3: fffff8800d9f8a70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {UITZONDERING} Ongeldige instructie Er is geprobeerd een ongeldige instructie uit te voeren.
FAULTING_IP:
fltmgr!FltpPerformPreCallbacks+7f2
fffff880`01002562 ff ???
CONTEXT: fffff8800d9f8a70 -- (.cxr 0xfffff8800d9f8a70)
rax=fffffa80186b7e30 rbx=fffffa8013400000 rcx=0000000000000063
rdx=fffffa8012e16300 rsi=fffffa80186b7d30 rdi=fffffa80136e3800
rip=fffff88001002562 rsp=fffff8800d9f9458 rbp=fffffa8015f03fa0
r8=0000000000000000 r9=0000000000000000 r10=fffff8000366f348
r11=fffffa80186b7e80 r12=0000000000000008 r13=fffff8800d9f9b10
r14=fffffa80182ec300 r15=fffff8800d9f95d0
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
fltmgr!FltpPerformPreCallbacks+0x7f2:
fffff880`01002562 ff ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: fsx.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
fltmgr!FltpPerformPreCallbacks+7f2
fffff880`01002562 ff ???
LAST_CONTROL_TRANSFER: from fffff8800d9f95d0 to fffff88001002562
STACK_TEXT:
fffff880`0d9f9458 fffff880`0d9f95d0 : fffff880`0100482d 00000000`00000000 fffffa80`182ec3f2 fffff880`0d9f9b00 : fltmgr!FltpPerformPreCallbacks+0x7f2
fffff880`0d9f9558 fffff880`0100482d : 00000000`00000000 fffffa80`182ec3f2 fffff880`0d9f9b00 fffff880`0d9f9aa0 : 0xfffff880`0d9f95d0
fffff880`0d9f9560 fffff880`01022a9f : fffffa80`135eec60 00000000`00000000 fffffa80`182ec010 fffffa80`182ec320 : fltmgr!FltpPassThroughFastIo+0x4d
fffff880`0d9f95a0 fffff800`037e5b58 : 00000000`00000045 fffff880`0d9f99e0 fffffa80`00000080 00000000`000007ff : fltmgr!FltpFastIoQueryOpen+0x10f
fffff880`0d9f9640 fffff800`037e1ec8 : fffffa80`135bc8d0 fffff800`00000000 fffffa80`183747b0 fffff880`00000001 : nt!IopParseDevice+0xad8
fffff880`0d9f97d0 fffff800`037e30e6 : 00000000`00000000 fffffa80`183747b0 fffffa80`15e0f5f0 fffffa80`12dfdde0 : nt!ObpLookupObjectName+0x588
fffff880`0d9f98c0 fffff800`037c30d6 : 00000000`00000001 00000000`0008e308 00000000`00000001 fffff880`0d9f9c08 : nt!ObOpenObjectByName+0x306
fffff880`0d9f9990 fffff800`034e6f93 : fffffa80`148d0b60 00000000`001f0001 fffffa80`148d0b60 00000000`00000000 : nt!NtQueryAttributesFile+0x145
fffff880`0d9f9c20 00000000`76e816ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e816ea
FOLLOWUP_IP:
fltmgr!FltpPerformPreCallbacks+7f2
fffff880`01002562 ff ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: fltmgr!FltpPerformPreCallbacks+7f2
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff8800d9f8a70 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
A 3B is usually caused by System service, Device driver, graphics driver, ?memory... difficult to tell at his point so we'll also look for other telltale signs.
1 of those is a warning on the LogMeIn software that you appear to be using.
LogMeIn Kernel Information Provider ROOT\LEGACY_LMIINFO\0000 This device is not present, is not working properly, or does not have all its drivers installed.
LogMeIn Mirror Driver ROOT\DISPLAY\0000 39
There is something wrong there... I would de-install (for testing). If you really need this kind of software, maybe Teamviewer would help. I've seen no probs with W7 on that.
Assuming the logmein issue is not, by itself, causing BSOD's when playing the game... we normally go for HW tests in order of the likeliness of faults appearring on heavy usage.
The first would be memory testing:
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
RAM - Test with Memtest86+
Please post back any results...
Quote