BSOD - irql_not_less_or_equal


  1. Posts : 43
    Windows 7 64-bit
       #1

    BSOD - irql_not_less_or_equal


    Hello!

    I've been here before with almost the same system as last time. This time I have a new GPU, and I swapped because I had a BSOD-free month or so and so I didn't think it would be a problem as I thought my "home cures" had worked. So I reinstalled windows to clean my computer from trash programs and such as I hadn't been too careful the latest month of what I downloaded and such. And guess what? On my new installation of Windows 7 64-bit Home Premium OEM (I have a disc. But it's really a OEM license that I haven't registered, due to the bluescreens. I prolly wont until they are completely gone), with Service Pack 1 installed (I didn't have that on the install before because I hadn't registered so it classed me as illegal. But I have my cd-key here ready to register as soon as I feel confident about it) and all other fixes they would want me to install.

    After that I reboot and then install my drivers for the GeForce 285 I had put in there that replaced my old GeForce 220. I reboot once again and starts playing a game after I installed one. I think it was GTA IV if that matters.

    I get a bluescreen after playing for like an hour or so. Then they came more commonly and now I can't bare it anymore. I can't even play Magicka in windowed mode without getting a bluescreen.

    I have some dumps bundled up and some of them are not from playing any games either. I can run programs like Autodesk 3ds Max 2011 and I can sometimes get a bluescreen, though rarely.

    I now get BSOD's every time I play a game or do something that pushes the computer a bit.

    People blame the motherboard. And I do too. But can anybody read the dumps and tell me if that's the case by your experience? Last time it gave me errors of a bunch of different stuff so you could not pin down a reason.

    The system is as follows:

    Asus P6X58D Premium
    Intel i7 920 2.67 Ghz
    GeForce 285
    RAM: can't remember their names but it's 3 times 2 Gb
    Seagate Barracuda 1 Tb

    I have taken of the side of the computer to allow more air to get there as the chassis does not have adequate airflow.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    ASACPI.sys the 2005 version is a huge cause of BSOD's

       Information

    Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
    Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
    Download and install it.
    Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
    Code:
    ASACPI.sys        fffff880`0443e000    fffff880`04446000    0x00008000    0x42476c4c    28/03/2005 06:30:36
    The CPU is also blamed, if you are overclocking stop it
    Test CPU https://www.sevenforums.com/tutorials...t-prime95.html

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffff78000100320, d, 0, fffff80002ed8947}
    
    Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    Probably caused by : intelppm.sys ( intelppm+39c2 )
    
    
    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: fffff78000100320, memory referenced
    Arg2: 000000000000000d, 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: fffff80002ed8947, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd0e8
     fffff78000100320 
    
    CURRENT_IRQL:  d
    
    FAULTING_IP: 
    nt!KeUpdateRunTime+47
    fffff800`02ed8947 8b38            mov     edi,dword ptr [rax]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88002f1b940 -- (.trap 0xfffff88002f1b940)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff78000100320 rbx=0000000000000000 rcx=fffff88002f1bb00
    rdx=0000017800000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ed8947 rsp=fffff88002f1bad0 rbp=0000000000000000
     r8=fffff880009f50c0  r9=000000005bf2aca2 r10=0000000000000a35
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!KeUpdateRunTime+0x47:
    fffff800`02ed8947 8b38            mov     edi,dword ptr [rax] ds:26c0:fffff780`00100320=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ecbbe9 to fffff80002ecc640
    
    STACK_TEXT:  
    fffff880`02f1b7f8 fffff800`02ecbbe9 : 00000000`0000000a fffff780`00100320 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02f1b800 fffff800`02eca860 : 00000000`00000002 00000000`0000003a 00000000`00000004 fffff880`009ea180 : nt!KiBugCheckDispatch+0x69
    fffff880`02f1b940 fffff800`02ed8947 : fffff880`009ea180 ffff2405`00000000 00000000`00002711 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`02f1bad0 fffff800`02ed8741 : 00000000`00000000 fffff880`02f1bb80 fffff880`009ea180 00000000`00000001 : nt!KeUpdateRunTime+0x47
    fffff880`02f1bb00 fffff880`03ea69c2 : fffff800`02ed5f09 00000000`0027d3ce fffffa80`06bb9cd8 fffffa80`06c4c480 : nt!KiSecondaryClockInterrupt+0x131
    fffff880`02f1bc98 fffff800`02ed5f09 : 00000000`0027d3ce fffffa80`06bb9cd8 fffffa80`06c4c480 fffffa80`07c40ed0 : intelppm+0x39c2
    fffff880`02f1bca0 fffff800`02ec433c : fffff880`009ea180 fffff880`00000000 00000000`00000000 fffff880`04552480 : nt!PoIdle+0x52a
    fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x2c
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    intelppm+39c2
    fffff880`03ea69c2 ??              ???
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  intelppm+39c2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: intelppm
    
    IMAGE_NAME:  intelppm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd
    
    FAILURE_BUCKET_ID:  X64_0xA_intelppm+39c2
    
    BUCKET_ID:  X64_0xA_intelppm+39c2
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 43
    Windows 7 64-bit
    Thread Starter
       #3

    yowanvista said:
    ASACPI.sys the 2005 version is a huge cause of BSOD's

       Information

    Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
    Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
    Download and install it.
    Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
    Code:
    ASACPI.sys        fffff880`0443e000    fffff880`04446000    0x00008000    0x42476c4c    28/03/2005 06:30:36
    The CPU is also blamed, if you are overclocking stop it
    Test CPU https://www.sevenforums.com/tutorials...t-prime95.html

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffff78000100320, d, 0, fffff80002ed8947}
    
    Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    Probably caused by : intelppm.sys ( intelppm+39c2 )
    
    
    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: fffff78000100320, memory referenced
    Arg2: 000000000000000d, 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: fffff80002ed8947, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd0e8
     fffff78000100320 
    
    CURRENT_IRQL:  d
    
    FAULTING_IP: 
    nt!KeUpdateRunTime+47
    fffff800`02ed8947 8b38            mov     edi,dword ptr [rax]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88002f1b940 -- (.trap 0xfffff88002f1b940)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff78000100320 rbx=0000000000000000 rcx=fffff88002f1bb00
    rdx=0000017800000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ed8947 rsp=fffff88002f1bad0 rbp=0000000000000000
     r8=fffff880009f50c0  r9=000000005bf2aca2 r10=0000000000000a35
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!KeUpdateRunTime+0x47:
    fffff800`02ed8947 8b38            mov     edi,dword ptr [rax] ds:26c0:fffff780`00100320=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ecbbe9 to fffff80002ecc640
    
    STACK_TEXT:  
    fffff880`02f1b7f8 fffff800`02ecbbe9 : 00000000`0000000a fffff780`00100320 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02f1b800 fffff800`02eca860 : 00000000`00000002 00000000`0000003a 00000000`00000004 fffff880`009ea180 : nt!KiBugCheckDispatch+0x69
    fffff880`02f1b940 fffff800`02ed8947 : fffff880`009ea180 ffff2405`00000000 00000000`00002711 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`02f1bad0 fffff800`02ed8741 : 00000000`00000000 fffff880`02f1bb80 fffff880`009ea180 00000000`00000001 : nt!KeUpdateRunTime+0x47
    fffff880`02f1bb00 fffff880`03ea69c2 : fffff800`02ed5f09 00000000`0027d3ce fffffa80`06bb9cd8 fffffa80`06c4c480 : nt!KiSecondaryClockInterrupt+0x131
    fffff880`02f1bc98 fffff800`02ed5f09 : 00000000`0027d3ce fffffa80`06bb9cd8 fffffa80`06c4c480 fffffa80`07c40ed0 : intelppm+0x39c2
    fffff880`02f1bca0 fffff800`02ec433c : fffff880`009ea180 fffff880`00000000 00000000`00000000 fffff880`04552480 : nt!PoIdle+0x52a
    fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x2c
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    intelppm+39c2
    fffff880`03ea69c2 ??              ???
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  intelppm+39c2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: intelppm
    
    IMAGE_NAME:  intelppm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd
    
    FAILURE_BUCKET_ID:  X64_0xA_intelppm+39c2
    
    BUCKET_ID:  X64_0xA_intelppm+39c2
    
    Followup: MachineOwner
    ---------
    Okey I'll try and do that!

    I'm not overclocking. I'm actually struggling to keep it from doing just that. BIOS resets it's settings about CPU speed and such sometimes when I get these errors and then I have to set it not do automaticly clock it or whatever the settings say. But I'll do that and see what's happens, thanks!
      My Computer


  4. Posts : 43
    Windows 7 64-bit
    Thread Starter
       #4

    So... that didn't help. Still getting the bluescreens. Though it took some time to actually get it instead of just crashing once i start something, it now took an hour or so.

    Dump is here and I'm now going to do the CPU test.
      My Computer


  5. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #5

    SimonWithTheHat said:
    So... that didn't help. Still getting the bluescreens. Though it took some time to actually get it instead of just crashing once i start something, it now took an hour or so.

    Dump is here and I'm now going to do the CPU test.
    Do you have any Zone Alarm software, if so remove them as they tend to cause BugCheck 7F

    If you have no such software run driver verifier(it will cause BSODs in order to identify the faulting driver) and upload the new dumps created dumps

    Driver Verifier - Enable and Disable
      My Computer


  6. Posts : 43
    Windows 7 64-bit
    Thread Starter
       #6

    yowanvista said:
    SimonWithTheHat said:
    So... that didn't help. Still getting the bluescreens. Though it took some time to actually get it instead of just crashing once i start something, it now took an hour or so.

    Dump is here and I'm now going to do the CPU test.
    Do you have any Zone Alarm software, if so remove them as they tend to cause BugCheck 7F

    If you have no such software run driver verifier(it will cause BSODs in order to identify the faulting driver) and upload the new dumps created dumps

    Driver Verifier - Enable and Disable
    I don't even know what Zone Alarm is so I doubt I have it. The CPU is getting overheated when I do that Stress test. Is this something that can cause these bluescreens?

    On the other hand it doubt it for the reason that the bluescreens happens randomly in games that doesn't even require much power. I can play the new Crysis 2 Demo without problem (so far) but a little indie game crashes the computer.. it annoys me.

    Now I'm rebooting to apply those verifier settings. I'll be back whenever I get the settings reseted so I can boot it normally again after the crash!

    EDIT: Back now. I booted twice and got two dumps in the following rar.
    Last edited by SimonWithTheHat; 06 Mar 2011 at 14:18. Reason: Adding dumps and info instead of posting again.
      My Computer


  7. Posts : 43
    Windows 7 64-bit
    Thread Starter
       #7

    bump!

    so i rendered a movie now in Adobe premiere and the temperature got up to 100 C, where CPU Temp would ask me if he would shut it down for me. I said no until I was done because I didn't want to start over but I kept watching so it didn't get above 100. Which it didn't. Is there a way to configure the CPU fan or something so it cools some more or is it already on full throttle automaticly?
      My Computer


  8. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #8

    SimonWithTheHat said:
    bump!

    so i rendered a movie now in Adobe premiere and the temperature got up to 100 C, where CPU Temp would ask me if he would shut it down for me. I said no until I was done because I didn't want to start over but I kept watching so it didn't get above 100. Which it didn't. Is there a way to configure the CPU fan or something so it cools some more or is it already on full throttle automaticly?
    The CPU should never have got above 80C.
    This suggest bad airflow in your case, defects in the CPU, insufficient cooler(s) or bad thermal paste
      My Computer


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

    yowanvista said:
    SimonWithTheHat said:
    bump!

    so i rendered a movie now in Adobe premiere and the temperature got up to 100 C, where CPU Temp would ask me if he would shut it down for me. I said no until I was done because I didn't want to start over but I kept watching so it didn't get above 100. Which it didn't. Is there a way to configure the CPU fan or something so it cools some more or is it already on full throttle automaticly?
    The CPU should never have got above 80C.
    This suggest bad airflow in your case, defects in the CPU, insufficient cooler(s) or bad thermal paste
    Okey. I've been looking around in the settings for the CPU now and I've tried setting everything that was on auto clock to something standard and I'll see what happens.
      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 08:20.
Find Us