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

Random "Fatal System Error: 0x00000139", after new Cc lazy writer. (After 1st resolution of CORE-14263)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Duplicate
    • Fix Version/s: 0.4.8
    • Component/s: NTCore
    • Labels:

      Description

      Yet another Test KVM #19298 like random crash: Stage 1, copying files.

      VPC 2004 + 128MiB.
      reactos-bootcdregtest-0.4.8-dev-939-g2595538-x86-gcc-lin-dbg.iso

      (ntoskrnl/kd/kdio.c:105) ReactOS 0.4.8-dev (Build 20180129-0.4.8-dev-939-g2595538) (Commit 2595538558f59671b6b68536c4e23d040e7bfc5c)
      (ntoskrnl/kd/kdio.c:106) 1 System Processor [127 MB Memory]
      (ntoskrnl/kd/kdio.c:107) Command Line: NOGUIBOOT KDSERIAL DEBUGPORT=COM1 FIRSTCHANCE
      ...
      (base/setup/usetup/filesup.c:259) NtOpenFile failed: c0000034, \Device\CdRom0\reactos\system32\kdvbox.dll
       
      *** Fatal System Error: 0x00000139
                             (0x00000003,0xFCBBC774,0xFCBBC71C,0x00000000)
       
      [7h
      Entered debugger on embedded INT3 at 0x0008:0x8094acc4.
      kdb:> 
       
      ==> Failed at 42% of file copy.

      NB: My keyboard doesn't work, so no "bt".

      Ftr, workaround should be to have more RAM, like 256 MiB.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Heis Spiter Pierre Schweitzer
                Reporter:
                Serge Gautherie Serge Gautherie
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: