System restart at unexpected times without BSOD.

Page 1 of 3 123 LastLast

  1. Posts : 25
    Windows 10 64-bit

    System restart at unexpected times without BSOD.


    I'm using this OptiPlex 5055 Ryzen CPU desktop and have uploaded this system's specifications under the "2nd PC Spec" section of my profile.

    This system often restarts itself at unexpected times, despite the fact that no resource intensive application is run on it (not even the Solitaire game in Windows 10!). Possibly the heaviest application that is run on this system is the Google Chrome Browser! Otherwise, its use is largely limited to the Microsoft Office suite.

    I've disabled "Automatically restart" option under Advanced System Settings as follows:
    System restart at unexpected times without BSOD.-image.png
    Despite this, I don't get the BSOD. The system simply restarts.

    So the only option I could think of at my disposal was memory dumps (which thankfully are being created every time the system witnesses such restart!).

    I used Nirsoft's BlueScreenView and got the following output:
    System restart at unexpected times without BSOD.-nirsoft.jpg
    As you can see, the culprit seems to be ntoskernel.exe.

    However, a little reading over the internet suggested related to ntoskernel crash suggested that this is likely to be a drivers issue. But to my disappointment, when I validated this PC's drivers' status with Dell Command Update application, the system already had all relevant drivers installed and updated to their latest versions by Dell's standards.
    System restart at unexpected times without BSOD.-untitled.jpg

    I also ran the Passmark's Memtest86 testing tool on this system and no problems were reported.

    I've run out of ideas at this point so I decided to create this thread.

    I ran the Beta Log collector tool and the zip file is attached for your reference (please see DESKTOP-2OOD0RP-(2019-04-16_19-01-26).zip).

    Kindly suggest possible issues/troubleshooting steps/solutions.

    P.S.: I might be incorrect in posting this thread under the BSOD Crashes and Debugging Forum since this system isn't giving me an actual BSOD. So please let me know in case I migrate this thread to another forum.
    Attached Thumbnails Attached Thumbnails System restart at unexpected times without BSOD.-image.png  
    System restart at unexpected times without BSOD. Attached Files
      My Computer

  2. Posts : 836
    Windows 8.1 Enterprise x64

    The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    1st parameter = 0x0 - A machine check exception occurred.
    Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [F:\041019-23312-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*
    Symbol search path is: SRV*
    Executable search path is: 
    Windows 10 Kernel Version 14393 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 14393.0.amd64fre.rs1_release.160715-1616
    Machine Name:
    Kernel base = 0xfffff801`9461e000 PsLoadedModuleList = 0xfffff801`94923060
    Debug session time: Wed Apr 10 06:19:01.900 2019 (UTC + 2:00)
    System Uptime: 0 days 0:00:07.581
    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, ffff8083d94418f8, 0, 0}
    Probably caused by : AuthenticAMD
    Followup:     MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffff8083d94418f8, 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:
    BUILD_VERSION_STRING:  14393.0.amd64fre.rs1_release.160715-1616
    DUMP_TYPE:  2
    BUGCHECK_P1: 0
    BUGCHECK_P2: ffff8083d94418f8
    BUGCHECK_P3: 0
    BUGCHECK_P4: 0
    BUGCHECK_STR:  0x124_AuthenticAMD
    CPU_COUNT: 8
    CPU_MHZ: da5
    CPU_VENDOR:  AuthenticAMD
    CPU_FAMILY: 17
    CPU_MODEL: 1
    PROCESS_NAME:  System
    ANALYSIS_SESSION_TIME:  04-16-2019 16:08:00.0225
    ANALYSIS_VERSION: 10.0.17763.132 amd64fre
    ffffc880`4130c5b0 fffff801`949fab21 : 00000000`00000000 ffff8083`d94418d0 fffff801`94916ae0 fffff801`949db280 : nt!WheapCreateLiveTriageDump+0x7b
    ffffc880`4130cae0 fffff801`94848848 : ffff8083`d94418d0 00000000`00000001 fffff801`9490f0f0 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
    ffffc880`4130cb10 fffff801`94849259 : fffff801`94916a80 fffff801`94916a80 fffff801`94916ae0 fffff801`94b77424 : nt!WheapProcessWorkQueueItem+0x48
    ffffc880`4130cb50 fffff801`94675d79 : fffff801`949db100 ffff8083`d9429040 ffff8083`00000000 fffff801`949db280 : nt!WheapWorkQueueWorkerRoutine+0x25
    ffffc880`4130cb80 fffff801`946ba4bd : ffffc880`40a79180 00000000`00000080 ffff8083`d708f3c0 ffff8083`d9429040 : nt!ExpWorkerThread+0xe9
    ffffc880`4130cc10 fffff801`9476d456 : ffffc880`40a79180 ffff8083`d9429040 fffff801`946ba47c 60c18348`60488b48 : nt!PspSystemThreadStartup+0x41
    ffffc880`4130cc60 00000000`00000000 : ffffc880`4130d000 ffffc880`41307000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    THREAD_SHA1_HASH_MOD_FUNC:  26acd050bd9f055d0a04825d57b9e0e6be9c1a07
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  132c000eaf3a0e557381dc4eba728b3e391a8d4b
    THREAD_SHA1_HASH_MOD:  30a3e915496deaace47137d5b90c3ecc03746bf6
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME:  AuthenticAMD
    STACK_COMMAND:  .thread ; .cxr ; kb
    TARGET_TIME:  2019-04-10T04:19:01.000Z
    OSBUILD:  14393
    SUITE_MASK:  272
    OSNAME:  Windows 10
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    USER_LCID:  0
    OSBUILD_TIMESTAMP:  2016-07-16 04:16:17
    BUILDDATESTAMP_STR:  160715-1616
    BUILDLAB_STR:  rs1_release
    BUILDOSVER_STR:  10.0.14393.0.amd64fre.rs1_release.160715-1616
    FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_cache_prv
    FAILURE_ID_HASH:  {cedb04af-9437-ee8e-2e67-54d858b5dbbc}
    Followup:     MachineOwner
    0: kd> !errrec ffff8083d94418f8
    Common Platform Error Record @ ffff8083d94418f8
    Record Id     : 01d4ef548287a2d7
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 4/10/2019 4:19:01 (UTC)
    Flags         : 0x00000002 PreviousError
    Section 0     : Processor Generic
    Descriptor    @ ffff8083d9441978
    Section       @ ffff8083d9441a50
    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   : 0x0000000000800f11
    Processor ID  : 0x0000000000000003
    Section 1     : x86/x64 Processor Specific
    Descriptor    @ ffff8083d94419c0
    Section       @ ffff8083d9441b10
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    Local APIC Id : 0x0000000000000003
    CPU Id        : 11 0f 80 00 00 08 08 03 - 0b 32 d8 7e 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  @ ffff8083d9441b10
    Section 2     : x86/x64 MCA
    Descriptor    @ ffff8083d9441a08
    Section       @ ffff8083d9441b90
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    Error         : GCACHEL0_ERR_ERR (Proc 3 Bank 5)
      Status      : 0xbea0000000000108
      Address     : 0x0101f800a7687253
      Misc.       : 0xd00a0fff01000000
    Do you have a latest BIOS version?
      My Computer

  3. Posts : 25
    Windows 10 64-bit
    Thread Starter

    I did run the Dell Command Update application and it didn't report any BIOS update being available.
    But at Dell's driver page for this system, I get this BIOS version 1.1.17 released on 13th Feb 2019 while the one installed in this system is 1.1.15 dated 22-06-2018. Let me try updating to 1.1.17 driver.

    - - - Updated - - -

    So I've updated to the 1.1.17 version of BIOS now. Let's see how it goes.
      My Computer

  4. Posts : 6
    Windows 10 1803

    HI @Ten64BitUser

    It's a bit of a relief to see your post as I've been fighting the same issue for a while....

    I have 45 of these machines at my office that I've been fighting with for months, most exhibiting similar issues to what you're having. I'm currently working with Dell Pro Support to try to resolve it.

    Timeline of problems:
    My issues started with the PC's randomly going blank/not responding. The fan would pulse, the power light was on, but that was it... BIOS 1.1.15 partially resolved this... We have a few machines this still occurs.

    Once we did some more testing and determined the PC's to be stable enough for use, we started pushing these to our development staff, that's when things went haywire. Constant blue screens and reboots. I've sent 10-20 minidumps to Dell already from various systems.

    The reboot/BSOD is entirely random as well. It can happen while in Notepad, IE/Chrome/FireFox, Windows Explorer, clicking start menu, or just simply letting the machine sit for a few minutes... Sometimes they reboot within minutes, sometimes it takes up to 3-4 days... And not always with a dump file no matter what options are enabled.

    While working with Dell Pro Support, I sent them one of our most problematic systems, which they have yet to be able to make crash in their test lab... Meanwhile we have multiple systems that still crash pretty frequently, and are in the process of being replaced with a different model (OptiPlex 5060 Intel) ASAP because my staff cannot continue to lose time/work. By the context of recent emails, it seems that Dell wants to blame an issue with our network/environment.

    Except.... We've had the issue while machines were both on and off domain...

    Some troubleshooting steps we did:
    We've upgraded bios to 1.1.17 on all machines, did advanced driver restore from Command|Update, as well as installing newer/refreshed drivers from the web and using Command|Update. Used Dell OEM Windows 10, used our own Windows 10 image, used Dell drivers, used microsoft default drivers, and even put one specific user on 3 different machines, and they each crashed... We have a new employee who isn't even finished with training, so she isn't doing anything even remotely heavy-hitting yet, that had her machine BSOD multiple times...

    To potentially help each other out... If I may ask a few questions about your systems:
    A. Are you using your own System Image or are you using the pre-installed Windows?
    B. What is your exact build out of these systems (HDD Size/Type, Ram Size, Exact Processor Used) **edit: I looked on your profile for 2nd PC spec and don't see anything**
    C. Are you noticing any network errors on these PC's after the reboot occurs?
    D. Would you be willing to DM me one of your service tags so I can look it up on and compare it to our builds?

    Also, feel free to ask me anything about what we've done, and what we're still experiencing with these machines. Example: If there's a specific quirk you're having that you're wondering if anyone else is having.

    Thanks in advance for your info!

    Our Machines:
    Optiplex Ryzen 5055 Small Form XCTO
    Win 10 Pro
    No CD/DVD
    M.2 256GB NVMe Class 40
    AMD R7 450 Graphics Card
    2x8GB DDR4 2400MHZ Memory (16gb)
    Ryzen 7 Pro 1700
    No SD Reader

    - - - Updated - - -

    I found your service tag from one of your screen shots.

    Info I needed from your build:
    Ram: 1x8GB DDR4 2400
    CPU: Ryzen Pro 1500
    HDD: 1TB 7200RPM SATA
    Video: Radeon R5 4302gb

    The only similarity would then be the MB/Case/Power Supply... Which points me to the MB as being the culprit overall.
    Last edited by iambucket; 17 Apr 2019 at 09:20. Reason: added information
      My Computer

  5. Posts : 32,454
    windows 10 professional version 1607 build 14393.969 64 bit


    To get help with the BSOD please open a new thread:

    BSOD - Posting Instructions - Windows 10 Forums

    Update the specs in the "My Computer" section:

    System Specs - Fill in at Ten Forums | Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)
      My Computer

  6. Posts : 6
    Windows 10 1803

    zbook said:

    To get help with the BSOD please open a new thread:

    BSOD - Posting Instructions - Windows 10 Forums
    That's just silly... We have the same system... With the same issues... I wanted a comparison. I don't need a new thread for that. I'm not trying to resolve my issues via the forum. I'm simply data gathering :)
      My Computer

  7. Posts : 32,454
    windows 10 professional version 1607 build 14393.969 64 bit

    Matching systems may have some differences with software and firmware.
      My Computer

  8. Posts : 25
    Windows 10 64-bit
    Thread Starter

    Even after updating to BIOS version 1.1.17, the system restarted on its own (again, without any BSOD). WhoCrashed lists the following details:

    On Thu 18-04-2019 14:47:05 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\041819-22578-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB43B)
    Bugcheck code: 0x124 (0x0, 0xFFFFA481386AC038, 0x0, 0x0)
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Any other ideas?
      My Computer

  9. Posts : 836
    Windows 8.1 Enterprise x64

    Insert new dumps (minidumps and full memory dump)
      My Computer

  10. Posts : 25
    Windows 10 64-bit
    Thread Starter


    I'm assuming that by minidumps, you're referring to the dumps in "C:\Windows\MiniDump" and by full memory dump, you're referring to "%SystemRoot%\MEMORY.DMP"?

    I've uploaded the former as For the latter, please see (Tenforums didn't allow me an upload this huge so I am sharing this from my Ondrive)

    Additionally, I've also uploaded the logs created by the Beta Log collector as DESKTOP-2OOD0RP-(2019-04-18_21-00-56).zip.

    Additionally, I had a few queries:
    1. I am not sure whether Google Drive sharing is allowed on this forum. Kindly let me know an alternative so that I may follow the protocol and change the sharing of the full memory dump file.
    2. I'm getting this message in my account seeking my ATTENTION and asking me to read the BSOD posting rules:
      Please let me know which wrong I committed and what amends are necessary in actions.
    Attached Thumbnails Attached Thumbnails System restart at unexpected times without BSOD.-image.png  
    System restart at unexpected times without BSOD. Attached Files
    Last edited by Ten64BitUser; 22 Apr 2019 at 00:09.
      My Computer


Related Threads
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 13:37.
Find Us

Windows 10 Forums