BSOD Driver_IRQL_not_lless_or_equal

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7
       #1

    BSOD Driver_IRQL_not_less_or_equal


    I have recently started receiving BSOD crashes for the driver issue listed above.

    I've attached my dump files in a zip. Can anyone assist me with figuring this out?
    Last edited by kimgesch; 22 May 2010 at 08:46. Reason: correct error in title
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    7 memory dump files - all dated from today.
    4 different STOP errors, blaming 7 different causes

    Normally I'd say this was a hardware problem - but all 4 STOP errors seem to relate to driver issues.

    And, the only non-Windows driver blamed is IDSvia64.sys - a component of your Norton/Symantec protection software. Please do the following:
    Anti-Virus Removal:
    Please do the following:
    - download a free antivirus for testing purposes: Free AntiVirus
    - uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
    - remove any remnants of Norton using this free tool: Download and run the Norton Removal Tool
    - IMMEDIATELY install and update the free antivirus
    - check to see if this fixes the BSOD's
    Summary of the BSOD's:
    Code:
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 09:13:14.613 2010 (GMT-4)
    System Uptime: 0 days 0:12:37.611
    BugCheck D1, {fffff7ffe2ae2ac3, e, 8, fffff7ffe2ae2ac3}
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 08:59:20.338 2010 (GMT-4)
    System Uptime: 0 days 0:17:17.335
    BugCheck BE, {fffff880042dd2c0, 800000007b044121, fffff88004a253d0, b}
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::Present+2290 )
    BUGCHECK_STR:  0xBE
    PROCESS_NAME:  Ribbons.scr
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 08:41:32.653 2010 (GMT-4)
    System Uptime: 0 days 0:00:23.261
    BugCheck A, {fffff47fffffffe0, 2, 1, fffff80002aafe7e}
    Probably caused by : CLFS.SYS ( CLFS!CClfsLogFcbPhysical::MapCacheData+105 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 08:37:43.368 2010 (GMT-4)
    System Uptime: 0 days 0:16:43.975
    BugCheck A, {fffff47fffffffe0, 2, 1, fffff80002ae7e7e}
    Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  dwm.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 08:20:03.272 2010 (GMT-4)
    System Uptime: 0 days 0:04:57.270
    BugCheck 50, {fffff901c1ffe894, 0, fffff96000085e87, 5}
    Probably caused by : win32k.sys ( win32k!draw_clrt_nf_ntb_o_to_temp_start+7b )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  iexplore.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 08:14:19.498 2010 (GMT-4)
    System Uptime: 0 days 0:02:33.495
    BugCheck 50, {ffffffffffffff8c, 1, fffff80002c062df, 0}
    Probably caused by : hardware ( nt!ExFreePool+961 )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  svchost.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 08:11:01.044 2010 (GMT-4)
    System Uptime: 0 days 9:55:00.042
    BugCheck A, {fffff47fffffffe0, 2, 1, fffff80002ae9e7e}
    *** WARNING: Unable to verify timestamp for IDSvia64.sys
    *** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
    Probably caused by : IDSvia64.sys ( IDSvia64+2d642 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
      My Computer


  3. Posts : 9
    Windows 7
    Thread Starter
       #3

    Thanks, I did the steps you recommended... but got another BSOD. here is the latest files from after I removed Norton.
    Last edited by kimgesch; 22 May 2010 at 14:25. Reason: Changed file
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    Sometimes there's multiple problems, and sometimes the memory dumps don't point to the proper things.
    So we'll run these memory dumps to see what we get....

    One of the errors points to ReadyBoost. Are you using a ReadyBoost flash drive in one of your USB ports?
    Do you have any other devices plugged into the USB ports?

    Beyond that, the problems seem to be hardware (the last 4 memory dump files had 3 different STOP errors and blamed 3 different causes). So, please run these free hardware tests:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
    Summary of the BSOD's:
    Code:
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 15:19:59.236 2010 (GMT-4)
    System Uptime: 0 days 0:00:37.859
    BugCheck 1, {73a32dd9, 0, ffff, fffff880047c0ca0}
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
    BUGCHECK_STR:  0x1
    PROCESS_NAME:  AvastSvc.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 15:18:14.221 2010 (GMT-4)
    System Uptime: 0 days 0:01:01.829
    BugCheck 1000007E, {ffffffffc000001d, fffff880018cf44c, fffff880035b67e8, fffff880035b6050}
    Probably caused by : rdyboost.sys ( rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeRedistribute+3c )
    BUGCHECK_STR:  0x7E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 15:16:28.266 2010 (GMT-4)
    System Uptime: 0 days 0:01:34.264
    BugCheck 1000007E, {ffffffffc0000005, fffff80002a6f98c, fffff88003392198, fffff88003391a00}
    Probably caused by : ntkrnlmp.exe ( nt!EtwpFlushActiveBuffers+220 )
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 22 15:08:25.480 2010 (GMT-4)
    System Uptime: 0 days 0:23:55.478
    BugCheck A, {fffff47fffffffe0, 2, 1, fffff80002a9ce7e}
    Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  svchost.exe
      My Computer


  5. Posts : 9
    Windows 7
    Thread Starter
       #5

    Thanks again,

    I ran the Hitachi DFT and received the disposition code 0x00. I still have to run the memory diagnostics. As far as the online scan, my USB wireless adapter is no longer being recognized, even though its showing in the device manager.
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    kimgesch said:
    Thanks again,

    I ran the Hitachi DFT and received the disposition code 0x00. I still have to run the memory diagnostics. As far as the online scan, my USB wireless adapter is no longer being recognized, even though its showing in the device manager.

    We need the actual DMP file created when the computer crashed. Use these to find and upload them to us. https://www.sevenforums.com/crash-loc...d-problem.html


    Thanks
    '
    Ken
      My Computer


  7. Posts : 9
    Windows 7
    Thread Starter
       #7

    I tried to get the dump files, however when I reboot, windows automatically goes into Start-up Repair (even in safe mode) then it goes to a BSOD again. The latest one said Interrupt_Exception_not_handled. I was able to run the memory test mentioned, and it said 419 under errors. Am I safe to assume the memory is causing this?
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    Yep, follow the instructions here to figure out which sticks are bad and which are good (start with Step 7): Memory Diagnostics
      My Computer


  9. Posts : 9
    Windows 7
    Thread Starter
       #9

    Thanks again!

    It looks like one of the memory sockets is bad on the mobo.


    it still won't boot though, it goes into start-up repair and then can't complete. After that it just asks to shut down the PC.
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    kimgesch said:
    I tried to get the dump files, however when I reboot, windows automatically goes into Start-up Repair (even in safe mode) then it goes to a BSOD again. The latest one said Interrupt_Exception_not_handled. I was able to run the memory test mentioned, and it said 419 under errors. Am I safe to assume the memory is causing this?
    First try a safe boot (F8)

    I dont know where those errors were generated but I do suspect you have some problem. Is it memory? not sure
      My Computer


 
Page 1 of 2 12 LastLast

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 02:41.
Find Us