Random BSOD's

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by royalandy, Jun 27, 2013.

  1. royalandy

    royalandy New Member

    Joined:
    Jun 27, 2013
    Messages:
    4
    Likes Received:
    0
    In the last week i have randomley BSOD's and total freeze's, just in windows and while i browsing on internet, never in games. So tuesday i decided to reinstall win 7, and bsod's and freeze's are still here.
    In last year i did not install new hardware, so this is not the problem, i try remove ram and replace it 1 by 1 and this still happen.

    Everytime on bluscreen is diferent error message:
    IRQL_NOT_LESS_OR_EQUAL ,
    MEMORY_MANAGMENT,
    PAGE_FAULT_IN_NONPAGED_AREA,
    KMODE_EXCEPTION_NOT_HANDLED
    or just total freeze.

    I know that my computer is not a new, but before bsod's it work great.

    Sorry for my bad english [​IMG]

    PC specs:
    Motherboard: MSI MS-7519
    CPU:Q8200
    RAM: 8GB
    Graphic:NVIDIA GeForce GTX 560 Ti 448

    Thanks in advance!View attachment 27-06-2013.rar
     
  2. Vir Gnarus

    Vir Gnarus Active Member

    Joined:
    Jan 8, 2013
    Messages:
    199
    Likes Received:
    9
    Your RAM or motherboard is most likely bad. Remove all RAM except first stick, then run Memtest86+ on it for 5+ passes (all tests once = 1 pass), then replace with another stick and repeat. Do the same for all your RAM sticks. If one shows up bad you found the bad RAM; if most or all show up bad it is most likely your motherboard that's bad; if none show up bad it's most likely your motherboard that's bad.

    Oh, make sure you do not have anything overclocked. Reset to safe defaults, not "normal".

    Analysts:

    CPU has reported an issue with memory bus during RAM-to-CPU crosstalk. Checked driver list and didn't see any motherboard software installed that can cause this. Most certainly bad hardware, with RAM/Mobo being most suspect.

    Code:
    2: kd>[COLOR=#0000cd] !analyze -v[/COLOR]
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    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 conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: [COLOR=#008000]fffffa8007a78038[/COLOR], Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`031d26f0 fffff800`02eddca9 : fffffa80`07a78010 fffffa80`0672d040 00000000`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`031d2c10 fffff800`02dbee87 : fffffa80`07a78010 fffff800`02e382d8 fffffa80`0672d040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`031d2c40 fffff800`02d26285 : fffff800`02e99ae0 00000000`00000001 fffffa80`07676820 fffffa80`0672d040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`031d2c80 fffff800`02c9c251 : fffff880`01160e00 fffff800`02d26260 fffffa80`0672d000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`031d2cb0 fffff800`02f30ede : 00000000`00000000 fffffa80`0672d040 00000000`00000080 fffffa80`0669e890 : nt!ExpWorkerThread+0x111
    fffff880`031d2d40 fffff800`02c83906 : fffff880`02f64180 fffffa80`0672d040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031d2d80 00000000`00000000 : fffff880`031d3000 fffff880`031cd000 fffff880`03d49740 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    ---------
    
    2: kd> [COLOR=#0000cd]!errrec [/COLOR][COLOR=#008000]fffffa8007a78038[/COLOR]
    ===============================================================================
    Common Platform Error Record @ fffffa8007a78038
    -------------------------------------------------------------------------------
    Record Id     : 01ce71bc578ddba4
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 6/25/2013 15:55:06 (UTC)
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007a780b8
    Section       @ fffffa8007a78190
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    [COLOR=#ff0000]Error Type    : BUS error
    Operation     : Generic[/COLOR]
    Flags         : 0x00
    Level         : 0
    CPU Version   : 0x0000000000010677
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007a78100
    Section       @ fffffa8007a78250
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : 77 06 01 00 00 08 04 00 - 9d e3 08 00 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  @ fffffa8007a78250
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007a78148
    Section       @ fffffa8007a782d0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    [COLOR=#ff0000]Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR[/COLOR] (Proc 0 Bank 0)
      Status      : 0xf200084000000800
    
     
  3. royalandy

    royalandy New Member

    Joined:
    Jun 27, 2013
    Messages:
    4
    Likes Received:
    0
    I've done everything you recommend, mem test return no errors. I found the problem, this crashes appears only when ram is in dual channel, no matther which ram i put in, crash in dual channel. Now I can have only 2 stick in, but only in single channel (no crashes at all about 5 days). I guess the motherboard is bad.
     
  4. Vir Gnarus

    Vir Gnarus Active Member

    Joined:
    Jan 8, 2013
    Messages:
    199
    Likes Received:
    9
    Ah, wonderful. Swapping sticks and whatnot actually kind of a two-fold test, to test configuration changes and also to test each stick for integrity issues. Glad you found the problem that easily, as motherboard issues often are very difficult to discover.

    Btw, did you make sure when you purchased the RAM that it was listed as compatible for that motherboard? It's also necessary to check RAM setups as well in their compatibility chart, as they typically show that some configurations are unsupported for certain RAM models whereas the same RAM does fine is installed differently. Honestly though, that only seems to happen with timer-shortened high-profile RAM sticks.
     

Share This Page

Loading...