Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
spaceport.sys bugcheck 0xd1

Answered spaceport.sys bugcheck 0xd1

  • Saturday, November 03, 2012 3:52 AM
     
      Has Code
    Sign In to Vote
    0

    The OS is installed on a separate hard drive connected to a silicon image 3512 controller, the sata ports on the motherboard are used in the storage pool (four 3TB hard drives in parity mode). I'm not sure if the pci card has a faulty driver or there is a bug in the storage pool driver, spaceport.sys is more likely to be related to the latter. The crash happens about once a day.

    I loaded the minidump into windbg, you can also download it from here: http://homesys.tv/110312-21875-01.zip

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa801e60000e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001390745, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80155bc6168
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 fffffa801e60000e 

CURRENT_IRQL:  2

FAULTING_IP: 
spaceport!LogDecodeEntryHeader+55
fffff880`01390745 42884409fe      mov     byte ptr [rcx+r9-2],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880080ae500 -- (.trap 0xfffff880080ae500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000016000630 rbx=0000000000000000 rcx=0000000000bd2000
rdx=0000000000bd1e00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001390745 rsp=fffff880080ae698 rbp=fffffa801da2e010
 r8=0000000000000000  r9=fffffa801da2e010 r10=fffffa801db19d90
r11=0000000000005e90 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
spaceport!LogDecodeEntryHeader+0x55:
fffff880`01390745 42884409fe      mov     byte ptr [rcx+r9-2],al ds:fffffa80`1e60000e=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff801558ea069 to fffff801558ead40

STACK_TEXT:  
fffff880`080ae3b8 fffff801`558ea069 : 00000000`0000000a fffffa80`1e60000e 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`080ae3c0 fffff801`558e88e0 : 00000000`00000001 fffffa80`03693000 ffffffff`ffd0d900 fffff880`080ae500 : nt!KiBugCheckDispatch+0x69
fffff880`080ae500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
spaceport!LogDecodeEntryHeader+55
fffff880`01390745 42884409fe      mov     byte ptr [rcx+r9-2],al

SYMBOL_NAME:  spaceport!LogDecodeEntryHeader+55

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: spaceport

IMAGE_NAME:  spaceport.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5010ab54

FAILURE_BUCKET_ID:  X64_0xD1_spaceport!LogDecodeEntryHeader+55

BUCKET_ID:  X64_0xD1_spaceport!LogDecodeEntryHeader+55

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



    • Edited by Gabest Saturday, November 03, 2012 3:54 AM
    •  
     

All Replies

  • Tuesday, November 06, 2012 9:21 AM
     
     
    Sign In to Vote
    0

    Hi,

    This BSOD occurred just after server startuped. Can you reproduce this BSOD? Or if occurs randomly?

    i found RAID5 in the call stack, and spaceport is related with 3th party storage device, so i would like to suggest  you upgrade all the storage related driver at first.  As we known, there are lots of driver upgrade after the RTM.




    “Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.”

     
  • Tuesday, November 06, 2012 9:33 AM
     
     
    Sign In to Vote
    0

    Randomly. Several times per hour, or once a day, but more frequently when there is heavy access to the disks, it will surely happen within an hour if I start copying something large. It has rebooted just now while I'm writing this. I can send you about a dozen minidumps if you want. The motherboard is a GIGABYTE GA-H61N-D2V, with the latest chipset and disk drivers can be found on gigabyte's support page. It's in a small NAS case (mini-ITX), we have several as file servers with identical hardware, this was the first time I tried to install 2012 on it, to test ReFS, but right now it runs on NTFS.

    P.S. Don't misunderstand me, I know this might be a hardware error, I'm only trying to help you guys finding possible bugs in spaceport.sys. Not being a kernel programmer myself, no idea if such error can be worked around avoiding a critical BSOD, but if the crash happens in my module, there is a chance I can do something to at least prevent bigger errors, like file system corruption, because that's the case now, chkdsk always finds something to correct.


    • Edited by Gabest Tuesday, November 06, 2012 9:52 AM
    • Edited by Gabest Tuesday, November 06, 2012 9:53 AM
    •  
     
  • Thursday, November 22, 2012 4:28 PM
     
     Answered
    Sign In to Vote
    0
    i understand you concern, but OS will engage a BSOD when it detects a critical error which can't recover and control, and continue working will caused the unexpected issue. For example, if a disk has hardware problem, spaceport.sys detectes this inconsistency, if this error also occurs in Kernel mode, therefore nt!KeBugCheckEx will be called to BSOD this server to show us we have a critical problem. but if a error only occurs in a process's user mode space, it won't impact other process and kernel mode, so at most OS only terminate this process, just like you said, restart part of the OS but not crash the whole OS. 

    “Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.”

     
  • Tuesday, December 25, 2012 5:37 AM
     
     
    Sign In to Vote
    0
    Hi, i am just following up to check if there is any updates on this issue.

    “Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.”