TechSpot

Kernel_mode_exception_not_handled_m

By ShadowTav
Apr 26, 2006
  1. Hello,

    I've run through all the guides here and I'm still not able to figure what is causing a KERNEL_MODE_EXCEPTION_NOT_HANDLED_M or a 0x1000008e error.

    I checked the ram and they are brand new (3 days old) nothing is wrong with them. mobo isn't leaking/blown, video card is updated and tested to be working correctly. I'm really confused on what is causing this. Hopefully someone here can take a look at the dumps and figure out what is going on. I tried contacting MS support but I'm getting zero back from them.

    Here are the only Errors and save dumps I could find in the event viewer, also am including dxdiag log and minidump attached.

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 4/24/2006
    Time: 10:51:40 PM
    User: N/A
    Computer: AKA
    Description:
    Error code 1000000a, parameter1 00000202, parameter2 00000002, parameter3 00000000, parameter4 804ef7eb.

    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 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 32 30 32 2c 20 000202,
    0038: 30 30 30 30 30 30 30 32 00000002
    0040: 2c 20 30 30 30 30 30 30 , 000000
    0048: 30 30 2c 20 38 30 34 65 00, 804e
    0050: 66 37 65 62 f7eb

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 4/24/2006
    Time: 11:53:39 PM
    User: N/A
    Computer: AKA
    Description:
    Error code 10000050, parameter1 e44ef730, parameter2 00000000, parameter3 bf0b6040, parameter4 00000001.

    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 35 1000005
    0020: 30 20 20 50 61 72 61 6d 0 Param
    0028: 65 74 65 72 73 20 65 34 eters e4
    0030: 34 65 66 37 33 30 2c 20 4ef730,
    0038: 30 30 30 30 30 30 30 30 00000000
    0040: 2c 20 62 66 30 62 36 30 , bf0b60
    0048: 34 30 2c 20 30 30 30 30 40, 0000
    0050: 30 30 30 31 0001

    Event Type: Information
    Event Source: Save Dump
    Event Category: None
    Event ID: 1001
    Date: 4/24/2006
    Time: 11:52:20 PM
    User: N/A
    Computer: AKA
    Description:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xe44ef730, 0x00000000, 0xbf0b6040, 0x00000001). A dump was saved in: C:\WINDOWS\Minidump\Mini042406-01.dmp.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type: Information
    Event Source: Save Dump
    Event Category: None
    Event ID: 1001
    Date: 4/26/2006
    Time: 3:27:55 AM
    User: N/A
    Computer: AKA
    Description:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf13a03e, 0xb91edbd4, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini042606-01.dmp.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



    ------------------
    System Information
    ------------------
    Time of this report: 4/26/2006, 18:55:33
    Machine name: AKA
    Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
    Language: English (Regional Setting: English)
    System Manufacturer: VIA Technologies, Inc.
    System Model: VT8365
    BIOS: Phoenix - AwardBIOS v6.00PG
    Processor: AMD Athlon(tm) XP 1600+, MMX, 3DNow, ~1.4GHz
    Memory: 1016MB RAM
    Page File: 272MB used, 1213MB available
    Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
    DX Setup Parameters: Not found
    DxDiag Version: 5.03.2600.2180 32bit Unicode
     

    Attached Files:

  2. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,088

    It's your video card drivers. There's a revision 2 of the 84.21s dated March 17th, give these a try, if you still have the same problem try installing an earlier version.
     
  3. ShadowTav

    ShadowTav TS Rookie Topic Starter

    Alright thank you. I been having this problem for a long time but it has been getting worse. Since you said drivers I do notice that every new driver I put in this happens more and more.
     
  4. ShadowTav

    ShadowTav TS Rookie Topic Starter

    Tried the drivers and I'm still getting the crashes.

    Here is the new one....
    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 5/1/2006
    Time: 7:48:26 PM
    User: N/A
    Computer: AKA
    Description:
    Error code 000000d1, parameter1 00000026, parameter2 00000002, parameter3 00000000, parameter4 f58188d4.

    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 30 30 30 30 30 30 64 000000d
    0020: 31 20 20 50 61 72 61 6d 1 Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 30 30 30 30 32 36 2c 20 000026,
    0038: 30 30 30 30 30 30 30 32 00000002
    0040: 2c 20 30 30 30 30 30 30 , 000000
    0048: 30 30 2c 20 66 35 38 31 00, f581
    0050: 38 38 64 34 88d4

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 5/1/2006
    Time: 7:49:15 PM
    User: N/A
    Computer: AKA
    Description:
    Error code 1000008e, parameter1 c0000046, parameter2 804fbabb, parameter3 ad6ec764, 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 34 36 2c 20 000046,
    0038: 38 30 34 66 62 61 62 62 804fbabb
    0040: 2c 20 61 64 36 65 63 37 , ad6ec7
    0048: 36 34 2c 20 30 30 30 30 64, 0000
    0050: 30 30 30 30 0000


    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 5/3/2006
    Time: 12:23:49 AM
    User: N/A
    Computer: AKA
    Description:
    Error code 0000000a, parameter1 00000028, parameter2 00000002, parameter3 00000000, parameter4 804f0bbc.

    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 30 30 30 30 30 30 30 0000000
    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 32 38 2c 20 000028,
    0038: 30 30 30 30 30 30 30 32 00000002
    0040: 2c 20 30 30 30 30 30 30 , 000000
    0048: 30 30 2c 20 38 30 34 66 00, 804f
    0050: 30 62 62 63 0bbc

    Minidumps attached.
     
  5. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Faulty ram

    The culprit is faulty ram. Run memtest to stress test the ram.

    Mini050106-01.dmp BugCheck 1000008E, {c0000046, 804fbabb, ad6ec764, 0}
    Probably caused by : kmixer.sys ( kmixer!PinDispatchClose+437 )

    Mini050306-01.dmp BugCheck A, {28, 2, 0, 804f0bbc}
    Probably caused by : win32k.sys ( win32k!vFreeKernelSection+37 )
     
  6. ShadowTav

    ShadowTav TS Rookie Topic Starter

    odd. I already ran tests and the ram checked out. I also bought new ram yesterday and still getting the same issue.
     
  7. Lekki_Sheep

    Lekki_Sheep TS Rookie Posts: 135

    When exactly does the error occur? I'd agree that it's not likely to be the RAM if you just put an entirely new supply in. Could be something to do with the mobo, but that's not likely either. If it's occuring without an obvious trigger try sifting through the system and app logs to see if you can find a connection with another event.
     
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...