TechSpot

help! New PC.. big PRoblem!

By rootwiler
Jan 11, 2007
  1. Hello, I'm new here so please bare with me!

    well, I bought myself a new PC 2 days ago, I did a format, installed all of the latest drivers.. I thought everything was working fine but now I get these BSOD when I play openGL games.. I can play, I will "ALT+TAB" to the desktop and then when I go back into the game.. I well get the BSOD and I am forced to reboot. I have tired all different kind of driver and now help.. so here ya go

    System : 3800+ AM2, M2N-E with 0701 bios (very latest), 7600GT(tried the latest drivers, now useing the 84.xx" .. drivers made no difference) 1 x 1gig patriot ram (PC5300), 1x320GIG sataII drive, 450WATT PSU.

    I have checked the wattages in the bios and they are all good.. so I am stumped! here is my minidump.. I have like 10 of them.. but I'll post one.
    1.

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini011007-09.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 ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Wed Jan 10 23:39:06.218 2007 (GMT-7)
    System Uptime: 0 days 0:20:04.928
    *********************************************************************
    * 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 ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ........................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    Unable to load image nv4_mini.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for nv4_mini.sys
    *** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {f7d4b020, 2, 1, f6727f38}

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

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

    Probably caused by : nv4_mini.sys ( nv4_mini+7af38 )

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

    0: 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: f7d4b020, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: f6727f38, address which referenced memory

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

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

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


    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4410cb0a

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

    CURRENT_IRQL: 2

    FAULTING_IP:
    nv4_mini+7af38
    f6727f38 8910 mov dword ptr [eax],edx

    CUSTOMER_CRASH_COUNT: 9

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from 86525a50 to f6727f38

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f7a2fe40 86525a50 863ff9c0 863ff994 86511cfc nv4_mini+0x7af38
    f7a2fe44 863ff9c0 863ff994 86511cfc f688cccb 0x86525a50
    f7a2fe48 863ff994 86511cfc f688cccb f7d4b020 0x863ff9c0
    f7a2fe4c 86511cfc f688cccb f7d4b020 863ff720 0x863ff994
    f7a2fe50 f688cccb f7d4b020 863ff720 00000000 0x86511cfc
    f7a2fe54 f7d4b020 863ff720 00000000 00000000 nv4_mini+0x1dfccb
    f7a2fe58 863ff720 00000000 00000000 00000000 0xf7d4b020
    f7a2fe5c 00000000 00000000 00000000 0001930d 0x863ff720


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nv4_mini+7af38
    f6727f38 8910 mov dword ptr [eax],edx

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nv4_mini+7af38

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nv4_mini

    IMAGE_NAME: nv4_mini.sys

    BUCKET_ID: WRONG_SYMBOLS

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

    If you need more, just say, I can give all 10 if that is whats needed.. but anyways.. if anyone can help that would be AWESOME! thanks!

    **off to google.. maybe I will find something.. haven't found anything in 2 hours..lol**
     
  2. nismo91

    nismo91 TS Evangelist Posts: 900   +15

    it's probably because incorrect driver in you 7600, see the "nv"s file over there?
    For me, most probably nv stands for the nvidia...
     
  3. rootwiler

    rootwiler TS Rookie Topic Starter

    well, I don't know cause I have tired a few different drivers but it doesn't seem to make a difference.. so.. I don't know :|
     
  4. peepnklown

    peepnklown TS Rookie Posts: 126

    What is your page file set to?
     
  5. rootwiler

    rootwiler TS Rookie Topic Starter

    1536MB ... 1.5x my ram..
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

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