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

Nvidia Driver < 181.22 has random crashes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      After https://github.com/reactos/reactos/pull/1499 will be merged, when running a 3D accelerated application, there is a 8/10 chance it will bugcheck the system.

      kdb:> bt
      Eip:
      <ntoskrnl.exe:152905 (:0 (RtlpBreakWithStatusInstruction))>
      Frames:
      <ntoskrnl.exe:89ead (ntoskrnl/ke/bug.c:1100 (KeBugCheckWithTf))>
      <ntoskrnl.exe:8a484 (ntoskrnl/ke/bug.c:1456 (KeBugCheckEx))>
      <ntoskrnl.exe:b57ea (ntoskrnl/mm/ARM3/pagfault.c:2024 (MmArmAccessFault))>
      <ntoskrnl.exe:e6d85 (ntoskrnl/mm/mmfault.c:251 (MmAccessFault))>
      <ntoskrnl.exe:13607a (ntoskrnl/ke/i386/traphdlr.c:1340 (KiTrap0EHandler))>
      <ntoskrnl.exe:36ac (:0 (KiTrap0E))>
      <nv4_disp.dll:44942>
      <win32k.sys:bd727 (win32ss/gdi/ntgdi/gdiobj.c:610 (GDIOBJ_vFreeObject))>
      <win32k.sys:bd92d (win32ss/gdi/ntgdi/gdiobj.c:665 (GDIOBJ_vDereferenceObject))>
      <win32k.sys:be568 (win32ss/gdi/ntgdi/gdiobj.c:1136 (GDIOBJ_vDeleteObject))>
      <win32k.sys:bef9c (win32ss/gdi/ntgdi/gdiobj.c:1570 (GDI_CleanupForProcess))>
      <win32k.sys:c0bcd (win32ss/gdi/ntgdi/init.c:56 (GdiProcessDestroy))>
      <win32k.sys:19317 (win32ss/user/ntuser/main.c:318 (ExitProcessCallback))>
      <win32k.sys:1965c (win32ss/user/ntuser/main.c:352 (Win32kProcessCallback))>
      <ntoskrnl.exe:10fee2 (ntoskrnl/ps/kill.c:750 (PspExitThread))>
      <ntoskrnl.exe:1102ec (ntoskrnl/ps/kill.c:1017 (PspTerminateThreadByPointer))>
      <ntoskrnl.exe:110c3f (ntoskrnl/ps/kill.c:1249 (NtTerminateProcess))>
      <ntoskrnl.exe:136e6e (ntoskrnl/include/internal/i386/ke.h:730 (KiSystemServiceHandler))>
      

      The trace is caused by https://git.reactos.org/?p=reactos.git;a=blob;f=win32ss/gdi/eng/driverobj.c;h=f1987df6afaf8bed5d0c9d919917396e4b3015ac;hb=HEAD#l32
      If you comment it out, you will hit the following 3 asserts:
      https://git.reactos.org/?p=reactos.git;a=blob;f=ntoskrnl/mm/ARM3/procsup.c;h=cbc784066a0cdb2dbbe01f9e4eef8b41b0367de2;hb=HEAD#l1279
      https://git.reactos.org/?p=reactos.git;a=blob;f=ntoskrnl/mm/ARM3/virtual.c;h=f0ab5d08f7b9f95676745ac666f9af9275206775;hb=HEAD#l510
      https://git.reactos.org/?p=reactos.git;a=blob;f=ntoskrnl/mm/ARM3/virtual.c;h=f0ab5d08f7b9f95676745ac666f9af9275206775;hb=HEAD#l521

      If you work around these as well, it wont crash anymore, however it is obviously not the solution.

      I can do hardware testing if needed when provided instructions.

      Attached: A hackfix for those who just want to get around it for now.

        Attachments

          Activity

            People

            • Assignee:
              bug zilla Bug Zilla
              Reporter:
              BieHDC BieHDC
            • Votes:
              5 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: