1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

BSOD (minidump)

By freshhh
Oct 22, 2008
  1. Hi there :)
    Please help me to fix this error!

    Minidump :

    Minidump : sharebee.com/5fc898fa

    NOTES :

    - file "SCSIPORT.SYS" is not present anywhere in my HD other than in websymbols dir (needed for the Debugger Tool)...
    - i don't have any scsi peripherical
    - i don't have any scsi card plugged
    - i don't use any virtual disk software like Daemon Tools...

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

    Loading Dump File [C:\TEST\MINIDUMP\Mini102208-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\websymbols*msdl.microsoft.com/download/symbols
    Executable search path is:
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.080813-1204
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
    Debug session time: Wed Oct 22 12:31:09.390 2008 (GMT+2)
    System Uptime: 0 days 0:04:15.508
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffffadf9c09aec4, 0, ffffffffffffffff}

    *** WARNING: Unable to verify checksum for SCSIPORT.SYS
    Probably caused by : SCSIPORT.SYS ( SCSIPORT!ScsiPortInterrupt+44 )

    Followup: MachineOwner

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

    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.
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffffadf9c09aec4, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, 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".

    fffffadf`9c09aec4 a217a5f39fc41352bc mov byte ptr [BC5213C49FF3A517h],al

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: ffffffffffffffff

    READ_ADDRESS: ffffffffffffffff






    EXCEPTION_RECORD: fffff80000117630 -- (.exr 0xfffff80000117630)
    ExceptionAddress: fffffadf9c09aec4
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    TRAP_FRAME: fffff800001176c0 -- (.trap 0xfffff800001176c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000909e3379 rbx=0000000000000000 rcx=0000000000000202
    rdx=000000000000082f rsi=0000000000000022 rdi=0000000000000000
    rip=fffffadf9c09aec4 rsp=fffff80000117858 rbp=fffff80000117900
    r8=000000000000082f r9=fffffadf9cc86bf0 r10=000000000000000f
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    fffffadf`9c09aec4 a217a5f39fc41352bc mov byte ptr [BC5213C49FF3A517h],al ds:0180:bc5213c4`9ff3a517=??
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80001080e86 to fffff8000102e890

    fffff800`00116f38 fffff800`01080e86 : 00000000`0000001e ffffffff`c0000005 fffffadf`9c09aec4 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00116f40 fffff800`0102e6af : fffff800`00117630 00000000`00800000 fffff800`001176c0 fffff800`00808000 : nt!KiDispatchException+0x128
    fffff800`00117540 fffff800`0102d30d : 00000000`00000000 fffff800`0102f557 00000000`00000000 00000000`00000000 : nt!KiExceptionExit
    fffff800`001176c0 fffffadf`9c09aec4 : fffff800`00117860 fffffadf`9c099268 fffff800`00117800 00000000`00000022 : nt!KiGeneralProtectionFault+0xcd
    fffff800`00117858 fffff800`00117860 : fffffadf`9c099268 fffff800`00117800 00000000`00000022 00000000`00000000 : 0xfffffadf`9c09aec4
    fffff800`00117860 fffffadf`9c099268 : fffff800`00117800 00000000`00000022 00000000`00000000 fffffadf`911a7000 : 0xfffff800`00117860
    fffff800`00117868 fffff800`00117800 : 00000000`00000022 00000000`00000000 fffffadf`911a7000 fffffadf`9c75c010 : 0xfffffadf`9c099268
    fffff800`00117870 00000000`00000022 : 00000000`00000000 fffffadf`911a7000 fffffadf`9c75c010 00000000`00010000 : 0xfffff800`00117800
    fffff800`00117878 00000000`00000000 : fffffadf`911a7000 fffffadf`9c75c010 00000000`00010000 fffff800`0102f700 : 0x22
    fffff800`00117880 fffffadf`911a7000 : fffffadf`9c75c010 00000000`00010000 fffff800`0102f700 00000000`00010000 : 0x0
    fffff800`00117888 fffffadf`9c75c010 : 00000000`00010000 fffff800`0102f700 00000000`00010000 fffffadf`8ebe0000 : 0xfffffadf`911a7000
    fffff800`00117890 00000000`00010000 : fffff800`0102f700 00000000`00010000 fffffadf`8ebe0000 00000000`00000000 : 0xfffffadf`9c75c010
    fffff800`00117898 fffff800`0102f700 : 00000000`00010000 fffffadf`8ebe0000 00000000`00000000 fffffadf`9c070000 : 0x10000
    fffff800`001178a0 fffffadf`903bc38e : 00000000`00000000 fffffadf`9bfac780 fffffadf`9c099268 f8000011`79800130 : nt!KiScanInterruptObjectList+0x40
    fffff800`001178f0 f8000011`00700fff : 00000000`0000ffff f8000011`0000006f fffffadf`9c07ffff 00000000`00000000 : SCSIPORT!ScsiPortInterrupt+0x44
    fffff800`00117920 00000000`0000ffff : f8000011`0000006f fffffadf`9c07ffff 00000000`00000000 fffffadf`9bfac630 : 0xf8000011`00700fff
    fffff800`00117928 f8000011`0000006f : fffffadf`9c07ffff 00000000`00000000 fffffadf`9bfac630 fffffadf`903bc38e : 0xffff
    fffff800`00117930 fffffadf`9c07ffff : 00000000`00000000 fffffadf`9bfac630 fffffadf`903bc38e ffff02df`905159c1 : 0xf8000011`0000006f
    fffff800`00117938 00000000`00000000 : fffffadf`9bfac630 fffffadf`903bc38e ffff02df`905159c1 fffffadf`9bfac780 : 0xfffffadf`9c07ffff
    fffff800`00117940 fffffadf`9bfac630 : fffffadf`903bc38e ffff02df`905159c1 fffffadf`9bfac780 fffff800`00117a50 : 0x0
    fffff800`00117948 fffffadf`903bc38e : ffff02df`905159c1 fffffadf`9bfac780 fffff800`00117a50 fffff800`00117c90 : 0xfffffadf`9bfac630
    fffff800`00117950 fffff800`0102f749 : 00000000`00000000 00000000`00000000 9c098e00`001094c8 00000000`fffffadf : SCSIPORT!ScsiPortInterrupt+0x44
    fffff800`00117980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiScanInterruptObjectList+0x89


    fffffadf`903bc38e 84c0 test al,al


    SYMBOL_NAME: SCSIPORT!ScsiPortInterrupt+44

    FOLLOWUP_NAME: MachineOwner




    FAILURE_BUCKET_ID: X64_0x1E_SCSIPORT!ScsiPortInterrupt+44

    BUCKET_ID: X64_0x1E_SCSIPORT!ScsiPortInterrupt+44

    Followup: MachineOwner
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...