Windows 8 and 8.1 Forums


BSOD, Event-41 Kernal-Power -Driver IRQL Not Less Or Equal

  1. #1


    Posts : 4
    Windows 8 - Ver 6.3 (build 9600)

    BSOD, Event-41 Kernal-Power -Driver IRQL Not Less Or Equal


    -
    This is a pretty much brand new laptop, that worked for 5 weeks no problem, but since changing country's and setting up my own wifi hotspot this seems to be happening. Below is the event log, and attached is the dm Log Collector file.

    It also seems to happen whilst watching netflix, but this could just be a coincidence because I watch a lot of netflix. I also recently fully updated windows, and my graphics. Still seems to happen.

    If I have not given enough information, please ask and I will provide. Thanks in advance.

    <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="2014-09-22T12:02:48.550333000Z" />

    <EventRecordID>11356</EventRecordID>

    <Correlation />

    <Execution ProcessID="4" ThreadID="8" />

    <Channel>System</Channel>

    <Computer>SPHLaptop</Computer>

    <Security UserID="S-1-5-18" />

    </System>


    - <EventData>
    <Data Name="BugcheckCode">209</Data>

    <Data Name="BugcheckParameter1">0x0</Data>

    <Data Name="BugcheckParameter2">0x2</Data>

    <Data Name="BugcheckParameter3">0x0</Data>

    <Data Name="BugcheckParameter4">0xfffff801b268ec03</Data>

    <Data Name="SleepInProgress">0</Data>

    <Data Name="PowerButtonTimestamp">0</Data>

    <Data Name="BootAppStatus">0</Data>

    </EventData>


    </Event>



      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    The memory dumps blame your networking drivers (e22w8x64.sys) - but as you've recently changed a lot related to your networking - I'd suggest running Driver Verifier according to these instructions: Driver Verifier Settings

    Also, please update your networking drivers to the latest, Win8.1 compatible version available from the manufacturer's website. Your drivers date from March of 2013 - well before Win8.1 came out.



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Sep 22 08:02:16.071 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092214-18125-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:43:17.807
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+6c03 )
    BugCheck D1, {0, 2, 0, fffff801b268ec03}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff801b268ec03, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_e22w8x64+6c03
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Sep 22 06:44:13.531 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092214-19515-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 4:25:34.266
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+6c03 )
    BugCheck D1, {0, 2, 0, fffff801f7606c03}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff801f7606c03, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_e22w8x64+6c03
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Sep 21 03:56:17.769 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092114-18062-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 5:10:21.504
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+6c03 )
    BugCheck D1, {0, 2, 0, fffff8002159bc03}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8002159bc03, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_e22w8x64+6c03
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Sep 20 22:45:22.020 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092114-19843-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 17:17:20.756
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+6c03 )
    BugCheck D1, {0, 2, 0, fffff800aca8ec03}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff800aca8ec03, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_e22w8x64+6c03
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Mon Sep 22 08:02:16.071 2014 (UTC - 4:00)**************************
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    Trufos.sys                  Fri Sep  7 10:08:07 2012 (5049FFC7)
    e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    iwdbus.sys                  Thu Sep 26 17:38:04 2013 (5244A93C)
    BdSpy.sys                   Tue Oct  8 11:08:10 2013 (52541FDA)
    iaStorA.sys                 Mon Oct 28 17:15:26 2013 (526ED3EE)
    dump_iaStorA.sys            Mon Oct 28 17:15:26 2013 (526ED3EE)
    NETwew00.sys                Thu Oct 31 10:01:47 2013 (527262CB)
    TeeDriverx64.sys            Wed Nov 27 12:56:32 2013 (52963250)
    igdkmd64.sys                Wed Dec 18 15:49:12 2013 (52B20A48)
    RtsPer.sys                  Fri Jan  3 03:32:36 2014 (52C675A4)
    SynTP.sys                   Thu Jan  9 22:16:42 2014 (52CF661A)
    Smb_driver_Intel.sys        Thu Jan  9 22:21:21 2014 (52CF6731)
    RTKVHD64.sys                Tue Jan 21 06:16:00 2014 (52DE56F0)
    BdNet.sys                   Thu Mar  6 11:30:56 2014 (5318A2C0)
    nvvad64v.sys                Fri Mar 28 09:32:06 2014 (533579D6)
    BdAgent.sys                 Tue May 13 11:05:29 2014 (537234B9)
    nvpciflt.sys                Wed Jul  2 13:34:06 2014 (53B4428E)
    nvlddmkm.sys                Wed Jul  2 13:42:02 2014 (53B4446A)
    nvkflt.sys                  Wed Jul  2 13:49:00 2014 (53B4460C)
    NvStreamKms.sys             Fri Jul 25 07:35:56 2014 (53D2411C)
    afwcore.sys                 Fri Aug  1 03:34:13 2014 (53DB42F5)
    afw.sys                     Fri Aug  1 03:34:17 2014 (53DB42F9)
    NSKernel.sys                Thu Sep  4 04:59:35 2014 (540829F7)
    
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=Trufos.sys
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=BdSpy.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=NETwew00.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPer.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=BdNet.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    BdAgent.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvkflt.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=afwcore.sys
    http://www.carrona.org/drivers/driver.php?id=afw.sys
    http://www.carrona.org/drivers/driver.php?id=NSKernel.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 4
    Windows 8 - Ver 6.3 (build 9600)


    I've done the driver updates, but the other thing that was suggested was too risky for me. I'm in Japan, and only just got here and have no means to do my work should this get stuck in an endless BSOD.

    However, I did google thst driver name and the error, and the first post was talking about MSI laptops and a conflict between the Killer e2200 network card and windows 8. So, I disabled the process and it seems to be fine now. No errors for 2 days. So this seems to be fixed.

    If it happens again I will post back here to let you guys know the fix didn't work.

    Thanks for all the help.
      My System SpecsSystem Spec

  4. #4


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I'm familiar with the Killer Networking Manager BSOD's and have found that updating your Killer drivers to a 2014 version is usually sufficient to solve the problem. The original workaround was to disable things - so, if it works for you, stick with it. :0)

    Good luck!
      My System SpecsSystem Spec

  5. #5


    Posts : 4
    Windows 8 - Ver 6.3 (build 9600)


    Unfortunately this, in the end, did not fix the problem. I had a few days of piece, then a new BSOD with the same filename happened.

    There is no updated drivers for my network card. 20/03/2013 is the date of my driver, now I did reinstall them (which caused its own problems, but I fixed those) but I just received the errors again.

    I'm hosting my own wireless network, sharing my wired connection through my wireless card (using netsh wlan in command prompt) could there be a correlation between the two, because I actually cannot remember this happening before I started to use my hosted network.
      My System SpecsSystem Spec

  6. #6


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Please zip up the contents of C:\Windows\Minidump and upload it with your next post. You may have to copy it to your Desktop in order to zip it up.

    In response to your questions, the general opinion is that BSOD's are events caused by problems with components running inside the kernel memory space. It depends on what you've done to host the network (and if it impinges upon the kernel memory space).

    Most people say that user-mode components can't cause BSOD's. But it's my opinion that they can cause them, but it's by indirect means. For example, if a user-mode component passes a badly formed request to a kernel-mode component, this may cause the kernel-mode component to error out and have a BSOD.

    In your case, I'd have to wonder what you did you setup/use the hosted network.
    That, along with the consistently same driver being named in the memory dump makes me suspect the network sub-system (either hardware or software). Please provide some details about this setup so we can figure out how to proceed.

    There are several ways to approach this (and numerous ways to troubleshoot this)
    Let's start with 2 different things:

    1) The Event ID 41 error is actually Windows just saying that it doesn't know why it shut down. This can be caused by a BSOD, by a hardware problem, or even by holding down the power switch to shutoff the computer.
    Please do the following:
    - open Event Viewer (run eventvwr.msc from the "Run" dialog))
    - expand the Custom Views category (left click on the > next to the words "Custom Views")
    - right click on Administrative Events
    - select "Save all Events in Custom View as..."
    - save the file as Admin.evtx
    - zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
    - upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

    FYI - There's more info on Event ID 41 errors here: http://support.microsoft.com/kb/2028504

    While waiting for a reply, please monitor your temps with this free utility: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

    2) Please run Driver Verifier according to these directions: Driver Verifier Settings
    The purpose here is to see if the system will force a BSOD that blames another driver (and hopefully, it's one with a networking component to it). Worst case is that it doesn't reveal anything - and then we'll continue to pursue troubleshooting the networking sub-system.
      My System SpecsSystem Spec

  7. #7


    Posts : 4
    Windows 8 - Ver 6.3 (build 9600)


    Thanks for taking the time to reply,

    Please find attached the two rar files you requested. I read that I could end up locked out of my computer when doing the driver verifier, so I'll post these, then do that and edit my reply.

    In regards to hosting my network I watched a youtube video, and then loaded CMD in admin, then I checked to see if the drivers allowed me to host my own hotspot, which they did so I enabled them (netsh wlan driver mode=allow)

    Then I did the setup of: Netsh wlan set hostednetwork ssid=blah key=80087355
    Then start hostednetwork.

    I could be wrong with the dates, but I'm actually sure this is around the time when it started. I have since disabled the drivers, which didn't help.

    **edit**

    I did the verifier, and I got stuck in an endless BSOD reboot cycle, so I used the restore driver to boot into safe mode and get the dump file before deleting the verifier settings. Please find attached the new dump files.
    Last edited by Khronnus; 01 Oct 2014 at 07:26. Reason: Adding a new dump file
      My System SpecsSystem Spec

  8. #8


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Do you have a link for the YouTube video? I'll get a friend who's a networking MVP to take a look at it and offer an opinion.
    IMO, it's possible that the netsh commands forced something that the network card wasn't able to handle - but it's unlikely. But, for example, if the network driver had a small glitch in an area that it normally didn't use - then this could have exposed that with the netsh commands - which in turn could have caused a BSOD (just thinking out loud here)

    I started backwards with this one. There were 2 Driver Verifier enabled memory dumps - and both blamed the networking driver.

    The only possible issue that I see in the Admin log is a bluetooth problem.
    Can you remove any bluetooth devices or disable them in the UEFI/BIOS?
    If not, can you disable them in the Device Manager? (ensure they're fully updated before disabling them)

    Try the Killer e2200 drivers from here: Driver Downloads | Qualcomm Atheros, Inc.

    If that doesn't fix it, then I'd contact the manufacturer for further support (I'd suspect that the network card has gone bad).
    Another way to test this would be to try another networking device (either a USB to wired connection, or a wireless USB device - while disabling the current devices on the system).

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Wed Oct  1 08:11:32.759 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\100114-15343-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:00:59.541
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+705f )
    BugCheck D1, {ffffcf81b6122f50, 2, 0, fffff801f1a8f05f}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: ffffcf81b6122f50, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff801f1a8f05f, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_VRF_e22w8x64+705f
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Oct  1 08:10:05.604 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\100114-18531-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:00:52.386
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+705f )
    BugCheck D1, {ffffcf820aefef50, 2, 0, fffff800d7f9b05f}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: ffffcf820aefef50, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff800d7f9b05f, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: AV_VRF_e22w8x64+705f
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Oct  1 07:40:56.525 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\100114-22921-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:26:53.260
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+6c03 )
    BugCheck D1, {0, 2, 0, fffff800bd606c03}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff800bd606c03, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_e22w8x64+6c03
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Oct  1 07:13:32.951 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\100114-19500-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 21:08:25.686
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+6c03 )
    BugCheck D1, {0, 2, 0, fffff800d361fc03}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff800d361fc03, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_e22w8x64+6c03
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 30 10:04:37.739 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\093014-22437-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 5:09:48.476
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+6c03 )
    BugCheck D1, {0, 2, 0, fffff80109406c03}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff80109406c03, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_e22w8x64+6c03
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 30 04:54:21.116 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\093014-24828-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 2:01:14.852
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+6c03 )
    BugCheck D1, {0, 2, 0, fffff801edf88c03}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff801edf88c03, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_e22w8x64+6c03
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 30 02:52:24.334 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\093014-28093-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:1 days 18:26:36.069
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
    Probably caused by :e22w8x64.sys ( e22w8x64+6a4a )
    BugCheck 1E, {ffffffffc0000005, fffff8014c806a4a, ffffd001181d47d8, ffffd001181d3fe0}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8014c806a4a, The address that the exception occurred at
    Arg3: ffffd001181d47d8, Parameter 0 of the exception
    Arg4: ffffd001181d3fe0, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x1E_c0000005_e22w8x64+6a4a
    CPUID:        "Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz"
    MaxSpeed:     2600
    CurrentSpeed: 2594
      BIOS Version                  E16F4IMT.70U
      BIOS Release Date             04/21/2014
      Manufacturer                  pcs
      Product Name                   
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Wed Oct  1 08:11:32.759 2014 (UTC - 4:00)**************************
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    Trufos.sys                  Fri Sep  7 10:08:07 2012 (5049FFC7)
    e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    iwdbus.sys                  Thu Sep 26 17:38:04 2013 (5244A93C)
    BdSpy.sys                   Tue Oct  8 11:08:10 2013 (52541FDA)
    
    
    iaStorA.sys                 Mon Oct 28 17:15:26 2013 (526ED3EE)
    dump_iaStorA.sys            Mon Oct 28 17:15:26 2013 (526ED3EE)
    NETwew00.sys                Thu Oct 31 10:01:47 2013 (527262CB)
    NSKernel.sys                Tue Nov 26 07:16:31 2013 (5294911F)
    TeeDriverx64.sys            Wed Nov 27 12:56:32 2013 (52963250)
    igdkmd64.sys                Wed Dec 18 15:49:12 2013 (52B20A48)
    RtsPer.sys                  Fri Jan  3 03:32:36 2014 (52C675A4)
    nvlddmkm.sys                Tue Jan  7 16:20:23 2014 (52CC6F97)
    nvpciflt.sys                Tue Jan  7 16:20:52 2014 (52CC6FB4)
    nvkflt.sys                  Tue Jan  7 16:21:02 2014 (52CC6FBE)
    SynTP.sys                   Thu Jan  9 22:16:42 2014 (52CF661A)
    Smb_driver_Intel.sys        Thu Jan  9 22:21:21 2014 (52CF6731)
    RTKVHD64.sys                Tue Jan 21 06:16:00 2014 (52DE56F0)
    BdNet.sys                   Thu Mar  6 11:30:56 2014 (5318A2C0)
    nvvad64v.sys                Fri Mar 28 09:32:06 2014 (533579D6)
    BdAgent.sys                 Tue May 13 11:05:29 2014 (537234B9)
    NvStreamKms.sys             Fri Jul 25 07:35:56 2014 (53D2411C)
    afwcore.sys                 Fri Aug  1 03:34:13 2014 (53DB42F5)
    afw.sys                     Fri Aug  1 03:34:17 2014 (53DB42F9)
    
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=Trufos.sys
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=BdSpy.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=NETwew00.sys
    http://www.carrona.org/drivers/driver.php?id=NSKernel.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPer.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=nvkflt.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=BdNet.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    BdAgent.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=afwcore.sys
    http://www.carrona.org/drivers/driver.php?id=afw.sys
      My System SpecsSystem Spec

BSOD, Event-41 Kernal-Power -Driver IRQL Not Less Or Equal
Related Threads
Solved Bsod: Driver irql not less or equal in BSOD Crashes and Debugging
Hello, guys. Few months earlier I got this Lenovo Ideacentre PC. Can't say exectly when it started, but I got BSOD three or four times already, Twice while playing Portal 2, once while in firefox, (don't remember when the first one was). The error is always the same Ц DRIVER IRQL NOT LESS OR EQUAL....
Hi, My computer has been shut down some times per day with BSOD, I've done the steps in the main post and here is the file attached, Hope you can help me..
Hi, I am getting these BSOD recently saying "driver irql not less or equal........" while atrying to use SF_Diagnostic_Tool I received this msg too... See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception...
I have had this problem before but only once and I did not pay heed to it. I download torrent quite a lot using bittorrent, and bsod has never occurred. But ever since this last torrent I have been downloading it has been happening quite often and only whenbittorretn is active. - - - - -
BSOD Driver irql not less or equal in BSOD Crashes and Debugging
Hello I've recently bought this laptop and over the last two days I've gotten two BSOD. I ran a driver update and found that all my drivers are up to date and am confused about what can be causing it. I've attached my dump files here. Thanks for any help that you can give me.
Solved Driver IRQL Not Less Or Equal BSOD when gaming in BSOD Crashes and Debugging
As the title says, I've been getting the said error when playing games. I already tried updating my graphic card's vga and vbios drivers, with no further results. Here's my computer spects: OS: Windows 8 Pro x64 Processor: AMD FX-8150 clocked at 3.60 GHz Motherboard: ASRock 970 Extreme4...
Solved Random BSOD (Driver IRQL not less or equal) in BSOD Crashes and Debugging
Hello, first and foremost, thankyou for reading this and be there just to help people. It's a selfless action that helps greatly us noobs. So, thankyou. Second, I'm spanish so my english might be a gramatical horror. I just installed Windows 8 Pro, and it all goes well except for those...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook