Error: IRQL_NOT_LESS_OR_EQUAL Error: CRITICAL_OBJECT_TERMINATION


  1. Posts : 11
    Windows 7 Home premium
       #1

    Error: IRQL_NOT_LESS_OR_EQUAL Error: CRITICAL_OBJECT_TERMINATION


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

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sat 22.8.2015 10:49:26 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082215-24601-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
    Bugcheck code: 0xA (0xFFFFFA8022B02010, 0x2, 0x1, 0xFFFFF800031872E6)
    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 that cannot be identified at this time.



    On Sat 22.8.2015 10:49:26 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x24A8B)
    Bugcheck code: 0xA (0xFFFFFA8022B02010, 0x2, 0x1, 0xFFFFF800031872E6)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    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 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 22.8.2015 3:32:52 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082215-34679-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005D01B10, 0xFFFFFA8005D01DF0, 0xFFFFF80003384E70)
    Error: CRITICAL_OBJECT_TERMINATION
    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 process or thread crucial to system operation has unexpectedly exited or been terminated.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    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 18.8.2015 15:28:35 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081815-31793-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008E72328, 0xFFFFF88008E71B80, 0xFFFFF880012B49DD)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® -käyttöjärjestelmä
    company: Microsoft Corporation
    description: NT File System Driver
    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 that cannot be identified at this time.

    i cant figure out is that problem RAM, HDD, GPU or drivers.this happens always when computer is sleepmode and i wake it up. runned memtest no errors, crystaldiskinfo was ok, gpu not overheating. so what is next step what i have to do?
    thanks
      My Computer


  2. Posts : 2,781
    Windows 10 Pro x64
       #2

    Hey there!
    Code:
    BugCheck A, {fffffa8022b02010, 2, 1, fffff800031872e6}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53 )
    Code:
    BugCheck F4, {3, fffffa8005d01b10, fffffa8005d01df0, fffff80003384e70}
    
    Probably caused by : csrss.exe
    Run sfc /scannow and chkdsk /r.
    Install the latest updates from Windows Update.

    Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

    SFC /SCANNOW Command - System File Checker

    Update your DirectX drivers.

    There's an 0xF4 code in your bugchecks. This could mean that there's a virus, a failing harddrive, failing RAM stick/s. Run SeaTools(DO NOT RUN FOR SSDS) SeaTools for DOS and Windows - How to Use Also run MemTest86+ for 8 passes. It must be MemTest86+. RAM - Test with Memtest86+ Scan your computer for viruses using Malwarebytes. Malwarebytes Anti-Malware Free
      My Computer


  3. Posts : 11
    Windows 7 Home premium
    Thread Starter
       #3

    seems like this cpu and ram was overclocked. so i set bios to default settings and no problems so far. thaks for fast reply.
      My Computer


  4. Posts : 2,781
    Windows 10 Pro x64
       #4

    No problem! It's my duty to help!
      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 13:52.
Find Us