locked
Windows BSOD - IRQL_NOT_LESS_OR_EQUAL and UNEXPECTED_KERNEL_MODE_TRAP RRS feed

  • Question

  • Having a bunch of issues with my pc.. i ve built this a while ago (1.5 years ago-ish). 

    Recently one of my ssd failed (i had win installed on it). I couldn't install windows successfully on my second ssd because the installation process kept failing.. turns out one of the RAM sticks must ve been corrupt. After I singled out which one it was, it all went fine..

    Now my win has been running just fine for a day but I started getting BSOD's when in a game or running a video. 

    Most of the time it gives the error IRQL_NOT_LESS_OR_EQUAL, and one time it gave the UNEXPECTED_KERNEL_MODE_TRAP error.

    I did 3 mem tests; my 3 remaining RAM sticks seem to be fine from the memtests' perspective.

    I used FurMark GPU Stress Test to see if the video card is one at fault, and got no BSOD as it was pushed to the limit.

    The only other things I can think of are PSU and mainboard ?

    And here are logs from the event viewer:

    ------------------------------------------------------

    Critical Error:

    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          3/4/2015 4:48:31 PM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      mihaipc
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>3</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2015-03-04T23:48:31.358245100Z" />
        <EventRecordID>1138</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>mihaipc</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">10</Data>
        <Data Name="BugcheckParameter1">0x49</Data>
        <Data Name="BugcheckParameter2">0x2</Data>
        <Data Name="BugcheckParameter3">0x1</Data>
        <Data Name="BugcheckParameter4">0xfffff8025e704e86</Data>
        <Data Name="SleepInProgress">0</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
        <Data Name="BootAppStatus">0</Data>
      </EventData>
    </Event>

    ------------------------------------------------------

    Another Error:

    Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          3/4/2015 4:48:55 PM
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mihaipc
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000049, 0x0000000000000002, 0x0000000000000001, 0xfffff8025e704e86). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030415-24484-02.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-03-04T23:48:55.000000000Z" />
        <EventRecordID>1152</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>mihaipc</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x0000000a (0x0000000000000049, 0x0000000000000002, 0x0000000000000001, 0xfffff8025e704e86)</Data>
        <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
        <Data Name="param3">030415-24484-02</Data>
      </EventData>
    </Event>

    ------------------------------------------------------

    And another Error:

    Log Name:      System
    Source:        Service Control Manager
    Date:          3/4/2015 4:49:06 PM
    Event ID:      7034
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mihaipc
    Description:
    The Service KMSELDI service terminated unexpectedly.  It has done this 1 time(s).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7034</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2015-03-04T23:49:06.730929500Z" />
        <EventRecordID>1155</EventRecordID>
        <Correlation />
        <Execution ProcessID="532" ThreadID="1792" />
        <Channel>System</Channel>
        <Computer>mihaipc</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Service KMSELDI</Data>
        <Data Name="param2">1</Data>
        <Binary>530065007200760069006300650020004B004D00530045004C00440049000000</Binary>
      </EventData>
    </Event>

    Thanks,

    Mihai

    Thursday, March 5, 2015 12:03 AM

Answers

  • These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.

    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!! 
     

    If you do not know what this means you probably are not



    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)



    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Saturday, March 7, 2015 7:04 PM
    Thursday, March 5, 2015 4:59 AM

All replies

  •  We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask


    Wanikiya and Dyami--Team Zigzag

    Thursday, March 5, 2015 12:26 AM
  • Ok, so it just crashed again while playing a detailed high def video, and I'm definetly getting the feeling that it's due to the video card. Windows installed the driver by itself though, I'm pretty sure it shouldn't be incompatible.

    The MEMORY.DMP is huge, so I upped the minidump like the procedure that you linked me to said. You can get them here (http://1drv.ms/1Fbxxu3). I hope they are related; there are 2 that are from about an hour ago (030415-24484-01 and ...-02.dmp)

    My pc's msinfo32 (http://1drv.ms/1Fbyoef) I can see there are some conflicts there but not sure what to make of them.

    I put the links as normal text - it seems I need to verify my account before I hyperlink anything.

    Anything else I should be upping ?

    Thanks !!

    Thursday, March 5, 2015 12:47 AM
  • These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.

    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!! 
     

    If you do not know what this means you probably are not



    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)



    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Saturday, March 7, 2015 7:04 PM
    Thursday, March 5, 2015 4:59 AM
  • I haven't replied as I've been running and re running the verifier and my pc isnt crashing now.. ironically ! so i'm still waiting on it..

    I did a memtest and everything showed up fine on that.

    Wednesday, March 11, 2015 5:52 PM
  • MO

    Sometimes verifier can act like a buffer between the driver and the OS.  It will not crash until the misbehaving driver is loaded and that may take 24 hours.  We can force the issue.


    Wanikiya and Dyami--Team Zigzag

    Wednesday, March 11, 2015 8:33 PM