TechSpot

IRQL_Driver_not_less_or_equal error using Vista

By bsod187
Mar 16, 2013
Post New Reply
  1. I keep getting the IRQL_DRiver not less or equal error about 20 minutes after booting.

    I uploaded a minidump of the error files, please help!
     

    Attached Files:

  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    The minidump is corrupt. We can't read it:oops:
     
  3. bsod187

    bsod187 TS Rookie Topic Starter Posts: 19

    What would cause the file to be corrupt?
     
  4. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    What antivirus program are you running? If you get another BSOD try going after a new minidump
     
  5. bsod187

    bsod187 TS Rookie Topic Starter Posts: 19

    I do not currently have an antivirus program installed, here is the latest minidump....
     

    Attached Files:

  6. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    This minidump is also corrupt. You may have a virus or other type of malware infection
     
  7. bsod187

    bsod187 TS Rookie Topic Starter Posts: 19

    What do you suggest I try?
     
  8. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

  9. bsod187

    bsod187 TS Rookie Topic Starter Posts: 19

    Could it be the program I am using to collect the dump, Is there another way to collect the dump?
     
  10. bsod187

    bsod187 TS Rookie Topic Starter Posts: 19

    Actually I was able to use a different program and I got the following output:

    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Wed 3/20/2013 2:54:13 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini031913-02.dmp
    This was probably caused by the following module: luafv.sys (luafv+0xB3E3)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820280D6, 0xFFFFFFFF9955FAE8, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\luafv.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: LUA File Virtualization Filter Driver
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Tue 3/19/2013 9:35:13 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini031913-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x271AF9)
    Bugcheck code: 0x10000050 (0xFFFFFFFF9C476014, 0x0, 0xFFFFFFFF82271AF9, 0x0)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 3/19/2013 5:20:37 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini031813-02.dmp
    This was probably caused by the following module: fltmgr.sys (fltmgr+0x4F10)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820765A4, 0xFFFFFFFF9B4B23E8, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Filesystem Filter Manager
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Mon 3/18/2013 1:09:37 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini031813-01.dmp
    This was probably caused by the following module: fltmgr.sys (fltmgr+0x4F10)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820765A4, 0xFFFFFFFF9AFD33E8, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Filesystem Filter Manager
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sun 3/17/2013 6:02:07 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini031713-01.dmp
    This was probably caused by the following module: unknown_module_89fa9000.sys (Unknown_Module_89fa9000+0x5053)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF89FAE053, 0xFFFFFFFF9D538A3C, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_89fa9000.sys .
    Google query: unknown_module_89fa9000.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



    On Sun 3/17/2013 3:09:34 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini031613-04.dmp
    This was probably caused by the following module: tcpip.sys (tcpip+0x5FEBC)
    Bugcheck code: 0x100000D1 (0x4, 0x2, 0x1, 0xFFFFFFFF8ECB7EBC)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: TCP/IP Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sat 3/16/2013 6:11:34 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini031613-03.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xB1423)
    Bugcheck code: 0x1000000A (0xFFFFFFFFA08D8004, 0x2, 0x1, 0xFFFFFFFF820B1423)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 3/16/2013 5:51:28 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini031613-02.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xA9C92)
    Bugcheck code: 0x100000D1 (0x0, 0x2, 0x8, 0x0)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 3/16/2013 5:41:48 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini031613-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xA91B0)
    Bugcheck code: 0x1000000A (0x0, 0x1B, 0x1, 0xFFFFFFFF820A91B0)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 3/9/2013 7:03:29 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini030913-02.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xA92C2)
    Bugcheck code: 0x1000000A (0x0, 0x1B, 0x1, 0xFFFFFFFF820A92C2)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 3/9/2013 5:07:19 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini030913-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xA91A4)
    Bugcheck code: 0x1000000A (0xF60068, 0x1B, 0x1, 0xFFFFFFFF820A91A4)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 3/4/2013 3:22:49 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini030313-03.dmp
    This was probably caused by the following module: unknown_module_82000000 (nt+0xA92C2)
    Bugcheck code: 0x1000000A (0x1, 0x1B, 0x1, 0xFFFFFFFF820A92C2)
    Error: CUSTOM_ERROR
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_82000000 .
    Google query: unknown_module_82000000 CUSTOM_ERROR



    On Sun 3/3/2013 7:42:01 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini030313-02.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xA91AB)
    Bugcheck code: 0x1000000A (0x0, 0x1B, 0x0, 0xFFFFFFFF820A91AB)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 3/3/2013 5:56:09 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini030313-01.dmp
    This was probably caused by the following module: netio.sys (NETIO+0x672A)
    Bugcheck code: 0x100000D1 (0xE701, 0x2, 0x1, 0xFFFFFFFF89DCD72A)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\drivers\netio.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Network I/O Subsystem
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sun 3/3/2013 4:04:16 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\Mini030213-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xF4820)
    Bugcheck code: 0x1000000A (0x0, 0x1B, 0x1, 0xFFFFFFFF820F4820)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    20 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    unknown_module_82000000
    unknown_module_89fa9000.sys

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
     
  11. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    You have so many non-discript errors, in addition of not having any antivirus or other anti-malware programs installed, that I still recommend that you post this where I suggested
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...