1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

What causes these BSOD's and how to solve it?

Discussion in 'Windows XP' started by Ragefhonor, 2017/08/17.

  1. 2017/08/17
    Ragefhonor

    Ragefhonor New Member Thread Starter

    Joined:
    2017/08/11
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Computer Experience:
    Very good
    Hi,

    I have problems with my PC i get often BSODs and can't find the reason

    Sometimes directly after start
    Sometimes few minutes after start
    I have made a virus scan and no infections have been found
    SMART looks fine
    No problems in SAFE Mode
    6 hours MEMTEST Passed
    In VGA Mode i also get BSOD
    Now i didnt had a BSOD for few days. Is it solved now?
    The last thing i did was removing and installing network drivers.

    Im afraid that they come back.

    Got these errors:


    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Fri Aug 11 07:13:41.188 2017 (UTC - 4:00)
    System Uptime: 0 days 0:00:55.261
    *******************************************************************************
    * *
    * 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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000, address which referenced memory

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    READ_ADDRESS: GetUlongFromAddress: unable to read from 80561f50
    00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    +0
    00000000 ?? ???

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    TRAP_FRAME: b84dbcb8 -- (.trap 0xffffffffb84dbcb8)
    ErrCode = 00000010
    eax=b8348cd0 ebx=b8348000 ecx=00000000 edx=8abe6a2c esi=b83489c0 edi=8055c0c0
    eip=00000000 esp=b84dbd2c ebp=b8348980 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    00000000 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 00000000 to 8054480c

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00000000 ?? ???

    STACK_TEXT:
    b84dbcb8 00000000 badb0d00 8abe6a2c badb0d00 nt!KiTrap0E+0x180
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b84dbd28 80545f9f 8abe6a2c 00000000 00000000 0x0
    b84dbd50 80545e84 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiTrap0E+180
    8054480c f7457000000200 test dword ptr [ebp+70h],20000h

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KiTrap0E+180

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f

    FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180

    BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180

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


    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Fri Aug 11 07:06:28.282 2017 (UTC - 4:00)
    System Uptime: 0 days 0:29:32.278
    *******************************************************************************
    * *
    * 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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000, address which referenced memory

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    READ_ADDRESS: GetUlongFromAddress: unable to read from 80561f50
    00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    +0
    00000000 ?? ???

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    TRAP_FRAME: b84dbcb8 -- (.trap 0xffffffffb84dbcb8)
    ErrCode = 00000010
    eax=b8348cd0 ebx=b8348000 ecx=00000000 edx=8abbfebc esi=b83489c0 edi=8055c0c0
    eip=00000000 esp=b84dbd2c ebp=b8348980 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    00000000 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 00000000 to 8054480c

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00000000 ?? ???

    STACK_TEXT:
    b84dbcb8 00000000 badb0d00 8abbfebc badb0d00 nt!KiTrap0E+0x180
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b84dbd28 80545f9f 8abbfebc 00000000 00000000 0x0
    b84dbd50 80545e84 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiTrap0E+180
    8054480c f7457000000200 test dword ptr [ebp+70h],20000h

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KiTrap0E+180

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f

    FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180

    BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180

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


    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:*** WARNING: Unable to verify timestamp for srv.sys
    *** ERROR: Module load completed but symbols could not be loaded for srv.sys

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Jul 5 14:35:09.421 2017 (UTC - 4:00)
    System Uptime: 0 days 0:03:04.170
    *******************************************************************************
    * *
    * 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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000, address which referenced memory

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    READ_ADDRESS: GetUlongFromAddress: unable to read from 80561f50
    00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    +0
    00000000 ?? ???

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from ffdffc70 to b812b552

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00000000 ?? ???

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80551430 ffdffc70 805288c1 ffdff000 8055c0c0 AmdK8+0x3552
    80551450 80545e6c 00000000 0000000e 00000000 0xffdffc70
    80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    AmdK8+3552
    b812b552 ?? ???

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: AmdK8+3552

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: AmdK8

    IMAGE_NAME: AmdK8.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_AmdK8+3552

    BUCKET_ID: 0xD1_CODE_AV_NULL_IP_AmdK8+3552

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


    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Jul 5 14:31:18.000 2017 (UTC - 4:00)
    System Uptime: 0 days 0:09:57.742
    *******************************************************************************
    * *
    * 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: 00f800de, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00f800de, address which referenced memory

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    READ_ADDRESS: GetUlongFromAddress: unable to read from 80561f50
    00f800de

    CURRENT_IRQL: 2

    FAULTING_IP:
    +0
    00f800de ?? ???

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    TRAP_FRAME: b84dbcb8 -- (.trap 0xffffffffb84dbcb8)
    ErrCode = 00000010
    eax=b8348cd0 ebx=b8348000 ecx=00f800de edx=88d0fae4 esi=b83489c0 edi=8055c0c0
    eip=00f800de esp=b84dbd2c ebp=b8348980 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    00f800de ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 00f800de to 8054480c

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00f800de ?? ???

    STACK_TEXT:
    b84dbcb8 00f800de badb0d00 88d0fae4 badb0d00 nt!KiTrap0E+0x180
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b84dbd28 80545f9f 88d0fae4 e4627f08 00000000 0xf800de
    b84dbd50 80545e84 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiTrap0E+180
    8054480c f7457000000200 test dword ptr [ebp+70h],20000h

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KiTrap0E+180

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f

    FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+180

    BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+180

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



    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Jul 5 12:07:39.718 2017 (UTC - 4:00)
    System Uptime: 1 days 6:24:17.625
    *******************************************************************************
    * *
    * 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: 00000000, memory referenced
    Arg2: 00000007, 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: 806eda02, address which referenced memory

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    READ_ADDRESS: GetUlongFromAddress: unable to read from 80561f50
    00000000

    CURRENT_IRQL: 7

    FAULTING_IP:
    hal!InbvDisplayString+4
    806eda02 6e outs dx,byte ptr [esi]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    TRAP_FRAME: b84dbbd8 -- (.trap 0xffffffffb84dbbd8)
    ErrCode = 00000000
    eax=000000ff ebx=8aff6370 ecx=00000000 edx=0000c88a esi=00000000 edi=8aff6c68
    eip=806eda02 esp=b84dbc4c ebp=b84dbc78 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    hal!InbvDisplayString+0x4:
    806eda02 6e outs dx,byte ptr [esi] ds:0023:00000000=??
    Resetting default scope

    MISALIGNED_IP:
    hal!InbvDisplayString+4
    806eda02 6e outs dx,byte ptr [esi]

    LAST_CONTROL_TRANSFER: from 806eda02 to 8054480c

    STACK_TEXT:
    b84dbbd8 806eda02 badb0d00 0000c88a 878f97a8 nt!KiTrap0E+0x180
    b84dbc78 b7f0f696 01ff6370 8afa4e14 8af99e1c hal!InbvDisplayString+0x4
    b84dbc8c 805455fc 8afa4e18 8aff6030 804ffbdc atapi!IdePortInterrupt+0x18
    b84dbcb0 805455a9 00000002 00000183 b84dbd50 nt!KiChainedDispatch2ndLvl+0x44
    b84dbcb0 b831b552 00000002 00000183 b84dbd50 nt!KiChainedDispatch+0x29
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b84dbd30 b8348c70 805288c1 b8348000 8055c0c0 AmdK8+0x3552
    b84dbd50 80545e6c 00000000 0000000e 00000000 0xb8348c70
    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    atapi!IdePortInterrupt+18
    b7f0f696 f6862801000004 test byte ptr [esi+128h],4

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: atapi!IdePortInterrupt+18

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: IP_MISALIGNED

    BUCKET_ID: IP_MISALIGNED

    Followup: MachineOwner
    ---------
     
  2. 2017/08/17
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    5,358
    Likes Received:
    294
    Trophy Points:
    1,093
    Location:
    New Zealand
    Computer Experience:
    intermediate

  3. to hide this advert.

  4. 2017/08/17
    Ragefhonor

    Ragefhonor New Member Thread Starter

    Joined:
    2017/08/11
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Computer Experience:
    Very good
    I will check the link,

    Today o got this one:

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Thu Aug 17 22:36:18.687 2017 (UTC - 4:00)
    System Uptime: 4 days 16:21:26.523
    *******************************************************************************
    * *
    * 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: b31fd004, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000001, 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: 8050234e, address which referenced memory

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    WRITE_ADDRESS: GetUlongFromAddress: unable to read from 80561f50
    b31fd004

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt!KiTimerExpiration+88
    8050234e 895f04 mov dword ptr [edi+4],ebx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    TRAP_FRAME: 80551390 -- (.trap 0xffffffff80551390)
    ErrCode = 00000002
    eax=8055cc88 ebx=8055cc88 ecx=8ae2e968 edx=000000ff esi=000000a1 edi=b31fd000
    eip=8050234e esp=80551404 ebp=80551428 iopl=0 nv up ei ng nz ac pe cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
    nt!KiTimerExpiration+0x88:
    8050234e 895f04 mov dword ptr [edi+4],ebx ds:0023:b31fd004=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 8050234e to 8054480c

    STACK_TEXT:
    80551390 8050234e badb0d00 000000ff b816b552 nt!KiTrap0E+0x180
    80551428 80545f9f 8055c4c0 00000000 018b01a0 nt!KiTimerExpiration+0x88
    80551440 8055be60 ffdffc50 00000000 8055be60 nt!KiRetireDpcList+0x61
    80551450 80545e84 00000000 0000000e 00000000 nt!KiIdleThread0
    80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiTimerExpiration+88
    8050234e 895f04 mov dword ptr [edi+4],ebx

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KiTimerExpiration+88

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f

    FAILURE_BUCKET_ID: 0xA_nt!KiTimerExpiration+88

    BUCKET_ID: 0xA_nt!KiTimerExpiration+88

    Followup: MachineOwner
     
  5. 2017/08/18
    Ragefhonor

    Ragefhonor New Member Thread Starter

    Joined:
    2017/08/11
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Computer Experience:
    Very good
    Later i got this one:

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Fri Aug 18 02:43:06.093 2017 (UTC - 4:00)
    System Uptime: 0 days 3:04:33.708
    *******************************************************************************
    * *
    * 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: 00000027, memory referenced
    Arg2: 00000007, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: b7f0f688, address which referenced memory

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    READ_ADDRESS: GetUlongFromAddress: unable to read from 80561f50
    00000027

    CURRENT_IRQL: 7

    FAULTING_IP:
    atapi!IdePortInterrupt+a
    b7f0f688 8b7028 mov esi,dword ptr [eax+28h]

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    TRAP_FRAME: b84dbc10 -- (.trap 0xffffffffb84dbc10)
    ErrCode = 00000000
    eax=ffffffff ebx=8afece1c ecx=00000007 edx=0000d407 esi=8afbfe14 edi=8afbfe18
    eip=b7f0f688 esp=b84dbc84 ebp=b84dbc8c iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    atapi!IdePortInterrupt+0xa:
    b7f0f688 8b7028 mov esi,dword ptr [eax+28h] ds:0023:00000027=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from b7f0f688 to 8054480c

    STACK_TEXT:
    b84dbc10 b7f0f688 badb0d00 0000d407 8acbed58 nt!KiTrap0E+0x180
    b84dbc8c 805455fc 8afbfe18 8afc2030 b79d62d8 atapi!IdePortInterrupt+0xa
    b84dbcb0 805455a9 0012a702 00000183 b84dbd50 nt!KiChainedDispatch2ndLvl+0x44
    b84dbcb0 b81ab552 0012a702 00000183 b84dbd50 nt!KiChainedDispatch+0x29
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b84dbd30 b8348c70 805288c1 b8348000 8055c0c0 AmdK8+0x3552
    b84dbd50 80545e6c 00000000 0000000e 06230216 0xb8348c70
    b84dbd54 00000000 0000000e 06230216 10b04b1b nt!KiIdleLoop+0x10


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    atapi!IdePortInterrupt+a
    b7f0f688 8b7028 mov esi,dword ptr [eax+28h]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: atapi!IdePortInterrupt+a

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: atapi

    IMAGE_NAME: atapi.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4802539d

    FAILURE_BUCKET_ID: 0xD1_atapi!IdePortInterrupt+a

    BUCKET_ID: 0xD1_atapi!IdePortInterrupt+a

    Followup: MachineOwner
    ---------
     
  6. 2017/08/18
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    5,358
    Likes Received:
    294
    Trophy Points:
    1,093
    Location:
    New Zealand
    Computer Experience:
    intermediate
    Have you updated your drivers and or BIOS?
     
  7. 2017/08/21
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,567
    Likes Received:
    471
    Trophy Points:
    1,093
    Location:
    Walnut Creek, California, United States
    Computer Experience:
    Intermediate+
    Hi RageofHonor, Welcome to Windowsbbs! :)

    Have you updated all your device drivers from your motherboard manufacturer, Asrock N68C-S UCC?

    Are you overclocking any components? Did you try performing a clean install of Windows XP and then updating the drivers to see if the computer still blue screens?
     
  8. 2017/08/25
    Ragefhonor

    Ragefhonor New Member Thread Starter

    Joined:
    2017/08/11
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Computer Experience:
    Very good
    Hi,


    In the meantime I had about 18 BSODs.


    I scanned the RAM in dual mode for about 8 hours without error.

    I have scanned my HDD for errors. NO errors found Disk passed the short and long test in the WD test programm.

    I have deleted the IDE/SATA, GPU and network drivers. Every time I had done that I thought that I have solved the problem. But I still get BSODs.

    Installed new drivers for my Network Card and GPU


    NVIDIA network:

    67.8.0.0

    2008-03-25


    NVIDIA GPU:


    6.14.13.4052

    2014-07-02


    My PC is not overclocked.


    Once my HDD transfer in HD Tune was 10 MB/s. Deleting the IDE control drivers solved the low speed. Now it’s about 160-180 MB/s. One of the controllers was in PIO mode and not DMA. Now it’s in DMA again.


    Did CHKDSK /r. no errors found


    Scanned the drive with MMHD for slow sectors and found about 8

    SMART looks good.


    The clocks don’t match. There is a difference in the CMOS time about 3 seconds.


    When I made a stress test of the RAM with one of the programs from HBCD it froze at 001033B8 (CPU1)

    In the program Troubleshooter I got Blank screen when testing the memory

    When I set Gold Memory to check how much RAM I have it froze at 3669808 KB with 3 colored layers (blue, green and aquamarine) and after a while I had small blinking rectangles at the screen.


    My LAN froze during start. Could not refresh the IP.


    CPU Max freq: x13.0 2600 MHz

    CPU Max voltage 1.3500V


    CPU temp 51*C

    M/B temp 40*C

    CPU Fan SPD 3590 RPM


    AM2 Boost Disabled

    Cool n Quiet Enabled

    Secure VM Enabled


    Floppy control Enabled

    Serial port address 3F8/IRQ4

    Paralel port 378

    Parallel port mode ECP+EPP

    EPP ver 1,9

    ECP Mode DMA ch. DMA3

    Paralel Port IRQ IRQ7


    In BIOS HDD is at SATA 2


    Vcore: 1.288 V

    +3.30 V 3.360 V

    +5.00 V 5.160 V

    +12.00 V 12.302 V


    Quiet Fan Disabled


    I would like to avoid reinstalling Windows. It would be a pain to install everything again. Especially the Audio Video Codecs.




    I have got a different kind of BSODs during the last days:



    Loading Dump File [C:\WINDOWS\Minidump\Mini082017-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Sun Aug 20 17:37:59.320 2017 (UTC + 2:00)

    System Uptime: 1 days 7:42:09.037

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ....

    Loading User Symbols

    Loading unloaded module list

    .......................


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {27, 7, 0, b7f0f688}


    Probably caused by : atapi.sys ( atapi!IdePortInterrupt+a )


    Followup: MachineOwner

    ---------



    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: 00000027, memory referenced

    Arg2: 00000007, IRQL

    Arg3: 00000000, value 0 = read operation, 1 = write operation

    Arg4: b7f0f688, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: 00000027


    CURRENT_IRQL: 7


    FAULTING_IP:

    atapi!IdePortInterrupt+a

    b7f0f688 8b7028 mov esi,dword ptr [eax+28h]


    CUSTOMER_CRASH_COUNT: 1


    DEFAULT_BUCKET_ID: DRIVER_FAULT


    BUGCHECK_STR: 0xD1


    TRAP_FRAME: b84dbc10 -- (.trap 0xffffffffb84dbc10)

    ErrCode = 00000000

    eax=ffffffff ebx=8af99e1c ecx=00000007 edx=0000d407 esi=8afb7e14 edi=8afb7e18

    eip=b7f0f688 esp=b84dbc84 ebp=b84dbc8c iopl=0 nv up ei pl zr na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

    atapi!IdePortInterrupt+0xa:

    b7f0f688 8b7028 mov esi,dword ptr [eax+28h] ds:0023:00000027=????????

    Resetting default scope


    LAST_CONTROL_TRANSFER: from b7f0f688 to 8054480c


    STACK_TEXT:

    b84dbc10 b7f0f688 badb0d00 0000d407 8adcac40 nt!KiTrap0E+0x180

    b84dbc8c 805455fc 8afb7e18 8afe7030 804ffbdc atapi!IdePortInterrupt+0xa

    b84dbca4 8054559c 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch2ndLvl+0x44

    b84dbca4 00000000 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch+0x1c



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    atapi!IdePortInterrupt+a

    b7f0f688 8b7028 mov esi,dword ptr [eax+28h]


    SYMBOL_STACK_INDEX: 1


    SYMBOL_NAME: atapi!IdePortInterrupt+a


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: atapi


    IMAGE_NAME: atapi.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 4802539d


    FAILURE_BUCKET_ID: 0xD1_atapi!IdePortInterrupt+a


    BUCKET_ID: 0xD1_atapi!IdePortInterrupt+a


    Followup: MachineOwner

    ----------------------------------------------------------------------


    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86

    Copyright (c) Microsoft Corporation. All rights reserved.



    Loading Dump File [C:\WINDOWS\Minidump\Mini082117-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Mon Aug 21 10:04:07.764 2017 (UTC + 2:00)

    System Uptime: 0 days 14:57:03.851

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .......

    Loading User Symbols

    Loading unloaded module list

    .................................


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {0, 2, 8, 0}


    Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+180 )


    Followup: MachineOwner

    ---------



    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: 00000000, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000008, value 0 = read operation, 1 = write operation

    Arg4: 00000000, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: 00000000


    CURRENT_IRQL: 2


    FAULTING_IP:

    +43e2faf017adfc0

    00000000 ?? ???


    CUSTOMER_CRASH_COUNT: 1


    DEFAULT_BUCKET_ID: DRIVER_FAULT


    BUGCHECK_STR: 0xD1


    TRAP_FRAME: b84dbcb8 -- (.trap 0xffffffffb84dbcb8)

    ErrCode = 00000010

    eax=b8348cd0 ebx=b8348000 ecx=00000000 edx=8ab2febc esi=b83489c0 edi=8055c0c0

    eip=00000000 esp=b84dbd2c ebp=b8348980 iopl=0 nv up ei pl zr na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

    00000000 ?? ???

    Resetting default scope


    LAST_CONTROL_TRANSFER: from 00000000 to 8054480c


    FAILED_INSTRUCTION_ADDRESS:

    +43e2faf017adfc0

    00000000 ?? ???


    STACK_TEXT:

    b84dbcb8 00000000 badb0d00 8ab2febc badb0d00 nt!KiTrap0E+0x180

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    b84dbd28 80545f9f 8ab2febc 00000000 00000000 0x0

    b84dbd50 80545e84 00000000 0000000e 0077005c nt!KiRetireDpcList+0x61

    b84dbd54 00000000 0000000e 0077005c 006e0061 nt!KiIdleLoop+0x28



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nt!KiTrap0E+180

    8054480c f7457000000200 test dword ptr [ebp+70h],20000h


    SYMBOL_STACK_INDEX: 0


    SYMBOL_NAME: nt!KiTrap0E+180


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nt


    IMAGE_NAME: ntkrpamp.exe


    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f


    FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180


    BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180


    Followup: MachineOwner

    ----------------------------------------------------------------------


    Loading Dump File [C:\WINDOWS\Minidump\Mini082117-02.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Mon Aug 21 11:06:41.159 2017 (UTC + 2:00)

    System Uptime: 0 days 1:02:34.942

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ....

    Loading User Symbols

    Loading unloaded module list

    ..................


    Use !analyze -v to get detailed debugging information.


    BugCheck A, {0, 1c, 1, 80502dcc}


    Probably caused by : ntkrpamp.exe ( nt!KiUnlinkThread+c )


    Followup: MachineOwner

    ---------



    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: 00000000, memory referenced

    Arg2: 0000001c, IRQL

    Arg3: 00000001, 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: 80502dcc, address which referenced memory


    Debugging Details:

    ------------------



    WRITE_ADDRESS: 00000000


    CURRENT_IRQL: 1c


    FAULTING_IP:

    nt!KiUnlinkThread+c

    80502dcc 8916 mov dword ptr [esi],edx


    CUSTOMER_CRASH_COUNT: 2


    DEFAULT_BUCKET_ID: DRIVER_FAULT


    BUGCHECK_STR: 0xA


    TRAP_FRAME: 8055123c -- (.trap 0xffffffff8055123c)

    ErrCode = 00000002

    eax=89827480 ebx=898276c0 ecx=898275c8 edx=00000040 esi=00000000 edi=00000000

    eip=80502dcc esp=805512b0 ebp=805512c4 iopl=0 nv up ei ng nz na pe cy

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287

    nt!KiUnlinkThread+0xc:

    80502dcc 8916 mov dword ptr [esi],edx ds:0023:00000000=????????

    Resetting default scope


    LAST_CONTROL_TRANSFER: from 80502dcc to 8054480c


    STACK_TEXT:

    8055123c 80502dcc badb0d00 00000040 80502eea nt!KiTrap0E+0x180

    805512b0 80502e2e 898276b8 898276c0 00000102 nt!KiUnlinkThread+0xc

    805512c4 80503025 00000000 805512e0 00000000 nt!KiUnwaitThread+0x12

    805512f0 8050218a be1fb0f9 000000bc 80551418 nt!KiWaitTest+0xab

    805513fc 80502377 8055c0c0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x7a

    80551428 80545f9f 8055c4c0 00000000 0003aabb nt!KiTimerExpiration+0xb1

    80551440 8055be60 ffdffc50 00000000 8055be60 nt!KiRetireDpcList+0x61

    80551450 80545e84 00000000 0000000e 00000000 nt!KiIdleThread0

    80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nt!KiUnlinkThread+c

    80502dcc 8916 mov dword ptr [esi],edx


    SYMBOL_STACK_INDEX: 1


    SYMBOL_NAME: nt!KiUnlinkThread+c


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nt


    IMAGE_NAME: ntkrpamp.exe


    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f


    FAILURE_BUCKET_ID: 0xA_nt!KiUnlinkThread+c


    BUCKET_ID: 0xA_nt!KiUnlinkThread+c


    Followup: MachineOwner


    -------------------------------------------------------------------



    Loading Dump File [C:\WINDOWS\Minidump\Mini082117-03.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Mon Aug 21 12:53:22.414 2017 (UTC + 2:00)

    System Uptime: 0 days 1:45:59.461

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ....

    Loading User Symbols

    Loading unloaded module list

    ..................


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {0, 2, 8, 0}


    Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+180 )


    Followup: MachineOwner

    ---------



    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: 00000000, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000008, value 0 = read operation, 1 = write operation

    Arg4: 00000000, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: 00000000


    CURRENT_IRQL: 2


    FAULTING_IP:

    +43e2faf0177dfc0

    00000000 ?? ???


    CUSTOMER_CRASH_COUNT: 3


    DEFAULT_BUCKET_ID: DRIVER_FAULT


    BUGCHECK_STR: 0xD1


    TRAP_FRAME: b84dbcb8 -- (.trap 0xffffffffb84dbcb8)

    ErrCode = 00000010

    eax=b8348cd0 ebx=b8348000 ecx=00000000 edx=8ab3fa9c esi=b83489c0 edi=8055c0c0

    eip=00000000 esp=b84dbd2c ebp=b8348980 iopl=0 nv up ei pl zr na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

    00000000 ?? ???

    Resetting default scope


    LAST_CONTROL_TRANSFER: from 00000000 to 8054480c


    FAILED_INSTRUCTION_ADDRESS:

    +43e2faf0177dfc0

    00000000 ?? ???


    STACK_TEXT:

    b84dbcb8 00000000 badb0d00 8ab3fa9c badb0d00 nt!KiTrap0E+0x180

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    b84dbd28 80545f9f 8ab3fa9c 00000000 00000000 0x0

    b84dbd50 80545e84 00000000 0000000e e1016c88 nt!KiRetireDpcList+0x61

    b84dbd54 00000000 0000000e e1016c88 e17e9668 nt!KiIdleLoop+0x28



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nt!KiTrap0E+180

    8054480c f7457000000200 test dword ptr [ebp+70h],20000h


    SYMBOL_STACK_INDEX: 0


    SYMBOL_NAME: nt!KiTrap0E+180


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nt


    IMAGE_NAME: ntkrpamp.exe


    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f


    FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180


    BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180


    Followup: MachineOwner

    ------------------------------------------------------------------------



    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 14:03:20.046 2017 (UTC + 2:00)

    System Uptime: 0 days 0:26:24.207

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ....

    Loading User Symbols

    Loading unloaded module list

    .............


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {80000914, 7, 0, b7f0c6c4}


    Probably caused by : atapi.sys ( atapi!AtapiInterrupt+14 )


    Followup: MachineOwner

    ---------



    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: 80000914, memory referenced

    Arg2: 00000007, IRQL

    Arg3: 00000000, value 0 = read operation, 1 = write operation

    Arg4: b7f0c6c4, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: 80000914


    CURRENT_IRQL: 7


    FAULTING_IP:

    atapi!AtapiInterrupt+14

    b7f0c6c4 8a8315090000 mov al,byte ptr [ebx+915h]


    CUSTOMER_CRASH_COUNT: 1


    DEFAULT_BUCKET_ID: DRIVER_FAULT


    BUGCHECK_STR: 0xD1


    TRAP_FRAME: b84dbbe8 -- (.trap 0xffffffffb84dbbe8)

    ErrCode = 00000000

    eax=8aff5030 ebx=7fffffff ecx=00000007 edx=0000d407 esi=8aff50e8 edi=8afb3b80

    eip=b7f0c6c4 esp=b84dbc5c ebp=b84dbc78 iopl=0 nv up ei pl zr na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

    atapi!AtapiInterrupt+0x14:

    b7f0c6c4 8a8315090000 mov al,byte ptr [ebx+915h] ds:0023:80000914=??

    Resetting default scope


    LAST_CONTROL_TRANSFER: from b7f0c6c4 to 8054480c


    STACK_TEXT:

    b84dbbe8 b7f0c6c4 badb0d00 0000d407 00000000 nt!KiTrap0E+0x180

    b84dbc78 b7f0f696 7fffffff 8afb3b7c 8afe6b84 atapi!AtapiInterrupt+0x14

    b84dbc8c 805455fc 8afb3b80 8aff4030 804ffbdc atapi!IdePortInterrupt+0x18

    b84dbca4 8054559c 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch2ndLvl+0x44

    b84dbca4 00000000 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch+0x1c



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    atapi!AtapiInterrupt+14

    b7f0c6c4 8a8315090000 mov al,byte ptr [ebx+915h]


    SYMBOL_STACK_INDEX: 1


    SYMBOL_NAME: atapi!AtapiInterrupt+14


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: atapi


    IMAGE_NAME: atapi.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 4802539d


    FAILURE_BUCKET_ID: 0xD1_atapi!AtapiInterrupt+14


    BUCKET_ID: 0xD1_atapi!AtapiInterrupt+14


    Followup: MachineOwner

    ------------------------------------------------------------------------


    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-02.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 15:24:09.515 2017 (UTC + 2:00)

    System Uptime: 0 days 0:49:44.256

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ....

    Loading User Symbols

    Loading unloaded module list

    ................


    Use !analyze -v to get detailed debugging information.


    BugCheck A, {8a0, 1e, 1, 80540b90}


    Unable to load image \SystemRoot\system32\DRIVERS\NVNRM.SYS, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for NVNRM.SYS

    *** ERROR: Module load completed but symbols could not be loaded for NVNRM.SYS

    Unable to load image \SystemRoot\system32\DRIVERS\AmdK8.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for AmdK8.sys

    *** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys

    Probably caused by : NVNRM.SYS ( NVNRM+3b18e )


    Followup: MachineOwner

    ---------



    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: 000008a0, memory referenced

    Arg2: 0000001e, IRQL

    Arg3: 00000001, 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: 80540b90, address which referenced memory


    Debugging Details:

    ------------------



    WRITE_ADDRESS: 000008a0


    CURRENT_IRQL: 1e


    FAULTING_IP:

    nt!KiAcquireSpinLock+0

    80540b90 f00fba2900 lock bts dword ptr [ecx],0


    CUSTOMER_CRASH_COUNT: 2


    DEFAULT_BUCKET_ID: DRIVER_FAULT


    BUGCHECK_STR: 0xA


    TRAP_FRAME: b84dbbd8 -- (.trap 0xffffffffb84dbbd8)

    ErrCode = 00000002

    eax=00000050 ebx=00000030 ecx=000008a0 edx=0000001f esi=00000000 edi=8afff394

    eip=80540b90 esp=b84dbc4c ebp=b84dbc64 iopl=0 nv up ei pl nz na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206

    nt!KiAcquireSpinLock:

    80540b90 f00fba2900 lock bts dword ptr [ecx],0 ds:0023:000008a0=????????

    Resetting default scope


    LAST_CONTROL_TRANSFER: from 80540b90 to 8054480c


    STACK_TEXT:

    b84dbbd8 80540b90 badb0d00 0000001f b84dbc20 nt!KiTrap0E+0x180

    b84dbc48 804fb857 8adfb3f4 8adfb288 b7aad2d8 nt!KiAcquireSpinLock

    b84dbc64 b7a6618e 000008a0 00000000 00000000 nt!KeInsertQueueDpc+0x47

    WARNING: Stack unwind information not available. Following frames may be wrong.

    b84dbc8c 805455fc 8ab86578 8ad99958 8a900800 NVNRM+0x3b18e

    b84dbcb0 805455a9 b7aad202 00000183 b84dbd50 nt!KiChainedDispatch2ndLvl+0x44

    b84dbcb0 b814b552 b7aad202 00000183 b84dbd50 nt!KiChainedDispatch+0x29

    b84dbd30 b8348c70 805288c1 b8348000 8055c0c0 AmdK8+0x3552

    b84dbd50 80545e6c 00000000 0000000e 00000000 0xb8348c70

    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    NVNRM+3b18e

    b7a6618e ?? ???


    SYMBOL_STACK_INDEX: 3


    SYMBOL_NAME: NVNRM+3b18e


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: NVNRM


    IMAGE_NAME: NVNRM.SYS


    DEBUG_FLR_IMAGE_TIMESTAMP: 0


    FAILURE_BUCKET_ID: 0xA_NVNRM+3b18e


    BUCKET_ID: 0xA_NVNRM+3b18e


    Followup: MachineOwner

    -------------------------------------------------------------------------


    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-03.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 16:26:26.031 2017 (UTC + 2:00)

    System Uptime: 0 days 1:00:59.771

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ....

    Loading User Symbols

    Loading unloaded module list

    ................


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {0, 2, 8, 0}


    Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+180 )


    Followup: MachineOwner

    ---------



    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: 00000000, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000008, value 0 = read operation, 1 = write operation

    Arg4: 00000000, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: 00000000


    CURRENT_IRQL: 2


    FAULTING_IP:

    +43e2faf0178dfc0

    00000000 ?? ???


    CUSTOMER_CRASH_COUNT: 3


    DEFAULT_BUCKET_ID: DRIVER_FAULT


    BUGCHECK_STR: 0xD1


    TRAP_FRAME: b84dbcb8 -- (.trap 0xffffffffb84dbcb8)

    ErrCode = 00000010

    eax=b8348cd0 ebx=b8348000 ecx=00000000 edx=8af677ac esi=b83489c0 edi=8055c0c0

    eip=00000000 esp=b84dbd2c ebp=b8348980 iopl=0 nv up ei pl zr na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

    00000000 ?? ???

    Resetting default scope


    LAST_CONTROL_TRANSFER: from 00000000 to 8054480c


    FAILED_INSTRUCTION_ADDRESS:

    +43e2faf0178dfc0

    00000000 ?? ???


    STACK_TEXT:

    b84dbcb8 00000000 badb0d00 8af677ac badb0d00 nt!KiTrap0E+0x180

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    b84dbd28 80545f9f 8af677ac 00000000 00000000 0x0

    b84dbd50 80545e84 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61

    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nt!KiTrap0E+180

    8054480c f7457000000200 test dword ptr [ebp+70h],20000h


    SYMBOL_STACK_INDEX: 0


    SYMBOL_NAME: nt!KiTrap0E+180


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nt


    IMAGE_NAME: ntkrpamp.exe


    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f


    FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180


    BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180


    Followup: MachineOwner

    -------------------------------------------------------------------------



    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-04.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 16:49:58.609 2017 (UTC + 2:00)

    System Uptime: 0 days 0:22:47.232

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ....

    Loading User Symbols

    Loading unloaded module list

    .............


    Use !analyze -v to get detailed debugging information.


    BugCheck A, {0, 7, 0, 806eda02}


    Probably caused by : hardware ( atapi!IdePortInterrupt+18 )


    Followup: MachineOwner

    ---------



    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: 00000000, memory referenced

    Arg2: 00000007, 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: 806eda02, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: 00000000


    CURRENT_IRQL: 7


    FAULTING_IP:

    hal!InbvDisplayString+4

    806eda02 6e outs dx,byte ptr [esi]


    CUSTOMER_CRASH_COUNT: 4


    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT


    BUGCHECK_STR: 0xA


    TRAP_FRAME: b84dbbd8 -- (.trap 0xffffffffb84dbbd8)

    ErrCode = 00000000

    eax=000000ff ebx=8afde370 ecx=00000000 edx=0000c88a esi=00000000 edi=8afdec68

    eip=806eda02 esp=b84dbc4c ebp=b84dbc78 iopl=0 nv up ei pl nz na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206

    hal!InbvDisplayString+0x4:

    806eda02 6e outs dx,byte ptr [esi] ds:0023:00000000=??

    Resetting default scope


    MISALIGNED_IP:

    hal!InbvDisplayString+4

    806eda02 6e outs dx,byte ptr [esi]


    LAST_CONTROL_TRANSFER: from 806eda02 to 8054480c


    STACK_TEXT:

    b84dbbd8 806eda02 badb0d00 0000c88a 8a96b2f8 nt!KiTrap0E+0x180

    b84dbc78 b7f0f696 01fde370 8af93e14 8aff5e1c hal!InbvDisplayString+0x4

    b84dbc8c 805455fc 8af93e18 8afde030 804ffbdc atapi!IdePortInterrupt+0x18

    b84dbca4 8054559c 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch2ndLvl+0x44

    b84dbca4 00000000 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch+0x1c



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    atapi!IdePortInterrupt+18

    b7f0f696 f6862801000004 test byte ptr [esi+128h],4


    SYMBOL_STACK_INDEX: 2


    SYMBOL_NAME: atapi!IdePortInterrupt+18


    FOLLOWUP_NAME: MachineOwner


    IMAGE_NAME: hardware


    DEBUG_FLR_IMAGE_TIMESTAMP: 0


    MODULE_NAME: hardware


    FAILURE_BUCKET_ID: IP_MISALIGNED


    BUCKET_ID: IP_MISALIGNED


    Followup: MachineOwner

    -------------------------------------------------------------------------


    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-05.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 17:59:38.687 2017 (UTC + 2:00)

    System Uptime: 0 days 1:08:16.427

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ..

    Loading User Symbols

    Loading unloaded module list

    ................


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {31, 9, 0, b830fc9f}


    Unable to load image \SystemRoot\system32\DRIVERS\AmdK8.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for AmdK8.sys

    *** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys

    Probably caused by : i8042prt.sys ( i8042prt!I8042MouseInterruptService+f )


    Followup: MachineOwner

    ---------



    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: 00000031, memory referenced

    Arg2: 00000009, IRQL

    Arg3: 00000000, value 0 = read operation, 1 = write operation

    Arg4: b830fc9f, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: 00000031


    CURRENT_IRQL: 9


    FAULTING_IP:

    i8042prt!I8042MouseInterruptService+f

    b830fc9f 837e3001 cmp dword ptr [esi+30h],1


    CUSTOMER_CRASH_COUNT: 5


    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT


    BUGCHECK_STR: 0xD1


    TRAP_FRAME: b84dbc10 -- (.trap 0xffffffffb84dbc10)

    ErrCode = 00000000

    eax=8af6d7fc ebx=b84dbd50 ecx=00000002 edx=00000003 esi=00000001 edi=8ae02270

    eip=b830fc9f esp=b84dbc84 ebp=b84dbc9c iopl=0 nv up ei ng nz na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286

    i8042prt!I8042MouseInterruptService+0xf:

    b830fc9f 837e3001 cmp dword ptr [esi+30h],1 ds:0023:00000031=????????

    Resetting default scope


    LAST_CONTROL_TRANSFER: from b830fc9f to 8054480c


    STACK_TEXT:

    b84dbc10 b830fc9f badb0d00 00000003 b80e9018 nt!KiTrap0E+0x180

    b84dbc9c 805457c5 8ae02270 8af6d670 01010009 i8042prt!I8042MouseInterruptService+0xf

    b84dbc9c b82fb552 8ae02270 8af6d670 01010009 nt!KiInterruptDispatch+0x45

    WARNING: Stack unwind information not available. Following frames may be wrong.

    b84dbd30 b8348c70 805288c1 b8348000 8055c0c0 AmdK8+0x3552

    b84dbd50 80545e6c 00000000 0000000e 00000000 0xb8348c70

    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    i8042prt!I8042MouseInterruptService+f

    b830fc9f 837e3001 cmp dword ptr [esi+30h],1


    SYMBOL_STACK_INDEX: 1


    SYMBOL_NAME: i8042prt!I8042MouseInterruptService+f


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: i8042prt


    IMAGE_NAME: i8042prt.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 48025c67


    FAILURE_BUCKET_ID: 0xD1_i8042prt!I8042MouseInterruptService+f


    BUCKET_ID: 0xD1_i8042prt!I8042MouseInterruptService+f


    Followup: MachineOwner

    -------------------------------------------------------------------------



    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-06.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 20:41:55.609 2017 (UTC + 2:00)

    System Uptime: 0 days 2:39:40.357

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ...

    Loading User Symbols

    Loading unloaded module list

    .............


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {ac, 5, 0, b7f0f68b}


    Unable to load image \SystemRoot\system32\DRIVERS\AmdK8.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for AmdK8.sys

    *** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys

    Probably caused by : atapi.sys ( atapi!IdePortInterrupt+d )


    Followup: MachineOwner

    ---------



    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: 000000ac, memory referenced

    Arg2: 00000005, IRQL

    Arg3: 00000000, value 0 = read operation, 1 = write operation

    Arg4: b7f0f68b, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: 000000ac


    CURRENT_IRQL: 5


    FAULTING_IP:

    atapi!IdePortInterrupt+d

    b7f0f68b ffb6ac000000 push dword ptr [esi+0ACh]


    CUSTOMER_CRASH_COUNT: 6


    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT


    BUGCHECK_STR: 0xD1


    TRAP_FRAME: b84dbc20 -- (.trap 0xffffffffb84dbc20)

    ErrCode = 00000000

    eax=8aff5730 ebx=b84dbd50 ecx=00000002 edx=00000007 esi=00000000 edi=8aff6b08

    eip=b7f0f68b esp=b84dbc94 ebp=b84dbc9c iopl=0 nv up ei pl zr na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

    atapi!IdePortInterrupt+0xd:

    b7f0f68b ffb6ac000000 push dword ptr [esi+0ACh] ds:0023:000000ac=????????

    Resetting default scope


    LAST_CONTROL_TRANSFER: from b7f0f68b to 8054480c


    STACK_TEXT:

    b84dbc20 b7f0f68b badb0d00 00000007 b80e86c9 nt!KiTrap0E+0x180

    b84dbc9c 805457c5 8aff6b08 8aff5030 01010005 atapi!IdePortInterrupt+0xd

    b84dbc9c b82fb552 8aff6b08 8aff5030 01010005 nt!KiInterruptDispatch+0x45

    WARNING: Stack unwind information not available. Following frames may be wrong.

    b84dbd30 b8348c70 805288c1 b8348000 8055c0c0 AmdK8+0x3552

    b84dbd50 80545e6c 00000000 0000000e 00000000 0xb8348c70

    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    atapi!IdePortInterrupt+d

    b7f0f68b ffb6ac000000 push dword ptr [esi+0ACh]


    SYMBOL_STACK_INDEX: 1


    SYMBOL_NAME: atapi!IdePortInterrupt+d


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: atapi


    IMAGE_NAME: atapi.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 4802539d


    FAILURE_BUCKET_ID: 0xD1_atapi!IdePortInterrupt+d


    BUCKET_ID: 0xD1_atapi!IdePortInterrupt+d


    Followup: MachineOwner

    ---------------------------------------------------------------------------



    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-07.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 20:45:10.578 2017 (UTC + 2:00)

    System Uptime: 0 days 0:00:54.191

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ........

    Loading User Symbols

    Loading unloaded module list

    ......


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {98000000, 2, 1, 8acae857}


    Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+180 )


    Followup: MachineOwner

    ---------



    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: 98000000, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000001, value 0 = read operation, 1 = write operation

    Arg4: 8acae857, address which referenced memory


    Debugging Details:

    ------------------



    WRITE_ADDRESS: 98000000


    CURRENT_IRQL: 2


    FAULTING_IP:

    +43e2faf0177dfc0

    8acae857 ?? ???


    CUSTOMER_CRASH_COUNT: 7


    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT


    BUGCHECK_STR: 0xD1


    TRAP_FRAME: b84dbcb8 -- (.trap 0xffffffffb84dbcb8)

    ErrCode = 00000002

    eax=b8348c15 ebx=b8348000 ecx=8acae850 edx=8acae7b4 esi=b83489c0 edi=8055c0c0

    eip=8acae857 esp=b84dbd2c ebp=b8348980 iopl=0 nv up ei pl nz na po nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202

    8acae857 ?? ???

    Resetting default scope


    LAST_CONTROL_TRANSFER: from 8acae857 to 8054480c


    STACK_TEXT:

    b84dbcb8 8acae857 badb0d00 8acae7b4 badb0d00 nt!KiTrap0E+0x180

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    b84dbd28 80545f9f 8acae7b4 00000022 00000000 0x8acae857

    b84dbd50 80545e84 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61

    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nt!KiTrap0E+180

    8054480c f7457000000200 test dword ptr [ebp+70h],20000h


    SYMBOL_STACK_INDEX: 0


    SYMBOL_NAME: nt!KiTrap0E+180


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nt


    IMAGE_NAME: ntkrpamp.exe


    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f


    FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+180


    BUCKET_ID: 0xD1_nt!KiTrap0E+180


    Followup: MachineOwner

    ---------------------------------------------------------------------------


    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-08.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 20:47:23.750 2017 (UTC + 2:00)

    System Uptime: 0 days 0:01:18.488

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .........

    Loading User Symbols

    Loading unloaded module list

    ......


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {0, 2, 8, 0}


    Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+180 )


    Followup: MachineOwner

    ---------



    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: 00000000, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000008, value 0 = read operation, 1 = write operation

    Arg4: 00000000, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: 00000000


    CURRENT_IRQL: 2


    FAULTING_IP:

    +43e2faf0178dfc0

    00000000 ?? ???


    CUSTOMER_CRASH_COUNT: 8


    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT


    BUGCHECK_STR: 0xD1


    TRAP_FRAME: b84dbcb8 -- (.trap 0xffffffffb84dbcb8)

    ErrCode = 00000010

    eax=b8348cd0 ebx=b8348000 ecx=00000000 edx=8aaffebc esi=b83489c0 edi=8055c0c0

    eip=00000000 esp=b84dbd2c ebp=b8348980 iopl=0 nv up ei pl zr na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

    00000000 ?? ???

    Resetting default scope


    LAST_CONTROL_TRANSFER: from 00000000 to 8054480c


    FAILED_INSTRUCTION_ADDRESS:

    +43e2faf0178dfc0

    00000000 ?? ???


    STACK_TEXT:

    b84dbcb8 00000000 badb0d00 8aaffebc badb0d00 nt!KiTrap0E+0x180

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    b84dbd28 80545f9f 8aaffebc 00000000 00000000 0x0

    b84dbd50 80545e84 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61

    b84dbd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nt!KiTrap0E+180

    8054480c f7457000000200 test dword ptr [ebp+70h],20000h


    SYMBOL_STACK_INDEX: 0


    SYMBOL_NAME: nt!KiTrap0E+180


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nt


    IMAGE_NAME: ntkrpamp.exe


    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f


    FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180


    BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+180


    Followup: MachineOwner

    --------------------------------------------------------------------------


    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-09.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 22:45:52.062 2017 (UTC + 2:00)

    System Uptime: 0 days 0:41:20.805

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .....

    Loading User Symbols

    Loading unloaded module list

    ...............


    Use !analyze -v to get detailed debugging information.


    BugCheck A, {b86b9f44, 7, 0, 8052ba14}


    *** WARNING: Unable to verify timestamp for nvgts.sys

    *** ERROR: Module load completed but symbols could not be loaded for nvgts.sys

    Probably caused by : nvgts.sys ( nvgts+36e7 )


    Followup: MachineOwner

    ---------



    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: b86b9f44, memory referenced

    Arg2: 00000007, 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: 8052ba14, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: b86b9f44


    CURRENT_IRQL: 7


    FAULTING_IP:

    nt!READ_REGISTER_ULONG+4

    8052ba14 8b02 mov eax,dword ptr [edx]


    CUSTOMER_CRASH_COUNT: 9


    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT


    BUGCHECK_STR: 0xA


    TRAP_FRAME: b84dbaac -- (.trap 0xffffffffb84dbaac)

    ErrCode = 00000000

    eax=b7f04160 ebx=b84cb034 ecx=00000078 edx=b86b9f44 esi=8afe1004 edi=b86aa000

    eip=8052ba14 esp=b84dbb20 ebp=b84dbb28 iopl=0 nv up ei ng nz na pe nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286

    nt!READ_REGISTER_ULONG+0x4:

    8052ba14 8b02 mov eax,dword ptr [edx] ds:0023:b86b9f44=????????

    Resetting default scope


    LAST_CONTROL_TRANSFER: from 8052ba14 to 8054480c


    STACK_TEXT:

    b84dbaac 8052ba14 badb0d00 b86b9f44 8ac4f008 nt!KiTrap0E+0x180

    b84dbb1c b7ee26e7 b86b9f44 b84dbbec b7eecf23 nt!READ_REGISTER_ULONG+0x4

    WARNING: Stack unwind information not available. Following frames may be wrong.

    b84dbb28 b7eecf23 8afe1004 b86b9f44 00000000 nvgts+0x36e7

    b84dbbec b7eecf9a 8afe1004 00000006 b84dbc28 nvgts+0xdf23

    b84dbbfc b7eee277 8afe1004 8afe1004 8b032a38 nvgts+0xdf9a

    b84dbc28 b7efb041 8afe1004 8b032af0 8b030e1c nvgts+0xf277

    b84dbc68 b7ee96f7 8afe1004 b84dbc8c b7ec9dd2 nvgts+0x1c041

    b84dbc74 b7ec9dd2 8afe1004 8b030e1c 8b030e18 nvgts+0xa6f7

    b84dbc8c 805455fc 8b030e18 8b032a38 b647f2d8 SCSIPORT!ScsiPortInterrupt+0x2a

    b84dbca4 8054559c 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch2ndLvl+0x44

    b84dbca4 00000000 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch+0x1c



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nvgts+36e7

    b7ee26e7 ?? ???


    SYMBOL_STACK_INDEX: 2


    SYMBOL_NAME: nvgts+36e7


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nvgts


    IMAGE_NAME: nvgts.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 4a4aab25


    FAILURE_BUCKET_ID: 0xA_nvgts+36e7


    BUCKET_ID: 0xA_nvgts+36e7


    Followup: MachineOwner

    --------------------------------------------------------------------------


    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-10.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 22:51:54.906 2017 (UTC + 2:00)

    System Uptime: 0 days 0:01:49.507

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ...........

    Loading User Symbols

    Loading unloaded module list

    ......

    *** WARNING: Unable to verify timestamp for nvgts.sys

    *** ERROR: Module load completed but symbols could not be loaded for nvgts.sys


    Use !analyze -v to get detailed debugging information.


    BugCheck 1000007F, {8, b8348d70, 0, 0}


    Probably caused by : nvgts.sys ( nvgts+e047 )


    Followup: MachineOwner

    ---------



    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)

    This means a trap occurred in kernel mode, and it's a trap of a kind

    that the kernel isn't allowed to have/catch (bound trap) or that

    is always instant death (double fault). The first number in the

    bugcheck params is the number of the trap (8 = double fault, etc)

    Consult an Intel x86 family manual to learn more about what these

    traps are. Here is a *portion* of those codes:

    If kv shows a taskGate

    use .tss on the part before the colon, then kv.

    Else if kv shows a trapframe

    use .trap on that value

    Else

    .trap on the appropriate frame will show where the trap was taken

    (on x86, this will be the ebp that goes with the procedure KiTrap)

    Endif

    kb will then show the corrected stack.

    Arguments:

    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT

    Arg2: b8348d70

    Arg3: 00000000

    Arg4: 00000000


    Debugging Details:

    ------------------



    BUGCHECK_STR: 0x7f_8


    CUSTOMER_CRASH_COUNT: 10


    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT


    LAST_CONTROL_TRANSFER: from b84dbc28 to b7eed047


    STACK_TEXT:

    WARNING: Stack unwind information not available. Following frames may be wrong.

    b84dbc18 b84dbc28 b7eed090 8afa9004 b84dbc68 nvgts+0xe047

    b84dbc1c b7eed090 8afa9004 b84dbc68 b7efb04f 0xb84dbc28

    b84dbc28 b7efb04f 8afa9004 8af8faf0 8af8de1c nvgts+0xe090

    b84dbc68 b7ee96f7 8afa9004 b84dbc8c b7ec9dd2 nvgts+0x1c04f

    b84dbc74 b7ec9dd2 8afa9004 8af8de1c 8af8de18 nvgts+0xa6f7

    b84dbc8c 805455fc 8af8de18 8af8fa38 8a85ea40 SCSIPORT!ScsiPortInterrupt+0x2a

    b84dbca4 8054559c 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch2ndLvl+0x44

    b84dbca4 00000000 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch+0x1c



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nvgts+e047

    b7eed047 ?? ???


    SYMBOL_STACK_INDEX: 0


    SYMBOL_NAME: nvgts+e047


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nvgts


    IMAGE_NAME: nvgts.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 4a4aab25


    FAILURE_BUCKET_ID: 0x7f_8_nvgts+e047


    BUCKET_ID: 0x7f_8_nvgts+e047


    Followup: MachineOwner

    --------------------------------------------------------------------------


    Loading Dump File [C:\WINDOWS\Minidump\Mini082417-11.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Thu Aug 24 22:54:49.234 2017 (UTC + 2:00)

    System Uptime: 0 days 0:01:14.972

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .....

    Loading User Symbols

    Loading unloaded module list

    ............


    Use !analyze -v to get detailed debugging information.


    BugCheck A, {b86a9fff, 7, 0, 8052ba14}


    *** WARNING: Unable to verify timestamp for nvgts.sys

    *** ERROR: Module load completed but symbols could not be loaded for nvgts.sys

    Probably caused by : nvgts.sys ( nvgts+36e7 )


    Followup: MachineOwner

    ---------



    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: b86a9fff, memory referenced

    Arg2: 00000007, 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: 8052ba14, address which referenced memory


    Debugging Details:

    ------------------



    READ_ADDRESS: b86a9fff


    CURRENT_IRQL: 7


    FAULTING_IP:

    nt!READ_REGISTER_ULONG+4

    8052ba14 8b02 mov eax,dword ptr [edx]


    CUSTOMER_CRASH_COUNT: 11


    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT


    BUGCHECK_STR: 0xA


    TRAP_FRAME: b84dbaac -- (.trap 0xffffffffb84dbaac)

    ErrCode = 00000000

    eax=b7f04160 ebx=b84cb034 ecx=00000078 edx=b86a9fff esi=8afe2004 edi=b86aa000

    eip=8052ba14 esp=b84dbb20 ebp=b84dbb28 iopl=0 nv up ei ng nz na pe cy

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287

    nt!READ_REGISTER_ULONG+0x4:

    8052ba14 8b02 mov eax,dword ptr [edx] ds:0023:b86a9fff=????????

    Resetting default scope


    LAST_CONTROL_TRANSFER: from 8052ba14 to 8054480c


    STACK_TEXT:

    b84dbaac 8052ba14 badb0d00 b86a9fff 8ac72008 nt!KiTrap0E+0x180

    b84dbb1c b7ee26e7 b86a9fff b84dbbec b7eecf23 nt!READ_REGISTER_ULONG+0x4

    WARNING: Stack unwind information not available. Following frames may be wrong.

    b84dbb28 b7eecf23 8afe2004 b86a9fff 00000000 nvgts+0x36e7

    b84dbbec b7eecf9a 8afe2004 00000006 b84dbc28 nvgts+0xdf23

    b84dbbfc b7eee277 8afe2004 8afe2004 8afada38 nvgts+0xdf9a

    b84dbc28 b7efb041 8afe2004 8afadaf0 8b034e1c nvgts+0xf277

    b84dbc68 b7ee96f7 8afe2004 b84dbc8c b7ec9dd2 nvgts+0x1c041

    b84dbc74 b7ec9dd2 8afe2004 8b034e1c 8b034e18 nvgts+0xa6f7

    b84dbc8c 805455fc 8b034e18 8afada38 8a84ab40 SCSIPORT!ScsiPortInterrupt+0x2a

    b84dbca4 8054559c 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch2ndLvl+0x44

    b84dbca4 00000000 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch+0x1c



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nvgts+36e7

    b7ee26e7 ?? ???


    SYMBOL_STACK_INDEX: 2


    SYMBOL_NAME: nvgts+36e7


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nvgts


    IMAGE_NAME: nvgts.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 4a4aab25


    FAILURE_BUCKET_ID: 0xA_nvgts+36e7


    BUCKET_ID: 0xA_nvgts+36e7


    Followup: MachineOwner

    ------------------------------------------------------------------------


    Loading Dump File [C:\WINDOWS\Minidump\Mini082517-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available


    WARNING: Whitespace at end of path element

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information


    Executable search path is:

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    Product: WinNt

    Built by: 2600.xpsp_sp3_qfe.130704-0421

    Machine Name:

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

    Debug session time: Fri Aug 25 00:09:28.781 2017 (UTC + 2:00)

    System Uptime: 0 days 0:00:52.523

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .....

    Loading User Symbols

    Loading unloaded module list

    ...........

    *** WARNING: Unable to verify timestamp for nvgts.sys

    ***


    Use !analyze -v to get detailed debugging information.


    BugCheck 1000007F, {8, b8348d70, 0, 0}


    Probably caused by : nvgts.sys ( nvgts+e047 )


    Followup: MachineOwner

    ---------



    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)

    This means a trap occurred in kernel mode, and it's a trap of a kind

    that the kernel isn't allowed to have/catch (bound trap) or that

    is always instant death (double fault). The first number in the

    bugcheck params is the number of the trap (8 = double fault, etc)

    Consult an Intel x86 family manual to learn more about what these

    traps are. Here is a *portion* of those codes:

    If kv shows a taskGate

    use .tss on the part before the colon, then kv.

    Else if kv shows a trapframe

    use .trap on that value

    Else

    .trap on the appropriate frame will show where the trap was taken

    (on x86, this will be the ebp that goes with the procedure KiTrap)

    Endif

    kb will then show the corrected stack.

    Arguments:

    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT

    Arg2: b8348d70

    Arg3: 00000000

    Arg4: 00000000


    Debugging Details:

    ------------------



    BUGCHECK_STR: 0x7f_8


    CUSTOMER_CRASH_COUNT: 1


    DEFAULT_BUCKET_ID: DRIVER_FAULT


    LAST_CONTROL_TRANSFER: from b84dbc28 to b7eed047


    STACK_TEXT:

    WARNING: Stack unwind information not available. Following frames may be wrong.

    b84dbc18 b84dbc28 b7eed090 8afaa004 b84dbc68 nvgts+0xe047

    b84dbc1c b7eed090 8afaa004 b84dbc68 b7efb04f 0xb84dbc28

    b84dbc28 b7efb04f 8afaa004 8af92af0 8afafb84 nvgts+0xe090

    b84dbc68 b7ee96f7 8afaa004 b84dbc8c b7ec9dd2 nvgts+0x1c04f

    b84dbc74 b7ec9dd2 8afaa004 8afafb84 8afafb80 nvgts+0xa6f7

    b84dbc8c 805455fc 8afafb80 8af92a38 8a844400 SCSIPORT!ScsiPortInterrupt+0x2a

    b84dbca4 8054559c 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch2ndLvl+0x44

    b84dbca4 00000000 00000000 b84dbcc0 805455a9 nt!KiChainedDispatch+0x1c



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nvgts+e047

    b7eed047 ?? ???


    SYMBOL_STACK_INDEX: 0


    SYMBOL_NAME: nvgts+e047


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nvgts


    IMAGE_NAME: nvgts.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 4a4aab25


    FAILURE_BUCKET_ID: 0x7f_8_nvgts+e047


    BUCKET_ID: 0x7f_8_nvgts+e047


    Followup: MachineOwner

    --------------------------------------------------------------------------
     
  9. 2017/08/25
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    3,793
    Likes Received:
    145
    Trophy Points:
    843
    Location:
    New Delhi, India
    Computer Experience:
    Experienced but ! en
    If your machine locked up during RAM test, it's most likely culprit. Swapping of RAM is the only sure way of knowing.
     
  10. 2017/08/29
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    5,358
    Likes Received:
    294
    Trophy Points:
    1,093
    Location:
    New Zealand
    Computer Experience:
    intermediate
    What RAM are you using? DDR2 or DDR3. Are they paired sticks?
    I would use the onboard graphics chipset and just 1 stick of RAM and remove any/all peripherals and see how it runs. (run in bare bones state)
    Has the CPU been disturbed at any time?
    Have you tried another PSU of known good quality.
     
  11. 2017/09/03
    Ragefhonor

    Ragefhonor New Member Thread Starter

    Joined:
    2017/08/11
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Computer Experience:
    Very good
    I’m using

    Goodram GR800D264L6/4GDC, GFC008223, DDR2, 2GB, PC2 - 6400 DIMM
    Goodram GR800D264L5/2G , GIG011886, DDR2, 2GB, PC2 - 6400 DIMM

    They are in Dual Channel


    BIOS says: 4096 MB
    Dual-Channel Memory Mode

    DDRII_1 :2048MB/266MHz DDR2_533
    DDRII_2 :2048MB/266MHz DDR2_533

    Tested each stick for 6 hours with Memtest

    Tested also in Dual

    I have removed my 8800 GT and now it’s running at the Onboard GPU

    Readings from GM during test:

    1971 MB/s Single CH normal mode > 2095392
    1876 MB/s Single CH checking avail mem > 2097151


    2390 MB/s Dual CH normal mode > 3668256
    MB/s Dual CH checking avail mem > 3668256
    Error at > 3669808


    2374 MB/s Dual CH normal mode > 3406112 without GPU
    checking avail mem > 3406112
    Error

    I have updated my Motherboard drivers few times but it didn’t help

    Yesterday I have turned of the Cool & Quiet mode in BIOS but it didn’t help

    Now I get BSODs 0A and 7F caused by ntkrnlpa.exe, nv4_mini.sys, nvgts.sys.


    At start I can see that my BIOS counts down and the last Code is 1A

    Connected also a diagnostic board to the MB and have now the code AA on it. I think it should be FF

    Maybe I have some bad caps left. The PC was fixed before because of bad caps. Or maybe cold joints. It was very warm when I used my PC after repair. Yesterday instead of BSOD Windows froze.

    What do you mean disturbed PCU?
    In the Service center they told me my PSU is OK.
     
  12. 2017/09/04
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    14,903
    Likes Received:
    379
    Trophy Points:
    1,093
    Hmm, since the bad caps fiasco was years ago, am I safe to think this board is old? It could just be failing... One other thing... ever checked for malware?
     
  13. 2017/09/07
    Ragefhonor

    Ragefhonor New Member Thread Starter

    Joined:
    2017/08/11
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Computer Experience:
    Very good
    Yes its a bit old. But not very old. I have tested my OS with many programs but i nothing was found. I already thought im infected with WannaCry. But Win Defender, MB, Webroot, AVG, Mcafe found nothing. I have scanned my OS with Combofix and it was not abble to fix the problem. The last thing i did was replacing my drivers with the drivers from 2013. It was stabile for until today. I has a BSOD again. Blue screen viewer thinks that nv4_mini.sys and ntkrnlpa.exe caused the BSOD

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Thu Sep 7 07:13:19.177 2017 (UTC - 4:00)
    System Uptime: 3 days 22:24:33.802
    *******************************************************************************
    * *
    * 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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 80522800, address which referenced memory

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    WRITE_ADDRESS: GetUlongFromAddress: unable to read from 80561f50
    00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiRemovePageByColor+66
    80522800 ff08 dec dword ptr [eax]

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    TRAP_FRAME: a767ab54 -- (.trap 0xffffffffa767ab54)
    ErrCode = 00000002
    eax=00000000 ebx=832bf800 ecx=00018e4a edx=0000000a esi=81eb9018 edi=00000000
    eip=80522800 esp=a767abc8 ebp=a767abe4 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210206
    nt!MiRemovePageByColor+0x66:
    80522800 ff08 dec dword ptr [eax] ds:0023:00000000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 80522800 to 8054480c

    STACK_TEXT:
    a767ab54 80522800 badb0d00 0000000a 8af75000 nt!KiTrap0E+0x180
    a767abe4 80522bde 00000001 00000009 e68befa8 nt!MiRemovePageByColor+0x66
    a767ac00 80514c7d 00000480 00000000 00000000 nt!MiRemoveZeroPage+0xd0
    a767ac18 805164ad 0c4053fc e68befa8 89954710 nt!MiResolveDemandZeroFault+0x123
    a767ac5c 8051662f 00000001 0c4053fc c0062028 nt!MiResolveProtoPteFault+0x1d9
    a767ace0 80520bf0 e68befa8 0c4053fc c0062028 nt!MiDispatchFault+0xf1
    a767ad4c 8054475c 00000001 0c4053fc 00000001 nt!MmAccessFault+0x1118
    a767ad4c 01dc5c2d 00000001 0c4053fc 00000001 nt!KiTrap0E+0xd0
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0831f4a0 00000000 00000000 00000000 00000000 0x1dc5c2d


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiRemovePageByColor+66
    80522800 ff08 dec dword ptr [eax]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MiRemovePageByColor+66

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

    BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

    Followup: MachineOwner
     
  14. 2017/09/07
    Ragefhonor

    Ragefhonor New Member Thread Starter

    Joined:
    2017/08/11
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Computer Experience:
    Very good
    I made a Debug by myself and i can see now that it looks like chrome caused the error this time. Is this correct?

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


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

    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*c:\symbols*Symbol information

    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Thu Sep 7 13:13:19.177 2017 (UTC + 2:00)
    System Uptime: 3 days 22:24:33.802
    Loading Kernel Symbols
    ...............................................................
    ...............................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {0, 2, 1, 80522800}

    Probably caused by : memory_corruption ( nt!MiRemovePageByColor+66 )

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

    0: kd> !analyze -v;r;kv;lmtn
    *******************************************************************************
    * *
    * 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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 80522800, address which referenced memory

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


    WRITE_ADDRESS: 00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiRemovePageByColor+66
    80522800 ff08 dec dword ptr [eax]

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: chrome.exe

    TRAP_FRAME: a767ab54 -- (.trap 0xffffffffa767ab54)
    ErrCode = 00000002
    eax=00000000 ebx=832bf800 ecx=00018e4a edx=0000000a esi=81eb9018 edi=00000000
    eip=80522800 esp=a767abc8 ebp=a767abe4 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210206
    nt!MiRemovePageByColor+0x66:
    80522800 ff08 dec dword ptr [eax] ds:0023:00000000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 80522800 to 8054480c

    STACK_TEXT:
    a767ab54 80522800 badb0d00 0000000a 8af75000 nt!KiTrap0E+0x180
    a767abe4 80522bde 00000001 00000009 e68befa8 nt!MiRemovePageByColor+0x66
    a767ac00 80514c7d 00000480 00000000 00000000 nt!MiRemoveZeroPage+0xd0
    a767ac18 805164ad 0c4053fc e68befa8 89954710 nt!MiResolveDemandZeroFault+0x123
    a767ac5c 8051662f 00000001 0c4053fc c0062028 nt!MiResolveProtoPteFault+0x1d9
    a767ace0 80520bf0 e68befa8 0c4053fc c0062028 nt!MiDispatchFault+0xf1
    a767ad4c 8054475c 00000001 0c4053fc 00000001 nt!MmAccessFault+0x1118
    a767ad4c 01dc5c2d 00000001 0c4053fc 00000001 nt!KiTrap0E+0xd0
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0831f4a0 00000000 00000000 00000000 00000000 0x1dc5c2d


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiRemovePageByColor+66
    80522800 ff08 dec dword ptr [eax]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MiRemovePageByColor+66

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

    BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

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

    eax=ffdff13c ebx=00000002 ecx=00000000 edx=80522800 esi=80522800 edi=00000000
    eip=8054480c esp=a767ab3c ebp=a767ab54 iopl=0 nv up ei ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00200286
    nt!KiTrap0E+0x180:
    8054480c f7457000000200 test dword ptr [ebp+70h],20000h ss:0010:a767abc4=00210206
    ChildEBP RetAddr Args to Child
    a767ab54 80522800 badb0d00 0000000a 8af75000 nt!KiTrap0E+0x180 (FPO: [0,0] TrapFrame @ a767ab54)
    a767abe4 80522bde 00000001 00000009 e68befa8 nt!MiRemovePageByColor+0x66 (FPO: [Non-Fpo])
    a767ac00 80514c7d 00000480 00000000 00000000 nt!MiRemoveZeroPage+0xd0 (FPO: [Non-Fpo])
    a767ac18 805164ad 0c4053fc e68befa8 89954710 nt!MiResolveDemandZeroFault+0x123 (FPO: [Non-Fpo])
    a767ac5c 8051662f 00000001 0c4053fc c0062028 nt!MiResolveProtoPteFault+0x1d9 (FPO: [Non-Fpo])
    a767ace0 80520bf0 e68befa8 0c4053fc c0062028 nt!MiDispatchFault+0xf1 (FPO: [Non-Fpo])
    a767ad4c 8054475c 00000001 0c4053fc 00000001 nt!MmAccessFault+0x1118 (FPO: [Non-Fpo])
    a767ad4c 01dc5c2d 00000001 0c4053fc 00000001 nt!KiTrap0E+0xd0 (FPO: [0,0] TrapFrame @ a767ad64)
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0831f4a0 00000000 00000000 00000000 00000000 0x1dc5c2d
    start end module name
    804d7000 806e5000 nt ntkrpamp.exe Thu Jul 04 04:08:15 2013 (51D4D90F)
    806e5000 80705d00 hal halmacpi.dll Sun Apr 13 20:31:27 2008 (4802517F)
    a842d000 a846de00 HTTP HTTP.sys Tue Oct 20 18:20:15 2009 (4ADDE33F)
    a887e000 a88d5600 srv srv.sys Thu Feb 17 14:18:01 2011 (4D5D2009)
    a89c6000 a89f2180 mrxdav mrxdav.sys Sun Apr 13 20:32:42 2008 (480251CA)
    a8b85000 a8b99480 wdmaud wdmaud.sys Sun Apr 13 21:17:18 2008 (48025C3E)
    a9a7d000 a9aa8000 dump_nvgts dump_nvgts.sys Wed Jul 01 02:17:41 2009 (4A4AAB25)
    a9aa8000 a9ab8200 Udfs Udfs.SYS Sun Apr 13 20:32:35 2008 (480251C3)
    a9ab9000 a9adc180 Fastfat Fastfat.SYS Sun Apr 13 21:14:28 2008 (48025B94)
    a9add000 a9b4c680 mrxsmb mrxsmb.sys Fri Jul 15 15:29:28 2011 (4E2040B8)
    a9b4d000 a9b77e80 rdbss rdbss.sys Sun Apr 13 21:28:38 2008 (48025EE6)
    a9b78000 a9c33000 VBoxDrv VBoxDrv.sys Sat Oct 11 13:47:43 2014 (543918DF)
    a9c33000 a9c52000 VBoxUSBMon VBoxUSBMon.sys Sat Oct 11 13:45:43 2014 (54391867)
    a9c52000 a9c73d00 afd afd.sys Wed Aug 17 15:49:53 2011 (4E4BC701)
    a9c74000 a9c99500 ipnat ipnat.sys Sun Apr 13 20:57:10 2008 (48025786)
    a9c9a000 a9cc1c00 netbt netbt.sys Sun Apr 13 21:20:59 2008 (48025D1B)
    a9cc2000 a9d1a480 tcpip tcpip.sys Fri Jun 20 13:51:09 2008 (485B99AD)
    a9d1b000 a9d2d600 ipsec ipsec.sys Sun Apr 13 21:19:42 2008 (48025CCE)
    a9d7e000 a9da1a80 portcls portcls.sys Sun Apr 13 21:19:40 2008 (48025CCC)
    a9da2000 aa011b80 viahduaa viahduaa.sys Fri Mar 01 05:21:18 2013 (51302CBE)
    aa078000 aa0aac00 NVNRM NVNRM.SYS Wed Jul 01 20:53:21 2009 (4A4BB0A1)
    aa0ab000 aa0bb480 NVENETFD NVENETFD.sys Wed Jul 01 20:53:29 2009 (4A4BB0A9)
    ac63c000 ac699f00 update update.sys Sun Apr 13 20:39:46 2008 (48025372)
    ac69a000 ac6bd000 VBoxNetFlt VBoxNetFlt.sys Sat Oct 11 13:45:42 2014 (54391866)
    ac6bd000 ac6ece80 rdpdr rdpdr.sys Sun Apr 13 20:32:50 2008 (480251D2)
    ac6ed000 ac6fde00 psched psched.sys Sun Apr 13 20:56:36 2008 (48025764)
    ac6fe000 ac714580 ndiswan ndiswan.sys Sun Apr 13 21:20:41 2008 (48025D09)
    ac715000 ac728f00 VIDEOPRT VIDEOPRT.SYS Sun Apr 13 20:44:39 2008 (48025497)
    acafa000 acafcf00 ws2ifsl ws2ifsl.sys Fri Aug 17 22:55:58 2001 (3B7D84DE)
    acb0e000 acb10280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
    acc31000 acc3be80 Fips Fips.SYS Sun Apr 13 20:33:27 2008 (480251F7)
    acc61000 acc69780 netbios netbios.sys Sun Apr 13 20:56:01 2008 (48025741)
    acff7000 acfff700 wanarp wanarp.sys Sun Apr 13 20:57:20 2008 (48025790)
    ad007000 ad015b00 drmk drmk.sys Sun Apr 13 20:45:12 2008 (480254B8)
    ad037000 ad045880 usbhub usbhub.sys Sun Apr 13 20:45:36 2008 (480254D0)
    ad057000 ad061000 NDProxy NDProxy.SYS Wed Nov 27 21:21:05 2013 (52965431)
    ad077000 ad080f00 termdd termdd.sys Sun Apr 13 20:38:36 2008 (4802532C)
    ad087000 ad08f900 msgpc msgpc.sys Sun Apr 13 20:56:32 2008 (48025760)
    ad09d000 ad09dc00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
    ad15b000 ad15ec80 mssmbios mssmbios.sys Sun Apr 13 20:36:45 2008 (480252BD)
    ad173000 ad175900 ndistapi ndistapi.sys Fri Jul 08 16:02:00 2011 (4E170DD8)
    ad1b9000 ad1ba080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
    ad1bb000 ad1bc080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
    ad1bd000 ad1bef00 FNETURPX FNETURPX.SYS Sat Oct 04 04:26:51 2008 (48E6D46B)
    ad1bf000 ad1c0080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
    ada2d000 ada2ef00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
    ada33000 ada34500 USBD USBD.SYS Fri Aug 09 02:55:05 2013 (52043DE9)
    b1340000 b1340d00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)
    b16f6000 b1700200 raspppoe raspppoe.sys Sun Apr 13 20:57:31 2008 (4802579B)
    b27b1000 b27b7500 usbprint usbprint.sys Sun Apr 13 20:47:37 2008 (48025549)
    b27b9000 b27bf200 HIDPARSE HIDPARSE.SYS Wed Jul 03 04:12:52 2013 (51D388A4)
    b3a9d000 b3aa8d00 raspptp raspptp.sys Sun Apr 13 21:19:47 2008 (48025CD3)
    b5358000 b5366d80 sysaudio sysaudio.sys Sun Apr 13 21:15:55 2008 (48025BEB)
    b56df000 b56e3500 watchdog watchdog.sys Sun Apr 13 20:44:59 2008 (480254AB)
    b6292000 b6e9fee0 nv4_mini nv4_mini.sys Thu Jan 31 08:42:13 2013 (510A2055)
    b6ea0000 b6ec2700 ks ks.sys Sun Apr 13 21:16:34 2008 (48025C12)
    b6ec3000 b6eeb000 HDAudBus HDAudBus.sys Thu May 26 17:46:29 2005 (4295EF55)
    b6eeb000 b6f0e300 USBPORT USBPORT.SYS Fri Aug 09 02:55:06 2013 (52043DEA)
    b6f0f000 b6f22980 parport parport.sys Sun Apr 13 20:40:09 2008 (48025389)
    b762d000 b762f900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
    b7631000 b7634900 ndisuio ndisuio.sys Sun Apr 13 20:55:57 2008 (4802573D)
    b7d2a000 b7d2d780 dump_diskdump dump_diskdump.sys Sun Apr 13 20:40:44 2008 (480253AC)
    b7d3e000 b7d41480 ausbmon ausbmon.sys Fri Dec 19 06:26:55 2008 (494B309F)
    b7d42000 b7d45d80 serenum serenum.sys Sun Apr 13 20:40:12 2008 (4802538C)
    b7d4a000 b7d4dd80 rsdrv rsdrv.sys Thu Feb 12 14:01:46 2009 (49941DBA)
    b7d76000 b7d8fc00 Mup Mup.sys Thu Apr 21 15:37:43 2011 (4DB03327)
    b7d90000 b7e1c600 Ntfs Ntfs.sys Sun Apr 13 21:15:49 2008 (48025BE5)
    b7e1d000 b7e2ff00 WudfPf WudfPf.sys Fri Sep 29 03:55:43 2006 (451C7D1F)
    b7e30000 b7e46b00 KSecDD KSecDD.sys Wed Jun 24 13:18:40 2009 (4A420B90)
    b7e47000 b7e73980 NDIS NDIS.SYS Sun Apr 13 21:20:35 2008 (48025D03)
    b7e74000 b7e95000 WRkrn WRkrn.sys Wed Jul 12 22:37:00 2017 (5966886C)
    b7e95000 b7ea6f00 sr sr.sys Sun Apr 13 20:36:50 2008 (480252C2)
    b7ea7000 b7ec6b00 fltmgr fltmgr.sys Sun Apr 13 20:32:58 2008 (480251DA)
    b7ec7000 b7ede880 SCSIPORT SCSIPORT.SYS Sun Apr 13 20:40:29 2008 (4802539D)
    b7edf000 b7f0a000 nvgts nvgts.sys Wed Jul 01 02:17:41 2009 (4A4AAB25)
    b7f0a000 b7f21900 atapi atapi.sys Sun Apr 13 20:40:29 2008 (4802539D)
    b7f22000 b7f47900 dmio dmio.sys Sun Apr 13 20:44:45 2008 (4802549D)
    b7f48000 b7f66a80 ftdisk ftdisk.sys Fri Aug 17 22:52:41 2001 (3B7D8419)
    b7f67000 b7f77c00 pci pci.sys Sun Apr 13 20:36:43 2008 (480252BB)
    b7f78000 b7fa6080 ACPI ACPI.sys Sun Apr 13 20:36:33 2008 (480252B1)
    b80a8000 b80b1300 isapnp isapnp.sys Sun Apr 13 20:36:40 2008 (480252B8)
    b80b8000 b80c2580 MountMgr MountMgr.sys Sun Apr 13 20:39:45 2008 (48025371)
    b80c8000 b80d4e80 VolSnap VolSnap.sys Sun Apr 13 20:41:00 2008 (480253BC)
    b80d8000 b80e0e00 disk disk.sys Sun Apr 13 20:40:46 2008 (480253AE)
    b80e8000 b80f4180 CLASSPNP CLASSPNP.SYS Sun Apr 13 21:16:21 2008 (48025C05)
    b81c8000 b81d8000 AmdK8 AmdK8.sys Sun Jul 02 07:39:38 2006 (44A75C1A)
    b81d8000 b81e7f00 serial serial.sys Sun Apr 13 21:15:44 2008 (48025BE0)
    b81e8000 b81f2b00 eusbmon eusbmon.sys Fri Oct 18 12:54:00 2013 (52611348)
    b81f8000 b8202480 imapi imapi.sys Sun Apr 13 20:40:57 2008 (480253B9)
    b8208000 b8217600 cdrom cdrom.sys Sun Apr 13 20:40:45 2008 (480253AD)
    b8218000 b8226600 redbook redbook.sys Sun Apr 13 20:40:27 2008 (4802539B)
    b8288000 b8295000 i8042prt i8042prt.sys Sun Apr 13 21:17:59 2008 (48025C67)
    b82a8000 b82b4880 rasl2tp rasl2tp.sys Sun Apr 13 21:19:43 2008 (48025CCF)
    b8328000 b832e180 PCIIDEX PCIIDEX.SYS Sun Apr 13 20:40:29 2008 (4802539D)
    b8330000 b8334d00 PartMgr PartMgr.sys Sun Apr 13 20:40:48 2008 (480253B0)
    b8338000 b833ca80 TDI TDI.SYS Sun Apr 13 21:00:04 2008 (48025834)
    b8340000 b8344280 speedfan speedfan.sys Sat Dec 29 21:59:33 2012 (50DF59B5)
    b8390000 b8394600 nblocker nblocker.sys Sun Aug 02 02:53:09 2009 (4A74E375)
    b83a8000 b83af000 AsrAppCharger AsrAppCharger.sys Fri Jun 11 08:37:02 2010 (4C11D98E)
    b83b0000 b83b6b00 ULCDRHlp ULCDRHlp.sys Wed Dec 22 21:47:09 2004 (41C9DD4D)
    b83b8000 b83c0000 nvnetbus nvnetbus.sys Wed Jul 01 20:53:32 2009 (4A4BB0AC)
    b83e8000 b83ec180 HWiNFO32 HWiNFO32.SYS Tue Mar 31 11:51:39 2015 (551A6E2B)
    b83f0000 b83f4580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
    b8408000 b840c080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
    b8438000 b843ca80 Msfs Msfs.SYS Sun Apr 13 20:32:38 2008 (480251C6)
    b8440000 b8447000 npf npf.sys Fri Mar 01 02:28:14 2013 (5130042E)
    b8448000 b844d200 vga vga.sys Sun Apr 13 20:44:40 2008 (48025498)
    b8478000 b847f880 Npfs Npfs.SYS Sun Apr 13 20:32:38 2008 (480251C6)
    b8488000 b848e180 kbdclass kbdclass.sys Sun Apr 13 20:39:46 2008 (48025372)
    b8490000 b8495b00 mouclass mouclass.sys Sun Apr 13 20:39:47 2008 (48025373)
    b8498000 b849c300 usbohci usbohci.sys Sun Apr 13 20:45:34 2008 (480254CE)
    b84a8000 b84af680 usbehci usbehci.sys Wed Mar 18 12:02:22 2009 (49C0D4BE)
    b84b8000 b84bb000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345)
    b84bc000 b84be800 compbatt compbatt.sys Sun Apr 13 20:36:36 2008 (480252B4)
    b84c0000 b84c3780 BATTC BATTC.SYS Sun Apr 13 20:36:32 2008 (480252B0)
    b85a8000 b85a9b80 kdcom kdcom.dll Fri Aug 17 22:49:10 2001 (3B7D8346)
    b85aa000 b85ab100 WMILIB WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
    b85ac000 b85ad700 dmload dmload.sys Fri Aug 17 22:58:15 2001 (3B7D8567)
    b85d2000 b85d3b00 ParVdm ParVdm.SYS Fri Aug 17 22:49:49 2001 (3B7D836D)
    b8630000 b8631100 swenum swenum.sys Sun Apr 13 20:39:52 2008 (48025378)
    b8670000 b8670d80 pciide pciide.sys Fri Aug 17 22:51:49 2001 (3B7D83E5)
    b8671000 b8671680 giveio giveio.sys Thu Apr 04 04:33:25 1996 (316334F5)
    b8751000 b8751b80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
    bd000000 bd011600 dxg dxg.sys Sun Apr 13 20:38:27 2008 (48025323)
    bd012000 bd45b400 nv4_disp nv4_disp.dll Thu Jan 31 08:36:14 2013 (510A1EEE)
    bd45c000 bd4a3000 ATMFD ATMFD.DLL Tue Jun 04 02:53:15 2013 (51AD3A7B)
    bf800000 bf9cad00 win32k win32k.sys Fri Feb 07 03:01:27 2014 (52F43E77)

    Unloaded modules:
    a38be000 a38e9000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a38be000 a38e9000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a395e000 a3989000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a39fe000 a3a29000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a3a9e000 a3ac9000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a3b3e000 a3b69000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a3c06000 a3c31000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a3c06000 a3c31000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a3e11000 a3e3c000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a4091000 a40bc000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a4091000 a40bc000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a4131000 a415c000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a44c9000 a44f4000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a45e1000 a460c000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a530b000 a5336000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a5916000 a5941000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a5f81000 a5fac000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a604c000 a6077000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a6167000 a6192000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a754f000 a757a000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    b8400000 b8407000 USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 00007000
    a76cb000 a76f6000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    b18f7000 b18fe000 USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 00007000
    a7b06000 a7b31000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    acec3000 acec5000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 00002000
    a7c71000 a7c9c000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    a8b37000 a8b62000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0002B000
    b87b3000 b87b4000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 00001000
    a8b62000 a8b85000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 00023000
    b82b8000 b82c5000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0000D000
    b6f73000 b6f81000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0000E000
    ac729000 ac72b000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 00002000
    b6f23000 b6f30000 STREAM.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0000D000
    b27a1000 b27a9000 CX88TUNE.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 00008000
    b81b8000 b81c5000 STREAM.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 0000D000
     
  15. 2017/09/10
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    5,358
    Likes Received:
    294
    Trophy Points:
    1,093
    Location:
    New Zealand
    Computer Experience:
    intermediate
    Sorry, I've been away for a short break. Please answer my questions accurately. What has happened recently to be a possible problem -
    have you added new hardware?
    loaded any new software?
    have you run sfc /scannow?

    You say it runs OK in Safe Mode. This would suggest you have driver corruption or software corruption. Safe Mode runs minimal basic drivers.
    You also stated that "caps" have been replaced. This would suggest the m/b may have been overclocked or run at high temperature.
    You don't state whether this was a new comp or whether you purchased a 2nd hand one?
    When I asked whether the CPU had been disturbed - CPU is your Central Processing Unit - the heart of the computer. If it is not fitted correctly, or the thermal paste is not assisting the transfer of heat from the CPU, it will overheat and/or the comp will be unstable, shutdown or cause problems.
    Your PSU is suggested as ideal for "gaming" hence my question about overclocking.
     
  16. 2017/09/11
    Ragefhonor

    Ragefhonor New Member Thread Starter

    Joined:
    2017/08/11
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Computer Experience:
    Very good
    I haven’t add new Hardware
    I didn’t install new software

    I tried run sfc /scannow but it wont scan my OS. Because it’s Windows XP SP2 with SP3 installed later. The scanner thinks I use the wrong CD/DVD

    Yes there are no problems in Safe Mode

    First time the Caps have been replaced in a PC Service center because they where swollen.
    Few in the CPU aeria, one at the power connector and one near the GPU.


    This year I had only 3 caps near the CPU that where swollen. And they replaced them like the last time.

    The MB was never Overclocked.
    It’s not a 2nd hand PC. It's my own. It runs 24/7

    In the service center they also replaced the thermal paste during the Caps replace. I have never removed the CPU or the cooling by myself.

    It’s possible that the CPU could get overheated once because the radiator was few years ago clogged by dust but after cleaning it: it got back to normal temperature. Now I have CPU temperature about 51*C / 123*F.

    The last thing I did was installing old drivers that I saved by Driver Copy and it looks like it's fine now but im not shure if it stays so. The OS is running now almost 4 days without BSOD.

    Time will show.
     
  17. 2017/09/11
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    5,358
    Likes Received:
    294
    Trophy Points:
    1,093
    Location:
    New Zealand
    Computer Experience:
    intermediate
    I used this method many times when I had XP SP3 on my early comps. It worked 100% every time.
    scannow sfc - LEARN how to use SFC.EXE (system file checker)
    From your description of your "cap" problems, I would renew the motherboard!!! :mad:
    Just to give you an idea - my comp (see my System Details) is running at 18°C at the moment.
    As I said in my first Post, XP is history and W10 is the way to go. ;) As XP has no support from MS, XP is definitely unsafe to use out on the web.:eek:
     

Share This Page