Windows 10: Multiple BSODS with different errors, caused by ntoskrnl.exe

Discus and support Multiple BSODS with different errors, caused by ntoskrnl.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; Latest dump shows a MEMORY_MANAGEMENT error, subtype 5100: 0x5100 - The allocation bitmap is corrupt. The memory manager is about to overwrite a... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by buncieboy, Feb 15, 2017.

  1. Ztruker Win User

    Multiple BSODS with different errors, caused by ntoskrnl.exe


    Latest dump shows a MEMORY_MANAGEMENT error, subtype 5100:
    0x5100 - The allocation bitmap is corrupt. The memory manager is about to overwrite a virtual address that was already in use.

    No additional info that helps id the problem. Nothing in eventlog.txt that helps either.

    Did you do the reinstall yet?
     
    Ztruker, Mar 2, 2017
    #46
  2. buncieboy Win User

    Nah not yet, I think Im going to have to as soon as I can *Sad
     
    buncieboy, Mar 2, 2017
    #47
  3. buncieboy Win User
    Will windows update install chipset drivers etc?
     
    buncieboy, Mar 2, 2017
    #48
  4. buncieboy Win User

    Multiple BSODS with different errors, caused by ntoskrnl.exe

    Keep or remove files on the install?
     
    buncieboy, Mar 2, 2017
    #49
  5. buncieboy Win User
    Have done a clean install, and will update you as it goes *Smile
     
    buncieboy, Mar 2, 2017
    #50
  6. buncieboy Win User
    Should I install any GPU driver updates, and any drivers from my mobo company, or just leave it if it doesn't cause any issues?
     
    buncieboy, Mar 2, 2017
    #51
  7. buncieboy Win User
    Well that lasted a whole hour, logs attached <3
     
    buncieboy, Mar 3, 2017
    #52
  8. Ztruker Win User

    Multiple BSODS with different errors, caused by ntoskrnl.exe

    Look at Device Manager. If no problems then just do Windows Updates and see how it goes.
     
    Ztruker, Mar 3, 2017
    #53
  9. buncieboy Win User
    That's what I did and I got that crash *Sad
     
    buncieboy, Mar 3, 2017
    #54
  10. buncieboy Win User
    I've uninstalled itunes, and am waiting for the next crash (hopefully there won't be one!). If it does crash Ill update / check GPU and chipset drivers, sound like a plan?
     
    buncieboy, Mar 3, 2017
    #55
  11. Ztruker Win User
    Yes, definite good plan.
     
    Ztruker, Mar 4, 2017
    #56
  12. buncieboy Win User
    Well it seems to be stable, I gave it a good clean out when I uninstalled itunes, so I'm going to wait until the end of the week and re install it, and then if its still stable everything's back to normal *Smile
     
    buncieboy, Apr 5, 2018
    #57
Thema:

Multiple BSODS with different errors, caused by ntoskrnl.exe

Loading...
  1. Multiple BSODS with different errors, caused by ntoskrnl.exe - Similar Threads - Multiple BSODS different

  2. Multiple BSOD errors, Different causes

    in Windows 10 Gaming
    Multiple BSOD errors, Different causes: Ive gotten multiple blue screens within the past month or so, 3 today alone. seems like its a 50/50 split between what causes it. It seems to be BEDaisy.sys and ntkrnlmp.exe. All drivers are up to date as well my windows version and havent downloaded and new programs or...
  3. Multiple BSOD errors, Different causes

    in Windows 10 Software and Apps
    Multiple BSOD errors, Different causes: Ive gotten multiple blue screens within the past month or so, 3 today alone. seems like its a 50/50 split between what causes it. It seems to be BEDaisy.sys and ntkrnlmp.exe. All drivers are up to date as well my windows version and havent downloaded and new programs or...
  4. Multiple BSOD caused by NTOSKRNL after KB5053602

    in Windows 10 Gaming
    Multiple BSOD caused by NTOSKRNL after KB5053602: Would someone be able to help me diagnose where it's coming from? I'm running Win11 23H2, I've run Memtest many times, stressed the CPU, etc. Nothing seems out of sorts, hardware-wise. This is a fresh install, too. If someone could help me read the minidump, I would be most...
  5. Multiple BSOD caused by NTOSKRNL after KB5053602

    in Windows 10 Software and Apps
    Multiple BSOD caused by NTOSKRNL after KB5053602: Would someone be able to help me diagnose where it's coming from? I'm running Win11 23H2, I've run Memtest many times, stressed the CPU, etc. Nothing seems out of sorts, hardware-wise. This is a fresh install, too. If someone could help me read the minidump, I would be most...
  6. BSOD caused by ntoskrnl

    in Windows 10 Gaming
    BSOD caused by ntoskrnl: Struggling with frequent BSODs on my PC lately. I've found the cause to be ntoskrnl.exe but couldn't figure out anything besides that. Appreciate any help on this.HERE's the link dump files here:...
  7. BSOD caused by ntoskrnl

    in Windows 10 Software and Apps
    BSOD caused by ntoskrnl: Struggling with frequent BSODs on my PC lately. I've found the cause to be ntoskrnl.exe but couldn't figure out anything besides that. Appreciate any help on this.HERE's the link dump files here:...
  8. BSOD multiple different times with different causes?

    in Windows 10 Software and Apps
    BSOD multiple different times with different causes?: Hello, I'm not great with any of the BSOD tech issues but I have been getting many blue screens and tried using WinDbg to figure out where the issue was with my dump files, but they each have different names so I'm confused on what I'm meant to do. These are some of the image...
  9. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  10. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
Tags: