BSOD IRQL_NOT_LESS_OR_EQUAL Stop 0x0000000A

Page 1 of 3 123 LastLast

  1. Posts : 11
    Windows 7 64 bit
       #1

    BSOD IRQL_NOT_LESS_OR_EQUAL Stop 0x0000000A


    Hi

    Suffering random BSOD's - they can occur while gaming or at desktop but also I can go for hours/days without any error and then multiple crashes. I haven't added any new hardware other than I bought a Thrustmaster RS 300 Steering wheel a couple of months back.

    I've done Windows Updates and Malware Checks and have updated Microsoft Security Essentials.

    Any help greatly appreciated.
      My Computer


  2. Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       #2

    Hello Sabre mate just run these for starters if you haven't already - in safe mode
    SFC /SCANNOW Command - System File Checker
    Disk Check < if necessary include the /f and /r in the command line as per Option2
      My Computer


  3. Posts : 11
    Windows 7 64 bit
    Thread Starter
       #3

    Okay thanks for the reply, I've tried the disk check previously but I'll try again and post back what I find.

    Cheers
      My Computer


  4. Posts : 11
    Windows 7 64 bit
    Thread Starter
       #4

    Okay I've ran scannow and it returned:

    "Windows Resource Protection did not find any integrity violations"

    I'm running chkdsk with /r and /f but I think it'll be a while so I'll report back when complete.

    Edit: chkdsk has completed "The volume is clean"

    Thanks for your help

    Cheers
    Last edited by Sabretooth; 31 Mar 2016 at 17:20.
      My Computer


  5. Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       #5

    Ok well sometimes it is worth running sfc a few times in a row just to be sure and for the time it takes not worth worrying about.

    The dump files are indicating the highlighted exe in the CODE area
    Code:
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntoskrnl.exe
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:wrong_symbols
    
    FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
    
    Followup: MachineOwner
    Now this can be a few things and I think it maybe worth first up running this
    RAM - Test with Memtest86+ do it for at least 8 passes as if you don't it isn't worth bothering to do it at all. That is of course unless errors start up fairly quickly then you can stop it and then it is down to finding the bad RAM stick. It does take a long time but worth it if only to eliiinate the RAM as a cause of failure.

    See my pic to see what you are looking for.
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #6

    ICIT2LOL said:
    The dump files are indicating the highlighted exe in the CODE area
    Code:
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntoskrnl.exe
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:wrong_symbols
    
    FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
    
    Followup: MachineOwner
    Now this can be a few things
    It means
    1. The setup of Windbg isn't proper on your system,
    2. You're missing the symbols.
      My Computer


  7. Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       #7

    Thanks axe mate I wasn't quite sure of where to start with this one that dump is so common:)
      My Computer


  8. Posts : 11
    Windows 7 64 bit
    Thread Starter
       #8

    Okay I've ran the memtest86+ for around 14 hours in which it made 11 passes. It seems there were 165 errors during pass 10 if I'm reading the screen right? I've attached an image below.

    I assume any error is bad? If this is the likely cause would it be easier to simply replace all of the RAM? Or is there a possibility that the test has ran too long and may be giving false results?

    Apologies for all the questions and thanks for your help once more.

      My Computer


  9. Posts : 7,050
    Windows 10 Pro
       #9

    What you now have to do is following:
    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.
      My Computer


  10. Posts : 11
    Windows 7 64 bit
    Thread Starter
       #10

    Thanks for the reply axe0

    Excuse my ignorance but is this process to establish if the RAM is indeed faulty? Or is it looking at something else?

    Each of the four sticks of RAM in each slot is going to take some time to test and I'm just wondering if I should just change the RAM. Obviously I don't want to do that if still trying to find the cause of the BSOD,s

    Apologies if I've misunderstood.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:26.
Find Us