Blue screen of death during Delphi 2010 debugging session

Discussion in 'Windows 64bit' started by Skybuck Flying, Dec 20, 2010.

  1. Hello,

    A blue screen of death occured again while I was debugging with Delphi 2010.

    Perhaps some memory got corrupted in previous runs.

    Also some classes where not being cleaned up properly in a dynamic array.

    But still this crash a bit more serious.

    Again two dumps I think a 400 MB file and a minidump.

    400MB file says: sptd.sys to blame ? hmm:

    (Minidump analysis and link will follow in second/reply post)

    "
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is:
    SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
    x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.100216-1301
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
    Debug session time: Mon Dec 20 06:34:34.656 2010 (GMT+1)
    System Uptime: 0 days 10:46:49.605
    Loading Kernel Symbols
    ................................................................
    .................................................................
    .........................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for
    details
    Loading unloaded module list
    ......................
    *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff800012c1308, 0, 6000}

    Page acb07 not present in the dump file. Type ".hh dbgerr004" for details
    Page accec not present in the dump file. Type ".hh dbgerr004" for details
    *** ERROR: Module load completed but symbols could not be loaded for
    sptd.sys
    PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for
    details
    PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for
    details
    Probably caused by : sptd.sys ( sptd+57a0f )

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

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

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800012c1308, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000006000, Parameter 1 of the exception

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

    Page acb07 not present in the dump file. Type ".hh dbgerr004" for details
    Page accec not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for
    details
    PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for
    details

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
    referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    nt!PspGetSetContextInternal+203
    fffff800`012c1308 488b58f8 mov rbx,qword ptr [rax-8]

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: 0000000000006000

    READ_ADDRESS: 0000000000006000

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x1E

    PROCESS_NAME: TestApplication

    CURRENT_IRQL: 1

    EXCEPTION_RECORD: fffffadf87a9a270 -- (.exr 0xfffffadf87a9a270)
    ExceptionAddress: fffff800012c1308
    (nt!PspGetSetContextInternal+0x0000000000000203)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000008
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000006000
    Attempt to read from address 0000000000006000

    TRAP_FRAME: fffffadf87a9a300 -- (.trap 0xfffffadf87a9a300)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000006008 rbx=0000000000000000 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800012c1308 rsp=fffffadf87a9a490 rbp=fffffadf8ca6db10
    r8=0000000000000000 r9=0000000000000000 r10=0f00000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    nt!PspGetSetContextInternal+0x203:
    fffff800`012c1308 488b58f8 mov rbx,qword ptr [rax-8]
    ds:a4f0:6000=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80001080e86 to fffff8000102e890

    STACK_TEXT:
    fffffadf`87a99b78 fffff800`01080e86 : 00000000`0000001e ffffffff`c0000005
    fffff800`012c1308 00000000`00000000 : nt!KeBugCheckEx
    fffffadf`87a99b80 fffff800`0102e6af : fffffadf`87a9a270 fffffa80`0000005e
    fffffadf`87a9a300 00001f80`00000080 : nt!KiDispatchException+0x128
    fffffadf`87a9a180 fffff800`0102d521 : fffffadf`99d9e8e8 fffffa80`054a6ed8
    fffffa80`054a6e00 fffffa80`04ecb010 : nt!KiExceptionExit
    fffffadf`87a9a300 fffff800`012c1308 : fffffadf`99a5f9b0 0f000000`00000000
    fffffadf`87a9b230 fffffadf`8ca6d5c0 : nt!KiPageFault+0x1e1
    fffffadf`87a9a490 fffff800`0104236b : fffffadf`995b8710 00000000`00000000
    fffffadf`995b8758 00000000`00000000 : nt!PspGetSetContextInternal+0x203
    fffffadf`87a9a9e0 fffff800`01027eb1 : fffff980`6efd1db8 fffff980`6efd1f38
    00000000`00000000 00000000`00000000 : nt!PspGetSetContextSpecialApc+0xab
    fffffadf`87a9aaf0 fffff800`0103bf97 : 00000000`ffffff00 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x215
    fffffadf`87a9ab90 fffff800`0102828e : 00000000`00000000 fffffa80`054a6b01
    fffffadf`995b87a8 fffffadf`995b8710 : nt!KiSwapThread+0x3e9
    fffffadf`87a9abf0 fffff800`0101f88c : 00000000`00000000 fffff980`00000005
    fffff980`6effb800 00000000`00000000 : nt!KeWaitForSingleObject+0x5a6
    fffffadf`87a9ac70 fffff800`0101f51b : fffffadf`9c7dba60 00000000`00000000
    00000000`ffffffff 00000011`d25a7ed8 : nt!KiSuspendThread+0x2c
    fffffadf`87a9acb0 fffff800`01027abd : fffffa80`054a6bb0 00000000`00000000
    fffff800`0101f860 00000000`00000000 : nt!KiDeliverApc+0x2d3
    fffffadf`87a9ad50 fffff800`010747cf : fffffadf`997cae80 fffffadf`87a9b201
    00000000`00000000 fffffadf`87a9b2b0 : nt!KiApcInterrupt+0xdd
    fffffadf`87a9aee0 fffffadf`90315a0f : fffffadf`9033d301 fffffadf`9c994000
    fffffadf`99d9e500 fffffadf`995eaf40 : nt!KeLeaveCriticalRegion+0x36
    fffffadf`87a9af10 fffffadf`902ffa65 : fffffadf`9033d3d8 fffffadf`99d9e590
    00000000`00000000 fffff800`011a98fd : sptd+0x57a0f
    fffffadf`87a9af40 fffffadf`9c9942ee : fffffadf`99d9e590 00000000`00000000
    fffffadf`9c994000 fffffadf`87a9b018 : sptd+0x41a65
    fffffadf`87a9aff0 fffffadf`99d9e590 : 00000000`00000000 fffffadf`9c994000
    fffffadf`87a9b018 fffffadf`9c597040 : 0xfffffadf`9c9942ee
    fffffadf`87a9aff8 00000000`00000000 : fffffadf`9c994000 fffffadf`87a9b018
    fffffadf`9c597040 00000000`00000000 : 0xfffffadf`99d9e590


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    sptd+57a0f
    fffffadf`90315a0f 488b742438 mov rsi,qword ptr [rsp+38h]

    SYMBOL_STACK_INDEX: d

    SYMBOL_NAME: sptd+57a0f

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: sptd

    IMAGE_NAME: sptd.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47cf3c13

    FAILURE_BUCKET_ID: X64_0x1E_sptd+57a0f

    BUCKET_ID: X64_0x1E_sptd+57a0f

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

    Bye,
    Skybuck.
     
    Skybuck Flying, Dec 20, 2010
    #1
    1. Advertising

  2. Minidump file:

    http://members.home.nl/hbthouppermans/MiniDump/Mini122010-01.dmp

    Minidump analysis:

    "
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini122010-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is:
    SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
    x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.100216-1301
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
    Debug session time: Mon Dec 20 06:34:34.656 2010 (GMT+1)
    System Uptime: 0 days 10:46:49.605
    Loading Kernel Symbols
    ................................................................
    .................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    ......................
    *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff800012c1308, 0, 6000}

    Unable to load image sptd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for
    sptd.sys
    Probably caused by : sptd.sys ( sptd+57a0f )

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

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

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800012c1308, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000006000, Parameter 1 of the exception

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
    referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    nt!PspGetSetContextInternal+203
    fffff800`012c1308 488b58f8 mov rbx,qword ptr [rax-8]

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: 0000000000006000

    READ_ADDRESS: 0000000000006000

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x1E

    PROCESS_NAME: TestApplication

    CURRENT_IRQL: 1

    EXCEPTION_RECORD: fffffadf87a9a270 -- (.exr 0xfffffadf87a9a270)
    ExceptionAddress: fffff800012c1308
    (nt!PspGetSetContextInternal+0x0000000000000203)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000008
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000006000
    Attempt to read from address 0000000000006000

    TRAP_FRAME: fffffadf87a9a300 -- (.trap 0xfffffadf87a9a300)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000006008 rbx=0000000000000000 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800012c1308 rsp=fffffadf87a9a490 rbp=fffffadf8ca6db10
    r8=0000000000000000 r9=0000000000000000 r10=0f00000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    nt!PspGetSetContextInternal+0x203:
    fffff800`012c1308 488b58f8 mov rbx,qword ptr [rax-8]
    ds:a4f0:00000000`00006000=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80001080e86 to fffff8000102e890

    STACK_TEXT:
    fffffadf`87a99b78 fffff800`01080e86 : 00000000`0000001e ffffffff`c0000005
    fffff800`012c1308 00000000`00000000 : nt!KeBugCheckEx
    fffffadf`87a99b80 fffff800`0102e6af : fffffadf`87a9a270 fffffa80`0000005e
    fffffadf`87a9a300 00001f80`00000080 : nt!KiDispatchException+0x128
    fffffadf`87a9a180 fffff800`0102d521 : fffffadf`99d9e8e8 fffffa80`054a6ed8
    fffffa80`054a6e00 fffffa80`04ecb010 : nt!KiExceptionExit
    fffffadf`87a9a300 fffff800`012c1308 : fffffadf`99a5f9b0 0f000000`00000000
    fffffadf`87a9b230 fffffadf`8ca6d5c0 : nt!KiPageFault+0x1e1
    fffffadf`87a9a490 fffff800`0104236b : fffffadf`995b8710 00000000`00000000
    fffffadf`995b8758 00000000`00000000 : nt!PspGetSetContextInternal+0x203
    fffffadf`87a9a9e0 fffff800`01027eb1 : fffff980`6efd1db8 fffff980`6efd1f38
    00000000`00000000 00000000`00000000 : nt!PspGetSetContextSpecialApc+0xab
    fffffadf`87a9aaf0 fffff800`0103bf97 : 00000000`ffffff00 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x215
    fffffadf`87a9ab90 fffff800`0102828e : 00000000`00000000 fffffa80`054a6b01
    fffffadf`995b87a8 fffffadf`995b8710 : nt!KiSwapThread+0x3e9
    fffffadf`87a9abf0 fffff800`0101f88c : 00000000`00000000 fffff980`00000005
    fffff980`6effb800 00000000`00000000 : nt!KeWaitForSingleObject+0x5a6
    fffffadf`87a9ac70 fffff800`0101f51b : fffffadf`9c7dba60 00000000`00000000
    00000000`ffffffff 00000011`d25a7ed8 : nt!KiSuspendThread+0x2c
    fffffadf`87a9acb0 fffff800`01027abd : fffffa80`054a6bb0 00000000`00000000
    fffff800`0101f860 00000000`00000000 : nt!KiDeliverApc+0x2d3
    fffffadf`87a9ad50 fffff800`010747cf : fffffadf`997cae80 fffffadf`87a9b201
    00000000`00000000 fffffadf`87a9b2b0 : nt!KiApcInterrupt+0xdd
    fffffadf`87a9aee0 fffffadf`90315a0f : fffffadf`9033d301 fffffadf`9c994000
    fffffadf`99d9e500 fffffadf`995eaf40 : nt!KeLeaveCriticalRegion+0x36
    fffffadf`87a9af10 fffffadf`9033d301 : fffffadf`9c994000 fffffadf`99d9e500
    fffffadf`995eaf40 fffffadf`99d9e8e8 : sptd+0x57a0f
    fffffadf`87a9af18 fffffadf`9c994000 : fffffadf`99d9e500 fffffadf`995eaf40
    fffffadf`99d9e8e8 fffffadf`902ffa65 : sptd+0x7f301
    fffffadf`87a9af20 fffffadf`99d9e500 : fffffadf`995eaf40 fffffadf`99d9e8e8
    fffffadf`902ffa65 fffffadf`9033d3d8 : 0xfffffadf`9c994000
    fffffadf`87a9af28 fffffadf`995eaf40 : fffffadf`99d9e8e8 fffffadf`902ffa65
    fffffadf`9033d3d8 fffffadf`99d9e590 : 0xfffffadf`99d9e500
    fffffadf`87a9af30 fffffadf`99d9e8e8 : fffffadf`902ffa65 fffffadf`9033d3d8
    fffffadf`99d9e590 00000000`00000000 : 0xfffffadf`995eaf40
    fffffadf`87a9af38 fffffadf`902ffa65 : fffffadf`9033d3d8 fffffadf`99d9e590
    00000000`00000000 fffff800`011a98fd : 0xfffffadf`99d9e8e8
    fffffadf`87a9af40 fffffadf`9033d3d8 : fffffadf`99d9e590 00000000`00000000
    fffff800`011a98fd fffffadf`99f363c0 : sptd+0x41a65
    fffffadf`87a9af48 fffffadf`99d9e590 : 00000000`00000000 fffff800`011a98fd
    fffffadf`99f363c0 fffffadf`99f363c0 : sptd+0x7f3d8
    fffffadf`87a9af50 00000000`00000000 : fffff800`011a98fd fffffadf`99f363c0
    fffffadf`99f363c0 fffffadf`99f36303 : 0xfffffadf`99d9e590


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    sptd+57a0f
    fffffadf`90315a0f ?? ???

    SYMBOL_STACK_INDEX: d

    SYMBOL_NAME: sptd+57a0f

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: sptd

    IMAGE_NAME: sptd.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47cf3c13

    FAILURE_BUCKET_ID: X64_0x1E_sptd+57a0f

    BUCKET_ID: X64_0x1E_sptd+57a0f

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

    Bye,
    Skybuck.
     
    Skybuck Flying, Dec 20, 2010
    #2
    1. Advertising

  3. Skybuck Flying

    Jeff Gaines Guest

    On 20/12/2010 in message
    <a9be8$4d0eee55$54190f09$1.nb.home.nl> Skybuck Flying
    wrote:

    >Hello,


    [snipped]

    There is no point in cross posting this to
    microsoft.public.windows.64bit.general, it's not a programming group.

    --
    Jeff Gaines Wiltshire UK
    There are 10 types of people in the world, those who do binary and those
    who don't.
     
    Jeff Gaines, Dec 20, 2010
    #3
  4. "Jeff Gaines" <> wrote in message
    news:...
    > On 20/12/2010 in message
    > <a9be8$4d0eee55$54190f09$1.nb.home.nl> Skybuck Flying
    > wrote:
    >
    >>Hello,

    >
    > [snipped]
    >
    > There is no point in cross posting this to
    > microsoft.public.windows.64bit.general, it's not a programming group.


    A programming newsgroup would not be suited.

    Since programming operating systems and drivers and kernels is something
    very special which only few people on this world can do.

    In case those few people wanna see the latest and greatest crashes via
    google, they might find these ones thanks to my postings in
    microsoft.public.windows.64bit.general.

    Bye,
    Skybuck.
     
    Skybuck Flying, Dec 29, 2010
    #4
  5. "Jeff Gaines" <> wrote in message
    news:...
    > On 20/12/2010 in message
    > <a9be8$4d0eee55$54190f09$1.nb.home.nl> Skybuck Flying
    > wrote:
    >
    >>Hello,

    >
    > [snipped]
    >
    > There is no point in cross posting this to
    > microsoft.public.windows.64bit.general, it's not a programming group.


    Further points which you seem to willingly and very pleasently want to
    ignore:

    1. Problems.
    2. Putting Microsoft under pressure.
    3. Attention to problems.
    4. Stability of operating systems.
    And so on...

    Especially point 4 is very interesting to *ME* and *ALL* general users of 64
    bit microsoft operating sytems. (Except people/idiots who don't care about
    crashes, perhaps you ? ;) :))

    Bye,
    Skybuck.
     
    Skybuck Flying, Dec 29, 2010
    #5
  6. "Jeff Gaines" <> wrote in message
    news:...
    > On 20/12/2010 in message
    > <a9be8$4d0eee55$54190f09$1.nb.home.nl> Skybuck Flying
    > wrote:
    >
    >>Hello,

    >
    > [snipped]
    >
    > There is no point in cross posting this to
    > microsoft.public.windows.64bit.general, it's not a programming group.


    Further reasons:

    5. Perhaps other users already have seen this bluescreen and might know a
    solution.
    And so forth...

    Bye,
    Skybuck ;) :)
     
    Skybuck Flying, Dec 29, 2010
    #6
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Angus McBagpipe

    Re: A Blue Screen of Death Question.

    Angus McBagpipe, Jun 21, 2003, in forum: Computer Support
    Replies:
    0
    Views:
    1,757
    Angus McBagpipe
    Jun 21, 2003
  2. Bob

    Blue screen of death..........

    Bob, Jul 3, 2003, in forum: Computer Support
    Replies:
    1
    Views:
    733
    °Mike°
    Jul 4, 2003
  3. rabraham7

    Blue screen of death

    rabraham7, Sep 18, 2003, in forum: Computer Support
    Replies:
    6
    Views:
    783
    slumpy
    Sep 22, 2003
  4. Ken Tucky

    Blue "Death" Screen

    Ken Tucky, Oct 23, 2003, in forum: Computer Support
    Replies:
    4
    Views:
    627
    Plato
    Oct 26, 2003
  5. Dennis
    Replies:
    2
    Views:
    2,200
Loading...

Share This Page