BSOD While gaming Error 0x0000000A


  1. Posts : 3
    Windows 7 64
       #1

    BSOD While gaming Error 0x0000000A


    I have been in the beta test for an online game Smite now for over a month. During the past 2 days my computer reboots very early into the game. The last few reboots have resulted in a BSOD. I have not installed any new hardware or software that I can think of, especially over the last few days. This is a computer my friend built so I am not sure of all of the specs, and I know he built it relatively cheap. I have done a decent amount of gaming on it, and this is my first encounter with any issues like this. I appreciate any and all help.
      My Computer


  2. Posts : 851
    Windows 8 Professional x64
       #2

    uninstall Hirez Studios, Inc software
    update your audio drivers
    update skype software


    http://beta.skype.com/en/

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {1c549d8c, 2, 0, fffff80002ca2b13}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: 000000001c549d8c, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff80002ca2b13, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec7100
    GetUlongFromAddress: unable to read from fffff80002ec71c0
     000000001c549d8c Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiProcessExpiredTimerList+103
    fffff800`02ca2b13 0fb6432b        movzx   eax,byte ptr [rbx+2Bh]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  Smite.exe
    
    TAG_NOT_DEFINED_c000000f:  FFFFF88002F92FB0
    
    TRAP_FRAME:  fffff88002f92680 -- (.trap 0xfffff88002f92680)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000008 rbx=0000000000000000 rcx=fffffa8003d2de68
    rdx=fffffa80058f65e0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ca2b13 rsp=fffff88002f92810 rbp=fffffa80058f6010
     r8=000000000000001f  r9=0000000000000000 r10=00000000000000de
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe cy
    nt!KiProcessExpiredTimerList+0x103:
    fffff800`02ca2b13 0fb6432b        movzx   eax,byte ptr [rbx+2Bh] ds:00000000`0000002b=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c97569 to fffff80002c97fc0
    
    STACK_TEXT:  
    fffff880`02f92538 fffff800`02c97569 : 00000000`0000000a 00000000`1c549d8c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02f92540 fffff800`02c961e0 : fffffa80`05e5f160 00000000`00000000 fffffa80`0592dc60 00000000`1c549d61 : nt!KiBugCheckDispatch+0x69
    fffff880`02f92680 fffff800`02ca2b13 : fffffa80`03d1a870 00000000`00000040 00000000`00000000 00000000`000007ff : nt!KiPageFault+0x260
    fffff880`02f92810 fffff800`02ca29be : 00000001`d23e6b1f fffff880`02f92e88 00000000`0000c3de fffff880`02f67148 : nt!KiProcessExpiredTimerList+0x103
    fffff880`02f92e60 fffff800`02ca27a7 : fffff880`02f631c1 fffffa80`0000c3de fffffa80`04b85a30 00000000`000000de : nt!KiTimerExpiration+0x1be
    fffff880`02f92f00 fffff800`02c9b105 : 00000000`00000000 fffffa80`06793640 00000000`00000000 fffff880`05380db0 : nt!KiRetireDpcList+0x277
    fffff880`02f92fb0 fffff800`02c9af1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`09646be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiProcessExpiredTimerList+103
    fffff800`02ca2b13 0fb6432b        movzx   eax,byte ptr [rbx+2Bh]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KiProcessExpiredTimerList+103
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+103
    
    BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+103
    
    Followup: MachineOwner
    ---------
      My Computer


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

    I appreciate the help on this. I was able to find the audio drivers I needed. I then uninstalled and reinstalled both skype and Smite and updated both to the most current versions. This has not been very successful. I still will get BSoD frequently while playing Smite, and I have even got it several times outside of the game while just browsing the net. Any other advice would be much appreciated, as I would really prefer to be able to play this game. I have attached the most recent log.

    Thanks in advance.
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    No security software?

    Make scans with the following:

    -Kaspersky TDSSKiller

    -ESET online scanner

    In addition, you may run the malicious software removal tool and WDO:

    Microsoft Security Essentials.
    Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
    Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

    Run a full scan with both (separately) once downloaded, installed and updated.
    Perform a System File Check:
    • Click on the
    • Type CMD on Search
    • Left click and Run as Administrator
    • Type SFC /scannow

    Full tutorial here:

    Upload a screenshot of your hard disk using CrystalDiskInfo:

    Make a hard drive test from the hard drive manufacturers website:

    Run Disk Check on your hard disk for file system errors and bad sectors on it:

    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

    The goal is to test all the RAM sticks and all the motherboard slots.

    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    *Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    *If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    *If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    *If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    *If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.
      My Computer


  5. Posts : 851
    Windows 8 Professional x64
       #5
      My Computer


  6. Posts : 3
    Windows 7 64
    Thread Starter
       #6

    Alright, so I still seem to be having issues. The BSoD has been happening more frequently it seems. Sometimes during a restart, sometimes while my computer is in sleep mode overnight. I did run the driver verifier, and went ahead and picked up Microsoft Security Essentials. Here is a recent log. Hope this helps.
      My Computer


 

  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 16:39.
Find Us