Windows 10: BSOD, cannot identify cause(s)

Discus and support BSOD, cannot identify cause(s) in Windows 10 BSOD Crashes and Debugging to solve the problem; I’ve been struggling with multiple BSOD crashes with my HP laptop, but I cannot identify the cause. I do not know how to decipher the stop code because... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Fantasma, Jun 4, 2019.

  1. Fantasma Win User

    BSOD, cannot identify cause(s)


    I’ve been struggling with multiple BSOD crashes with my HP laptop, but I cannot identify the cause. I do not know how to decipher the stop code because it looks like an actual barcode. Pls assistance would be much appreciated

    :)
     
    Fantasma, Jun 4, 2019
    #1
  2. Msap14 Win User

    BSOD Hardware Caused???

    they do weird things like that, which all seem like something else is failing.
    One of the worst things to diagnose, they seem to only quit when they want to.

    Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

    the follow was taken from some website:

    It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

    1. System fails to boot
    2. System re-boots intermittently
    3. General Protection Fault
    4. Illegal Operation
    5. Stop Error, or BSoD (Blue Screen OfDeath)

    Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

    Before suspecting the CPU, rule out all the possibilities listed below.

    1. The Operating System
    2. A peripheral port device
    3. A bad memory module
    4. The hard disk drive
    5. The power supply
    6. The motherboard

    If you have ruled out out all the other possibilities, investigate the items listed below.

    1. Overheating
    2. A short circuit
    3. ESD
     
    Msap14, Jun 4, 2019
    #2
  3. 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.
     
  4. zbook Win User

    BSOD, cannot identify cause(s)

    BSOD when updating W10 Insider Preview (installation)


    The BSOD minidump did not display a definitive misbehaving driver.
    All of the BSOD have been C2 Bad pool caller.
    The suggested steps for finding cause and effect are RAM testing with Memtest86+ version 5.01 and Windows driver verifier.
    If the Memtest86+ version 5.01 displays malfunctioning RAM / DIMM /MB then the troubleshooting will be completed once the hardware component is identified. If the Memtest86+ version 5.01 is negative then the next step would be windows driver verifier.
    If you prefer a clean install that is another option if hardware is ruled out.

    The memory dump will take a while to download. So it will be troubleshooted later today.
     
    zbook, Jun 4, 2019
    #4
Thema:

BSOD, cannot identify cause(s)

Loading...
  1. BSOD, cannot identify cause(s) - Similar Threads - BSOD cannot identify

  2. Need help identifying cause of BSOD. Information available.

    in Windows 10 BSOD Crashes and Debugging
    Need help identifying cause of BSOD. Information available.: Hello there, I've encountered a BSOD DPC_WATCHDOG_VIOLATION and would like to know the cause of it. I have the the dump information available to share if anyone could spare some time to have a look please? Kind Regards,...
  3. Experiencing reboot loop, BSOD, cannot identify the cause.

    in Windows 10 Drivers and Hardware
    Experiencing reboot loop, BSOD, cannot identify the cause.: Hello, i am having an issue with my PC and after doing many google searches my self I am at a loss, i cannot figure out the issue. I have several problems, they are: - When i boot the PC, it appears windows boots twice before going to the login screen - Once i am logged...
  4. Frequent Crashes/BSODs With No Identifiable Pattern or Cause

    in Windows 10 BSOD Crashes and Debugging
    Frequent Crashes/BSODs With No Identifiable Pattern or Cause: The computer I'm using now is the first one I ever built - I completed it about two years ago. For many months now I've had frequent crashes with no identifiable cause. There doesn't seem to be a correlation between RAM-intensive activities and crashes. Sometimes I'll only...
  5. Identifying root cause of BYOD

    in Windows 10 BSOD Crashes and Debugging
    Identifying root cause of BYOD: Hi, I've got a computer with a BYOD about every half an hour or less. So far I have: Looked up BYOD codes and tried the following: 1. Rolled back drivers for ones updated before the BYOD started occuring 2. Applied outstanding Windows Updates 3. Checked for any BIOS...
  6. Help with identifying cause of BSODs - dumps included

    in Windows 10 BSOD Crashes and Debugging
    Help with identifying cause of BSODs - dumps included: These are my memory dumps just from yesterday. Can you please help me identify the cause of these? https://drive.google.com/open?id=1MURuPWp8c4ZT9Na6THI4Rccn-E7UV0hg https://drive.google.com/open?id=1PeLvOhfQh_OLTHr2DeLfloPDhNaioOi5...
  7. Identifying driver causing BSOD

    in Windows 10 BSOD Crashes and Debugging
    Identifying driver causing BSOD: My laptop suddenly went into BSOD with the error IRQL_NOTLESS_OR_EQUAL. I tried using a bsod viewer to identify the driver but it just states ntoskrnl.exe. I have the dump files available, will it be helpful in identifying the driver that is causing this issue?...
  8. Help identifying BSOD?

    in Windows 10 BSOD Crashes and Debugging
    Help identifying BSOD?: I'm running Windows 10 and my 2 month old computer crashed a couple of times over the last few weeks while playing a video game (PUBG to be specific, and both crashes occurred on menu screen). I'd like to figure out the cause if at all possible. The dump file can be found...
  9. USB cannot be identified.

    in Windows 10 Drivers and Hardware
    USB cannot be identified.: I shut off windows insider preview, try to use USB to install Windows 10 version 1809 on my computer as dual system . When the windows installer runs, it says that the USB device cannot be indentified and windows installation cannot continue. This problem has happened in...
  10. Hangup cause identified but not fixed

    in Windows 10 Support
    Hangup cause identified but not fixed: I've several times reported an intermittent hangup where I cannot start programs for up to 10 minutes, but already running programs continue running. (The 10 minutes is a sort of a guess. I usually power down and restart rather than wait.) I've confirmed at least one cause -...