Windows 8 and 8.1 Forums

BSOD Error code 139

  1. #21


    Posts : 40
    Windows 8.1 Pro 64bit, Linux Mint 17 64bit


    Another BSOD at startup, but different error code (progress?), I think IRQL_NOT_LESS_OR_EQUAL. I already removed Virtualbox and I think I updated NvStreamKms.sys, and then disabled it to be on the safe side. I did not get to removing Avast yet.

    Here's the dump (I forgot to remove the last minidump from it, sorry): Attachment 55322


    Edit: I just looked at the minidump and found this:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffd7fffffe7e0, 2, 1, fffff80048304ba2}
    
    Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+122 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffd7fffffe7e0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80048304ba2, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80048572168
    GetUlongFromAddress: unable to read from fffff800485721f8
     fffffd7fffffe7e0 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiRemoveAnyPage+122
    fffff800`48304ba2 f0410fba6e1000  lock bts dword ptr [r14+10h],0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  dasHost.exe
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    DEVICE_OBJECT: fffffa80141b39d0
    
    TRAP_FRAME:  fffff8801c10be20 -- (.trap 0xfffff8801c10be20)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000014
    rdx=fffff8004856b1c0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80048304ba2 rsp=fffff8801c10bfb0 rbp=fffff8801c10c000
     r8=000000000000007f  r9=0000000000000000 r10=0000000000000000
    r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiRemoveAnyPage+0x122:
    fffff800`48304ba2 f0410fba6e1000  lock bts dword ptr [r14+10h],0 ds:00000000`00000010=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80048274769 to fffff80048275440
    
    STACK_TEXT:  
    fffff880`1c10bcd8 fffff800`48274769 : 00000000`0000000a fffffd7f`ffffe7e0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`1c10bce0 fffff800`48272fe0 : 00000000`00000001 00000000`00000004 00000000`00000000 fffff880`1c10be20 : nt!KiBugCheckDispatch+0x69
    fffff880`1c10be20 fffff800`48304ba2 : fffffa80`141d0de0 fffffa80`141d0d70 fffff880`1c10c0a8 00000000`00000800 : nt!KiPageFault+0x260
    fffff880`1c10bfb0 fffff800`482bdb44 : 00000000`00000010 fffffa80`00000000 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x122
    fffff880`1c10c070 fffff800`482fa32e : fffff980`00000001 00000000`00000000 fffff6fc`c00d1008 00000064`09b57930 : nt!MiGetPage+0x359
    fffff880`1c10c150 fffff800`482e0926 : 00000000`00000000 00000000`00000000 fffff880`1c10c340 fffff880`1c10c328 : nt!MmCopyToCachedPage+0x25e
    fffff880`1c10c2f0 fffff800`482dfeb2 : fffffa80`13f55010 00000064`09b57930 fffff880`1c10c440 fffff880`00000000 : nt!CcMapAndCopyInToCache+0x236
    fffff880`1c10c3e0 fffff880`018f74e2 : fffffa80`141b39d0 fffff880`1c10c700 00000000`000000cc 00000000`00000000 : nt!CcCopyWriteEx+0x1b2
    fffff880`1c10c480 fffff880`018fc66a : fffffa80`13223e10 fffff880`1c10c700 fffff880`1c10c718 00000000`00000000 : Ntfs!NtfsCommonWrite+0xd42
    fffff880`1c10c6d0 fffff880`015414ee : fffffa80`14166b80 fffffa80`141cc790 fffffa80`141cc790 fffffa80`141ccb78 : Ntfs!NtfsFsdWrite+0x22a
    fffff880`1c10c790 fffff880`0153f0b6 : fffffa80`0dffa8d0 fffffa80`141b39d0 fffffa80`141cc790 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x25e
    fffff880`1c10c830 fffff800`4868af88 : 00000000`00000001 fffff880`1c10c911 fffffa80`141b39d0 00000000`00000000 : fltmgr!FltpDispatch+0xb6
    fffff880`1c10c890 fffff800`48655bda : fffffa80`141b39d0 00000000`00000000 00000000`00000000 fffffa80`141b39d0 : nt!IopSynchronousServiceTail+0x158
    fffff880`1c10c960 fffff800`48274453 : 00000000`00000501 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x809
    fffff880`1c10ca90 000007fc`9b2d2c2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000064`0927eb38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fc`9b2d2c2a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiRemoveAnyPage+122
    fffff800`48304ba2 f0410fba6e1000  lock bts dword ptr [r14+10h],0
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiRemoveAnyPage+122
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  54546002
    
    IMAGE_VERSION:  6.2.9200.17166
    
    IMAGE_NAME:  memory_corruption
    
    BUCKET_ID_FUNC_OFFSET:  122
    
    FAILURE_BUCKET_ID:  AV_nt!MiRemoveAnyPage
    
    BUCKET_ID:  AV_nt!MiRemoveAnyPage
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_nt!miremoveanypage
    
    FAILURE_ID_HASH:  {de099fa2-7835-1495-f447-6ce78ff90329}
    
    Followup: MachineOwner
    ---------
    Would I be safe to assume my RAM is bad?

    Edit #2: Also, any suggestions on what I should replace avast with in the meantime?
    Last edited by kingsomeguy; 16 Dec 2014 at 01:17.

      My System SpecsSystem Spec

  2. #22


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


    I asked the 8.1 question to get a general idea of the state of the system over time.
    If you'll note, my profile info states "Win8.1Pro - Finally!!!" I couldn't install it for months - and I presume that a series of updates from Samsung (my laptop manufacturer) and Microsoft finally let it install!

    What caused you to think that the RAM was bad?
    In most cases I first assume that a STOP 0xA error is due to a misbehaving driver (although it can be caused by bad hardware also).
    In this case the output states "This is usually caused by drivers using improper addresses."
    I'd suggest that you run Driver Verifier according to these instructions: Driver Verifier Settings
    I can't recall if you've run it before, but the sudden change in the memory dumps might warrant running it again anyways.

    Also, memory corruption is a generic term. Most often it refers to corruption in the information stored at addresses in virtual memory (so the RAM isn't directly involved). But it's possible for it to be hardware.
    If you're concerned, try the memory test here: Hardware Diagnostics
    Also try running Prime95 - as the Blend test is a good RAM test that stresses different areas of the RAM than MemTest does.

    When removing Avast, use the in-built Windows Defender and the Windows firewall. It's already there, it's free, and in most cases it'll start itself up when you remove the Avast.

    Our biggest problem here is determining why the BSOD's changed:
    - did we fix the original, and this is an entirely new problem?
    - did we partly fix the original, and this is a result of the partial fix
    - did we not fix the original, and this is an entirely new problem?
    - is this just a continuation of a complicated BSOD sequence?

    I'd suggest that we continue along as we have been and see if anything changes.
    Driver Verifier won't change anything (once you turn it back off), so it may help us see what else is going on without disrupting what we're currently doing.

    Keep an eye on the 3rd party driver lists. Drivers duplicated in each of the memory dumps are the most likely to be a cause.

    Don't worry about removing the memory dumps. A part of my "process" is to see which dumps haven't been run - and then run only those.

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Dec 15 20:25:59.319 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\121514-40828-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.17166.amd64fre.win8_gdr.141031-1551
    System Uptime:0 days 0:01:33.938
    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
    Probably caused by :memory_corruption ( nt!MiRemoveAnyPage+122 )
    BugCheck A, {fffffd7fffffe7e0, 2, 1, fffff80048304ba2}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
    Arguments: 
    Arg1: fffffd7fffffe7e0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80048304ba2, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  dasHost.exe
    FAILURE_BUCKET_ID: AV_nt!MiRemoveAnyPage
    CPUID:        "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3400
      BIOS Version                  F3
      BIOS Release Date             06/03/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H97M-D3H
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    
    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 Dec 15 20:25:59.319 2014 (UTC - 5:00)**************************
    intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
    BthHfAud.sys                Sat Feb  2 02:24:42 2013 (510CBF3A)
    BthA2DP.sys                 Fri May 31 23:08:25 2013 (51A965A9)
    bcbtums.sys                 Thu Oct 17 16:45:30 2013 (52604C6A)
    TeeDriverx64.sys            Thu Mar 13 14:21:52 2014 (5321F740)
    dump_iaStorA.sys            Thu Apr  3 19:00:05 2014 (533DE7F5)
    iaStorA.sys                 Thu Apr  3 19:00:05 2014 (533DE7F5)
    RTKVHD64.sys                Wed May 28 08:17:12 2014 (5385D3C8)
    Rt630x64.sys                Tue Jun 17 07:56:46 2014 (53A02CFE)
    nvhda64v.sys                Mon Jul 21 10:17:53 2014 (53CD2111)
    IntcDAud.sys                Tue Sep  9 08:36:30 2014 (540EF44E)
    nvvad64v.sys                Thu Sep 25 11:39:23 2014 (5424372B)
    igdkmd64.sys                Mon Sep 29 13:51:21 2014 (54299C19)
    VBoxAswDrv.sys              Wed Nov  5 06:58:43 2014 (545A10F3)
    aswMonFlt.sys               Thu Nov  6 07:53:07 2014 (545B6F33)
    aswKbd.sys                  Thu Nov  6 07:53:07 2014 (545B6F33)
    aswRvrt.sys                 Thu Nov  6 07:53:22 2014 (545B6F42)
    aswVmm.sys                  Thu Nov  6 07:53:31 2014 (545B6F4B)
    aswRdr2.sys                 Thu Nov  6 07:54:02 2014 (545B6F6A)
    aswHwid.sys                 Thu Nov  6 07:55:01 2014 (545B6FA5)
    aswNdisFlt.sys              Thu Nov  6 07:55:50 2014 (545B6FD6)
    aswSP.sys                   Thu Nov  6 08:09:55 2014 (545B7323)
    aswStm.sys                  Thu Nov  6 08:11:00 2014 (545B7364)
    nvlddmkm.sys                Wed Nov 12 15:51:31 2014 (5463C853)
    aswSnx.sys                  Fri Nov 21 06:17:12 2014 (546F1F38)
    
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=BthHfAud.sys
    http://www.carrona.org/drivers/driver.php?id=BthA2DP.sys
    http://www.carrona.org/drivers/driver.php?id=bcbtums.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    VBoxAswDrv.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=aswMonFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
    http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
    http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
    http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
    http://www.carrona.org/drivers/driver.php?id=aswHwid.sys
    http://www.carrona.org/drivers/driver.php?id=aswNdisFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswSP.sys
    http://www.carrona.org/drivers/driver.php?id=aswStm.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
      My System SpecsSystem Spec

  3. #23


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


    I don't know how this'll show up, but it's a table showing the 3rd party drivers from the last 4 memory dumps:
    If you scroll to the bottom, there's a bar to scroll horizontally

    Code:
    **************************Mon Dec 15 20:25:59.319 2014 (UTC - 5:00)************************** **************************Sun Dec 14 06:26:37.745 2014 (UTC - 5:00)************************** **************************Mon Dec 1 16:25:22.203 2014 (UTC - 5:00)************************** **************************Thu Nov 20 17:49:16.741 2014 (UTC - 5:00)**************************
    intelppm.sys Mon Nov 5 22:55:02 2012 (50988A16) intelppm.sys Mon Nov 5 22:55:02 2012 (50988A16) intelppm.sys Mon Nov 5 22:55:02 2012 (50988A16) intelppm.sys Mon Nov 5 22:55:02 2012 (50988A16)
    BthHfAud.sys Sat Feb 2 02:24:42 2013 (510CBF3A) BthHfAud.sys Sat Feb 2 02:24:42 2013 (510CBF3A) BthHfAud.sys Sat Feb 2 02:24:42 2013 (510CBF3A) BthHfAud.sys Sat Feb 2 02:24:42 2013 (510CBF3A)
    BthA2DP.sys Fri May 31 23:08:25 2013 (51A965A9) BthA2DP.sys Fri May 31 23:08:25 2013 (51A965A9) BthA2DP.sys Fri May 31 23:08:25 2013 (51A965A9) BthA2DP.sys Fri May 31 23:08:25 2013 (51A965A9)
    bcbtums.sys Thu Oct 17 16:45:30 2013 (52604C6A) bcbtums.sys Thu Oct 17 16:45:30 2013 (52604C6A) bcbtums.sys Thu Oct 17 16:45:30 2013 (52604C6A) bcbtums.sys Thu Oct 17 16:45:30 2013 (52604C6A)
    TeeDriverx64.sys Thu Mar 13 14:21:52 2014 (5321F740) TeeDriverx64.sys Thu Mar 13 14:21:52 2014 (5321F740) TeeDriverx64.sys Thu Mar 13 14:21:52 2014 (5321F740) TeeDriverx64.sys Thu Mar 13 14:21:52 2014 (5321F740)
    dump_iaStorA.sys Thu Apr 3 19:00:05 2014 (533DE7F5) nvvad64v.sys Fri Mar 28 09:32:06 2014 (533579D6) nvvad64v.sys Fri Mar 28 09:32:06 2014 (533579D6) nvvad64v.sys Fri Mar 28 09:32:06 2014 (533579D6)
    iaStorA.sys Thu Apr 3 19:00:05 2014 (533DE7F5) dump_iaStorA.sys Thu Apr 3 19:00:05 2014 (533DE7F5) iaStorA.sys Thu Apr 3 19:00:05 2014 (533DE7F5) iaStorA.sys Thu Apr 3 19:00:05 2014 (533DE7F5)
    RTKVHD64.sys Wed May 28 08:17:12 2014 (5385D3C8) iaStorA.sys Thu Apr 3 19:00:05 2014 (533DE7F5) dump_iaStorA.sys Thu Apr 3 19:00:05 2014 (533DE7F5) dump_iaStorA.sys Thu Apr 3 19:00:05 2014 (533DE7F5)
    Rt630x64.sys Tue Jun 17 07:56:46 2014 (53A02CFE) VBoxUSBMon.sys Fri May 16 08:01:15 2014 (5375FE0B) VBoxUSBMon.sys Fri May 16 08:01:15 2014 (5375FE0B) VBoxNetFlt.sys Fri May 16 08:01:15 2014 (5375FE0B)
    nvhda64v.sys Mon Jul 21 10:17:53 2014 (53CD2111) VBoxNetFlt.sys Fri May 16 08:01:15 2014 (5375FE0B) VBoxNetFlt.sys Fri May 16 08:01:15 2014 (5375FE0B) VBoxUSBMon.sys Fri May 16 08:01:15 2014 (5375FE0B)
    IntcDAud.sys Tue Sep 9 08:36:30 2014 (540EF44E) VBoxNetAdp.sys Fri May 16 08:01:16 2014 (5375FE0C) VBoxNetAdp.sys Fri May 16 08:01:16 2014 (5375FE0C) VBoxNetAdp.sys Fri May 16 08:01:16 2014 (5375FE0C)
    nvvad64v.sys Thu Sep 25 11:39:23 2014 (5424372B) VBoxDrv.sys Fri May 16 08:04:43 2014 (5375FEDB) VBoxDrv.sys Fri May 16 08:04:43 2014 (5375FEDB) VBoxDrv.sys Fri May 16 08:04:43 2014 (5375FEDB)
    igdkmd64.sys Mon Sep 29 13:51:21 2014 (54299C19) RTKVHD64.sys Wed May 28 08:17:12 2014 (5385D3C8) RTKVHD64.sys Wed May 28 08:17:12 2014 (5385D3C8) RTKVHD64.sys Wed May 28 08:17:12 2014 (5385D3C8)
    VBoxAswDrv.sys Wed Nov 5 06:58:43 2014 (545A10F3) Rt630x64.sys Tue Jun 17 07:56:46 2014 (53A02CFE) Rt630x64.sys Tue Jun 17 07:56:46 2014 (53A02CFE) Rt630x64.sys Tue Jun 17 07:56:46 2014 (53A02CFE)
    aswMonFlt.sys Thu Nov 6 07:53:07 2014 (545B6F33) nvhda64v.sys Mon Jul 21 10:17:53 2014 (53CD2111) nvhda64v.sys Mon Jul 21 10:17:53 2014 (53CD2111) aswHwid.sys Thu Jun 26 07:31:26 2014 (53AC048E)
    aswKbd.sys Thu Nov 6 07:53:07 2014 (545B6F33) NvStreamKms.sys Fri Jul 25 07:35:56 2014 (53D2411C) NvStreamKms.sys Fri Jul 25 07:35:56 2014 (53D2411C) aswMonFlt.sys Thu Jun 26 07:32:51 2014 (53AC04E3)
    aswRvrt.sys Thu Nov 6 07:53:22 2014 (545B6F42) IntcDAud.sys Tue Sep 9 08:36:30 2014 (540EF44E) IntcDAud.sys Tue Sep 9 08:36:30 2014 (540EF44E) aswRdr2.sys Thu Jun 26 07:33:28 2014 (53AC0508)
    aswVmm.sys Thu Nov 6 07:53:31 2014 (545B6F4B) igdkmd64.sys Mon Sep 29 13:51:21 2014 (54299C19) igdkmd64.sys Mon Sep 29 13:51:21 2014 (54299C19) aswKbd.sys Thu Jun 26 07:34:01 2014 (53AC0529)
    aswRdr2.sys Thu Nov 6 07:54:02 2014 (545B6F6A) VBoxAswDrv.sys Wed Nov 5 06:58:43 2014 (545A10F3) VBoxAswDrv.sys Wed Nov 5 06:58:43 2014 (545A10F3) aswSnx.sys Thu Jun 26 07:34:44 2014 (53AC0554)
    aswHwid.sys Thu Nov 6 07:55:01 2014 (545B6FA5) aswKbd.sys Thu Nov 6 07:53:07 2014 (545B6F33) aswKbd.sys Thu Nov 6 07:53:07 2014 (545B6F33) aswRvrt.sys Thu Jun 26 07:35:39 2014 (53AC058B)
    aswNdisFlt.sys Thu Nov 6 07:55:50 2014 (545B6FD6) aswMonFlt.sys Thu Nov 6 07:53:07 2014 (545B6F33) aswMonFlt.sys Thu Nov 6 07:53:07 2014 (545B6F33) aswVmm.sys Thu Jun 26 07:35:49 2014 (53AC0595)
    aswSP.sys Thu Nov 6 08:09:55 2014 (545B7323) aswRvrt.sys Thu Nov 6 07:53:22 2014 (545B6F42) aswRvrt.sys Thu Nov 6 07:53:22 2014 (545B6F42) aswNdisFlt.sys Thu Jun 26 07:36:26 2014 (53AC05BA)
    aswStm.sys Thu Nov 6 08:11:00 2014 (545B7364) aswVmm.sys Thu Nov 6 07:53:31 2014 (545B6F4B) aswVmm.sys Thu Nov 6 07:53:31 2014 (545B6F4B) aswStm.sys Thu Jun 26 07:47:09 2014 (53AC083D)
    nvlddmkm.sys Wed Nov 12 15:51:31 2014 (5463C853) aswRdr2.sys Thu Nov 6 07:54:02 2014 (545B6F6A) aswRdr2.sys Thu Nov 6 07:54:02 2014 (545B6F6A) aswSP.sys Wed Jul 2 13:38:12 2014 (53B44384)
    aswSnx.sys Fri Nov 21 06:17:12 2014 (546F1F38) aswHwid.sys Thu Nov 6 07:55:01 2014 (545B6FA5) aswHwid.sys Thu Nov 6 07:55:01 2014 (545B6FA5) nvhda64v.sys Mon Jul 21 10:17:53 2014 (53CD2111)
    aswNdisFlt.sys Thu Nov 6 07:55:50 2014 (545B6FD6) aswNdisFlt.sys Thu Nov 6 07:55:50 2014 (545B6FD6) NvStreamKms.sys Fri Jul 25 07:35:56 2014 (53D2411C)
    aswSP.sys Thu Nov 6 08:09:55 2014 (545B7323) aswSP.sys Thu Nov 6 08:09:55 2014 (545B7323) IntcDAud.sys Tue Sep 9 08:36:30 2014 (540EF44E)
    aswStm.sys Thu Nov 6 08:11:00 2014 (545B7364) aswStm.sys Thu Nov 6 08:11:00 2014 (545B7364) igdkmd64.sys Mon Sep 29 13:51:21 2014 (54299C19)
    nvlddmkm.sys Wed Nov 12 15:51:31 2014 (5463C853) nvlddmkm.sys Wed Nov 12 15:51:31 2014 (5463C853) nvlddmkm.sys Mon Nov 3 15:40:19 2014 (5457E833)
    aswSnx.sys Fri Nov 21 06:17:12 2014 (546F1F38) aswSnx.sys Fri Nov 21 06:17:12 2014 (546F1F38)
      My System SpecsSystem Spec

  4. #24


    Posts : 40
    Windows 8.1 Pro 64bit, Linux Mint 17 64bit


    I assumed RAM due to previous experiences with memory_corruption ending up being caused by bad RAM.
    I'm running Driver Verifier and awaiting for any BSODs.
    When I went to add all third party drivers, intelppm.sys came up as a driver from Microsoft. Should it be from Microsoft?

    Edit: I attempted to run Prime95; first attempt the CPU temperature got to 100ฐC within 5 sec, so I went to make sure the fan was seated properly and applied some Artic Silver 5. Second attempt hit 90ฐC after a minute or two. I'm probably going to go buy a water cooler before I attempt using Prime95 again.
    Last edited by kingsomeguy; 16 Dec 2014 at 19:33.
      My System SpecsSystem Spec

  5. #25


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


    intelppm.sys is one of those drivers that just doesn't fit the usual models. It's a Microsoft driver that's used for the Intel processors.
    In short, the only way to update it is through Windows Update.

    It sounds like something isn't cooling your CPU properly. Most stock coolers (with adequate contact between the CPU and cooler) will be able to keep the temps down to reasonable levels (less than 80บC).

    If the system overheats that fast on Prime95 - I have to wonder about how it's doing when the BSOD's occur?
    Please monitor your system's temperatures with this free tool: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
    It records the max system temps, so you should be able to see what it was after you reboot the system (after a BSOD).
      My System SpecsSystem Spec

  6. #26


    Posts : 40
    Windows 8.1 Pro 64bit, Linux Mint 17 64bit


    Normally, temperatures are around 30-40บ idle or when browsing on Firefox (when most BSODs happened to me), and at most normally when i'm playing games or something along those lines the max I usually see is 80บC. I do agree something is wrong with the cooling otherwise.
    HWMonitor Min/Max values keep resetting after a restart for me, is there something i'm not doing right?

    Edit: I'm almost certain its how my case/PSU fans are somewhat near the CPU fan, however, is an improvement from my last case I had about a month ago. Would a water cooler for the CPU help with that situation?
      My System SpecsSystem Spec

  7. #27


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


    I'm uncertain, as I've only used the max values on rare occasions.
    But you mention that they get up to 80บC during gaming - I'd suspect that they get higher at times, and that is what's causing the BSOD's.

    Here's a nice discussion on temp monitors: Best app to monitor CPU/GPU temps? - Steam Users' Forums
    Be aware that some of them are also known to cause BSOD's - but that's not a real big issue right now as you already have BSOD's

    It does complicate things a bit - so we may have to try several of them until we find one that doesn't have a BSOD problem, yet it provides the info that we need.
      My System SpecsSystem Spec

  8. #28


    Posts : 40
    Windows 8.1 Pro 64bit, Linux Mint 17 64bit


    So far, no BSODs with Driver Verifier on. Should I wait a little longer or should I do something else?
      My System SpecsSystem Spec

  9. #29


    Redmond
    Posts : 651
    Windows 8.1 x64


    It actually does look like kernel pool is corrupt, the reference address is corrupt, and the memory to reference is corrupt - they're all potentially valid memory addresses (nothing odd here), but none of the addresses point to valid memory:
    Code:
    3: kd> !pool fffff80048304ba2Pool page fffff80048304ba2 region is Nonpaged pool
    GetUlongFromAddress: unable to read from fffff800484ad470
    Unable to get pool big page table. Check for valid symbols.
    fffff80048304000 is not valid pool. Checking for freed (or corrupt) pool
    Bad previous allocation size @fffff80048304000, last size was 0
    ***
    *** An error (or corruption) in the pool was detected;
    *** Attempting to diagnose the problem.
    ***
    *** Use !poolval fffff80048304000 for more details.
    Pool page [ fffff80048304000 ] is __inVALID.
    
    Analyzing linked list...
    [ fffff80048304000 ]: invalid previous size [ 0x3c ] should be [ 0x0 ]
    [ fffff80048304000 --> fffff80048304380 (size = 0x380 bytes)]: Corrupt region
    
    
    Scanning for single bit errors...
    None found
    The fact that driver verifier made the problem disappear means it's very likely actually a driver issue, and not bad hardware. Driver verifier, by default, uses special hooks to monitor driver function calls and catch offending bad code doing specific IRQL behaviors and memory allocations/de-allocations. However, if kernel pool corruption is happening due to a buffer overrun or underrun, then having driver verifier on can simply cause the problem to no longer happen due to the overhead imposed by the driver verifier engine (for example, the driver could have a race condition that causes bad behavior, but adding the overhead causes the problem to no longer occur because the race condition is slowed to the point it never happens).

    Since these dumps have pool corruption, and driver verifier "fixes" things, I'd say we probably want to use special pool rather than driver verifier at this point to catch the offender. It seems we have a driver causing pool over or underruns, not necessarily doing other bad things in the driver itself.
      My System SpecsSystem Spec

  10. #30


    Posts : 40
    Windows 8.1 Pro 64bit, Linux Mint 17 64bit


    So I would want to keep special pool on for third party drivers then in Driver Verifier settings?
      My System SpecsSystem Spec

Page 3 of 6 FirstFirst 12345 ... LastLast
BSOD Error code 139
Related Threads
Windows 8 crashes without error code or BSOD in BSOD Crashes and Debugging
My sony vaio laptop with windows 8 crashes frequently without any BSOD or error code. I am here attaching sf debug files. Please let me know , how to resolve this issue. Thnaks
BSOD Error Code 0x8000000000000002 in BSOD Crashes and Debugging
Hi, I can't remember exactly what I was doing but my Laptop crashed and I looked in eventviewer and found the error code
BSOD on File:\ BCD error code 0xc0000034 in BSOD Crashes and Debugging
After shutting down because of nonresponding applications, I started to the computer again to find the computer would not fail on automatic fix, after going through this several times I was presented with a BSOD on BSOD on File:\ BCD error code 0xc0000034, I do not have an installation cd, the...
Random BSOD error code 0x124 in BSOD Crashes and Debugging
Hello, I've recently upgraded my pc where I installed a new Motherboard (ASUS Z87-PLUS) , CPU (I5 4670k) and a GPU (GTX780TI). After having done this I've started encountering some problems while using it. The computer has started BSODing along with the message "WHEA_UNCORRECTABLE_ERROR". The...
BSOD error code 0xc000000f in BSOD Crashes and Debugging
Ok everyone i am new to alot of this windows stuff.. about my problem: i turned off my computer last night woke up this morning and a blue screen popped up saying "Recovery Your PC needs to be repaired A required device isnt connected or cant be accessed Error code:0xc000000f you"ll need to...
Hi guys, im brand new to this forum and although i see my self as good with computers i am currently at a dead end with this.... and just before people ask, It bsod's and sticks at 0% and creates no minidump file. Sorry if this has been talked about before, but after a lot of searching on the...
(BSOD) Error Code: 0xc0000185 in BSOD Crashes and Debugging
First of all sorry for not using the BSOD Posting Instructions -__-; I couldn't even get to my desktop to do so... Here is the full information of my Blue Screen, any thoughts/help appreciated. ________________________________________ Recovery Your PC needs to be Repaired The operating...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook