locked
BSOD : IRQL_NOT_LESS_OR_EQUAL Caused By ntoskrnl.exe ( nt+90413 ) RRS feed

  • Question

  • Hi ..

    This Problem Happens To Me Every Time I Install Windows 7 ..
    When I Leave A Download Or Something A BSOD Happens ..
    And the blue screen top says IRQL_NOT_LESS_OR_EQUAL ..
    IT'S A FRESH INSTALL SO THIS IS NOT FROM A SECURITY PROGRAM !

    I Can See It's From The Driver ( Nvidia GeForce FX 5200 ) ..
    Because When I Uninstalled The Driver ..

    THE BSOD Disappeared ..
    THERE IS NO A WINDOWS 7 DRIVER FOR NVIDIA GEFORCE FX 5200 .. AND I TRIED THE VISTA DRIVER AND XP DRIVER .. AND STILL THE BSOD !

    Anyway ..

    Here Is The Analysation Of The Dump File ..

     

    Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Mohamed\Desktop\New folder\022811-29250-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 7601 (Service Pack 1) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0x82813000 PsLoadedModuleList = 0x829535b0
    Debug session time: Mon Feb 28 23:34:01.088 2011 (GMT+2)
    System Uptime: 0 days 0:31:25.932
    *********************************************************************
    * 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, {83be67f0, 2, 1, 828a3413}
    
    ***** 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                   ***
    ***                                  ***
    *************************************************************************
    *********************************************************************
    * 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+                  *
    *********************************************************************
    *********************************************************************
    * 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+                  *
    *********************************************************************
    Probably caused by : ntoskrnl.exe ( nt+90413 )
    
    Followup: MachineOwner
    ---------
    
    
    

    The Dump File Can Be Downloaded From Here :

    http://www.mediafire.com/?oojerehtmf85o14

     

    Please HELP MEEEEE .. :S :S :S

     

    Monday, February 28, 2011 10:24 PM

Answers

  • 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.

    STACK_TEXT: 
    80d86c5c 828a3413 badb0d00 00000000 82c1cba9 nt!KiTrap0E+0x2cf
    80d86d44 82997454 00000000 80d86d90 829fc400 nt!MmZeroPageThread +0x271
    80d86d50 829fc400 8080a538 bc491a7e 00000000 nt!Phase1Initialization+0x14
    80d86d90 8289c969 82997440 8080a538 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0xA_nt!MmZeroPageThread+271


    You have a RAM issue. The ZeroPageThread, which overrides all free RAM with Zeros before it is used by applications later, causes issues.

    Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2][3] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If memtest86+ detects errors, test each module its own and replace the faulty RAM.

    If the memtest tells no error, please download CPU-Z [4], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    André

    [1] http://www.memtest.org/download/4.20/memtest86+-4.20.iso.zip
    [2] http://www.imgburn.com/index.php?act=download
    [3] http://forum.imgburn.com/index.php?showtopic=61
    [4] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Leo Huang Wednesday, March 9, 2011 6:54 AM
    Tuesday, March 1, 2011 1:55 PM