System Lock and Reboot

[jornov 0]

Hello:

Please someone help me. I can fly quietly for some time even days without problems. The next day can be the opposite even under the same circumstances. The system gets blocked momentarily black screen and the system reboots. Restarting the computer sends a message from windows that was a problem and sends a memory dump file. After trying countless solutions, I decided reformat my computer and put it at factory point. And then reinstall P3D following all the recomendations, however the problem persists . I have applied all kinds of diagnostic and the results are that the equipment works properly. This only happens to me being inside Prepar3D. The only addon is the PMDG B737 NGX. This PC is dedicated to my simulator only, I am the only user. 

Specifications: Dell Alienware X51, Windows 8 Pro, Intel® Core i7-3770 CPU @3.40 Ghz, 3.40 Ghz
8 GB RAM (7.90GB free) 64 bits, X64
NVIDIA Gforce GTX 660 Controller 305.46 Directx 11 2,304 mb Video 1,536 MB GDDR5.
I will appreciate any help.

Jorge Novelo

[Harold_Finch 29]

X51 huh? 

 

My x51 acted exactly like that before the GPU gave up the ghost.  

[jornov 0]

If you solved please enlighten me the way. It should be noted that I am not a computer expert , I guess the GPU refers to the video card in my case NVIDIA.

Regards

[Harold_Finch 29]

Yes, when it died I replaced it.  Same computer is running fine now with new card.   I think it was heat related, the case on the X51 is very small and poorly ventilated.  I replaced it with a Nvidia GTX 970, but most smaller thinner cards will fit.  The X-51 is an "interesting" computer to work on.  The graphics card plugs into a 90 degree adapter board so that the card can fit in the case.  There are YouTube videos out there showing step by step replacement.

[jornov 0]

It hurts to hear that because now I can not make spending to try. I have one doubt, a full day can work well and the next under the same conditions no, at the first 5 minutes or less fail, only runing the Prepar3D and PMDG B737 simulator. 8 GB of RAM will suffice ? I can see that most users have more than that, what you think ?

 

Thank you for your comments

[downscc 1,327]

Full names on all posts in the PMDG forums please.

 

Yes, 8 GB of RAM is sufficient but having less than 2GB of VRAM is a constraint, when it runs out of VRAM it starts using your system RAM.  You might get lucky and all you need to do is clean filters and blow dust off of cooling fins inside your case.  There is lots of free utility software out there to monitor your CPU and GPU temperatures.

 

Report back with a solution if found.

[jornov 0]

Hello:

 

I took your advice and now I 'm monitoring my computer. Yesterday was one of those days that everything worked perfect. My GPU temperature never exceeded 80 ° C under load. In general, all other parameters behave within the normal range . I keep trying and hope that when the fault occurs can realize these parameters at the right time. I will report my experience.

 

Jorge Novelo

[wedgantilles 76]

Hello Jorge,

 

If you still have issue and if as I understood you get dumps in c:\windows\MiniDump when the crash/reboot appear, you should have a go by analyzing the latest dump at http://www.osronline.com/page.cfm?name=Analyze

 

By uploading your dump file it will be processed and analyzed, and you should now what happens with more accurate information which could be of some help. You could do the same on your own computer locally but for that you wold need the windows debugging tools, as well as the symbols for your OS, so the web analyzer is more convenient I believe.

[jornov1 0]

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
 

[scandinavian13 5,192]

IMAGE_NAME:  nvlddmkm.sys

 

Roll your NVIDIA drivers back to 362 or before, or update to 365 (potentially - it was 364 that had all kinds of issues...I'm currently running 361 and haven't bothered to poke the bear by updating to 365).