TechSpot

Blue screen, event ID 1003 category 102

By Muralidharan
May 31, 2010
  1. Dear Friends.

    I am getting a blue dump error when i open any of the mdeia files or any other files
    i get to see the event id 1003 category (102)

    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 37 1000007
    0020: 66 20 20 50 61 72 61 6d f Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 30 30 30 30 30 38 2c 20 000008,
    0038: 62 38 33 34 38 64 37 30 b8348d70
    0040: 2c 20 30 30 30 30 30 30 , 000000
    0048: 30 30 2c 20 30 30 30 30 00, 0000
    0050: 30 30 30 30 0000

    I have updated the driver and installed the update patch as well but still i am getting the blue dump error. I replaced the ram, bought a new DDR2 ram and checked but still the problem exist
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    How to find and post your Minidump Files:

    My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

    It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually.
     
  3. garalare

    garalare TS Rookie

    Mini dump file attached

    I have been getting auto reboots unexpectedly. Can somebody tell me if the *.dmp file offers any clues on what is going on and how to fix this from happening?

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 6/18/2010
    Time: 5:41:19 PM
    User: N/A
    Computer: YOUR-4DACD0EA75
    Description:
    Error code 1000000a, parameter1 00000016, parameter2 0000001c, parameter3 00000000, parameter4 80502eb4.


    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 30 1000000
    0020: 61 20 20 50 61 72 61 6d a Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 30 30 30 30 31 36 2c 20 000016,
    0038: 30 30 30 30 30 30 31 63 0000001c
    0040: 2c 20 30 30 30 30 30 30 , 000000
    0048: 30 30 2c 20 38 30 35 30 00, 8050
    0050: 32 65 62 34 2eb4
     

    Attached Files:

  4. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    garalare - Please in the future do not attach to another post if you have an issue because people will think you are helping the original poster rather than knowing you need help yourself. Plus, attention needs to be placed on the person who started the thread. Create your onw and we'll be glad to help you.

    Your issue is with the driver adasprot32.sys and there is almost nothing on the net defining what it is or what software it belongs to.

    However, after much searching this is the software it belongs to: http://www.systweak.com/aso/
     
  5. garalare

    garalare TS Rookie

    Thank you

    Thank you for your help
     
  6. garalare

    garalare TS Rookie

    to: route 44

    I have found the folder that contains the minidump files and see that the first one appeared June 8, which seems about right as that is when I first started experiencing this problem. I do use Advanced system optimizer and System Protector which is software made by systweak. Could you see if these other minidumps reference anythinhg else or is it just the driver adasprot32.sys ?
     

    Attached Files:

  7. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    All five minidump errors are the same 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.)


    All five cite the same driver adasprot32.sys as the cause of your system crashes because it is trying to access a higher IRQL than it is designed for.

    Try the following:

    1. Update the software or...

    2. Uninstall and reinstall the software. Sometimes this works.

    * If neither step resolves it contact the software manufacture and make sure you tell them six minidumps were read, the code, and the driver specifically cited as the cause of your issues.
     
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...