Windows 10: Getting a blue screen of death randomly

Discus and support Getting a blue screen of death randomly in Windows 10 BSOD Crashes and Debugging to solve the problem; description says it all. Ill come back to my computer and its frozen, or blue screened. I looked at the WinDBG and have the info but I am a little... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by CleanPinch123, Apr 11, 2021.

  1. Getting a blue screen of death randomly


    description says it all. Ill come back to my computer and its frozen, or blue screened. I looked at the WinDBG and have the info but I am a little confused on how to read it? Any help would be greatly appreicated. I am fearing it is something but I would rather have someone tell me why its doing it. I can post other minidumps if needed as well from previous days.


    [COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\041121-38343-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff802`6f200000 PsLoadedModuleList = 0xfffff802`6fe2a490Debug session time: Sun Apr 11 12:42:16.019 2021 UTC - 7:00System Uptime: 0 days 1:24:00.686Loading Kernel Symbols........................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.......For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff802`6f5f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8c0a`579c67e0=00000000000001392: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a critical data structure. The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments:Arg1: 0000000000000003, A LIST_ENTRY has been corrupted i.e. double remove.Arg2: ffff8c0a579c6b00, Address of the trap frame for the exception that caused the bugcheckArg3: ffff8c0a579c6a58, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, ReservedDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5343 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 31432 Key : Analysis.Init.CPU.mSec Value: 656 Key : Analysis.Init.Elapsed.mSec Value: 75534 Key : Analysis.Memory.CommitPeak.Mb Value: 85 Key : FailFast.Name Value: CORRUPT_LIST_ENTRY Key : FailFast.Type Value: 3 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1BUGCHECK_CODE: 139BUGCHECK_P1: 3BUGCHECK_P2: ffff8c0a579c6b00BUGCHECK_P3: ffff8c0a579c6a58BUGCHECK_P4: 0TRAP_FRAME: ffff8c0a579c6b00 -- [/COLOR][COLOR=rgba0, 0, 255, 1].trap 0xffff8c0a579c6b00[/COLOR][COLOR=rgba30, 30, 30, 1]NOTE: The trap frame does not contain all registers.[/COLOR][COLOR=rgba0, 0, 255, 1]Some register values may be zeroed or incorrect.[/COLOR][COLOR=rgba30, 30, 30, 1]rax=fffff8026b212d48 rbx=0000000000000000 rcx=0000000000000003rdx=ffffbf8c44b7ea30 rsi=0000000000000000 rdi=0000000000000000rip=fffff8026f6360fd rsp=ffff8c0a579c6c90 rbp=0000000000001280 r8=0000000000000001 r9=0000000000000084 r10=0000000000000000r11=fffff8026f200000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na po cynt!KiCancelTimer+0x1cf1ad:fffff802`6f6360fd cd29 int 29hResetting default scopeEXCEPTION_RECORD: ffff8c0a579c6a58 -- [/COLOR][COLOR=rgba0, 0, 255, 1].exr 0xffff8c0a579c6a58[/COLOR][COLOR=rgba30, 30, 30, 1]ExceptionAddress: fffff8026f6360fd nt!KiCancelTimer+0x00000000001cf1ad ExceptionCode: c0000409 Security check failure or stack buffer overrun ExceptionFlags: 00000001NumberParameters: 1 Parameter[0]: 0000000000000003Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY BLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemERROR_CODE: NTSTATUS 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.EXCEPTION_CODE_STR: c0000409EXCEPTION_PARAMETER1: 0000000000000003EXCEPTION_STR: 0xc0000409STACK_TEXT: ffff8c0a`579c67d8 fffff802`6f607b69 : 00000000`00000139 00000000`00000003 ffff8c0a`579c6b00 ffff8c0a`579c6a58 : nt!KeBugCheckExffff8c0a`579c67e0 fffff802`6f607f90 : 00000000`00000001 00000000`00000002 00000000`000367ac ffff8380`000081c0 : nt!KiBugCheckDispatch+0x69ffff8c0a`579c6920 fffff802`6f606323 : ffffbf8c`55a2e700 00000000`00000000 ffffbf8c`55a2e7c0 fffff802`6f40ecc6 : nt!KiFastFailDispatch+0xd0ffff8c0a`579c6b00 fffff802`6f6360fd : 00000000`00000000 00000000`00000000 ffffbf8c`44b30e28 fffff802`6f46b6e9 : nt!KiRaiseSecurityCheckFailure+0x323ffff8c0a`579c6c90 fffff802`6f43650b : ffffbf8c`44b30db0 ffffffff`ffffffff ffffe9de`31332a43 00000000`00000000 : nt!KiCancelTimer+0x1cf1adffff8c0a`579c6d40 fffff802`6f436aaf : ffffbf8c`44b7e8a0 ffffbf8c`44b7e801 ffffbf8c`44b7e801 00000000`00000002 : nt!KeCancelTimer+0x3bffff8c0a`579c6d70 fffff802`6f4376cc : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PopFxProcessWork+0x2b3ffff8c0a`579c6e20 fffff802`6f4375fc : 00000000`00000005 00000000`00000001 00000000`00000000 ffffbf8c`44930101 : nt!PopFxActivateComponentWorker+0x68ffff8c0a`579c6e70 fffff802`7282ae03 : ffffbf8c`449301a0 ffffbf8c`564d92d0 ffffbf8c`50d08248 00000000`00000000 : nt!PoFxActivateComponent+0x13cffff8c0a`579c6f00 fffff802`7282a4ec : 00000000`00000000 00000000`00000000 00000000`00000000 ffffbf8c`449251a0 : storport!RaidStartIoPacket+0x6d3ffff8c0a`579c7030 fffff802`7282a28a : 00000000`00000000 00000000`00000000 ffffbf8c`4492fe10 00000000`00000000 : storport!RaUnitScsiIrp+0x21cffff8c0a`579c70d0 fffff802`6f452f55 : ffffbf8c`50d08010 ffffbf8c`50d08010 ffffbf8c`4492fe10 00000000`00000000 : storport!RaDriverScsiIrp+0x5affff8c0a`579c7110 fffff802`7228b58d : ffffbf8c`4492fe10 ffffbf8c`50d08010 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55ffff8c0a`579c7150 fffff802`722810d6 : ffffbf8c`43efb410 00000000`00000007 ffffbf8c`50d08248 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0xadffff8c0a`579c7190 fffff802`6f452f55 : 00000000`00000007 ffffbf8c`50d08010 ffffbf8c`50d08010 ffffbf8c`4491b8b0 : ACPI!ACPIDispatchIrp+0xc6ffff8c0a`579c7210 fffff802`7228b58d : ffffbf8c`4491b8b0 ffffbf8c`50d08010 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55ffff8c0a`579c7250 fffff802`722810d6 : ffffbf8c`44841890 00000000`00000007 ffffbf8c`50d08248 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0xadffff8c0a`579c7290 fffff802`6f452f55 : 00000000`00000007 00000000`00000000 00000000`00001000 ffffbf8c`44b28a20 : ACPI!ACPIDispatchIrp+0xc6ffff8c0a`579c7310 fffff802`734d176f : 00000000`00000000 00000000`00001000 ffffbf8c`44b28a20 fffff802`6f44bc2f : nt!IofCallDriver+0x55ffff8c0a`579c7350 00000000`00000000 : 00000000`00001000 ffffbf8c`44b28a20 fffff802`6f44bc2f 00000000`00000020 : IaNVMeF+0x176fSYMBOL_NAME: nt!KiCancelTimer+1cf1adMODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]nt[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.870STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1cf1adFAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiCancelTimerOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {0a906956-eabe-15a9-fdee-848f8aa430ba}Followup: MachineOwner---------2: kd> .trap 0xffff8c0a579c6b00NOTE: The trap frame does not contain all registers.[/COLOR][COLOR=rgba0, 0, 255, 1]Some register values may be zeroed or incorrect.[/COLOR][COLOR=rgba30, 30, 30, 1]rax=fffff8026b212d48 rbx=0000000000000000 rcx=0000000000000003rdx=ffffbf8c44b7ea30 rsi=0000000000000000 rdi=0000000000000000rip=fffff8026f6360fd rsp=ffff8c0a579c6c90 rbp=0000000000001280 r8=0000000000000001 r9=0000000000000084 r10=0000000000000000r11=fffff8026f200000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na po cynt!KiCancelTimer+0x1cf1ad:fffff802`6f6360fd cd29 int 29h[/COLOR]

    :)
     
    CleanPinch123, Apr 11, 2021
    #1
  2. Ryan Pag Win User

    Blue screen of death issue

    Hi Malcolm,

    Blue screen of death error can be caused either by hardware failure or software compatibility. To help you resolve the blue screen of death issue, we would like to get more information:

    • Please provide the complete stop error message that you are getting.
    • Were there any changes made prior to the issue?

    We recommend following the troubleshooting steps in the article:
    Troubleshoot blue screen errors


    Should you need further help, you're always welcome to post back.
     
    Ryan Pag, Apr 11, 2021
    #2
  3. John Sarc Win User
    Blue Screen of Death

    We appreciate the information.

    To get better assistance in resolving Blue Screen of Death, we suggest that you get in touch with our
    Answer Desk as it has the experts and advanced troubleshooting steps regarding this issue.

    Regards.
     
    John Sarc, Apr 11, 2021
    #3
  4. Getting a blue screen of death randomly

    Blue Screen of Deaths on a Daily

    Hi,

    Blue screen errors can occur if a serious problem causes Windows to shut down or restart unexpectedly. This error can be caused by both hardware and software issues. To isolate your concern, we'd like to know if there were any changes made
    prior to the issue.

    In the meantime, we suggest that you follow the steps provided on this link for blue screen error basic
    troubleshooting. Once you're on the page, select the option on when do you get the error and proceed with the steps listed.

    Let us know how it goes after performing the suggested steps.
     
    Eileen Gal, Apr 11, 2021
    #4
Thema:

Getting a blue screen of death randomly

Loading...
  1. Getting a blue screen of death randomly - Similar Threads - Getting blue screen

  2. Getting a blue screen of death randomly

    in Windows 10 BSOD Crashes and Debugging
    Getting a blue screen of death randomly: The description says it all. Ill come back to my computer and its frozen, or blue screened. I looked at the WinDBG and have the info but I am a little confused on how to read it? Any help would be greatly appreicated. I am fearing it is something but I would rather have...
  3. Still getting blue screen of death?

    in Windows 10 Installation and Upgrade
    Still getting blue screen of death?: After Microsoft told me to update pc with sfc scannow ,but now it wont even repair, how can you tell everyone that it would be a safe bet to upgrade from windows 7 to 10,big disappointment Microsoft!....
  4. WHEA Blue Screen Of Death Random

    in Windows 10 Drivers and Hardware
    WHEA Blue Screen Of Death Random: This blue screen of death is randomly appearing, Usually in game. after that my windows boot drive not detected. i have remove it and reattach to fix that problem and after some time some times minutes sometimes days, it willl come back Here is the XML -<Event...
  5. Blue Screen Of Death happens randomly

    in Windows 10 BSOD Crashes and Debugging
    Blue Screen Of Death happens randomly: For the last few months I've been getting occasional blue screens. There are two types of errors that I get, the most common is MEMORY_MANAGEMENT BSOD and the next most common is SYSTEM_SERVICE_EXCEPTION what failed: luafv.sys. Here is a list of things I've tried to do...
  6. Keep getting Blue Screen of Death

    in Windows 10 BSOD Crashes and Debugging
    Keep getting Blue Screen of Death: Hello, I keep getting BSOD randomly on my computer. I have ran memtest, GPU tests, CPU test and Intel tests and Hard Drive test softwares and have not found any issues each time I run them. I have a few mini dumps from each one if anyone can help me out. Thanks in...
  7. Random Blue screen of death FAULTY_HARDWARE_CORRUPTED_PAGE

    in Windows 10 BSOD Crashes and Debugging
    Random Blue screen of death FAULTY_HARDWARE_CORRUPTED_PAGE: I recently experienced a lot of random BSOD crashes Error: FAULTY_HARDWARE_CORRUPTED_PAGE. It happened quite randomly even after Iupdated all drivers/firmware to the latest version. I tested the system with both Dell pre-boot diagnostic PSA/ePSA and MemTest86 v8.3 tools for...
  8. Random Blue Screens Of Death at startup

    in Windows 10 BSOD Crashes and Debugging
    Random Blue Screens Of Death at startup: I've been getting random BSODs with what I believe was 0xc000021a as the stop code. I thought I had fixed this by doing a repair reinstall of windows which worked fine for a week until now, same error of this BSOD again. Here is updated minidump:...
  9. Random blue screens of death of shutdown/restart

    in Windows 10 BSOD Crashes and Debugging
    Random blue screens of death of shutdown/restart: On the occasional shutdown or restart, I get treated to a blue screen crash. I have reset windows 10 so am assuming it's a hardware issue. Dump: Dump Msinfo: Msinfo Any help would be great....
  10. Random blue screen of deaths!!!

    in Windows 10 BSOD Crashes and Debugging
    Random blue screen of deaths!!!: I get blue screen of deaths usually when I'm watching YouTube videos or playing video games it also happens at random. Attachment 51018 Any help would be much appreciated 31892