BSOD when intensive strain on pc and power functions, like shuttingdow


  1. Posts : 5
    windows 10
       #1

    BSOD when intensive strain on pc and power functions, like shuttingdow


    Sometimes when i play a really intensive game on my system it crashes with a error code of non correctable. also whenever i shutdown, sleep, or restart the pc hangs/crashes and then restarts, when this happens i get a nonpaged error. This problem has been happening for about 2 weeks i tried reinstalling with i disk image but i think it restored the problem.


    Thanks for your help
    Attachment 107757
    BSOD file included


    i have an older bsod file also if you want but it dosent include the crashing when on heavy strain that happend afterwards
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    Lookas like a fatal machine check:
    Code:
    2: kd> !errrec ffffe5032bc43028
    ===============================================================================
    Common Platform Error Record @ ffffe5032bc43028
    -------------------------------------------------------------------------------
    Record Id     : 01d22ff79a1dd05b
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 10/27/2016 2:39:35 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe5032bc430a8
    Section       @ ffffe5032bc43180
    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  : 0x0000000000000004
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe5032bc430f0
    Section       @ ffffe5032bc43240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000004
    CPU Id        : c3 06 03 00 00 08 10 04 - bf fb fa 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  @ ffffe5032bc43240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe5032bc43138
    Section       @ ffffe5032bc432c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : DCACHEL0_WR_ERR (Proc 2 Bank 1)
      Status      : 0xbf80000000000124
      Address     : 0x000000041e447c00
      Misc.       : 0x0000000000000086
    The following is from a post by Patrick Barker for the same error in a different forum:
    Code:
    The specific type of error is DCACHEL0_WR_ERR. This implies a L0 Cache Write error.  
    ---------------------
    
      
    There is only so much you can do with a  bugcheck like this until it comes down to a faulty processor that will  need to be replaced. Start from 1 and work downward:
    
    1. Ensure your temperatures are within standard and  nothing's overheating. You can use a program such as Speccy if you'd  like to monitor temps - http://www.piriform.com/speccy
    
    2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting -  http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm
    
    3. Ensure your BIOS is up to date.
    
    4. The only software conflict  that can usually cause *124 bugchecks are OS to BIOS utilities from  manufacturer's like Asus' AI Suite. If you have something like this  software-wise, remove it ASAP.
    
    5. If all of the above fail, the only left to do is replace your processor as it is faulty.
    If you read further down, clearing the CMOS resolved the problem. Give the suggested fixes a try.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:47.
Find Us




Windows 10 Forums