1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista BSOD, while playing (ntkrpamp.exe?)

Discussion in 'Legacy Windows' started by twizz, 2009/02/11.

  1. 2009/02/11
    twizz

    twizz Inactive Thread Starter

    Joined:
    2009/02/11
    Messages:
    4
    Likes Received:
    0
    Ok, so i had 64-bit Vista before, and got BSOD almost every time I tried to play something, and had some other issues with it so i changed to 32-bit Vista, and now I got the same problem :confused:

    I were playing Colin Mcrae DiRT and got BSOD, here's the Bug check:

    Microsoft (R) Windows Debugger Version 6.11.0001.402 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

    Symbol search path is: SRV*c:\Program Files\Debugging Tools for Windows (x86)\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0x81a4e000 PsLoadedModuleList = 0x81b65c70
    Debug session time: Wed Feb 11 08:00:34.667 2009 (GMT+2)
    System Uptime: 0 days 0:12:55.540
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details
    Loading unloaded module list
    ....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {0, 1b, 1, 81b01c1f}

    Page ada92 not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details
    Probably caused by : ntkrpamp.exe ( nt!KiUnwaitThread+19 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 0000001b, 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: 81b01c1f, address which referenced memory

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

    Page ada92 not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details

    WRITE_ADDRESS: 00000000

    CURRENT_IRQL: 1b

    FAULTING_IP:
    nt!KiUnwaitThread+19
    81b01c1f 890a mov dword ptr [edx],ecx

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: DiRT.exe

    TRAP_FRAME: 8039dd8c -- (.trap 0xffffffff8039dd8c)
    ErrCode = 00000002
    eax=85647ce8 ebx=00000000 ecx=00000000 edx=00000000 esi=853fe200 edi=853fe290
    eip=81b01c1f esp=8039de00 ebp=8039de14 iopl=0 nv up ei ng nz na pe cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210287
    nt!KiUnwaitThread+0x19:
    81b01c1f 890a mov dword ptr [edx],ecx ds:0023:00000000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 81b01c1f to 81aa8d24

    STACK_TEXT:
    8039dd8c 81b01c1f badb0d00 00000000 8039ddd4 nt!KiTrap0E+0x2ac
    8039de14 81b0494b 00000000 81b4ae90 00000310 nt!KiUnwaitThread+0x19
    8039df28 81b04876 8039df70 8039df02 8039df78 nt!KiTimerListExpire+0x76
    8039df88 81b043c3 00000000 00000000 0000c231 nt!KiTimerExpiration+0x2a0
    8039dff4 81b02935 9ec9bd10 00000000 00000000 nt!KiRetireDpcList+0xba
    8039dff8 9ec9bd10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    81b02935 00000000 0000001b 00c7850f bb830000 0x9ec9bd10


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiUnwaitThread+19
    81b01c1f 890a mov dword ptr [edx],ecx

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KiUnwaitThread+19

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa

    FAILURE_BUCKET_ID: 0xA_nt!KiUnwaitThread+19

    BUCKET_ID: 0xA_nt!KiUnwaitThread+19

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

    So it would be awesome if someone could help me with this :)

    My computer specs are:
    Asus a3m78 pro
    club 3d hd4850
    amd phenom x4 II 920
    4gb 1066mhz ddr2
    500gb seagate hdd
    creative xtreme audio sound card
    vista ultimate 32-bit
    and antec sonata III
     
    twizz,
    #1
  2. 2009/02/11
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Arie,
    #2


  3. to hide this advert.

  4. 2009/02/11
    twizz

    twizz Inactive Thread Starter

    Joined:
    2009/02/11
    Messages:
    4
    Likes Received:
    0
    wow :eek: so that really could be the reason for BSOD..
    But when I had 64-bit vista, I had that problem with GTA IV (didn't even get to gameplay) and with Assassin's Creed. Haven't tried GTA IV with 32-bit and the Assassin's Creed worked perfectly so I really hope that I messed up my 64-bit somehow :p

    Thanks for the answer :)
     
    twizz,
    #3
  5. 2009/02/11
    twizz

    twizz Inactive Thread Starter

    Joined:
    2009/02/11
    Messages:
    4
    Likes Received:
    0
    darn.. now I were playing LOTR Conquest and BSOD came again..
    I don't think that it's caused by not supported graphic card in two games, because the BSOD message is the same..

    I hope that someone know how to help :)
    here's the crash dump for this another BSOD:

    Microsoft (R) Windows Debugger Version 6.11.0001.402 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

    Symbol search path is: SRV*c:\Program Files\Debugging Tools for Windows (x86)\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0x81c3e000 PsLoadedModuleList = 0x81d55c70
    Debug session time: Wed Feb 11 22:22:29.614 2009 (GMT+2)
    System Uptime: 0 days 0:50:55.990
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols

    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {6f51a2c, ff, 0, 81c918f2}

    Probably caused by : ntkrpamp.exe ( nt!KiInterruptDispatch+2 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 06f51a2c, memory referenced
    Arg2: 000000ff, 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: 81c918f2, address which referenced memory

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


    READ_ADDRESS: 06f51a2c

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!KiInterruptDispatch+2
    81c918f2 8b472c mov eax,dword ptr [edi+2Ch]

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: System

    TRAP_FRAME: 8b763c00 -- (.trap 0xffffffff8b763c00)
    ErrCode = 00000000
    eax=0015de34 ebx=8b763cf8 ecx=8b74c1e0 edx=00000000 esi=8b748000 edi=06f51a00
    eip=81c918f2 esp=8b763c74 ebp=8b763c74 iopl=0 nv up di pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010046
    nt!KiInterruptDispatch+0x2:
    81c918f2 8b472c mov eax,dword ptr [edi+2Ch] ds:0023:06f51a2c=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 81c918f2 to 81c98d24

    STACK_TEXT:
    8b763c00 81c918f2 badb0d00 00000000 81cf94ff nt!KiTrap0E+0x2ac
    8b763c74 8ab3b9d8 badb0d00 00000000 8b74c1e0 nt!KiInterruptDispatch+0x2
    8b763ce4 8ab3b091 81cf9de4 86443c78 8b749f90 processr!C1Halt+0x4
    8b763ce8 81cf9de4 86443c78 8b749f90 8b763d50 processr!C1Idle+0x5
    8b763cf8 81cf9d32 8647bc08 00000000 892a5098 nt!PpmCallIdleHandler+0x2e
    8b763d50 81cf2ea1 00000000 0000000e 00000000 nt!PoIdle+0x2d1
    8b763d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiInterruptDispatch+2
    81c918f2 8b472c mov eax,dword ptr [edi+2Ch]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KiInterruptDispatch+2

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa

    FAILURE_BUCKET_ID: 0xA_nt!KiInterruptDispatch+2

    BUCKET_ID: 0xA_nt!KiInterruptDispatch+2

    Followup: MachineOwner
    ---------
     
    twizz,
    #4
  6. 2009/02/12
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Since it always happen with game play, temperature could also be an issue. Check your CPU temp when running the game.
     
    Arie,
    #5
  7. 2009/02/19
    twizz

    twizz Inactive Thread Starter

    Joined:
    2009/02/11
    Messages:
    4
    Likes Received:
    0
    okay, well the problem wasn't the temperature, it was my Kingston HyperX 1066mhz memory modules.. had to manually set the right settings for those @ bios and now everything works :)
     
    twizz,
    #6
  8. 2009/02/20
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Thanks for posting back & great you got it solved.
     
    Arie,
    #7

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...