Windows 10: BSOD issues cannot find a solution

Discus and support BSOD issues cannot find a solution in Windows 10 Drivers and Hardware to solve the problem; Hi there, Have been struggling with this problem for months now. At random intervals sometimes days, sometimes minutes I get a selection of BSoDs.... Discussion in 'Windows 10 Drivers and Hardware' started by jake2021, Jan 24, 2021.

  1. jake2021 Win User

    BSOD issues cannot find a solution


    Hi there,


    Have been struggling with this problem for months now. At random intervals sometimes days, sometimes minutes I get a selection of BSoDs. Uusally IRQL Not less or equal but there are a few it could be, not just a single error. Sometimes it's talking about trying to access memory that isn't available or something - sorry I don't have all of the codes listed..


    Minidumps here: https://1drv.ms/u/s!AvX_Q3emKjIwhEx13XaFrZvQbi_u?e=xPidEQ


    Interestingly the most recent BSoD doesn't seem to have created a minidump - not sure if that's important


    WhoCrashed tells me:


    On Sat 23/01/2021 15:01:30 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\012321-11031-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780
    Bugcheck code: 0xA 0x10, 0x2, 0x0, 0xFFFFF804160973E9
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 23/01/2021 15:01:30 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: ntkrnlmp.exe nt!setjmpex+0x8299
    Bugcheck code: 0xA 0x10, 0x2, 0x0, 0xFFFFF804160973E9
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 23/01/2021 14:49:53 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\012321-10734-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780
    Bugcheck code: 0x139 0x4, 0xFFFF9A001F3FE010, 0xFFFF9A001F3FDF68, 0x0
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The kernel has detected the corruption of a critical data structure.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 14/01/2021 19:36:19 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\011421-14296-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x3F3EA0
    Bugcheck code: 0x139 0x3, 0xFFFFF68E9B317380, 0xFFFFF68E9B3172D8, 0x0
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The kernel has detected the corruption of a critical data structure.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 09/11/2020 14:03:28 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\110920-14281-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x3F3EA0
    Bugcheck code: 0xA 0xFFFFC08000011958, 0x2, 0x1, 0xFFFFF8016C1EEBC3
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 09/11/2020 13:45:48 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\110920-10421-01.dmp
    This was probably caused by the following module: hardware.sys hardware
    Bugcheck code: 0x1000007E 0xFFFFFFFFC0000005, 0xFFFFF80049B244E4, 0xFFFFF201E4EBA748, 0xFFFFF201E4EB9F80
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
    Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    I have formatted and reinstalled numerous times. I have run memtest and the other recommended memory testing tools and not had any issues. I have tried 3 power supplies and currently running a fairly high quality Corsair PSU so I really do not believe it is PSU related. Potentially it could be related to my GPU but I did purchase a cheap alternative to test and if memory serves I still had issues otherwise I would have purchased a new card at the time.


    Would love to get some help on this as I've reached my limit of troubleshooting.


    Thanks a lot.

    :)
     
    jake2021, Jan 24, 2021
    #1
  2. Johan45 Win User

    AMD FX OC'ers Club

    That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

    At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.
     
    Johan45, Jan 24, 2021
    #2
  3. alexsubri Win User
    BSOD- atikmpag.sys

    This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:
    • Drivesweeper all drivers & in Safe Mode
    • Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
    • After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers
    BSOD issues cannot find a solution [​IMG]


    Once your done, restart the PC and then try installing the latest drivers.


    I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

    Best of luck! *Toast :toast:
     
    alexsubri, Jan 24, 2021
    #3
  4. Donna Men Win User

    BSOD issues cannot find a solution

    BSOD issue after fixing another BSOD error

    Hi Williams,

    There are several reasons why BSOD occur, which has different resolution. To check for any corruption or the integrity of your computer's Windows, we suggest that you perform a
    Check Disk by following these steps:

    • Type cmd in the search bar.
    • Right-click on the Command Prompt, then Run as administrator.
    • Type chkdsk x: /r, the /r command will fix errors found on the disk.

    Let us know if you need further assistance.
     
    Donna Men, Jan 24, 2021
    #4
Thema:

BSOD issues cannot find a solution

Loading...
  1. BSOD issues cannot find a solution - Similar Threads - BSOD issues cannot

  2. [Please Help] BSOD issues no solutions are working

    in Windows 10 Software and Apps
    [Please Help] BSOD issues no solutions are working: Hi, I would really appreciate assistance with this issue as the problem affects my only PC and I need this PC for important things. Windows 10 Pro. For around 2 years I have had BSOD problems, usually occuring soon after start up, however, if I restarted once or twice these...
  3. Cant find a solution for BAD_POOL_CALLER BSOD

    in Windows 10 Gaming
    Cant find a solution for BAD_POOL_CALLER BSOD: Hello, Since a while my PC gets a BSOD and crashes with a BAD_POOL_CALLER Error. Fight now my PC wont even Run for 5 min before crashing. Ive tried Most of the things the web told me-update Windows drivers-update device drivers-sfc Scan/repair which tells me it found some...
  4. Cant find a solution for BAD_POOL_CALLER BSOD

    in Windows 10 Software and Apps
    Cant find a solution for BAD_POOL_CALLER BSOD: Hello, Since a while my PC gets a BSOD and crashes with a BAD_POOL_CALLER Error. Fight now my PC wont even Run for 5 min before crashing. Ive tried Most of the things the web told me-update Windows drivers-update device drivers-sfc Scan/repair which tells me it found some...
  5. Persistent BSOD, cant find solution

    in Windows 10 BSOD Crashes and Debugging
    Persistent BSOD, cant find solution: bsod irql_not_less_or_equal. This bastard have been showing up for months now. I tried the checklists I found on google. I need your help, if you please. It seems to happen mostly when im using the chrome web-browser. But it could be coincidence. It happens most days! Very...
  6. Multiple BSOD, cannot find any solution

    in Windows 10 BSOD Crashes and Debugging
    Multiple BSOD, cannot find any solution: Hello, I recently have been getting a string of blue screens that I cannot troubleshoot. These bluescreens only occur whenever I am playing a game such as Monster Hunter World, DiRT Rally, and Escape from Tarkov. I have uploaded the dump files here:...
  7. (UPDATED) - Can't find a solution to "freezing without BSOD"

    in Windows 10 BSOD Crashes and Debugging
    (UPDATED) - Can't find a solution to "freezing without BSOD": I created a topic on September 3, 2019 titled "Can't find a solution to "freezing without BSOD". I did everything Independent Advisor said to me. Since that day I run my computer without any problem. But in last 48 hours I had two freezes without BSOD again. The first...
  8. Can't find a solution to "freezing without BSOD".

    in Windows 10 BSOD Crashes and Debugging
    Can't find a solution to "freezing without BSOD".: Since the day I got my own build PC, I experience lots of "freeze" without any blue screen. Early times, I was having "freeze" with glitching sound. But later on, glitching went into silence. Now I'm just having "freeze" without sound and blue screen. I thought, It might be...
  9. BSOD (GreenSOD?) - Unable to find a solution anywhere

    in Windows 10 BSOD Crashes and Debugging
    BSOD (GreenSOD?) - Unable to find a solution anywhere: The primary display goes solid green and the secondary screen goes black. The audio - if playing - repeats the last few milliseconds of whatever was playing just before the screen changed. I should mention that this doesn't happen very frequently. Usually once every few...
  10. Trying to find solution to ongoing network issues.

    in Windows 10 Network and Sharing
    Trying to find solution to ongoing network issues.: I know MS killed the support for the SMB 1 protocol. After trying all the so called trick to no avail and also uninstalled the SMB 1 protocol and just left the SMB installed and tried the MS trick to enable the network discovery as outlined in the article,...