[ros-bugs] [Bug 1256] RESOURCE_NOT_OWNED BSoD

[ReactOS.Bugzilla at reactos.org]

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





------- Additional Comments From osexpert at gmail.com  2006-01-10 21:33 CET -------
I've add same more debug prints. I get the hit from my additional assert.

./ntoskrnl/ex/resource.c:1775 CPU0) CurrentThread 818c15c0
(./ntoskrnl/ex/resource.c:1776 CPU0) Resource @ 817400d8
(./ntoskrnl/ex/resource.c:1781 CPU0)  ActiveCount = 0001  Flags = 
IsOwnedExclusive
(./ntoskrnl/ex/resource.c:1783 CPU0)  NumberOfExclusiveWaiters = 0000
(./ntoskrnl/ex/resource.c:1786 CPU0)    Thread = 81c7dd10, Count = 01
(./ntoskrnl/ex/resource.c:1789 CPU0)    Thread = 00000000, Count = 00
(./ntoskrnl/ex/resource.c:1804 CPU0)    Thread = 00000000, Count = 00
(./ntoskrnl/ex/resource.c:1804 CPU0)    Thread = 00000000, Count = 00
Assertion Resource->OwnerThreads[0].OwnerThread == Thread failed 
at ./ntoskrnl/ex/resource.c:1809
A problem has been detected and ReactOS has been shut down to prevent damage 
to your computer.

Technical information:

*** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000)

Frames:
<ntoskrnl.exe:2595 (./ntoskrnl/ke/bug.c:483 (KeBugCheckEx))>
<ntoskrnl.exe:25cd (./ntoskrnl/ke/bug.c:504 (KeBugCheck))>
<ntoskrnl.exe:27dbc (./ntoskrnl/ex/resource.c:1809 (ExReleaseResourceLite))>
<vfatfs.sys:115ed (drivers/fs/vfat/volume.c:357 (VfatQueryVolumeInformation))>
<vfatfs.sys:dd19 (drivers/fs/vfat/misc.c:121 (VfatDispatchRequest))>
<vfatfs.sys:de8f (drivers/fs/vfat/misc.c:167 (VfatBuildRequest))>
<ntoskrnl.exe:4407a (./ntoskrnl/io/irp.c:1076 (IofCallDriver))>
<ntoskrnl.exe:43ff2 (./ntoskrnl/io/irp.c:1020 (IoCallDriver))>
<ntoskrnl.exe:4f72b (./ntoskrnl/io/vpb.c:190 (NtQueryVolumeInformationFile))>
<ntoskrnl.exe:a255a (ntoskrnl\ke\i386\syscall.S:372 (KiSystemService))>
<kernel32.dll:fe11 (./lib/kernel32/file/volume.c:617 (GetVolumeInformationW))>



-- 
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, or are watching the QA contact.