CTD

[zmak 331]

Hi

 

Cant seem to get through a single flight all week with BSOD x101 driver issues but just got this crash and want to see if its  driver problem related

 

thanks

 

 Log Name:      Application

Source:        Application Error

Date:          28/10/14 9:41:31 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      bb-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x74a2cb49

Faulting process id: 0x2c0

Faulting application start time: 0x01cff2a4e827f687

Faulting application path: E:\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report Id: 81165b44-5eb0-11e4-ab40-c8600024690b

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-10-28T14:41:31.000000000Z" />

    <EventRecordID>905108</EventRecordID>

    <Channel>Application</Channel>

    <Computer>bb-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>unknown</Data>

    <Data>0.0.0.0</Data>

    <Data>00000000</Data>

    <Data>c0000005</Data>

    <Data>74a2cb49</Data>

    <Data>2c0</Data>

    <Data>01cff2a4e827f687</Data>

    <Data>E:\Microsoft Flight Simulator X\fsx.exe</Data>

    <Data>unknown</Data>

    <Data>81165b44-5eb0-11e4-ab40-c8600024690b</Data>

  </EventData>

</Event>

[Jim Young 2,356]

There is nothing in your Event Viewer log that shows what might have caused fsx to crash. Usually, when it states "unknown" as the faulting module, it is really a StackHash. If you have been having BSOD's with bugcheck code 0x101, this usually means you need more vcore if your are overclocking. About the only safe fix though would be to return your overclock to the optimal defaults and try the overclock again as it failed.

 

Best regards,

[zmak 331]

Thanks Jim will set OC back to default, forgot to do that. 

cheers

[zmak 331]

 

 

f you have been having BSOD's with bugcheck code 0x101, this usually means you need more vcore if your are overclocking. About the only safe fix though would be to return your overclock to the optimal defaults and try the overclock again as it failed.

 

Jim, wanted to thank you for this you saved me from nearly buying one of those driver updater programs and it wouldn't have worked any way!

 

it was a vcore problem indeed

 

cheers

[Driver170 42]

Still get those driver updaters though!

 

This vcore is all in nick N guide on simforums i highly recommend you check it out. I followed his haswell guide got my OC at 40ghz and never happier. Fsx is clear and smooth. This man is a genious i wish i followed his advice a long time ago as i have had many problems with my setup due to following bull youtube videos and letting a company OC my system who didn't have a clue. My cpu temp never reaches 45C volts set at 1.12 its all in good working order. No random crashes anymore

[Jim Young 2,356]

This vcore is all in nick N guide on simforums i highly recommend you check it out. I followed his haswell guide got my OC at 40ghz and never happier.

I have the same motherboard and CPU as NickN (got mine first) and followed his guide and my system crashed constantly. Set my OC to 4.2 and let ASUS do the rest and my system and fsx/p3d is stable as all get out. Nick's settings do not work for everyone and that's the point I want to make here. Testing, testing, testing for stability is the solution but I do not have time for all of that.

 

Best regards,

[Driver170 42]

I have all the same hardware as nick aswell. Couldn't get a more stable platform following his guide! Did you increase things like he mentions then test? He does mention his starting settings may not be for everyone and thats why you have got to test, it takes alot of time and patience. Something that isn't performed over night. Getting a quick and dirty OC or simple as pressing a key, won't make you understand this fine art - as i have learned badly because i was one of those guys and paid the price.

[zmak 331]

Very interesting stuff. I will head over there and have  look as Im relatively new to the OC game and mine have been quick and dirty!

[Driver170 42]

Really? Honest man go over and read all his guide on how to setup and complete system from how to install OS7 tweak OS7 make it optimal get rid of the crap you don't need. Tweaking FSX and NVIDIA inspector setup and finally the haswell guide how to OC !

 

 

Thats why you are having all these crashes you need to start clean and by following nicks guide hes a genious. Thats what i had to do i had months of problems with all sorts of crashes.

 

BECAUSE, i didn't listen or take the time (patience) to go away and read through and follow his guide to the letter.

 

INSTEAD i opted for the quick N dirty method slap the disc in run fsx and hit a few buttons for an OC lol

 

Any trouble or need help PM me

[Jim Young 2,356]

Thanks Vernon. I do not have any problems whatsoever running FSX. I have no blurries, no stuttering, no CTD's, no freezes. I do respect his guidance. Always have, always will. Like he says in his guide, the settings do not work for everyone and I'm one of the everyone...

 

Best regards,

[Driver170 42]

Well its working for you jim don't go changing it