TechSpot

BSOD irql not less than or equal to Windows 7

By Punk182
Jun 1, 2011
Post New Reply
  1. CPU: intel i7 950 @ 3.07 GHz

    Motherboard: ASUS P6X58D PREMIUM

    Ram Speed, size and #sticks:
    3 STICKS
    KHX2000C9AD3T1FK3/6GX
    KINGSTON
    *RAN MEMTEST ONLY TWO ARE INSTALLED*

    GPU: 2 NVIDIA GeForce GTS 450 (SLI LINKED)

    PSU (do not leave this out): Delta Electronics EFB0812EH power supply

    OS: WINDOWS 7 ULITMATE



    MINIDUMP FILE:


    Loading Dump File [C:\Users\Frankie\Videos\060111-22651-01.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\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`0360b000 PsLoadedModuleList = 0xfffff800`03848e50
    Debug session time: Wed Jun 1 17:02:08.580 2011 (UTC - 4:00)
    System Uptime: 0 days 14:18:28.720
    *********************************************************************
    * 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\ntoskrnl.exe, Win32 error 0n2
    *** 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
    .....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {fffffaba075d7a10, 2, 1, fffff80003684c9c}

    ***** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 : ntoskrnl.exe ( nt+79c9c )

    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: fffffaba075d7a10, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80003684c9c, 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: fffff8000360b000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

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

    CURRENT_IRQL: 0

    FAULTING_IP:
    nt+79c9c
    fffff800`03684c9c f00fba2e07 lock bts dword ptr [rsi],7

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    LAST_CONTROL_TRANSFER: from fffff8000367aca9 to fffff8000367b740

    STACK_TEXT:
    fffff880`0b7d0838 fffff800`0367aca9 : 00000000`0000000a fffffaba`075d7a10 00000000`00000002 00000000`00000001 : nt+0x70740
    fffff880`0b7d0840 00000000`0000000a : fffffaba`075d7a10 00000000`00000002 00000000`00000001 fffff800`03684c9c : nt+0x6fca9
    fffff880`0b7d0848 fffffaba`075d7a10 : 00000000`00000002 00000000`00000001 fffff800`03684c9c 00000000`00000000 : 0xa
    fffff880`0b7d0850 00000000`00000002 : 00000000`00000001 fffff800`03684c9c 00000000`00000000 00000000`00000000 : 0xfffffaba`075d7a10
    fffff880`0b7d0858 00000000`00000001 : fffff800`03684c9c 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
    fffff880`0b7d0860 fffff800`03684c9c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
    fffff880`0b7d0868 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x79c9c


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt+79c9c
    fffff800`03684c9c f00fba2e07 lock bts dword ptr [rsi],7

    SYMBOL_STACK_INDEX: 6

    SYMBOL_NAME: nt+79c9c

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntoskrnl.exe

    BUCKET_ID: WRONG_SYMBOLS

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

    0: kd> lmvm nt
    start end module name
    fffff800`0360b000 fffff800`03be7000 nt T (no symbols)
    Loaded symbol image file: ntoskrnl.exe
    Image path: \SystemRoot\system32\ntoskrnl.exe
    Image name: ntoskrnl.exe
    Timestamp: Sat Jun 19 00:16:41 2010 (4C1C44A9)
    CheckSum: 005489D7
    ImageSize: 005DC000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

    BSOD TENDS TO HAPPEN WHILE CPU IS BEING USED HEAVILY.
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    We want you to go ahead and attach your minidumps so that we can read them.

    How to find and post your Minidump Files:

    My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

    It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually.
     
  3. Punk182

    Punk182 TS Rookie Topic Starter

    Thank You. Here are my last 5 minidumps.
     

    Attached Files:

  4. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    Your mini9dumps cited corrupted memory as your issue. How many times did you run memtest for? The minimum is 7 Passes and the more the better. Is your memory designed for tri-channel? If so, why are only two sticks installed?

    *** If Memtest shows no errors then find the voltage specs of your RAM and compare it to the voltage setting in your BIOS. Do they match?
     
  5. Punk182

    Punk182 TS Rookie Topic Starter

    Rodger that... For some reason the mtest passed all 7 but it never recognized one of the ram chips... So I just ordered the same set of ram and returning the others as defective... So I will be posting to let u know what happens.. Thank you this was boggling my mind for days because the chips are recommend through the mobos book.. I will be posting if I have anymore problems
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    Yes, please keep us updated.
     
  7. Punk182

    Punk182 TS Rookie Topic Starter

    Still only reads two of the chips... The mobos book says that the specific chips will run in tri channel but for some reason the motherboard keeps running them in dual channel. I am currently running another memtest to see if that shows anything, but we'll have to see.
     
  8. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    You may need a BIOS update. Have you researched your board to see if this is a problem experienced by others?
     
  9. John Digweed

    John Digweed TS Rookie

    I have the same error message... playing Diablo 3...
     

    Attached Files:

  10. Tmagic650

    Tmagic650 TS Ambassador Posts: 20,915   +167

    Looks like a video driver issue John...
     
  11. John Digweed

    John Digweed TS Rookie

    For sure... but I don't know what exactly is the issue
     
     
  12. Tmagic650

    Tmagic650 TS Ambassador Posts: 20,915   +167

    Try updating the video driver first. What video card do you have installed?
     
  13. John Digweed

    John Digweed TS Rookie

    NVIDIA GTS 450 and I use NVidia cd installer. also have the live update directly from their website
     
  14. Tmagic650

    Tmagic650 TS Ambassador Posts: 20,915   +167

    Have you applied all the Windows Updates?
     
  15. John Digweed

    John Digweed TS Rookie

    Yes... all
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033
    Additional information about the problem:
    BCCode: a
    BCP1: FFFFFA0008D07F4E
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF80003686FF4
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
    Files that help describe the problem:
    C:\Windows\Minidump\101414-20373-01.dmp
    C:\Users\woo\AppData\Local\Temp\WER-53102-0.sysdata.xml
    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    I just want to throw it out... I'm dead on D3 with a HC hero
     
  16. Tmagic650

    Tmagic650 TS Ambassador Posts: 20,915   +167

    Go to C:\windows\minidump. Minidump files have a .dmp extension.There should be new minidumps associated with this new error. Select all the .dmp files and right-click sending these files to a compressed(zipped)folder. Upload this folder as a file here
     


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.