jornov1
-
Content Count
7 -
Donations
$0.00 -
Joined
-
Last visited
Posts posted by jornov1
-
-
It is most likely due to incompatibility with the video driver. In my experience is afraid to update it, on many occasions it has given me more problems than advantages. I prefer to stay as I am if there is no other solution.
Jorge Novelo
-
Thank you for trying to help me, unfortunately it did not work. It seems that the solution is not so simple. I would like this to be seen by an expert member to advise us. I guess I will not be the only one in this situation.
-
Hi Friends:
I would like to know what the letters that flash in front of the selected speed with the IAS / MACH dial on the autopilot panel mean. I could not find this. Now I have "A" flashing in front of .78 M. Flying at FL380 and .78 Mach speed. I can`t see any wrong.
Thank you
Jorge Novelo
-
Thank you for your help I found it following your instruction.
Greetings from Mexico
Jorge Novelo
-
Hello friends:
I have been a PMDG user and their products for years. Sorry for my ignorance that you are referring to the center of operations. How to access it. Thank you
.
-
Hello Harold
Thank you for your interest I followed your recommendation and I think the problem is related to memory addresses here is the result.
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.17617.amd64fre.win8_gdr.151230-0600
Machine Name:
Kernel base = 0xfffff803`7801f000 PsLoadedModuleList = 0xfffff803`782ebb20
Debug session time: Wed May 4 10:24:16.002 2016 (UTC - 4:00)
System Uptime: 1 days 14:03:25.127
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff888041abff8, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800537f64f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80378377170
GetUlongFromAddress: unable to read from fffff803783771f8
fffff888041abff8 Nonpaged pool
FAULTING_IP:
nvlddmkm+df64f
fffff880`0537f64f 4c891cd0 mov qword ptr [rax+rdx*8],r11
MM_INTERNAL_CODE: 2
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800a9462e0 -- (.trap 0xfffff8800a9462e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880041ac000 rbx=0000000000000000 rcx=fffffa800bf78150
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800537f64f rsp=fffff8800a946470 rbp=fffff8800a946490
r8=000014ff77fabe04 r9=00000000000000ff r10=0000000000000000
r11=000014ff77fabe04 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nvlddmkm+0xdf64f:
fffff880`0537f64f 4c891cd0 mov qword ptr [rax+rdx*8],r11 ds:fffff888`041abff8=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8037813a51c to fffff80378079140
STACK_TEXT:
fffff880`0a9460f8 fffff803`7813a51c : 00000000`00000050 fffff888`041abff8 00000000`00000001 fffff880`0a9462e0 : nt!KeBugCheckEx
fffff880`0a946100 fffff803`780b3e4b : 00000000`00000001 fffff888`041abff8 fffffa80`0b5c5080 fffff880`01684477 : nt! ?? ::FNODOBFM::`string'+0x32cf0
fffff880`0a9461a0 fffff803`78076bee : 00000000`00000001 000000ff`77fabe18 fffff880`0a946300 fffff880`0a9462e0 : nt!MmAccessFault+0x55b
fffff880`0a9462e0 fffff880`0537f64f : fffffa80`0b5c5080 00007c9a`fdcedb40 00007c9b`6918ad40 fffff803`78784e3b : nt!KiPageFault+0x16e
fffff880`0a946470 fffffa80`0b5c5080 : 00007c9a`fdcedb40 00007c9b`6918ad40 fffff803`78784e3b fffff880`0a9464c0 : nvlddmkm+0xdf64f
fffff880`0a946478 00007c9a`fdcedb40 : 00007c9b`6918ad40 fffff803`78784e3b fffff880`0a9464c0 fffff880`0537f6ce : 0xfffffa80`0b5c5080
fffff880`0a946480 00007c9b`6918ad40 : fffff803`78784e3b fffff880`0a9464c0 fffff880`0537f6ce 00000000`00000000 : 0x7c9a`fdcedb40
fffff880`0a946488 fffff803`78784e3b : fffff880`0a9464c0 fffff880`0537f6ce 00000000`00000000 00000020`00000002 : 0x7c9b`6918ad40
fffff880`0a946490 fffff880`053603fe : fffff880`0a946510 fffff880`0537f728 00000000`10000104 00000000`000002cc : hal!KeQueryPerformanceCounter+0x4b
fffff880`0a9464c0 fffff880`0a946510 : fffff880`0537f728 00000000`10000104 00000000`000002cc 00000000`00000001 : nvlddmkm+0xc03fe
fffff880`0a9464c8 fffff880`0537f728 : 00000000`10000104 00000000`000002cc 00000000`00000001 00000000`c1d00081 : 0xfffff880`0a946510
fffff880`0a9464d0 00000000`10000104 : 00000000`000002cc 00000000`00000001 00000000`c1d00081 00000000`00000000 : nvlddmkm+0xdf728
fffff880`0a9464d8 00000000`000002cc : 00000000`00000001 00000000`c1d00081 00000000`00000000 00000000`00000000 : 0x10000104
fffff880`0a9464e0 00000000`00000001 : 00000000`c1d00081 00000000`00000000 00000000`00000000 00000000`00000002 : 0x2cc
fffff880`0a9464e8 00000000`c1d00081 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : 0x1
fffff880`0a9464f0 00000000`00000000 : 00000000`00000000 00000000`00000002 00000000`00000000 fffff880`0a946550 : 0xc1d00081
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+df64f
fffff880`0537f64f 4c891cd0 mov qword ptr [rax+rdx*8],r11
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nvlddmkm+df64f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5017f42b
FAILURE_BUCKET_ID: X64_AV_nvlddmkm+df64f
BUCKET_ID: X64_AV_nvlddmkm+df64f
Followup: MachineOwner
---------What do you think. The first part I understand that refers to an address out of memory, the rest is russian to me.
Regards
Jorge Novelo
FMC Flight plans from P3D v3 to v4
in PMDG 737NGX | 737NGXu
Posted
I do not know the program you use to work out the plans. I do them directly in the FMC and I save them via "SAVE", these plans are saved with the state of the airplane. I see that there are three files .sav, .fmc and .rte these files I have copied them to their similar file from v3 to v4. Thank you if you indicate step by step what you have done.
Regards