JAJ_TV

Thanks for all this help guys! I've done tests which each RAM chip in one by one but would never cause a BSOD however when putting both in together again it caused a BSOD but have done a BIOS update and now I've been able to do a whole flight on Ultra everything (was trying to see if it would BSOD) So I'm hoping that has fixed it, ill update with more flights etc but I'm hoping it has now been sorted with the update! Once again thanks for the help its really appreciated!

Right initial results looking good still in the sim etc going to now try to a short 1 journey if it doesn't BSOD during the trip i would believe the issue is fixed, once again thanks for all your help!

Yeah im just having one of those days right just updated the MB lets give it another try and see what happens ill update with any results i encounter

Right ive tired both sticks by themselves but were fine put them both in and BSOD again - im stuck for what to do!

So tested both sticks neither one throwing up BSOD ill chuck both in again and see if i can get it to BSOD if not i guess its MB

Also have just done a SFC scan and it fixed all these corrupted drivers - 2019-02-07 10:07:11, Info CSI 000053df [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired 2019-02-07 10:09:12, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP 2019-02-07 10:09:12, Info CBS TiWorker signaled for shutdown, going to exit. 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: ExecutionEngineFinalize 2019-02-07 10:09:12, Info CBS Execution Engine Finalize 2019-02-07 10:09:12, Info CBS Execution Engine Finalize 2019-02-07 10:09:12, Info CBS Ending the TiWorker main loop. 2019-02-07 10:09:12, Info CBS Starting TiWorker finalization. 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: ManifestCacheFinalize 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: ExecutionEngineFinalize 2019-02-07 10:09:12, Info CBS CBS Engine already deativated 2019-02-07 10:09:12, Info CBS CBS Engine already deativated 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: PackageTrackerFinalize 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: CoreResourcesUnload 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: SessionManagerFinalize 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: CapabilityManagerFinalize 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: WcpUnload 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: DrupUnload 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: CfgMgr32Unload 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: DpxUnload 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: SrUnload 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: CbsEsdUnload 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: CbsEventUnregister 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: AppContainerUnload 2019-02-07 10:09:12, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end. 2019-02-07 10:09:12, Info CBS Ending TiWorker finalization. 2019-02-07 10:09:12, Info CBS Ending the TrustedInstaller main loop. 2019-02-07 10:09:12, Info CBS Starting TrustedInstaller finalization. 2019-02-07 10:09:12, Info CBS Ending TrustedInstaller finalization.

No worries at all anything i can to make the life easier for those helping me aha! I have got 2 sticks 8GB each - the only time i get BSOD is flying in P3D so should i try it with each stick in and wait for one to go wrong? Once again thanks for the help!

Hey guys here are the results of my MemTest86 https://imgur.com/gallery/HRZOP3r

Yeah i run other CPU intensive games like FSX SE and they run fine they just get OOM which is why i moved to P3D which is when the BSOD started coming but my thought process is that FSX only ever let there be 3.5GB VRAM because of 32bit but now P3D can use all of it maybe it is causing an issue with my RAM that i havent seen before. Right i have done the MemTest86 over night came back with 3 errors i will try post a two pics i took of the test results. Maybe you guys can make better sense of it than me.

Thank you im going to give it a try and see what it comes back with, its strange because if it is a OC issue my PC has been stable on it for months since i built it, however i only ever get the BSOD when flying in P3D

Hey Dave, Ive updated everything on the PC with Driver booster and still getting BSOD, ive downloaded app crash view however its not showing P3D or any app crash around the time when the BSOD occurred. System Specs: i7-8700K OC @5GHz ASUS ROG STRIX GTX 1080TI ASUS ROG STRIX Z370-F Gaming MB Samsung Evo 960 512GB SSD 2TB Hybrid drive Corsair H100i V2 Corsair HX850i PSU Corsair Vengence LPX 16GB 3000MHz RAM

Hey guys im experiencing some BSOD as well only recently installed P3d V4.4 moved over from FSX SE but getting this from Mini Dump Any help would be hugely appreciated!: Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000096, Exception code that caused the bugcheck Arg2: fffff800249ca919, Address of the instruction which caused the bugcheck Arg3: ffffae8dd01a7010, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction. FAULTING_IP: nt!KiSystemServiceExit+1ce fffff800`249ca919 0f30 wrmsr CONTEXT: ffffae8dd01a7010 -- (.cxr 0xffffae8dd01a7010) rax=0000000000000001 rbx=0000000000000001 rcx=0000000000000049 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800249ca919 rsp=ffffae8dd01a7a00 rbp=ffffae8dd01a7a80 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=ffff9d0bade4d700 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 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+0x1ce: fffff800`249ca919 0f30 wrmsr Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: Prepar3D.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 00007ff8e397b024 to fffff800249ca919 STACK_TEXT: ffffae8d`d01a7a00 00007ff8`e397b024 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x1ce 000000e0`ab1bfce8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff8`e397b024 FOLLOWUP_IP: nt!KiSystemServiceExit+1ce fffff800`249ca919 0f30 wrmsr SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiSystemServiceExit+1ce FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5c2b0c3d STACK_COMMAND: .cxr 0xffffae8dd01a7010 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!KiSystemServiceExit+1ce BUCKET_ID: X64_0x3B_nt!KiSystemServiceExit+1ce Followup: MachineOwner