P3DV4.4 Crash

[JAJ_TV 0]

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.
 

[vc10man 732]

Yes, try one stick at a time to see which throws up that BSOD error. You'll soon have the problem solved. If neither stick throws up that BSOD, then I'd suspect your motherboard memory controller. Depending on which make of motherboard it is, you may need to get the BIOS updated/flashed, etc. Hope this helps.

[vc10man 732]

8 minutes ago, JAJ_TV said:

Once again thanks for the help!

No sweat. Welcome.

[JAJ_TV 0]

1 hour ago, vc10man said:

Yes, try one stick at a time to see which throws up that BSOD error. You'll soon have the problem solved. If neither stick throws up that BSOD, then I'd suspect your motherboard memory controller. Depending on which make of motherboard it is, you may need to get the BIOS updated/flashed, etc. Hope this helps.

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

[JAJ_TV 0]

2 hours ago, vc10man said:

Yes, try one stick at a time to see which throws up that BSOD error. You'll soon have the problem solved. If neither stick throws up that BSOD, then I'd suspect your motherboard memory controller. Depending on which make of motherboard it is, you may need to get the BIOS updated/flashed, etc. Hope this helps.

 

3 hours ago, Jim Young said:

I do not think a bad OC will cause a BSOD.  Bad OC's usually result in an NTDLL.dll error or StackHash.  Think bad memory stick but then the BSOD Code indicates Windows was being updated and there are now driver issues.  OP updated all drivers but did not check for corrupted windows drivers.

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

[vc10man 732]

What did I just say above? If both sticks are okay, then its most probably the motherboard memory controller, in which case first try a BIOS update, or replace the motherboard. Are the afore-mentioned help suggestions  so difficult to follow or understand? It's not rocket science😀

 

 

 

Edited February 7, 2019 by vc10man

[JAJ_TV 0]

23 minutes ago, vc10man said:

What did I just say above? If both sticks are okay, then its most probably the motherboard memory controller, in which case first try a BIOS update, or replace the motherboard. Are the afore-mentioned help suggestions  so difficult to follow or understand? It's not rocket science😀

 

 

 

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  

[vc10man 732]

Great. That's the +ve way to resolve issues, or seek help. Well Done.

[JAJ_TV 0]

30 minutes ago, vc10man said:

Great. That's the +ve way to resolve issues, or seek help. Well Done.

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!

[vc10man 732]

11 minutes ago, JAJ_TV said:

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!

Good to know, because I have known RAM issues causing MemTest86 failures  due to simple things like dirt, etc in the memory slots. Hopefully, re-seating the modules has resolved any BSOD issues.

[Bob Scott 7,719]

Another thing I'd do is bump up the memory voltage just a little bit.  It looks like the memory might be running right on the ragged edge of stability.  Try bumping it up maybe a hundredth of a volt.  Another possibility is to leave it at its current voltage and reduce the clock speed slightly.

Those corrupted drivers are a bad sign, though...a faulty memory module can cause progressive corruption of files on the computer, and who knows what else might have been affected beyond the drivers while operating with that misbehaving RAM.

As far as BSODs, yes, they absolutely can be and quite often are caused by hardware...I don't know any serious overclockers that haven't seen a BSOD while pushing a system to its limits in a clocking drill.  In fact, certain types of BSODs are important clues as to what parts of the mobo aren't keeping up...some are associated with CPU core, some with uncore, etc.  BSODs associated with IRQ_NOT_EQUAL_TO errors are often associated with failing video cards.  And so on.

Regards

[Jim Young 2,356]

OP states he only gets BSOD's with P3Dv4.4 and we all know for a fact it cannot be P3Dv4.4 that causes BSOD's. However, if you are adding 32 bit software that is not backward compatible, that should cause a crash but not sure it would be a BSOD.  I would suspect if a third party program that is not 64 bit might affect drivers required to operate that program.  I recently spent hours searching for the cause of my BSOD's and it was a bad memory module.  The system read it as if it was working perfectly and tests were not crashing the system, but, when removing it, the crashes stopped and my system has been working perfectly since then.  BSOD's can be frustrating for sure!

[JAJ_TV 0]

1 hour ago, Jim Young said:

OP states he only gets BSOD's with P3Dv4.4 and we all know for a fact it cannot be P3Dv4.4 that causes BSOD's. However, if you are adding 32 bit software that is not backward compatible, that should cause a crash but not sure it would be a BSOD.  I would suspect if a third party program that is not 64 bit might affect drivers required to operate that program.  I recently spent hours searching for the cause of my BSOD's and it was a bad memory module.  The system read it as if it was working perfectly and tests were not crashing the system, but, when removing it, the crashes stopped and my system has been working perfectly since then.  BSOD's can be frustrating for sure!

 

4 hours ago, w6kd said:

Another thing I'd do is bump up the memory voltage just a little bit.  It looks like the memory might be running right on the ragged edge of stability.  Try bumping it up maybe a hundredth of a volt.  Another possibility is to leave it at its current voltage and reduce the clock speed slightly.

Those corrupted drivers are a bad sign, though...a faulty memory module can cause progressive corruption of files on the computer, and who knows what else might have been affected beyond the drivers while operating with that misbehaving RAM.

As far as BSODs, yes, they absolutely can be and quite often are caused by hardware...I don't know any serious overclockers that haven't seen a BSOD while pushing a system to its limits in a clocking drill.  In fact, certain types of BSODs are important clues as to what parts of the mobo aren't keeping up...some are associated with CPU core, some with uncore, etc.  BSODs associated with IRQ_NOT_EQUAL_TO errors are often associated with failing video cards.  And so on.

Regards

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!