BSOD while playing DS2 and watching stream


  1. Posts : 2
    Windows 7 64 bit
       #1

    BSOD while playing DS2 and watching stream


    not really running my pc hard, just BSoD pretty commonly when playing darksouls 2 and listening to music or watching a stream. i see issues with WDF01000.sys, curious if anything else
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Allot of important info is missing from your zip, please follow Blue Screen of Death (BSOD) Posting Instructions to grab all and upload a new report here.
      My Computer


  3. Posts : 2
    Windows 7 64 bit
    Thread Starter
       #3

    thought i had followed those, well. while im going through that again, i have compressed a log of 3 minidumps maybe this will help some while i run through this process again.

    edit: have updloaded the new zip they gave me as well. the file size of this one leaves me with more hope =p
    Last edited by brendanv; 22 Mar 2015 at 00:33. Reason: adding a file
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Code:
    
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\Debug Home-PC-Fri_03_20_2015_223914_10\032015-20311-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
    Machine Name:
    Kernel base = 0xfffff800`0260b000 PsLoadedModuleList = 0xfffff800`0284f890
    Debug session time: Fri Mar 20 20:10:24.243 2015 (UTC + 6:00)
    System Uptime: 0 days 0:00:14.743
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    .............................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa80087ba8f8, 0, 0}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: fffffa80087ba8f8, 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:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`01fa15b0 fffff800`028cccb9 : fffffa80`087ba8d0 fffffa80`06d2c040 00000000`0000000e 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`01fa1ad0 fffff800`027ad157 : fffffa80`087ba8d0 fffff800`028272d8 fffffa80`06d2c040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`01fa1b00 fffff800`02714505 : fffff800`02888d00 00000000`00000001 fffffa80`07c22820 fffffa80`06d2c040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`01fa1b40 fffff800`02689a95 : fffff880`01045e00 fffff800`027144e0 fffffa80`06d2c000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`01fa1b70 fffff800`0291eb8a : 00000000`00000000 fffffa80`06d2c040 00000000`00000080 fffffa80`06d20840 : nt!ExpWorkerThread+0x111
    fffff880`01fa1c00 fffff800`026718e6 : fffff880`01d42180 fffffa80`06d2c040 fffff880`01d4d040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`01fa1c40 00000000`00000000 : fffff880`01fa2000 fffff880`01f9c000 fffff880`021ee760 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_bus_prv
    
    FAILURE_ID_HASH:  {78c2f422-5335-4ef3-5cef-a28518da5023}
    
    Followup: MachineOwner
    ---------
    
    
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try
      My Computer


 

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

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