Bsod irql not less or equal

Page 1 of 4 123 ... LastLast

  1. Posts : 16
    Windows 7 home premium 64bits
       #1

    Bsod irql not less or equal


    Hi everybody,

    This is my first post and I usually speak french, so sorry if my english isn't really good.

    I have a BSOD at start up. Sometime, I am able to start windows in Safe mode but not always. My computer is a Gateway and I have the windows that came already in it. My computer is something like 1 week before the end of the warranty but Gateway are juste able to tell me to format it. I would like to repair it without loosing everything I have in it. Any Clues? I was able to start whocrashed and here is what it told me:

    windows version: Windows 7 , 6.1, build: 7600
    windows dir: C:\Windows
    CPU: AuthenticAMD AMD Turion(tm) II Dual-Core Mobile M500 AMD586, level: 16
    2 logical processors, active mask: 3
    RAM: 4024795136 total
    VM: 2147352576, free: 2005176320


    Crash Dump Analysis


    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.


    On Wed 1/26/2011 9:20:31 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012611-21387-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0x3D (0xFFFFF880009F7FF0, 0x0, 0x0, 0xFFFFF88000C1AE56)
    Error: INTERRUPT_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check appears very infrequently.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 1/26/2011 12:59:15 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012611-20997-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CA05A1, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 1/26/2011 12:50:34 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-25880-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88005DA0698, 0xFFFFF88005D9FF00, 0xFFFFF8800124D620)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Système d’exploitation Microsoft® Windows®
    company: Microsoft Corporation
    description: Pilote du système de fichiers NT
    Bug check description: This indicates a problem occurred in the NTFS file system.
    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 which cannot be identified at this time.


    On Wed 1/26/2011 12:32:29 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-20794-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0x18AD5C)
    Bugcheck code: 0xD1 (0xFFFFF9600021AD5C, 0xA, 0x0, 0xFFFFF88000FBDADF)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\win32k.sys
    product: Système d’exploitation Microsoft® Windows®
    company: Microsoft Corporation
    description: Pilote Win32 multi-utilisateurs
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 which cannot be identified at this time.


    On Wed 1/26/2011 12:29:19 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-21777-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88004C74698, 0xFFFFF88004C73F00, 0xFFFFF8800124C620)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Système d’exploitation Microsoft® Windows®
    company: Microsoft Corporation
    description: Pilote du système de fichiers NT
    Bug check description: This indicates a problem occurred in the NTFS file system.
    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 which cannot be identified at this time.


    On Wed 1/26/2011 12:14:09 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-27986-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0xA (0xFFFFFA82C64CACF8, 0x2, 0x0, 0xFFFFF80002C13557)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 1/26/2011 12:11:12 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-20046-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0xD1 (0x60, 0xA, 0x0, 0xFFFFF88000C0AADF)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 1/26/2011 12:08:37 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-21465-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70710)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 1/26/2011 12:05:11 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-17940-01.dmp
    This was probably caused by the following module: amdsata.sys (amdsata+0xAE56)
    Bugcheck code: 0xD1 (0x61, 0xA, 0x1, 0xFFFFF88000DEDE56)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\amdsata.sys
    product: AHCI 1.2 Device Driver
    company: Advanced Micro Devices
    description: AHCI 1.2 Device Driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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: amdsata.sys (AHCI 1.2 Device Driver, Advanced Micro Devices).
    Google query: amdsata.sys Advanced Micro Devices DRIVER_IRQL_NOT_LESS_OR_EQUAL




    On Tue 1/25/2011 11:51:04 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-19624-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0xA (0xFFFFFA82C4FBC750, 0x2, 0x0, 0xFFFFF80002021557)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Tue 1/25/2011 11:30:24 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-20779-01.dmp
    This was probably caused by the following module: unknown_module_00000000_00000001.sys (Unknown_Module_00000000_00000001+0x9)
    Bugcheck code: 0xD1 (0x76F28000, 0x2, 0x1, 0xFFFFF8800101C2E4)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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_00000000_00000001.sys .
    Google query: unknown_module_00000000_00000001.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL




    On Tue 1/25/2011 11:28:56 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-19203-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70710)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Tue 1/25/2011 11:27:05 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-23914-01.dmp
    This was probably caused by the following module: storport.sys (storport+0x12E4)
    Bugcheck code: 0xD1 (0x7719D000, 0x2, 0x1, 0xFFFFF8800105D2E4)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\storport.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Storage Port Driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 which cannot be identified at this time.


    On Tue 1/25/2011 11:25:15 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-22011-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0xA (0xFFFFFA82C63881C0, 0x2, 0x0, 0xFFFFF80002C21557)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Tue 1/25/2011 11:10:51 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012511-20654-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0x3D (0xFFFFF880036B5110, 0x0, 0x0, 0xFFFFF88000C4FE56)
    Error: INTERRUPT_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check appears very infrequently.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



    Thanks for your help!
      My Computer


  2. Posts : 6,668
    Windows 7 x64
       #2

    https://www.sevenforums.com/crashes-d...tructions.html

    I appreciate your effort, but actually having access to the actual dump files seems a lot more helpful to the star troubleshooters here.
      My Computer


  3. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #3

    Maguscreed is spot on. We do need the files.
      My Computer


  4. Posts : 16
    Windows 7 home premium 64bits
    Thread Starter
       #4

    Well, I'm not at home right now but will try to post them when I'll be back.

    Thanks for your time!
      My Computer


  5. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #5

    Very good, Jubin. We will be here. :)
      My Computer


  6. Posts : 16
    Windows 7 home premium 64bits
    Thread Starter
       #6

    Hello again,

    Here you are!

    I hope that with that someone will be able to help me.

    If you need anything else, let me know! I just saw that there is other recommandation on the BSOD page, I will try to open the computer again and use System File Collection app. I will post it if someone need more informations

    Thanks again for your time!
      My Computer


  7. Posts : 6,668
    Windows 7 x64
       #7

    I'm admittedly not that great with dump files, but what I'm seeing is a failure in
    amdsata.sys / AtBroker.exe

    This could be caused if your volume shadow copy service is not running.
    Sadly that is the only cause I know off hand.
      My Computer


  8. Posts : 16
    Windows 7 home premium 64bits
    Thread Starter
       #8

    Maguscreed said:
    I'm admittedly not that great with dump files, but what I'm seeing is a failure in
    amdsata.sys / AtBroker.exe

    This could be caused if your volume shadow copy service is not running.
    Sadly that is the only cause I know off hand.
    Maybe it's my english or maybe it's my computer knowledge but I really don't know what is the shadow copy service and how I can make it run.

    Anyway, I will soon be able to post the other files some of you may need.

    Thanks for your help Maguscreed
      My Computer


  9. Posts : 6,668
    Windows 7 x64
       #9

    right click my computer , then choose manage, when that window opens on the left hand side at the bottom click services and applications, then in the window on the right double click services. Scroll until you locate the volume shadow copy service. Right click it, and choose start. Then right click it again go to properties and change the startup type to automatic (delayed start) using the drop down menu.

    I'm not 100% this will fix your problem, but it won't hurt anything either.
      My Computer


  10. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #10

    Jubin, thank you for the dump files and I will look at them. Please follow the instructions in this tutorial and upload all of the files to us.

    https://www.sevenforums.com/crashes-d...tructions.html

    I looked at your four most recent dumps. All four blame Windows system files, which are very unlikely to be the real cause.
    Bugcheck 3D, (2X), INTERRUPT_EXCEPTION_NOT_HANDLED. BSOD Index.

    Bugcheck A (2X), IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
    Because I do not have all of the files, I do not know what antivirus program you are running; so I can't address that. I do find out of date drivers loaded on your system. Outdated drivers can and do cause BSOD's. The one in bold font is quite obsolete; it is an XP driver. Update the following drivers through the links privided. If there is no update, uninstall the software/hardware the drivers are associated with.
    amdsata.sys Tue Apr 28 19:33:25 2009 - AMD AHCI 1.2 Device Driver. AMD.com | Support & Downloads.

    CAX_CNXT.sys Fri Feb 13 16:19:32 2009 - Conexant Modem Audio. Conexant: Support

    CAX_DPV.sys Fri Feb 13 16:24:50 2009 - Conexant Modem. Conexant: Support

    CAXHWAZL.sys Fri Feb 13 16:20:54 2009 - Conexant Modem. Conexant: Support

    k57nd60a.sys Sat Jun 20 07:34:49 2009 - Broadcom NetLink (TM) Gigabit Ethernet driver. Broadcom.com - Downloads & Support.

    mdmxsdk.sys Mon Jun 19 17:27:26 2006 - Conexant Modem Diagnostic Interface x86 Driver. Conexant: Support

    NTIDrvr.sys Tue Mar 24 23:09:39 2009 - NTI CD-ROM Filter Driver by NewTech Infosystems (likely a part of Acer Empowering Technology). OEM none at NTI - Support - OEM Resources - DVD Burning Software, Data Backup Software, CD Burning, Blu-ray Burning Software - Official Site.

    UBHelper.sys Mon Apr 27 04:48:19 2009 - NTI CD & DVD-Maker or NTI Backup NOW! or NTI CD-Maker by NewTech Infosystems (usually in Acer Empowering Technology). OEM none at NTI - Support - OEM Resources - DVD Burning Software, Data Backup Software, CD Burning, Blu-ray Burning Software - Official Site.

    usbfilter.sys Fri Apr 03 07:39:51 2009 - AMD USB Filter Driver (likely part of the chipset drivers). AMD.com | Support & Downloads.

    XAudio64.sys Wed Apr 29 14:21:07 2009 - Conexant Modem Audio Conexant Modem Audio. Conexant: Support.
    Update these drivers, reboot and see how your system runs. Please post back and let us know. If you get another BSOD, upload it and we will go from there. And please upload the rest of the files by following the instructions in the tutorial I linked to.
    Last edited by CarlTR6; 27 Jan 2011 at 20:39.
      My Computer


 
Page 1 of 4 123 ... 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 10:23.
Find Us