1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Vista crashes to BSOD when playing music/games/video

Discussion in 'Windows Vista' started by rydog420, Jul 19, 2007.

Thread Status:
Not open for further replies.
Advertisement
  1. rydog420

    rydog420 Thread Starter

    Joined:
    Jul 19, 2007
    Messages:
    2
    Windows will crash to BSOD after about 10-15 minutes of playing a game, listening to music, or watching video. This started happening about a month ago. Up until then everything was fine. I though I found some people with the same problem when I search on Google, but updating their BIOS fixed their problem, it didn't fix mine.

    I have updated all of the drivers I could think of and flashed my BIOS to the newest version on the ECS website (I have an ECS KA3 MVP motherboard). This didn't fix the problem. I also made sure I downloaded the Vista driver from Nvidia for my graphics card. I have also run a Memtest and had not errors, and I ran a video card stability test and everything was fine (didn’t even crash). I checked all of the temperatures on the restart and they are all in normal operating range. Here is what the BSOD says everytime.

    Driver_IRQL_NOT_LESS_OR_EQUAL
    ***Stop: 0x000000D1 (0x00000008, 0x00000002, 0x00000001, 0x81F215B2)
    ***ndis.sys - address 81F215B2 base at 81EFC000, Datestamp 454962FD

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.0.6000.2.0.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: d1
    BCP1: 00000008
    BCP2: 00000002
    BCP3: 00000001
    BCP4: 81F215B2
    OS Version: 6_0_6000
    Service Pack: 0_0
    Product: 768_1

    Here is the info from my latest crash dump file…


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


    Loading Dump File [C:\Windows\Minidump\Mini071907-08.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0
    Debug session time: Thu Jul 19 19:58:11.508 2007 (GMT-4)
    System Uptime: 0 days 0:16:32.175
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ......................................
    Loading User Symbols
    *** WARNING: Unable to verify timestamp for ndis.sys
    *** ERROR: Module load completed but symbols could not be loaded for ndis.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {8, 2, 1, 81f215b2}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : ndis.sys ( ndis+255b2 )

    Followup: MachineOwner


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


    Loading Dump File [C:\Windows\Minidump\Mini071907-08.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0
    Debug session time: Thu Jul 19 19:58:11.508 2007 (GMT-4)
    System Uptime: 0 days 0:16:32.175
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ......................................
    Loading User Symbols
    *** WARNING: Unable to verify timestamp for ndis.sys
    *** ERROR: Module load completed but symbols could not be loaded for ndis.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {8, 2, 1, 81f215b2}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : ndis.sys ( ndis+255b2 )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000008, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 81f215b2, address which referenced memory

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************

    MODULE_NAME: ndis

    FAULTING_MODULE: 82000000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4549b2fd

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    00000008

    CURRENT_IRQL: 2

    FAULTING_IP:
    ndis+255b2
    81f215b2 ?? ???

    CUSTOMER_CRASH_COUNT: 8

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from 81f215b2 to 8208fc44

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    82857f00 81f215b2 badb0d00 87481c10 00000008 nt+0x8fc44
    82857f7c 81fc4920 87c50c88 82857f9c 82857fac ndis+0x255b2
    82857fa0 81fc341e 8747fc58 00000000 00000001 ndis+0xc8920
    82857fd4 81fc35c8 870b6488 87c50c88 00000001 ndis+0xc741e
    82857ff4 8dc10d7c 870b6488 87c50c88 00000001 ndis+0xc75c8
    82858018 8dc11927 8726d000 00000000 00000000 0x8dc10d7c
    8285803c 81fc3521 8726d000 00000000 00000000 0x8dc11927
    82858064 81f25aa4 870b6488 87c50c88 00000000 ndis+0xc7521
    828580a4 81f259d0 870b6488 00858108 00000001 ndis+0x29aa4
    828580e0 81fc49fd 8747fc58 82858108 00000001 ndis+0x299d0
    828580fc 81fc772b 8747fc58 87481c10 828581e8 ndis+0xc89fd
    8285810c 8e586982 828581d4 8747fc58 87481c10 ndis+0xcb72b
    828581e8 81fc688d 874ea000 8615ec88 00000082 0x8e586982
    82858214 81fc6732 82858234 82858234 00000000 ndis+0xca88d
    8285827c 81effae4 872130e8 85bc6b88 00000000 ndis+0xca732
    8285829c 81effb98 85bc6b88 85bc6b88 00000000 ndis+0x3ae4
    828582b4 8e407e20 87c0c0d0 85bc6b88 00000000 ndis+0x3b98
    82858330 81effb76 87c46cf8 85bc6b88 00000000 0x8e407e20
    8285834c 81fc364a 85bc6b88 85bc6b88 00000000 ndis+0x3b76
    82858370 8f6b9453 87c34008 85bc6b88 00000000 ndis+0xc764a
    82858408 8f6b7935 87c31a98 00000000 8285858c 0x8f6b9453
    82858448 8f6b8f6a 8f7029c8 00000000 00000000 0x8f6b7935
    82858480 8f6b8601 8f7029c8 8285858c 8f7029c8 0x8f6b8f6a
    82858518 8f6b7e01 0085858c 828586c8 85eb2850 0x8f6b8601
    82858670 8f6ba2ea 00000000 00000007 8f7029c8 0x8f6b7e01
    82858690 8f6895d2 87beb0a0 828586a8 87beb0a0 0x8f6ba2ea
    82858718 8f68952e 87beb0a0 82858800 85ce6740 0x8f6895d2
    82858768 8f6bb21b 87beb0a0 00000001 82858800 0x8f68952e
    82858854 8f6ae41e 88255020 00000002 00000632 0x8f6bb21b
    82858880 8f6ba5d7 00000001 00000000 82858964 0x8f6ae41e
    828588b0 8f6bf3e4 87beb9d0 87be7808 87be7810 0x8f6ba5d7
    828588cc 8f6bf60b 87beb9d0 87be7808 82858908 0x8f6bf3e4
    828588dc 8f6b1124 828588f0 c000023e 00000000 0x8f6bf60b
    82858908 8f6b0ef4 8f702bac 82858964 c000023e 0x8f6b1124
    82858928 8f6b0e23 8f7029c8 00000006 82858964 0x8f6b0ef4
    8285897c 8f6ac4de 8f7029c8 00000006 00000000 0x8f6b0e23
    82858a0c 8f6b074a 87c36df0 00000000 870b6401 0x8f6ac4de
    82858a88 8f6b0063 87c31a98 87c4fc28 00000000 0x8f6b074a
    82858ab0 81fc30b0 87c31a98 87c4fc28 00000000 0x8f6b0063
    82858ae4 81fb58a2 00c34008 87c4fc28 00000000 ndis+0xc70b0
    82858b0c 81fb5819 00000000 82027c97 872130e8 ndis+0xb98a2
    82858c88 81f17fc6 872130e8 00000000 00000000 ndis+0xb9819
    82858cc4 81f17df3 858cf400 82868120 82858d40 ndis+0x1bfc6
    82858ce8 820a93ae 8613a618 00000000 a9a3796d ndis+0x1bdf3
    82858d50 820912ae 00000000 0000000e 00000000 nt+0xa93ae
    82858d54 00000000 0000000e 00000000 00000000 nt+0x912ae


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    ndis+255b2
    81f215b2 ?? ???

    SYMBOL_STACK_INDEX: 1

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ndis.sys

    SYMBOL_NAME: ndis+255b2

    BUCKET_ID: WRONG_SYMBOLS

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


    Any ideas? I’m not sure what to try next. Thanks.
     
  2. Iakona724

    Iakona724

    Joined:
    Jul 5, 2006
    Messages:
    60
    I believe I may have the same problem as you. I've only had vista for a coupe of days, so I haven't really been able to look into it, but I'll post back with more details eventually. I've had this occur once while I was playing music, and another time while I was watching a movie. I believe it may be a problem with Windows Media Center.
     
  3. Iakona724

    Iakona724

    Joined:
    Jul 5, 2006
    Messages:
    60
    Update: Problem reoccurred just yesterday while I was playing music on iTunes, but I can't seem to reproduce the BSOD.

    P.S. I have similar problems, but I'm not sure about the error messages, I'll post pics if I can.
     
  4. rydog420

    rydog420 Thread Starter

    Joined:
    Jul 19, 2007
    Messages:
    2
    I found that if i disable my onboard network adapter the problem doesn't occur.
     
  5. Iakona724

    Iakona724

    Joined:
    Jul 5, 2006
    Messages:
    60
    I FINALLY figured my issue out about a week ago... it was my RAM voltage was at the standard 1.8v meanwhile my RAM needed 2.2v. Since I've increased the voltage I've been BSOD free.
     
  6. HM9408

    HM9408

    Joined:
    Jul 15, 2008
    Messages:
    27
    Man, you are NOT the only one having thi problem. I have it too ;)... It happens SPECIALLY when watching Youtube videos. I'm tired of this. I thought it was my motherboard, but I'd just remembered that I have an ATIRadeon x1650 PRO, so I don't get it... Maybe it's a plugin in Vista that bothers with media playback. Oh no!!! It can't be because it also bothers (at least it's me) when I make video calls in Skype.!?!? Maybe it's just Vista going mad :(. Hope someone has a solution.
     
  7. Iakona724

    Iakona724

    Joined:
    Jul 5, 2006
    Messages:
    60
    Read the post above yours... Raising my RAM voltage solved the problem for me.
     
  8. HM9408

    HM9408

    Joined:
    Jul 15, 2008
    Messages:
    27
    How can I do that?
     
  9. Iakona724

    Iakona724

    Joined:
    Jul 5, 2006
    Messages:
    60
    There should be an option to do that somewhere in your BIOS
     
  10. HM9408

    HM9408

    Joined:
    Jul 15, 2008
    Messages:
    27
    Ok. I'll search for it. Thanks.
     
  11. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/597991

  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.
    Dismiss Notice