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

eBoostr 4.5 causes bugcheck 0x7e when attempting to meter disk drive performance

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 0.4.15
    • NTCore
    • VirtualBox 7.0.15.

    Description

      ReactOS 0.4.15-dev-5506-ge942eea. eBoostr 4.5 causes BSOD 0x7E when it tries to meter the performance of \Device\HarddiskVolume1 after first run.

      Steps to reproduce:

      1. Download eBoostr 4.5 here: https://s3-ap-northeast-1.amazonaws.com/degica-prod.product-files/3/eBoostr.exe.
      2. Install and reboot.
      3. After next startup a trial notification dialog will appear. Click the 1st "Continue" button.
      4. The message box with proposing to run the devices detection will appear. Click "Yes".
      5. The wizard will appear. Click "Next".

      The detection will be started. First, available device(s) will be detected. Then unavailable memory will be checked with error 0x100 failure. And finally it will do an attempt to check performance of \\?\GLOBALROOT\Device\HarddiskVolume1. After this, bugcheck 0x7E will appear:

      *** Fatal System Error: 0x0000007e
                             (0xC0000005,0xF784B25E,0xF7569BD8,0xF75698DC)
      

      In the call stack, besides ntoskrnl.exe, classpnp.sys driver will be visible:

      Eip:
      <ntoskrnl.exe:19d6b8 (sdk/lib/rtl/i386/debug_asm.S:56 (RtlpBreakWithStatusInstruction))>
      Frames:
      <ntoskrnl.exe:94d21 (ntoskrnl/ke/bug.c:1066 (KeBugCheckWithTf))>
      <ntoskrnl.exe:9528b (ntoskrnl/ke/bug.c:1413 (KeBugCheckEx))>
      <ntoskrnl.exe:1393d9 (ntoskrnl/ps/thread.c:129 (PspUnhandledExceptionInSystemThread))>
      <ntoskrnl.exe:13942e (ntoskrnl/ps/thread.c:159 (_SEH3$_FilterFunction.47173))>
      <ntoskrnl.exe:17748f (sdk/lib/pseh/i386/pseh3.c:80 (_SEH3$_GetFilterResult))>
      <ntoskrnl.exe:1775a9 (sdk/lib/pseh/i386/pseh3.c:299 (_SEH3$_except_handler))>
      <ntoskrnl.exe:19d813 (sdk/lib/rtl/i386/except_asm.s:185 (RtlpExecuteHandler2))>
      <ntoskrnl.exe:19d7e7 (sdk/lib/rtl/i386/except_asm.s:151 (RtlpExecuteHandlerForUnwind))>
      <ntoskrnl.exe:15a4c2 (ntoskrnl/ke/i386/exp.c:872 (KiDispatchException))>
      <ntoskrnl.exe:15a9e2 (ntoskrnl/ke/i386/exp.c:1081 (KiDispatchExceptionFromTrapFrame))>
      <ntoskrnl.exe:15f829 (ntoskrnl/include/internal/i386/ke.h:770 (KiTrap0EHandler))>
      <ntoskrnl.exe:36ae (:0 (KiTrap0E))>
      <classpnp.sys:46259 (sdk/lib/drivers/ntoskrnl_vista/etw.c:46 (IopWorkItemExCallback))>
      <ntoskrnl.exe:76ad4 (ntoskrnl/io/iomgr/iowork.c:24 (IopWorkItemCallback))>
      <ntoskrnl.exe:3fb1c (ntoskrnl/ex/work.c:158 (ExpWorkerThreadEntryPoint))>
      <ntoskrnl.exe:1392da (ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup))>
      <ntoskrnl.exe:15bed9 (ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup))>
      <ntoskrnl.exe:1392ad (ntoskrnl/ps/thread.c:63 (PspUserThreadStartup))>
      <ec835356>
      Couldn't access memory at 0x57E58959!
      

      Possibly our classpnp driver fails on calling Vista+ IopWorkItemExCallback from ntoskrnl_vista, what causes an issue. Maybe we can get rid of that NT6+ Ex call in classpnp and just use XP/2003 non-Ex routine (IopWorkItemCallback or something like that).
      SeeĀ eBoostr.log for details.

      UPD: by using classpnp.sys + disk.sys replacement from Windows 2003 SP2, the BSOD is no longer occuring for me. The check completes successfully:

      So this problem is indeed caused by our classpnp driver.

      Attachments

        1. hangs2.png
          hangs2.png
          38 kB
        2. eBoostr.log
          293 kB
        3. success.png
          success.png
          40 kB
        4. image-2022-12-11-18-51-48-434.png
          image-2022-12-11-18-51-48-434.png
          16 kB
        5. eboostr-fixed.png
          eboostr-fixed.png
          48 kB

        Issue Links

          Activity

            People

              Illen Illen
              Oleg Dubinskij Oleg Dubinskiy
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: