Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-18082

[REGRESSION] Multiple software fails in random ReactOS versions after c7e090

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Blocker
    • None
    • None

    Description

      Here I will recapitulate the software that crashes my VM with "Exiting with an invalid trap frame? (No MAGIC in trap frame)", guru meditation or BSOD without any text that reports a Fatal System Error: 0x0000000f. Sometimes the VM could enter in Guru meditation. Acts really as random as Missingno in the first Pokemon Gen.

      Friendly reminder is a GCC only issue. I can run and close this software under MSVC without issue.

      All the quoted builds are not the only one that fails, and change the log behavior in versions without any code that causes apparently affects the functions. I will progressively upload log files and videos. Sorry for doing the ticket progressively.

      Some previous or current versions change the behavior (allows to close, or crash differently) so I can't see the trigger accurate. The only causal relationship I found is that every software makes the VM to crash after closing it depending the size of the isos or the version of the files that contains. The MiQueryPageTableReferences code reverted NTOS MM - undo c7e090.diff makes the software to close it correctly. PointerPde error? Page Table?

      BUT: I don't know if it's the cause or the unhidder. I know nothing about what does the kernel.

      If you face some any issues like that in your casual testing, tell me, please.

      Software tested Working ver.
      post c7e090
      (with log)
      Failing version
      (with log)
      Factusol 2016 Unknown c7e0906 and 0078d14 FACTUSOL FATAL ERROR.log
      WPA Supplicant 1b35626 WPAS OK.log 0078d14 WPAS FATAL ERROR.log
      OpenMPT 0078d14 OPENMPT OK.log 1b35626 OPENMPT FATAL ERROR.log
      TeamViewer 11 Unknown 0078d14

      If I can do something to help you, devs, ask me without problem.

      *** Fatal System Error: 0x0000001a
                             (0x00000400,0xC00032C0,0xE149D308,0xE149D440)
      Entered debugger on embedded INT3 at 0x0008:0x805874CB.
      kdb:> bt
      Eip:
      <ntoskrnl.exe:1874cc (srv/buildbot/worker_data/Build_GCCLin_x86/build/sdk/lib/rtl/i386/debug_asm.S:56 (RtlpBreakWithStatusInstruction))>
      Frames:
      <ntoskrnl.exe:8a75d (ntoskrnl/ke/bug.c:1066 (KeBugCheckWithTf))>
      <ntoskrnl.exe:8acc7 (ntoskrnl/ke/bug.c:1413 (KeBugCheckEx))>
      <ntoskrnl.exe:de9a5 (ntoskrnl/mm/ARM3/virtual.c:483 (MiDeletePte))>
      <ntoskrnl.exe:ded25 (ntoskrnl/mm/ARM3/virtual.c:702 (MiDeleteVirtualAddresses))>
      <ntoskrnl.exe:c75c9 (ntoskrnl/mm/ARM3/section.c:801 (MiRemoveMappedView))>
      <ntoskrnl.exe:c4c17 (ntoskrnl/mm/ARM3/procsup.c:1280 (MmCleanProcessAddressSpace))>
      <ntoskrnl.exe:11df3a (ntoskrnl/ps/kill.c:895 (PspExitThread))>
      <ntoskrnl.exe:11e040 (ntoskrnl/ps/kill.c:1017 (PspTerminateThreadByPointer))>
      <ntoskrnl.exe:11e524 (ntoskrnl/ps/kill.c:1249 (NtTerminateProcess))>
      <ntoskrnl.exe:3fe5 (:0 (KiSystemCallTrampoline))>
      <ntoskrnl.exe:14a5ec (ntoskrnl/ke/i386/traphdlr.c:1844 (KiSystemServiceHandler))>
      <ntoskrnl.exe:3e2f (:0 (KiFastCallEntry))>
      

       

       

      Attachments

        1. Closing_Messenger_5_debug_log.txt
          490 kB
        2. FACTUSOL BUG MSVC - 680f103.txt
          387 kB
        3. FACTUSOL FATAL ERROR.log
          266 kB
        4. NTOS MM - undo c7e090.diff
          4 kB
        5. OPENMPT FATAL ERROR.log
          113 kB
        6. OPENMPT OK.log
          14 kB
        7. WPAS FATAL ERROR.log
          8 kB
        8. WPAS OK.log
          8 kB

        Issue Links

          Activity

            People

              zefklop jgardou
              julenuri julenuri
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: