Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: The Fugitive on February 15, 2026, 08:25:35 PM

Title: DMP files
Post by: The Fugitive on February 15, 2026, 08:25:35 PM
Correct me if Im wrong, there is no way for any of us to view dmp files correct?

My journey with the film viewer is going well, but I still get crashes. The first was due to not having the right map for the film. I seem to remember the film would run but it wouldnt show any land. This rig the film crashes as it starts with the windows...."search for help on the internet" error. I have since downloaded all the films and that has cleared that up.

I have one film that plays about 5-10 seconds and then crashes and it creates a dmp file. If I knew why it was crashing I might be able to tweak my system.
Title: Re: DMP files
Post by: Animl-AW on February 15, 2026, 09:56:06 PM
Weird you ask. Just found those a few days ago. I think I have over 100.

No, you can’t read them, some form of encryption, memory garble, maybe parts of the film files itself.

Chances are HT may know what the issue is since it’s been fixed before. <shrug>

I wonder if a windows update log may show something.  Needle in hat stack
Title: Re: DMP files
Post by: Animl-AW on February 15, 2026, 10:58:35 PM
Do you know whats in the film that crashes every 5-10 sec?
Some objects/animations or there associated sound will crash a film 100% of the time.
Title: Re: DMP files
Post by: The Fugitive on February 16, 2026, 09:51:45 AM
I ran one dmp file through a windbg and I got this out of the analyze command. As I thought, total gibberish to me.

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 750

    Key  : Analysis.Elapsed.mSec
    Value: 7695

    Key  : Analysis.IO.Other.Mb
    Value: 1

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 51

    Key  : Analysis.Init.CPU.mSec
    Value: 921

    Key  : Analysis.Init.Elapsed.mSec
    Value: 97282

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 208

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 x86fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Failure.Bucket
    Value: INVALID_POINTER_WRITE_c000000 5_ahfilm.exe!Unknown

    Key  : Failure.Exception.Code
    Value: 0xc0000005

    Key  : Failure.Exception.IP.Address
    Value: 0x4460cc

    Key  : Failure.Exception.IP.Module
    Value: ahfilm

    Key  : Failure.Exception.IP.Offset
    Value: 0x460cc

    Key  : Failure.Hash
    Value: {160145c3-31ff-6843-8289-5301f928355d}

    Key  : Failure.ProblemClass.Primary
    Value: INVALID_POINTER_WRITE

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 136240

    Key  : Timeline.Process.Start.DeltaS ec
    Value: 56

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1


FILE_IN_CAB:  ahfilm_030604_2026_2_15_0_50_ 8.dmp

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
eax=4e1769e0 ebx=4e176970 ecx=00000000 edx=00000000 esi=00000000 edi=4e089238
eip=004460cc esp=001af44c ebp=001af468 iopl=0         nv up ei pl zr ac pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010256
ahfilm+0x460cc:
004460cc 0f1102          movups  xmmword ptr [edx],xmm0 ds:002b:00000000=????????????????????????????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 004460cc (ahfilm+0x000460cc)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 00000000
Attempt to write to address 00000000

PROCESS_NAME:  ahfilm.exe

WRITE_ADDRESS:  00000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  00000000

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
001af468 00446429     00000000 4e088fd0 4e187228 ahfilm+0x460cc
001af48c 00444302     4e176970 000002a5 00000002 ahfilm+0x46429
001af4ac 004bc881     4e187228 00000441 4e187228 ahfilm+0x44302
001af4cc 004bfc8b     4e187228 00000441 4e187228 ahfilm+0xbc881
001af560 005af4f9     4e187228 00000001 00000440 ahfilm+0xbfc8b
001af588 00594cfe     02edf690 00000017 00000440 ahfilm+0x1af4f9
001af5b0 005947cc     02edbed8 00000001 00000400 ahfilm+0x194cfe
001afa54 00594672     02411318 00000001 02411318 ahfilm+0x1947cc
001afaa0 004b9c56     02411318 001afac8 001afaf8 ahfilm+0x194672
001afbd0 004bb2d9     030df460 00000000 0022c000 ahfilm+0xb9c56
001aff28 006302cb     00400000 00000000 03392c27 ahfilm+0xbb2d9
001aff74 74cf5d49     0022c000 74cf5d30 001affdc ahfilm+0x2302cb
001aff84 777fd83b     0022c000 fa0ab2c4 00000000 kernel32!BaseThreadInitThunk+0x19
001affdc 777fd7c1     ffffffff 778445e0 00000000 ntdll!__RtlUserThreadStart+0x2b
001affec 00000000     00630392 0022c000 00000000 ntdll!_RtlUserThreadStart+0x1b


STACK_COMMAND: ~0s; .ecxr ; kb

IP_IN_PAGED_CODE:
ahfilm+460cc
004460cc 0f1102          movups  xmmword ptr [edx],xmm0

SYMBOL_NAME:  ahfilm+460cc

MODULE_NAME: ahfilm

IMAGE_NAME:  ahfilm.exe

FAILURE_BUCKET_ID:  INVALID_POINTER_WRITE_c000000 5_ahfilm.exe!Unknown

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x86

OSNAME:  Windows 10

FAILURE_ID_HASH:  {160145c3-31ff-6843-8289-5301f928355d}

Followup:     MachineOwner
---------
Title: Re: DMP files
Post by: Animl-AW on February 16, 2026, 10:18:05 AM
Pay attention to error codes. Glad you did that to bring it out front.
Network is also a red flag.

The 0xc0000005 error is a Windows "Access Violation" indicating a program tried to use memory it doesn't have permission to access, often caused by buggy software, corrupted system files, faulty RAM, or DEP restrictions.

Some things you can TRY as workarounds.

Run System File Checker (SFC): Open Command Prompt as administrator and run sfc /scannow to fix corrupted system files. Meh!

* Disable Data Execution Prevention (DEP): Some apps conflict with this security feature. Search for "View advanced system settings" -> Performance Settings -> Data Execution Prevention, and turn it off for the specific program causing issues.

Update/Reinstall Drivers: Outdated display or audio drivers can cause this error.

* Disable Third-Party Antivirus: Temporarily disable antivirus software to check if it's blocking applications.

Check RAM: Run the Windows Memory Diagnostic tool to check for faulty physical memory.

* Adjust Virtual Memory: Increase the paging file size if it is too small, or set it to "automatically manage"
Title: Re: DMP files
Post by: Animl-AW on February 16, 2026, 10:39:49 AM
Side thought
I remember in my old app I wrote “XP Game Launcher” (I think a MS worker/AH player stole the concept - Game Mode) I had a Flush Memory process, where it would flood memory to push what was stored in there out.

When I would manually fast forward in a film that data is just blasting to the edge of over-whelming memory.  Just reading/writing with no leashes on speed. Voices are out of places, even repeating. There COULD be a sound issue, fleeting guess.
Title: Re: DMP files
Post by: The Fugitive on February 16, 2026, 11:04:14 AM
I ran it through another analyzer and that one concluded it was a driver issue with hitech.sys. So it seems Im back to updates that Hitech didnt add through the years that he did add to the game.
Title: Re: DMP files
Post by: Animl-AW on February 16, 2026, 11:13:14 AM
I ran it through another analyzer and that one concluded it was a driver issue with hitech.sys. So it seems Im back to updates that Hitech didnt add through the years that he did add to the game.

I agree. It is what it is. I lost faith in seeing movement on it. Disappointed.

As mentioned above on possible driver conflict. The others were just POSSIBLE work-arounds, not a fix. A fix is an update.