Windows 10: Having random BSOD after a few hardware changes but could not be related

Discus and support Having random BSOD after a few hardware changes but could not be related in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello everyone. I want to go on to comment on my problem. I have a 2070 super and decided to buy a 3070. My system, in general, was extremely stable,... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by manubesada, Dec 28, 2020.

  1. Having random BSOD after a few hardware changes but could not be related


    Hello everyone. I want to go on to comment on my problem.

    I have a 2070 super and decided to buy a 3070. My system, in general, was extremely stable, without major problems.

    A couple of weeks ago, I updated windows to its latest version and together, I installed the new gpu. The crashes randomly started to appear mostly BSOD and idle reboot.

    This is what I did:

    -clean installation of windows and roll back to 2004.

    -change of thermal paste, reinstallation of rams and adjustment of psu cables.

    -reinstallation with ddu of video drivers.

    -change to stock of rams.

    This persisted with the problems and evidently did not solve anything.

    -memtest 4 passes 3 times; win on all records, prime 95, occt multiple passes; heaven benchmark and furmark, ALL WITHOUT PROBLEMS.

    -temperatures and voltages are within normal parameters.

    Although the problems persisted, since I rolled back to 2004, the system went almost 24 hours without crashes until... BSOD APC MISMATCH, like almost all the previous ones. I have a debug to paste here and everything points to the culprit being the EPIC laucnher but I'm not sure, that's why I ask you.

    This is my configuration: -3600xt stock -2x8 ram 3200xmp team group. -3070 zotac -psu seasonic m12II 750w bronze. -asrock b550 gaming velocita. -nvm drive 500gb wd blue. -id cooling 224.

    This is the debug:

    Bugcheck Analysis

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



    APC_INDEX_MISMATCH 1

    This is a kernel internal error. The most common reason to see this

    bugcheck is when a filesystem or a driver has a mismatched number of

    calls to disable and re-enable APCs. The key data item is the

    Thread->CombinedApcDisable field. This consists of two separate 16-bit

    fields, the SpecialApcDisable and the KernelApcDisable. A negative value

    of either indicates that a driver has disabled special or normal APCs

    respectively without re-enabling them; a positive value indicates that

    a driver has enabled special or normal APCs respectively too many times.

    Arguments:

    Arg1: 00007fff16acc034, Address of system call function or worker routine

    Arg2: 0000000000000000, Thread->ApcStateIndex

    Arg3: 000000000000ffff, Thread->SpecialApcDisable << 16 Thread->KernelApcDisable

    Arg4: ffff9003193f7b80, Call type 0 - system call, 1 - worker routine



    Debugging Details:

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





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 1



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-6FSP1S8



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 12



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 71



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: 1



    BUGCHECK_P1: 7fff16acc034



    BUGCHECK_P2: 0



    BUGCHECK_P3: ffff



    BUGCHECK_P4: ffff9003193f7b80



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    PROCESS_NAME: EpicGamesLauncher.exe



    STACK_TEXT:

    ffff9003`193f79b8 fffff807`75207769 : 00000000`00000001 00007fff`16acc034 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx

    ffff9003`193f79c0 fffff807`75207633 : 00000000`00000000 ffffe288`ff4d8360 ffff9003`193f7b18 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69

    ffff9003`193f7b00 00007fff`16acc034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe

    000000e8`7f10f948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`16acc034





    SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 1fe



    FAILURE_BUCKET_ID: 0x1_SysCallNum_4_nt!KiSystemServiceExitPico



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {52cd694c-15ec-48c3-924a-3539560711db}



    Followup: MachineOwner

    :)
     
    manubesada, Dec 28, 2020
    #1
  2. ARC
    Arc Win User

    Random BSOD while browsing internet


    BitDefender is nothing special. mwac.sys causes BSODs anywhere.
    A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
    In that very thread, the suggested action apparently worked.

    The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
    As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
    That is why I posted that my suggestion may work, or may not. Let us see where it goes.
     
  3. ARC
    Arc Win User
    Random BSODs "Bad_Pool_Caller"


    This BSOD happens anywhere, irrespective of BitDefender. It takes place even when the antivirus is MSE in case of Windows 7. The most common cause is an expired trial or a cracked installation. Some examples:

    We are on our way of troubleshooting. If the uninstallation and reinstallation does not work, we will take the next step.

    I, in general, know what I am doing and what I am suggesting. If I feel that I am unable to control the issue, I will definitely ask for help.
     
  4. Ztruker Win User

    Having random BSOD after a few hardware changes but could not be related

    Random BSOD while browsing internet


    Sorry, Bitdefender is a problem: BSOD BAD_POOL_HEADER - mwac.sys - Malwarebytes Anti-Malware Help - Malwarebytes Forums

     
    Ztruker, Dec 28, 2020
    #4
Thema:

Having random BSOD after a few hardware changes but could not be related

Loading...
  1. Having random BSOD after a few hardware changes but could not be related - Similar Threads - Having random BSOD

  2. Getting BSOD randomly after few days or hours.

    in Windows 10 Gaming
    Getting BSOD randomly after few days or hours.: I randomly get BSOD in few days and even few hours of keeping on my computer this issue has started most probably after a powercut but i installed new Windows just 2 days before because of the same problem it happens randomly and my system works fine for some hours like today...
  3. Random BSODs - memory related?

    in Windows 10 Ask Insider
    Random BSODs - memory related?: Hi guys, as of late i've experienced two random BSODS. The system is fairly new and a clean OS has been installed upon build. Looking at the dmp files it appears that it is related to BSOD 11/04/21 - REFERENCE_BY_POINTER, fltmgr.sys and ntoskrnl.exe appear to be the culprits...
  4. MEMORY_MANAGEMENT and other BSODs, hardware related

    in Windows 10 BSOD Crashes and Debugging
    MEMORY_MANAGEMENT and other BSODs, hardware related: Hey, about a week and a half ago I upgraded my system to a Ryzen 5 5600X with a B550 motherboard, and it seemed to be working fine. However, at some point, I started getting MEMORY_MANAGEMENT BSODs, and they became more frequent, to the point of me booting my computer and...
  5. Random BSoDs (BUGCODE_USB_DRIVE) Could it be a hardware problem?

    in Windows 10 Ask Insider
    Random BSoDs (BUGCODE_USB_DRIVE) Could it be a hardware problem?: Hey Everyone, I have been facing random BSoDs on a used laptop (Dell Latitude E5450) I purchased from a friend lately. I hope if you can diagnose the problem and mention if it could be a hardware related problem so I could return the laptop back if it is! Here is the Log...
  6. Lots of BSOD after hardware change

    in Windows 10 BSOD Crashes and Debugging
    Lots of BSOD after hardware change: Hello! I previously had the ASUS X570 Pro motherboard. I just changed to an Aorus X570 Elite WIFI. I was getting BSOD so I tried to troubleshoot them when it happened. Then I did clean installs of Windows 10 a few times and it hasn't help. It's at the point where I can't run...
  7. Random BSODs relating to ntsoskrnl.exe

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs relating to ntsoskrnl.exe: I've been getting random BSODs every once in a while since I built a new pc. I posted a question here about a month ago, and I was told to uninstall some program and turn off fast startup, which seemed to help. I stopped getting BSODs for about a month, and then recently...
  8. BSOD after hardware change

    in Windows 10 BSOD Crashes and Debugging
    BSOD after hardware change: Recently I installed a new GPU in my PC. After installing the Nvidia drivers I started to receive bsod stop errors. I removed to new card and drivers and installed the original GPU/drivers but im still geting bsod errors. I tried reinstalling windows 10 on the ssd but that...
  9. BSOD - Possibly hardware related?

    in Windows 10 BSOD Crashes and Debugging
    BSOD - Possibly hardware related?: Hi all, I have an MSi GT70 20C Laptop that I've had numerous problems with. When I first ordered this laptop it was dead on arrival, and had to be shipped back for fixing. Since i've gotten it back, I have had BSODs ranging from 0-2 times a week up to 6 times in a...
  10. Upgrade problems related to a hardware change

    in Windows 10 Support
    Upgrade problems related to a hardware change: I think I've figured out what my upgrade problem is caused by. I stopped get new Insider Builds and could not change some settings (grayed out). This started when I upgraded my Samsung SSD from 128GB to 256GB and then restored the Windows 10 to the 256. There seems to be...