locked
Computer Constantly Crashing [0x00000019 , 0x000000F4 , 0x00000024 , 0x000000BE , 0x0000001A] with Dump Files RRS feed

  • Question

  • New netbook. Has had problems with crashing and rebooting instances. Programs often "Not Respond". 

     

    http://cid-910834cef0fd2a0b.skydrive.live.com/redir.aspx?resid=910834CEF0FD2A0B!3505&authkey=RsRGUyoSOYY%24

     

    I look on Event Viewer and I see 5 critical errors, along with several "errors" and "warnings" 

     

    criticals errors say "kernal-power" event ID 41 task category (63)

     

    I have a lot of Service Control Errors as well (which are the level of "error")

    Sunday, November 21, 2010 2:56 AM

Answers

  • The error "event ID 41 task" has so many different scenarios.

    Go to this Microsoft Support link and check which is your scenario.

     

    I saw a lot of people having this issue found that the problem was the driver.

    Maybe you might wanna check the updates for drivers (most OEM Vendors posts their latest version of driver)


    • Marked as answer by Arthur Xie Friday, December 3, 2010 3:50 AM
    Sunday, November 21, 2010 5:18 AM
  • MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 00061940, A PDE has been unexpectedly invalidated.

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0x1a_61940_nt!MiSwapWslEntries+59

    ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) - An attempt was made to write to readonly memory.

    NTFS_FILE_SYSTEM (24)

    This indicates a problem occurred in ntfs.sys , the driver file that allows the system to read and write to NTFS drives.

    Cause

    One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

    Resolution

    To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

    Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition .


    STACK_TEXT: 
    a39aeaa4 87f319aa ac449cdc ac449cb0 ac449cb0 nt!RtlSplay+0xd3
    a39aeabc 87f34546 a3d20e7c 00000020 ac449b08 Ntfs!NtfsInsertNameLink+0xaf
    a39aead0 87f13b5e ac449cb0 00006a20 2477c081 Ntfs!NtfsInsertPrefix+0x33
    a39aebf4 87f2746c 8441ed60 86ad74b0 a3d20d08 Ntfs!NtfsOpenFile +0x93e
    a39aecdc 87ead244 8441ed60 86ad74b0 ae511238 Ntfs!NtfsCommonCreate+0xd84
    a39aed1c 81c8611e ae5111d0 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20


    CRITICAL_OBJECT_TERMINATION (f4)
    - A process or thread crucial to system operation has unexpectedly exited or been terminated.

    STACK_TEXT: 
    8ec56c9c 81f1e0d7 000000f4 00000003 86d1f760 nt!KeBugCheckEx+0x1e
    8ec56cc0 81ea1ed2 81e6add0 86d1f8cc 86d1f9d0 nt!PspCatchCriticalBreak+0x71
    8ec56cf0 81ea3d6f 86d1f760 86eae528 c0000005 nt!PspTerminateAllThreads+0x2d
    8ec56d24 81c8544a ffffffff c0000005 002fe7a0 nt!NtTerminateProcess+0x1a2
    8ec56d24 771b64f4 ffffffff c0000005 002fe7a0 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    002fe7a0 00000000 00000000 00000000 00000000 0x771b64f4


    FAILURE_BUCKET_ID:  0xF4_e_IMAGE__(M___

    BUCKET_ID:  0xF4_e_IMAGE__(M___

    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 00000003, the pool freelist is corrupt.


    MODULE_NAME: Pool_Corruption

    FAILURE_BUCKET_ID:  0x19_3_nt!ExDeferredFreePool+336



    So it looks like your RAM is damaged. Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2] to do this), reboot your PC and scan your RAM 4-5hours for errors. If it detects errors, replace the faulty RAM. Also run chkdsk to check your HDD.

    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
    [2] http://www.imgburn.com/index.php?act=download


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Arthur Xie Friday, December 3, 2010 3:50 AM
    Sunday, November 21, 2010 12:07 PM

All replies

  • The error "event ID 41 task" has so many different scenarios.

    Go to this Microsoft Support link and check which is your scenario.

     

    I saw a lot of people having this issue found that the problem was the driver.

    Maybe you might wanna check the updates for drivers (most OEM Vendors posts their latest version of driver)


    • Marked as answer by Arthur Xie Friday, December 3, 2010 3:50 AM
    Sunday, November 21, 2010 5:18 AM
  • MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 00061940, A PDE has been unexpectedly invalidated.

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0x1a_61940_nt!MiSwapWslEntries+59

    ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) - An attempt was made to write to readonly memory.

    NTFS_FILE_SYSTEM (24)

    This indicates a problem occurred in ntfs.sys , the driver file that allows the system to read and write to NTFS drives.

    Cause

    One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

    Resolution

    To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

    Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition .


    STACK_TEXT: 
    a39aeaa4 87f319aa ac449cdc ac449cb0 ac449cb0 nt!RtlSplay+0xd3
    a39aeabc 87f34546 a3d20e7c 00000020 ac449b08 Ntfs!NtfsInsertNameLink+0xaf
    a39aead0 87f13b5e ac449cb0 00006a20 2477c081 Ntfs!NtfsInsertPrefix+0x33
    a39aebf4 87f2746c 8441ed60 86ad74b0 a3d20d08 Ntfs!NtfsOpenFile +0x93e
    a39aecdc 87ead244 8441ed60 86ad74b0 ae511238 Ntfs!NtfsCommonCreate+0xd84
    a39aed1c 81c8611e ae5111d0 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20


    CRITICAL_OBJECT_TERMINATION (f4)
    - A process or thread crucial to system operation has unexpectedly exited or been terminated.

    STACK_TEXT: 
    8ec56c9c 81f1e0d7 000000f4 00000003 86d1f760 nt!KeBugCheckEx+0x1e
    8ec56cc0 81ea1ed2 81e6add0 86d1f8cc 86d1f9d0 nt!PspCatchCriticalBreak+0x71
    8ec56cf0 81ea3d6f 86d1f760 86eae528 c0000005 nt!PspTerminateAllThreads+0x2d
    8ec56d24 81c8544a ffffffff c0000005 002fe7a0 nt!NtTerminateProcess+0x1a2
    8ec56d24 771b64f4 ffffffff c0000005 002fe7a0 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    002fe7a0 00000000 00000000 00000000 00000000 0x771b64f4


    FAILURE_BUCKET_ID:  0xF4_e_IMAGE__(M___

    BUCKET_ID:  0xF4_e_IMAGE__(M___

    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 00000003, the pool freelist is corrupt.


    MODULE_NAME: Pool_Corruption

    FAILURE_BUCKET_ID:  0x19_3_nt!ExDeferredFreePool+336



    So it looks like your RAM is damaged. Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2] to do this), reboot your PC and scan your RAM 4-5hours for errors. If it detects errors, replace the faulty RAM. Also run chkdsk to check your HDD.

    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
    [2] http://www.imgburn.com/index.php?act=download


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Arthur Xie Friday, December 3, 2010 3:50 AM
    Sunday, November 21, 2010 12:07 PM