[ros-bugs] [Bug 4995] METABUG: uniata: timing issues

[ReactOS.Bugzilla at reactos.org]

http://www.reactos.org/bugzilla/show_bug.cgi?id=4995


eadthem <padamsn at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |padamsn at gmail.com




--- Comment #69 from eadthem <padamsn at gmail.com>  2011-05-08 17:08:47 CET ---
i had a fatal system error/cant read memory similar to ------- Comment  #7 From
wojo664  2009-12-07 19:52:38 CET  [reply] -------  

see attachment
"KDB info from a cant read memory error similar to  ------- Comment  #7 From
wojo664  2009-12-07 19:52:38 CET  [reply] -------"

hardware amd athlon xp 3000+ barton 2GB ram  KT400 VIA chipset (VT8377)
south(VT8235) MSI ms-6590 2GB ram 1gb used.

oracle VM virtualbox 4.0.0. R69151

virtual box config file http://final.servegame.com/ros/virtualbox/


I noticed someone mention issues with SMSS.exe . I have had crashes at that
point with smss.exe and hivesys and they are at
http://final.servegame.com/ros/hivesys_smss/


-------------imediate area near the crash---------------

====== PCI BUS DETECTION COMPLETE =======

PC Compatible Eisa/Isa HAL Detected
(ntoskrnl/io/pnpmgr/pnpinit.c:403) Need to build DACL
(ntoskrnl/io/iomgr/iorsrce.c:882) IoReportResourceUsage is halfplemented!
(ntoskrnl/io/iomgr/iorsrce.c:882) IoReportResourceUsage is halfplemented!
(ntoskrnl/io/iomgr/driver.c:1540) '\Driver\buslogic' initialization failed,
status (0xc00000c0)
(ntoskrnl/io/iomgr/arcname.c:338) Boot device found
(drivers/filesystems/cdfs/common.c:107) STATUS_VERIFY_REQUIRED
(drivers/filesystems/cdfs/fsctl.c:590) CDFS: IRP_MN_VERIFY_VOLUME
(drivers/filesystems/cdfs/fsctl.c:467) CdfsVerifyVolume() called
(drivers/filesystems/cdfs/fsctl.c:488) Volume has been verified!
(drivers/filesystems/cdfs/common.c:112) IoVerifyVolume() returned (Status 0)
(ntoskrnl/cc/copy.c:222) IoPageRead failed, Status 80000016
(ntoskrnl/io/iomgr/file.c:420) Using IopParseDevice() hack. Requested invalid
attributes: 1
(ntoskrnl/io/iomgr/file.c:420) Using IopParseDevice() hack. Requested invalid
attributes: 1
(ntoskrnl/fstub/disksup.c:255) ZwOpenSymbolicLinkObject failed for
\ArcName\multi(0)disk(0)rdisk(2), status=c0000034
(ntoskrnl/fstub/disksup.c:255) ZwOpenSymbolicLinkObject failed for
\ArcName\multi(0)disk(0)rdisk(2), status=c0000034
Drive letter already used!
(drivers/filesystems/cdfs/common.c:196) STATUS_VERIFY_REQUIRED
(drivers/filesystems/cdfs/fsctl.c:590) CDFS: IRP_MN_VERIFY_VOLUME
(drivers/filesystems/cdfs/fsctl.c:467) CdfsVerifyVolume() called
(drivers/filesystems/cdfs/fsctl.c:488) Volume has been verified!
(drivers/filesystems/cdfs/common.c:203) IoVerifyVolume() returned (Status 0)
(drivers/filesystems/cdfs/create.c:148) Status 80000016

*** Fatal System Error: 0x0000006b
                       (0x80000016,0x00000002,0x00000000,0x00000000)

Entered debugger on embedded INT3 at 0x0008:0x808ffdfc.
kdb:> 
kdb:> bt
Eip:
<ntoskrnl.exe:ffdfd (lib/rtl/i386/debug_asm.S:39
(RtlpBreakWithStatusInstruction))>
Frames:
<ntoskrnl.exe:abaa (ntoskrnl/ke/bug.c:1110 (KeBugCheckWithTf at 24))>
<ntoskrnl.exe:acf5 (ntoskrnl/ke/bug.c:1438 (KeBugCheckEx at 20))>
<ntoskrnl.exe:e5d5c (ntoskrnl/ps/psmgr.c:305 (PsLocateSystemDll at 0))>
<ntoskrnl.exe:6f788 (ntoskrnl/io/iomgr/iomgr.c:570 (IoInitSystem at 4))>
<ntoskrnl.exe:43ae7 (ntoskrnl/ex/init.c:1764 (Phase1InitializationDiscard at 4))>
<ntoskrnl.exe:44129 (ntoskrnl/ex/init.c:1973 (Phase1Initialization at 4))>
<ntoskrnl.exe:ed61a (ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup at 8))>
<ntoskrnl.exe:5bd6 (ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup at 0))>
<ntoskrnl.exe:ed5b6 (ntoskrnl/ps/thread.c:625 (PsCreateSystemThread at 28))>
<ffffffff>
<ntoskrnl.exe:4a04 (ntoskrnl/ke/i386/kiinit.c:674
(KiSystemStartupBootStack at 0))>
<0000000e>
Couldn't access memory at 0x0007767C!

-------------imediate area near the crash---------------


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.