fengye110 / dokan

Automatically exported from code.google.com/p/dokan
0 stars 0 forks source link

Blue screen: IRQL_NOT_LESS_OR_EQUAL - #2 #98

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

I/O over a period of time.

What is the expected output? What do you see instead?

A blue screen with the following crash log.  This issue may be a duplicate
of 97 (http://code.google.com/p/dokan/issues/detail?id=97), but the stack
is significantly different.

What version of the product are you using? On what operating system?

dokan-0.4.2.1238 x86
Windows 2003 Server, 32-bit (quad core)

Please provide any additional information below.

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000130, memory referenced
Arg2: d000001b, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on
chips which support this level of status)
Arg4: 8082e170, address which referenced memory

Debugging Details:
------------------

READ_ADDRESS:  00000130 

CURRENT_IRQL:  1b

FAULTING_IP: 
nt!KiInsertQueueApc+2a
8082e170 8b8c8630010000  mov     ecx,dword ptr [esi+eax*4+130h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  javaw.exe

TRAP_FRAME:  b8615a80 -- (.trap 0xffffffffb8615a80)
ErrCode = 00000000
eax=00000000 ebx=00000001 ecx=86bf9a70 edx=00000000 esi=00000000 edi=86bf9a70
eip=8082e170 esp=b8615af4 ebp=b8615b0c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!KiInsertQueueApc+0x2a:
8082e170 8b8c8630010000  mov     ecx,dword ptr [esi+eax*4+130h]
ds:0023:00000130=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8082e170 to 8088c993

STACK_TEXT:  
b8615a80 8082e170 badb0d00 00000000 00000000 nt!KiTrap0E+0x2a7
b8615b0c 8082ab87 86bf9a70 86bf9a30 00000000 nt!KiInsertQueueApc+0x2a
b8615b2c 8081e257 86bf9a70 860e7028 00000000 nt!KeInsertQueueApc+0x43
b8615b60 b9b0842d 00000001 00000000 00000000 nt!IopfCompleteRequest+0x201
b8615b88 b9b05545 85fd81e0 861b61c8 00000004 dokan!DokanCompleteWrite+0xfd
[c:\foo\sys\write.c @ 242]
b8615bd4 b9b09f06 8a7e9030 fac7b3a0 01d1ab3f dokan!DokanCompleteIrp+0x205
[c:\foo\sys\event.c @ 342]
b8615c3c 8081df85 8a7e9030 fac7b3a0 89bf7028
dokan!DokanDispatchDeviceControl+0x2a6 [c:\foo\sys\device.c @ 104]
b8615c50 808f5437 fac7b410 89bf7028 fac7b3a0 nt!IofCallDriver+0x45
b8615c64 808f61bf 8a7e9030 fac7b3a0 89bf7028 nt!IopSynchronousServiceTail+0x10b
b8615d00 808eed08 00000254 00000000 00000000 nt!IopXxxControlFile+0x5e5
b8615d34 808897bc 00000254 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b8615d34 7c82860c 00000254 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
29f87ec8 00000000 00000000 00000000 00000000 0x7c82860c

STACK_COMMAND:  kb

FOLLOWUP_IP: 
dokan!DokanCompleteWrite+fd [c:\foo\sys\write.c @ 242]
b9b0842d ??              ???

FAULTING_SOURCE_CODE:  
   238:     }
   239: 
   240:     IoCompleteRequest(irp, IO_NO_INCREMENT);
   241: 
>  242:     DokanPrintNTStatus(status);
   243:     DDbgPrint("<== DokanCompleteWrite\n");
   244: 
   245:     //FsRtlExitFileSystem();
   246: }
   247: 

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dokan!DokanCompleteWrite+fd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dokan

IMAGE_NAME:  dokan.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  495ada90

FAILURE_BUCKET_ID:  0xA_dokan!DokanCompleteWrite+fd

BUCKET_ID:  0xA_dokan!DokanCompleteWrite+fd

Followup: MachineOwner
---------

Original issue reported on code.google.com by gdhuse.c...@gmail.com on 17 Jul 2009 at 5:32

Attachments:

GoogleCodeExporter commented 9 years ago
Hi, I am also working on dokan. In my System (XP professional 32 bit) there 
have the same problem. 

There is any solution to the issue?

Thanks.

kunzhong

Original comment by coachzh...@gmail.com on 12 Jan 2012 at 7:54