Windows 10: Running into BSOD, even after reset

Discus and support Running into BSOD, even after reset in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, I am running into BSOD even after windows reset, below are the details from the debugger. Microsoft R Windows Debugger Version 10.0.19041.1... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by JoelRajan, Aug 30, 2020.

  1. JOELRAJAN
    JoelRajan Win User

    Running into BSOD, even after reset


    Hi,


    I am running into BSOD even after windows reset, below are the details from the debugger.




    Microsoft R Windows Debugger Version 10.0.19041.1 X86

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\083020-11812-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available





    ************* Path validation summary **************

    Response Time ms Location

    Deferred SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 16 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff805`7b000000 PsLoadedModuleList = 0xfffff805`7bc2a2f0

    Debug session time: Sun Aug 30 20:37:43.491 2020 UTC + 5:30

    System Uptime: 1 days 23:54:56.136

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    .....................

    Loading User Symbols

    Loading unloaded module list

    ..................................................

    For analysis of this file, run !analyze -v

    12: kd>

    12: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    KERNEL_MODE_HEAP_CORRUPTION 13a

    The kernel mode heap manager has detected corruption in a heap.

    Arguments:

    Arg1: 0000000000000012, Type of corruption detected

    Arg2: ffff9c834be02100, Address of the heap that reported the corruption

    Arg3: ffff9c835574f000, Address at which the corruption was detected

    Arg4: 0000000000000000



    Debugging Details:

    ------------------



    *** WARNING: Unable to verify timestamp for win32k.sys



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 8



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on LAPTOP-PA3K0ACO



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 14



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 78



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: 13a



    BUGCHECK_P1: 12



    BUGCHECK_P2: ffff9c834be02100



    BUGCHECK_P3: ffff9c835574f000



    BUGCHECK_P4: 0



    CORRUPTING_POOL_ADDRESS: fffff8057bcfa390: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd

    fffff8057bc0f2f0: Unable to get Flags value from nt!KdVersionBlock

    fffff8057bc0f2f0: Unable to get Flags value from nt!KdVersionBlock

    unable to get nt!MmSpecialPagesInUse

    ffff9c835574f000



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: System



    STACK_TEXT:

    ffffd186`edfdf428 fffff805`7b59c2c8 : 00000000`0000013a 00000000`00000012 ffff9c83`4be02100 ffff9c83`5574f000 : nt!KeBugCheckEx

    ffffd186`edfdf430 fffff805`7b59c328 : 00000000`00000012 ffffd186`edfdf540 ffff9c83`4be02100 00000000`00000000 : nt!RtlpHeapHandleError+0x40

    ffffd186`edfdf470 fffff805`7b59bf55 : ffff9c83`5574f000 ffff9c83`4be02280 ffff9c83`4be02280 fffff805`7b23c6b7 : nt!RtlpHpHeapHandleError+0x58

    ffffd186`edfdf4a0 fffff805`7b41866c : ffff9c83`557f3710 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpLogHeapFailure+0x45

    ffffd186`edfdf4d0 fffff805`7b240c04 : ffff9093`00000000 ffff9c83`541e6770 00000000`00000004 00000000`00000000 : nt!RtlpHpVsContextFree+0x1d657c

    ffffd186`edfdf570 fffff805`7b9c2019 : 00000000`00006b40 00000000`00000000 00000000`00000000 01000000`00100000 : nt!ExFreeHeapPool+0x4d4

    ffffd186`edfdf650 fffff805`7f5b5676 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExFreePool+0x9

    ffffd186`edfdf680 fffff805`7f5b2a5b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxPoolFree+0x3e [minkernel\wdf\framework\shared\object\wdfpool.cpp @ 456]

    ffffd186`edfdf6c0 fffff805`7f5c66a8 : 00000000`00000000 ffff9c83`557f4558 ffffd186`edfdf7f8 fffff805`aff80500 : Wdf01000!FxObject::Release+0x11b [minkernel\wdf\framework\shared\inc\private\common\fxobject.hpp @ 881]

    ffffd186`edfdf710 fffff805`aff28312 : ffff9c83`557f4210 00000000`0000000f ffffd186`edfdf7b8 ffff9c83`557f4558 : Wdf01000!imp_WdfObjectDereferenceActual+0x48 [minkernel\wdf\framework\shared\object\fxobjectapi.cpp @ 118]

    ffffd186`edfdf750 fffff805`aff27f6b : 00000000`0000000f 00000000`00000000 00000000`0000001f fffff805`aff269c8 : USBXHCI!ESM_RunStateMachine+0x372

    ffffd186`edfdf7b0 fffff805`aff5592d : ffff9c83`541b73e0 00000000`00000000 ffff9c83`557cd830 00000000`00000004 : USBXHCI!ESM_AddEvent+0xfb

    ffffd186`edfdf7f0 fffff805`aff51c1c : ffff9c83`53f7bce0 00000000`00000000 00000000`00000000 fffff805`affc762f : USBXHCI!DeviceSlot_ControllerResetPreReset+0x61

    ffffd186`edfdf820 fffff805`aff537d8 : ffff9c83`53cf10d0 fffff805`aff72901 00000000`ebe40011 0000637c`ac30efd8 : USBXHCI!Controller_InternalReset+0x124

    ffffd186`edfdf880 fffff805`affdd5d1 : 00000000`00000000 00000000`00000000 00000000`00000050 00000000`000005fa : USBXHCI!Controller_UcxEvtReset+0x58

    ffffd186`edfdf8e0 fffff805`affc757a : 00000000`ebe40011 00000000`00000000 00000000`00000004 00000000`00000000 : ucx01000!ControllerResetStateEntryFunc_CallHCDToReset1+0x11

    ffffd186`edfdf910 fffff805`affdc777 : 00000000`00000002 fffff805`aff72998 fffff805`aff80460 ffff9c83`53ef6d60 : ucx01000!StateMachineEngine_EventAdd+0x26a

    ffffd186`edfdf970 fffff805`aff5190c : 00000000`00000002 fffff805`aff72998 fffff805`aff80460 00000000`00000000 : ucx01000!UcxControllerNeedsReset+0x37

    ffffd186`edfdf9a0 fffff805`aff52fa7 : ffff9c83`53ef6d60 ffffd186`edfdfa80 ffff9c83`53ef6d60 ffffd186`edfdfa80 : USBXHCI!Controller_InitiateRecovery+0x16c

    ffffd186`edfdfa40 fffff805`7f5bc6a7 : ffff9c83`53ef6c60 ffff9c83`00000006 00000000`00000006 00000000`00000000 : USBXHCI!Controller_TelemetryReportWorker+0x317

    ffffd186`edfdfac0 fffff805`7b2d9d75 : ffff9c83`53f91100 00000000`00000000 ffff9c83`5400d6d0 fffff805`7f5bc5c0 : Wdf01000!FxWorkItem::WorkItemThunk+0xe7 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 431]

    ffffd186`edfdfb00 fffff805`7b233f45 : ffff9c83`6f09e040 ffff9c83`6f09e040 fffff805`7b2d9c40 00000000`00000000 : nt!IopProcessWorkItem+0x135

    ffffd186`edfdfb70 fffff805`7b346745 : ffff9c83`6f09e040 00000000`00000080 ffff9c83`4c527100 00000000`00000001 : nt!ExpWorkerThread+0x105

    ffffd186`edfdfc10 fffff805`7b3e5598 : ffff8c01`14ce2180 ffff9c83`6f09e040 fffff805`7b3466f0 00000000`00000246 : nt!PspSystemThreadStartup+0x55

    ffffd186`edfdfc60 00000000`00000000 : ffffd186`edfe0000 ffffd186`edfda000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28





    SYMBOL_NAME: nt!ExFreePool+9



    IMAGE_NAME: Pool_Corruption



    IMAGE_VERSION: 10.0.19041.450



    MODULE_NAME: Pool_Corruption



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 9



    FAILURE_BUCKET_ID: 0x13a_12_nt!ExFreePool



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {0e8bc89c-9b1f-e697-ed6c-83210db041e2}



    Followup: Pool_corruption

    ---------



    12: kd>

    Implicit thread is now ffff9c83`6f09e040

    :)
     
    JoelRajan, Aug 30, 2020
    #1
  2. REGENERATION
    Regeneration Win User

    Getting BSOD 0x124 error

    Ignore what everone said here.

    0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

    If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

    If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

    Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.
     
    Regeneration, Aug 30, 2020
    #2
  3. TFWUL
    tfwul Win User
    OneDrive not running - reset won't work - how to get latest version?

    Thanks for the suggestion.
    The reason why I wanted to do a reset or re-install is to indeed get OneDrive in that list. Currently it isn't.
     
    tfwul, Aug 30, 2020
    #3
  4. CPLPRO
    cplpro Win User

    Running into BSOD, even after reset

    7 different BSoD

    Hey guys,

    I have a serious problem. I make it as short as possible:

    • system runs 100 % fine with the 10.12
    • updatet to Catalyst 11.1 -> BSoD
    • updatet to 11.1 Hotfix -> BSoD
    • rollback to 10.12 -> BSoD
    • removed ALL AMD files manually, installed 10.12 -> BSoD
    • Temps are fine
    • no sfc /scannow errors
    • no chkdsk errors
    • Prime, Furmark all fine
    • regardless what driver I install -> BSoD
    • I did no hw changes, no OC
    Here are my BSoDs I receive:
    • 0x0000010e
    • 0x1000007e
    • 0x0000007e
    • 0x0000004e
    • 0x0000003b
    • dxgmms1.sys
    • PFN_LIST_CORRUPT
    They all refer to the GPU of course ...

    From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
    Apparently the 11.1 damaged my system irreparable.

    Any advice or info would be very much appreciated *Smile Running into BSOD, even after reset :)
     
    cplpro, Aug 30, 2020
    #4
Thema:

Running into BSOD, even after reset

Loading...

  1. Running into BSOD, even after reset - Similar Threads - Running BSOD reset

  2. BSOD even after Resetting/System Restore.

    in Windows 10 Gaming
    BSOD even after Resetting/System Restore.: Hello!This started happening recently where my PC would seemingly randomly BSOD https://i.gyazo.com/ae293392fc770b1b9d8f162e5ce1131f.jpg image of it. . It happens out of nowhere. Initially I thought it was due to a specific app/game I was using since the first 3-4 times it...

  3. BSoD even after system reset

    in Windows 10 Gaming
    BSoD even after system reset: Hi,I've had my Lenovo Laptop with Windows 11 for a little of a year now. Recently it will crash periodically every couple hours with either "bad pool caller" and "kernel mode heap corruption. I though an entire system reboot would solve the problem but it did not. I have also...

  4. BSoD even after system reset

    in Windows 10 Software and Apps
    BSoD even after system reset: Hi,I've had my Lenovo Laptop with Windows 11 for a little of a year now. Recently it will crash periodically every couple hours with either "bad pool caller" and "kernel mode heap corruption. I though an entire system reboot would solve the problem but it did not. I have also...

  5. ntoskrnl.exe BSOD even after Windows reset

    in Windows 10 Gaming
    ntoskrnl.exe BSOD even after Windows reset: I have had 2 BSOD in the last 2 weeks, i reset my Windows some time ago and it stopped crashing, but it started again recently, i did a RAM test and it said everything was good, CrystalDiskInfo was all my drives are good. I always crashes when i'm away from my PC.I suspect it...

  6. Frequent BSODs even after Windows reset

    in Windows 10 BSOD Crashes and Debugging
    Frequent BSODs even after Windows reset: This has been an on and off issue for a while now, but the persistence of this problem has been bugging me quite a bit. A few months ago, my computer started experiencing frequent BSODs. And by frequent, I mean on one day I got four in the span of an hour. Now, a few days...

  7. BSODs Even after doing a system reset

    in Windows 10 BSOD Crashes and Debugging
    BSODs Even after doing a system reset: Hello, For maybe around a month now, I have been having constant BSODs and attempting to fix it myself hasn't been very productive. Note: These BSODs only occur whenever I play a game, mainly Monster Hunter: World. I've tried doing a windows restore using a flashdrive, and...

  8. Constant BSOD even after system reset

    in Windows 10 BSOD Crashes and Debugging
    Constant BSOD even after system reset: Hello. For months I have been suffering from constant BSODs, especially when playing games, but it can happen at random too. I recently made a system reset hoping it would fix the problem, but when I tried playing one of the games that used to cause me a great amount of...

  9. Recurring BSODs, even after reset.

    in Windows 10 BSOD Crashes and Debugging
    Recurring BSODs, even after reset.: I have been getting multiple BSODs on my computer, during normal use. The errors show mostly CRITICAL_PROCESS_DIED or UNEXPECTED_STORE_EXCEPTION. I then did tests on my RAM, HDD, ran SFC, DISM and reinstalled drivers. I still got them after that, so I got fed up and did a...

  10. BSOD even after full reset

    in Windows 10 BSOD Crashes and Debugging
    BSOD even after full reset: Yesterday I started getting BSOD errors randomly. Happened 3 times, was all very sudden. I ran Windows Memory Diagnostic a few times, all checked out. I formatted and reinstalled Windows, hoping to have everything fixed. After reinstalling some of my programs, another BSOD...