BSOD when trying to stream using xsplit

[JamesKappa]

Hey guys, My friends having a few issues with her computer.
When she tries to start streaming she keeps getting a BSOD (using xsplit)
I've got her to download the log collector and upload it for me to post here,
If you guys could help out and sift though and see what the problem is that would be amazing.

 

[axe0]

Hi JamesKappa,

Welcome to the 7forums.

Please move some files from the C partition to increase the free space to at least 10-15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background.

   Warning

Less free space could cause BSOD's

The error is 0x124 WHEA_UNCORRECTABLE_ERROR (Windows Hardware Error Architecture)
This means that there are problems with your hardware, but this error is also caused by overclocking or faulty drivers.

The problem is that there is a time out problem with the cache on core 4.

5: kd> !errrec fffffa800d30c028
===============================================================================
Common Platform Error Record @ fffffa800d30c028
-------------------------------------------------------------------------------
Record Id     : 01d1028855179644
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/9/2015 12:45:56 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800d30c0a8
Section       @ fffffa800d30c180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000005

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800d30c0f0
Section       @ fffffa800d30c240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000005
CPU Id        : c3 06 03 00 00 08 10 05 - 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  @ fffffa800d30c240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800d30c138
Section       @ fffffa800d30c2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR="red"]Error         : Internal timer (Proc 5 Bank 4)[/COLOR]
  Status      : 0xbe00000000800400
  Address     : 0x000000006b22f8cc
  Misc.       : 0x000000006b22f8cc

Looking at the stack, it starts with the CPU driver.
Please check Intel for driver updates for the CPU.

   Note

Please make sure nothing is overclocked, if there is anything overclocked revert back to stock.

STACK_TEXT:  
fffff880`03091b58 fffff800`02e12a3b : 00000000`00000124 00000000`00000000 fffffa80`0d30c028 00000000`be000000 : nt!KeBugCheckEx
fffff880`03091b60 fffff800`02fd6e63 : 00000000`00000001 fffffa80`0d0eda60 00000000`00000000 fffffa80`0d0edab0 : hal!HalBugCheckSystem+0x1e3
fffff880`03091ba0 fffff800`02e12700 : 00000000`00000728 fffffa80`0d0eda60 fffff880`03091f30 fffff880`03091f00 : nt!WheaReportHwError+0x263
fffff880`03091c00 fffff800`02e12052 : fffffa80`0d0eda60 fffff880`03091f30 fffffa80`0d0eda60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03091d50 fffff800`02e11f0d : 00000000`00000008 00000000`00000001 fffff880`03091fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03091d90 fffff800`02e05e88 : 00000000`00000000 fffff880`03089180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03091dc0 fffff800`02ebaeac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03091df0 fffff800`02ebad13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03091f30 fffff880`057b9c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`030b1b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR="Red"]intelppm[/COLOR]!MWaitIdle+0x19

Some information about this driver.

5: kd> lmvm intelppm
start             end                 module name
fffff880`057b7000 fffff880`057cd000   intelppm   (pdb symbols)          C:\ProgramData\dbg\sym\intelppm.pdb\08BB31C0378D48EC8CB513240E096A171\intelppm.pdb
    Loaded symbol image file: intelppm.sys
    Mapped memory image file: C:\ProgramData\dbg\sym\intelppm.sys\4A5BC0FD16000\intelppm.sys
    Image path: \SystemRoot\system32\DRIVERS\intelppm.sys
    Image name: [U]intelppm.sys[/U]
    Timestamp:        [COLOR="red"][U]Tue Jul 14 01:19:25 2009[/U][/COLOR] (4A5BC0FD)
    CheckSum:         0000F4EC
    ImageSize:        00016000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     intelppm.sys
    OriginalFilename: intelppm.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  Processor Device Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

 

[JamesKappa]

I managed to get a friend of mine (who happens to be a network engineer) to have a look on her computer via teamviewer, He free'd up about 36GB on her C drive and fixed a few other niggling problems. She started streaming to test if it had fixed the problem (usually crashes after a couple of mins) The stream lasted maybe half an hour before crashing (so the free space certainly helped) he did however say if the problem occured that it would most likely be a problem with the RAM. Would replacing both Dimms solve the problem in your opinion? Or is that just one of many possible solutions and/or causes (if it is even the cause)

 

[axe0]

Can he explain why he thinks that?

 

[JamesKappa]

Intel drivers up to date, Nothing overclocked.