TechSpot

System error please help!

By zoidberg666
Apr 15, 2006
  1. hey,
    I've been getting this error
    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 4/16/2006
    Time: 10:04:56 AM
    User: N/A
    Computer: SALES
    Description:
    Error code 1000008e, parameter1 c0000005, parameter2 bf80bec7, parameter3 b85a6818, parameter4 00000000.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 31 30 30 30 30 30 38 1000008
    0020: 65 20 20 50 61 72 61 6d e Param
    0028: 65 74 65 72 73 20 63 30 eters c0
    0030: 30 30 30 30 30 35 2c 20 000005,
    0038: 62 66 38 30 62 65 63 37 bf80bec7
    0040: 2c 20 62 38 35 61 36 38 , b85a68
    0048: 31 38 2c 20 30 30 30 30 18, 0000
    0050: 30 30 30 30 0000

    It's been rebooting when I'm doing stuff can someone please help. Thanks.

    I've checked ram, hard drive etc. Have no idea.
     
  2. howard_hopkinso

    howard_hopkinso TS Rookie Posts: 24,177   +19

    Hello and welcome to Techspot.

    Go HERE and follow the instructions.

    If that doesn`t help. Zip 5 or 6 of your latest minidumps together and attach them here.

    Regards Howard :wave: :wave:
     
  3. zoidberg666

    zoidberg666 TS Rookie Topic Starter

    Ok but I'm going to attach the minidumps anyway.

    Thanks
     
  4. howard_hopkinso

    howard_hopkinso TS Rookie Posts: 24,177   +19

    2 minidumps crash with memory corruption(1 byte memory corruption) and a bugcheck of 8E.

    1 minidump crashes at win32k.sys. This is a Windows system file. It has a bugcheck of BE.

    1 minidump crashes at SYMEVENT.SYS. Symantec/Norton security product. It has a bugcheck of 0A.

    0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

    A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

    0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

    A driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware. If a driver file is named in the error message, try to correct the problem by disabling, removing, or rolling back the driver.

    0x0000000A: IRQL_NOT_LESS_OR_EQUAL

    Typically due to a bad driver, or faulty or incompatible hardware or software. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)

    Update your Symantec/Norton security product.

    Faulty ram is probably the culprit.

    Regards Howard :)
     
  5. zoidberg666

    zoidberg666 TS Rookie Topic Starter

    OK i'll change ram again. Thanks.
     
Topic Status:
Not open for further replies.

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...