BSOD IRQL_NOT_LESS and SYSTEM_THREAD_EXCEPTION

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 64bit
       #1

    BSOD IRQL_NOT_LESS and SYSTEM_THREAD_EXCEPTION


    Hello, I am making this post because I've been getting BSOD's a lot more often than before. I started getting them about 4 months ago, and I ran memtest for about 3 hours as well as WD Diagnostic with no errors. The oldest components of my PC are the HD and RAM, which are bout 4 years old. My PSU is an HX750 which is 1 year old. No overclocks are being done, and my CPU is water cooled, so temps, I'm pretty sure is not a problem. My GPU is an XFX 6970, which never goes above 64C. The most common time I get the BSOD's is around 2-4 hours of game play in CS:GO, and randomly after alt-tabbing to the desktop while playing. Very rarely do I crash while not playing. I honestly can not figure out what is causing this, so any help would be of great help. Thanks in advance. :)
      My Computer


  2. Posts : 9
    Windows 7 64bit
    Thread Starter
       #2

    It seems like I missed a few files, apparently, here they are. Sorry about that.
      My Computer


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

    Bump
      My Computer


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

    I just got another BSOD while playing CS:GO, please help. I don't think I've ever seen this BSOD, its TIMER_OR_DPC_INVALID.
      My Computer


  5. Posts : 9
    Windows 7 64bit
    Thread Starter
       #5

    Bump
      My Computer


  6. Posts : 9
    Windows 7 64bit
    Thread Starter
       #6

    Could anyone please help? I've ran some memtests a few times with no errors. Please help, I keep randomly getting BSODs.
      My Computer


  7. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #7

    Give me 15 mins to finish my dinner and I'll take a look - apologies you had to wait this long.
      My Computer


  8. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #8

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff8002326d5f2, 2, 8, fffff8002326d5f2}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffff8002326d5f2, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff8002326d5f2, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034af100
    GetUlongFromAddress: unable to read from fffff800034af1c0
     fffff8002326d5f2 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    +5cfba30
    fffff800`2326d5f2 ??              ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  MSIAfterburner
    Uninstall MSIAfterburner, reset any overclocks back to default and ensure the video driver is up-to-date. Monitor for further BSOD and post findings please.
      My Computer


  9. Posts : 9
    Windows 7 64bit
    Thread Starter
       #9

    I really appreciate it! I'll have msi deleted. I'll post any other problems I get. Again, I appreciate the help! Thank you.
      My Computer


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

    I just got another BSOD while playing CS:GO... Starting the year pretty well it seems hahaha. I have never seen this one before. Any help?
      My Computer


 
Page 1 of 2 12 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 11:59.
Find Us