Windows 8 and 8.1 Forums


Intermittent BSOD's 'ntoskrnl.exe+5b1f85'

  1. #1


    Posts : 3
    Windows 8

    Intermittent BSOD's 'ntoskrnl.exe+5b1f85'


    Hi guys, wondering if you can help. I've recently throw some upgrades into my system prior to these bluescreens making me sad - an r9 290x, Samsung Evo 250GB SSD, Asus Xonar DG and a 750w Corsair PSU. I'm trying to find the culprit of this problem, but upgrading so many parts has made it quite tricky...

    For background , the rest of the system is an AMD 8350, Gigabyte ga-78lmt-usb3 (I know, it's the last upgrade on my list), 16GB's of RAM, a WD Green 1TB HDD, a H100, 8 case fans (including the 4 in push/pull on the H100 ofc) - This stuff was all running absolutely 100% perfect , the things I have removed are a 600W OCZ PSU and a GTX 660.

    I did not transfer the OS, I completely wiped my WD drive after backing up externally, and installed fresh Windows 8 on my system. I have since run all updates, to ensure the OS is completely up to date.

    These BSOD's are happening intermittently - two times it has happened while I have been on the desktop - one of them happened a few minutes after I booted up my computer and was just casually browsing the internet, but most of the time they have happened to me while gaming - this is primarily what I use the computer for however, so although it points to the GPU 98% of my usage is while gaming.

    I have tested everything to the best of my ability thus far

    GPU - I have run both 3DMark and Heaven for over 30 minutes to test for GPU stability. Not only does it not crash, it looks so awesome. I have also played Battlefield for over an hour on it (max settings, 4x MSAA no vsync so stressing the card) as well as played for 5-6 hour sprints in FFXIV:ARR - granted that's not the most stressful of games though.

    RAM - MEM test, 300% on all 16GB's. The system was running for hours while doing this.

    SSD/HDD - I have used the Samsung provided tool on the SSD and it states the the SSD is 100% healthy. The HDD I am yet to test so will have to report back, but given that I was using it for 6 months and it was not touched at all (other than changing the SATA power over) during the upgrade process.

    CPU -
    Prime95 ran for the duration of the last episode of The Walking Dead, no core/thread fails

    Soundcard - Not sure how to test this if I'm completely honest. All of my audio is running through it, and I've disabled my onboard audio.

    PSU - Again, not sure what I can do to test this - but it's not crapping out during benchmarks, so there's that.


    So I just..I don't know. I've used bluescreenview to look at the dumps, but I've never dabbled in this sort of thing beyond stability checking on things. I've attached my latest dmp file, that happened not too long before I started typing this post. If anyone with a bit more knowledge than me could take a look I'd really appreciate any advice you could give.

    Help me eight forums you are my only hope!

    (Also, it wouldn't let me attach the .dmp file - I .rar'd it up, so if you do need me to give it to you another way (mediafire maybe?) then please just let me know.

      My System SpecsSystem Spec

  2. #2


    Posts : 3
    Windows 8

    Update: SF_Diagnostic_Tool files


    Just ran the SF_Diagnostic_Tool.exe and here is the zip of the files attached.
      My System SpecsSystem Spec

  3. #3


    Posts : 660
    windows 8.1


    All your dumpfiles are BugCheck 124, {0, ffffe00002441038, 0, 0}
    Probably caused by : AuthenticAMD
    Usual causes: Hardware, Incompatibility, May be driver corruption

    Code:
    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: ffffe00002441038, 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:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    STACK_TEXT:  
    ffffd000`20967500 fffff802`e83ee2e8 : ffffe000`0044c180 ffffe000`02441010 fffff802`e8350f00 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x81
    ffffd000`20967a30 fffff802`e823524c : ffffe000`02441010 ffffd000`20967b50 fffff802`e8350fa0 ffffe000`0044c040 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
    ffffd000`20967a60 fffff802`e8236069 : fffff802`e8350fa0 ffffd000`20967b50 fffff802`e8350fa0 ffffd000`20967b50 : nt!WheapProcessWorkQueueItem+0x48
    ffffd000`20967aa0 fffff802`e811e1b9 : fffff802`e8554094 fffff802`e8236044 ffffc000`002df430 ffffe000`0044c040 : nt!WheapWorkQueueWorkerRoutine+0x25
    ffffd000`20967ad0 fffff802`e810a2e4 : 00000000`00000000 ffffe000`0044c040 ffffe000`0044c040 ffffe000`001ab040 : nt!ExpWorkerThread+0x2b5
    ffffd000`20967b80 fffff802`e81d12c6 : ffffd000`201e8180 ffffe000`0044c040 ffffd000`201f4340 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`20967be0 00000000`00000000 : ffffd000`20968000 ffffd000`20961000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME:  AuthenticAMD
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv
    FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}
    Followup: MachineOwner
    After running the errrec command.
    Code:
    Common Platform Error Record @ ffffe00002441038
    -------------------------------------------------------------------------------
    Record Id     : 01cf4eb197bd1805
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 4/2/2014 20:24:49 (UTC)
    Flags         : 0x00000002 PreviousError
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000024410b8
    Section       @ ffffe00002441190
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 3
    CPU Version   : 0x0000000000600f20
    Processor ID  : 0x0000000000000000
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00002441100
    Section       @ ffffe00002441250
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    Local APIC Id : 0x0000000000000000
    CPU Id        : 20 0f 60 00 00 08 08 00 - 0b 32 98 3e ff fb 8b 17
                    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  @ ffffe00002441250
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00002441148
    Section       @ ffffe000024412d0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
      Status      : 0xfe00000000070f0f
      Address     : 0x00000000fd7869b8
      Mi

    This error does not always indicate a failure in the processor, but can also be caused by problems in the BIOS, so before sending the CPU back to the manufacturer or purchasing a replacement, always ensure that all of the system drivers and the bios are up to date.
    You should perform a stress test on the CPU to help determine whether a hardware issue exists
    You have already the latest Bios versionF4 from 2012/10/19 installed but it is probably not compatible with windows 8.1.
    Make sure you have the latest chipset installed.

    To keep your system as stable as can be, please if you do stop all overclocking.

    MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Windows systems (it'sdriver is usually RTCore64.sys).
    Please un-install it immediately! (source Usasma BSODexpert).

    Advice to run some CPU stress test to exclude hardware faillure.

    In the WER= Windows Error Report i found a report with USB\VID_05AC&PID_12A8. This belongs to a Apple mobile device in your driverlist i found
    USBAAPL64 Apple Mobile USB Drive Kernel 27/11/2012 23:38:02 .See if there is a windows 8.1 driver.





      My System SpecsSystem Spec

  4. #4


    Posts : 3
    Windows 8


    Quote Originally Posted by lifetec View Post
    All your dumpfiles are BugCheck 124, {0, ffffe00002441038, 0, 0}
    Probably caused by : AuthenticAMD
    Usual causes: Hardware, Incompatibility, May be driver corruption

    Code:
    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: ffffe00002441038, 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:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    STACK_TEXT:  
    ffffd000`20967500 fffff802`e83ee2e8 : ffffe000`0044c180 ffffe000`02441010 fffff802`e8350f00 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x81
    ffffd000`20967a30 fffff802`e823524c : ffffe000`02441010 ffffd000`20967b50 fffff802`e8350fa0 ffffe000`0044c040 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
    ffffd000`20967a60 fffff802`e8236069 : fffff802`e8350fa0 ffffd000`20967b50 fffff802`e8350fa0 ffffd000`20967b50 : nt!WheapProcessWorkQueueItem+0x48
    ffffd000`20967aa0 fffff802`e811e1b9 : fffff802`e8554094 fffff802`e8236044 ffffc000`002df430 ffffe000`0044c040 : nt!WheapWorkQueueWorkerRoutine+0x25
    ffffd000`20967ad0 fffff802`e810a2e4 : 00000000`00000000 ffffe000`0044c040 ffffe000`0044c040 ffffe000`001ab040 : nt!ExpWorkerThread+0x2b5
    ffffd000`20967b80 fffff802`e81d12c6 : ffffd000`201e8180 ffffe000`0044c040 ffffd000`201f4340 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`20967be0 00000000`00000000 : ffffd000`20968000 ffffd000`20961000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME:  AuthenticAMD
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv
    FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}
    Followup: MachineOwner
    After running the errrec command.
    Code:
    Common Platform Error Record @ ffffe00002441038
    -------------------------------------------------------------------------------
    Record Id     : 01cf4eb197bd1805
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 4/2/2014 20:24:49 (UTC)
    Flags         : 0x00000002 PreviousError
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000024410b8
    Section       @ ffffe00002441190
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 3
    CPU Version   : 0x0000000000600f20
    Processor ID  : 0x0000000000000000
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00002441100
    Section       @ ffffe00002441250
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    Local APIC Id : 0x0000000000000000
    CPU Id        : 20 0f 60 00 00 08 08 00 - 0b 32 98 3e ff fb 8b 17
                    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  @ ffffe00002441250
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00002441148
    Section       @ ffffe000024412d0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
      Status      : 0xfe00000000070f0f
      Address     : 0x00000000fd7869b8
      Mi

    This error does not always indicate a failure in the processor, but can also be caused by problems in the BIOS, so before sending the CPU back to the manufacturer or purchasing a replacement, always ensure that all of the system drivers and the bios are up to date.
    You should perform a stress test on the CPU to help determine whether a hardware issue exists
    You have already the latest Bios versionF4 from 2012/10/19 installed but it is probably not compatible with windows 8.1.
    Make sure you have the latest chipset installed.

    To keep your system as stable as can be, please if you do stop all overclocking.

    MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Windows systems (it'sdriver is usually RTCore64.sys).
    Please un-install it immediately! (source Usasma BSODexpert).

    Advice to run some CPU stress test to exclude hardware faillure.

    In the WER= Windows Error Report i found a report with USB\VID_05AC&PID_12A8. This belongs to a Apple mobile device in your driverlist i found
    USBAAPL64 Apple Mobile USB Drive Kernel 27/11/2012 23:38:02 .See if there is a windows 8.1 driver.





    Hi there, thanks very much for the response.

    I'm at work at the moment, but I will be following your advice when I get home.

    I do however know that all my drivers (inc. chipset) are up to date. Although yes, the BIOS probably doesn't have support for Windows 8.1, I have been running this processor/motherboard since Windows 8 came out, and upgraded to Windows 8.1 when it was released..strange that if that is causing it, that it's giving me problems now and hasn't for the past year or so.

    All overclocks have been reset, I was only using MSI Afterburner to monitor the GPU temp. This will be removed to see if the problem persists.

    So do you believe this is definately the processor's fault? Is there a possibility it could be the motherboard? I only ask because I was meaning to buy a new one anyway, so I could always get a more up to date motherboard before RMA'ing my processor to test it with..

    That Apple Mobile USB Drive Kernel is probably the tethering driver, it does seem to play up when I've used it in the past - as it was installing I actually removed my phone (I hadn't meant to leave it in tether mode) so I'll pop that in tonight and let it fully install/update.
      My System SpecsSystem Spec

Intermittent BSOD's 'ntoskrnl.exe+5b1f85'
Related Threads
Hello I have recently 'refreshed' my laptop, and since then I have been getting intermittent BSOD. This seems to happen randomly, I havent been able to pin down a pattern of what I'm doing when it occurs. Recently I have installed a new Antivirus and Firewall, (Avast, Online Armor). I read...
Intermittent freezing, but NO BSOD or reboot in Performance & Maintenance
Hi It boots OK. Dell 755 dual core 1.8 3.5Gb ram, For some time now, the machine will suddenly freeze, after 10 sec or so back to working, using any program. When I open outlook I'm now getting a message saying outlook didn't close properly, or personal folder didn't close properly. I...
Intermittent BSOD's on new PC in BSOD Crashes and Debugging
Hi all, Brought a new computer from Pc world a month ago and my computer keeps restarting itself intermittently. I took it back to PC world who did a few diagnostic checks on it (no thorough ones though), factory reset it and then returned it back to me. After a week, so far so good, and now...
Intermittent BSOD error in Windoes 8 - 32 BIT in BSOD Crashes and Debugging
Hello All, I have a Windows 8 - 32 Bit OS installed on my system. off Late I am getting intermittent BSODs at regular intervals. I updated all the drivers, but it doesn't seem to resolve the problem. Attaching the diagnostic zip file, kindly check and let me know what could be the problem. ...
Hello, I've been having some problems with my self-built Windows 8 PC for some time now. I took advantage of the cheap Windows 8 upgrade pricing when I built a new PC and moved a copy of Win7 to this machine, then immediately upgraded. Basically, 50-75% of the time when it put the computer...
Intermittent BSOD in BSOD Crashes and Debugging
Hi, about a year ago I have put together this system and installed Windows 7 on it. Soon after that it started BSOD about once a week. Since I have a Vertex SSD in the system and have heard about it could possibly cause some BSOD once in a while, I didn't think too much of it. But it felt like the...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook