Windows 8 and 8.1 Forums

multiple BSOD's with different errors.

  1. #1

    Posts : 1
    windows 8.1

    multiple BSOD's with different errors.

    This is my first post on any forum really need help figuring this out, sorry if I don't post something correctly.

    I have had errors since day one with this custom computer from digital storm, and have had to replace ram, and the ssd because of hardware failure. The system is fairly stable now but only running two sticks of ram at 8gbs each. originally was running 32gb but 1 stick went bad, when I install the replacement ram is when I really start to get these errors. To get my computer back to this stable point I can only run two of the original sticks of ram and still occasionally get errors when gaming or sometimes at random. hopefully the crash files can give you guys an idea of where I should start. let me know if you guys need anything else.

      My System SpecsSystem Spec

  2. #2

    Posts : 2,097
    Windows 8.1 Industry Pro B-)

    Hi sno7373 ^_^,

    I have analyzed your dump files and below has been provided an analysis of the same for informative purposes :-

    A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error condition.
    Let's check the Parameter 2 and see what it reveals -
    1: kd> !errrec ffffe00150364028
    Common Platform Error Record @ ffffe00150364028
    Record Id     : 01d0d91092606095
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 8/17/2015 17:23:00 (UTC)
    Flags         : 0x00000000
    Section 0     : Processor Generic
    Descriptor    @ ffffe001503640a8
    Section       @ ffffe00150364180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Generic
    Flags         : 0x00
    Level         : 0
    CPU Version   : 0x00000000000306c3
    Processor ID  : 0x0000000000000001
    Section 1     : x86/x64 Processor Specific
    Descriptor    @ ffffe001503640f0
    Section       @ ffffe00150364240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    Local APIC Id : 0x0000000000000001
    CPU Id        : c3 06 03 00 00 08 10 01 - bf fb da 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    Proc. Info 0  @ ffffe00150364240
    Section 2     : x86/x64 MCA
    Descriptor    @ ffffe00150364138
    Section       @ ffffe001503642c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    Error         : DCACHEL0_WR_ERR (Proc 1 Bank 1)
      Status      : 0xbf80000000000124
      Address     : 0x000000019e56fa00
      Misc.       : 0x0000000000000086
    We can see that the system crashed because Windows detected that the CPU was not able to write to the L0 Cache of the CPU (Bank 1). This error (Same Cache and Bank is blamed) is consistent across different dump files (2 of them are NTFS_FILE_SYSTEM).

    This indicates that this is a faulty processor we are dealing with. And like you said that you are still experiencing the problem after removing the RAM sticks, it is very likely that the CPU is the problem here.

    In case you are overclocking, please STOP and immediately reset back to STOCK settings before we proceed further.

    Below is a list of 3rd party drivers present on your system -
    **************************Wed Aug 19 07:29:42.520 2015 (UTC + 5:30)**************************
    AsUpIO.sys                  Tue Aug  3 08:17:59 2010 (4C57835F)
    ASUSFILTER.sys              Tue Sep 20 21:16:33 2011 (4E78B559)
    AiChargerPlus.sys           Thu Apr 19 06:47:35 2012 (4F8F67AF)
    btwl2cap.sys                Thu Jul 26 20:44:41 2012 (50115EE1)
    AsIO.sys                    Wed Aug 22 15:24:47 2012 (5034AC67)
    asmtufdriver.sys            Fri Sep 28 16:25:29 2012 (50658221)
    HECIx64.sys                 Tue Dec 18 01:02:21 2012 (50CF7345)
    Rt630x64.sys                Fri Dec 28 05:34:06 2012 (50DCE1F6)
    btwpanfl.sys                Tue Jan  1 03:12:33 2013 (50E206C9)
    ndisrd.sys                  Thu Feb 21 08:10:15 2013 (5125890F)
    btwavdt.sys                 Thu Feb 21 21:55:06 2013 (51264A62)
    btwaudio.sys                Thu Feb 21 21:55:57 2013 (51264A95)
    btwrchid.sys                Thu Feb 21 21:56:05 2013 (51264A9D)
    vmic_x64.sys                Wed Feb 27 14:36:50 2013 (512DCCAA)
    e1i63x64.sys                Wed Mar 20 13:07:29 2013 (51496739)
    bcmwl63a.sys                Tue Apr 23 16:30:13 2013 (517669BD)
    RTKVHD64.sys                Tue Jul 16 17:40:14 2013 (51E53826)
    bcbtums.sys                 Wed Aug  7 20:41:22 2013 (5202639A)
    intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
    btwampfl.sys                Sat Aug 31 00:02:26 2013 (5220E53A)
    nvhda64v.sys                Fri Apr 17 00:33:16 2015 (55300774)
    mfencbdc.sys                Tue Jun 23 00:22:33 2015 (55885971)
    mfehidk.sys                 Sat Jun 27 04:40:48 2015 (558DDBF8)
    mfewfpk.sys                 Sat Jun 27 04:41:02 2015 (558DDC06)
    mfeavfk.sys                 Sat Jun 27 04:41:56 2015 (558DDC3C)
    mfefirek.sys                Sat Jun 27 04:42:59 2015 (558DDC7B)
    mfeaack.sys                 Sat Jun 27 04:45:39 2015 (558DDD1B)
    nvvad64v.sys                Thu Jul  2 07:42:51 2015 (55949E23)
    nvlddmkm.sys                Fri Aug  7 04:48:07 2015 (55C3EB2F)
    **************************Tue Aug 18 11:59:49.818 2015 (UTC + 5:30)**************************
    npf.sys                     Fri Jun 25 22:20:58 2010 (4C24DE72)
    cfwids.sys                  Sat Jun 27 04:43:28 2015 (558DDC98)
    NvStreamKms.sys             Fri Jul 17 07:13:42 2015 (55A85DCE)
    mfesapsn.sys                Tue Aug  4 20:43:20 2015 (55C0D690)
    **************************Mon Aug 17 22:53:00.095 2015 (UTC + 5:30)**************************
    wdcsam64.sys                Wed Apr 16 14:09:08 2008 (4805BB2C)
    **************************Mon Aug 17 11:08:54.978 2015 (UTC + 5:30)**************************
    nvlddmkm.sys                Fri Aug  7 08:52:42 2015 (55C42482)
    **************************Mon Aug 10 09:57:11.394 2015 (UTC + 5:30)**************************
    xusb22.sys                  Tue Mar 18 13:48:41 2014 (53280161)
    mfedisk.sys                 Thu Feb 12 03:23:04 2015 (54DBCF40)
    mfencbdc.sys                Fri Mar 27 01:14:11 2015 (5514618B)
    nvlddmkm.sys                Thu Jul 23 05:45:54 2015 (55B0323A)
    mfesapsn.sys                Mon Jul 27 23:31:05 2015 (55B671E1)
    **************************Sun Aug  2 03:32:59.258 2015 (UTC + 5:30)**************************
    NvStreamKms.sys             Fri Jun 12 00:18:02 2015 (5579D7E2)
    vmic_x64.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.
    mfeaack.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.
    mfesapsn.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.
    mfedisk.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.
    mfesapsn.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.

    Kindly follow the below steps -
    1. Please remove any ASUS Bloatware (Drivers Highlighted in RED) present on the system. These bloatware utilities are known to cause problems and hence before we proceed further, make sure that they have been removed.
    2. Like I said above, reset to STOCK settings in case you are overclocking.
    3. Please run Prime95 according to this guide -

      Prime95 download site:
      Prime95 Setup:
      - extract the contents of the zip file to a location of your choice
      - double click on the executable file
      - select "Just stress testing"
      - select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
      - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
      The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
      Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
      Monitor the CPU temperature and DON'T let it exceed 85║C. If it does, then you probably have a CPU cooling problem.
      - CPU temps exceeding 60║C can cause errors in Prime95. Fix the cooling solution first, then run Prime95 again.
      This won't necessarily crash the system - but check the output in the test window for errors.
      The Test selection box and the stress.txt file describes what components that the program stresses.
      NOTE: Errors should be considered when:
      - the system BSOD's during Prime95
      - the system freezes during Prime95 (this is different than the extreme slowness caused by the program using all your RAM and CPU)
      - the Prime95 program crashes
      - the Prime95 program shows errors in it's display
      - there are errors in the Prime95 results file
      More details on the use of this test:
    4. Kindly run the Intel Burn Test according to this **LINK** and report back any errors.

    While running the stress tests, please keep a check on the temperature of the system using the free utility CoreTemp. Report back the system temperatures as well while the system is idle and when you are running the stress tests.

    Let me know how it goes ^_^

      My System SpecsSystem Spec

multiple BSOD's with different errors.
Related Threads
Hello, I am having frequent BSOD with Kmode_Exception_not_handled and occasionally no error code. I have tried to remedy this by updating drivers, unistalling programs that I don't use/programs I've installed since the error started becoming common. I also tried to verify drivers but I got...
BSOD - Multiple Errors. Custom PC in BSOD Crashes and Debugging
I have a custom PC and have been dealing with BSOD for a little while now. It was very random at first but now it happens almost daily. I have tried updating drivers and even bought a new graphics card to no avail. It happens at random, sometimes i will be putting heavy load on the PC and other...
BSOD multiple errors, multiple situations in BSOD Crashes and Debugging
Hey EightForums, I am new to you however not new to troubleshooting over forums as I used to run Ubuntu and as you may know that is non-stop forum troubleshooting. So lets get into this. Having some trouble with my girlfriend's windows 8.1 PC. I've tried doing a system refresh with no luck....
Multiple BSOD errors in BSOD Crashes and Debugging
I own a dell precision m6800. For about 3 weeks now I have been experiencing a lot of BSOD almost everyday. Sometimes without doing anything the laptop bluescreens. I have tried restoring to factory setting but BSOD keeps occuring. I downloaded the bluescreenview and i see most of the bsod are...
Solved BSOD's at random, multiple errors in BSOD Crashes and Debugging
I've been having fairly frequent, seemingly random BSOD's lately, only major hardware change I've made recently was upgrade my videocard to my current Nvidia GTX 750 Ti. Errors are multiple, including Kernel_Security_Check_Failure, PFN_List_Corrupt, and System_Service_Exception. Ran memory...
Solved windows 8.1 multiple BSOD Errors in BSOD Crashes and Debugging
Hello.. I have mltiple BSOD errors..:cry:
Multiple BSOD errors in BSOD Crashes and Debugging
Hi! i have a clean install of windows 8 x64 and i see BSODs every 1 or 2 or 3 days. even one time before installing win 8, when i inserted DVD of windows to install it, a BSOD accured! windows is totally updated and hard disk is free of errors (based on windows error checking tool report). I...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook