[SOLVED] Frequent blue screen crash

[maltebogner]

Hey,

my windows 10 crashes with a blue screen frequently. I thought it might be connected with an audio driver, since it happened a few times while using audioproductionsoftware. Anyhow, it happened aswell during the startup. I used "Whocrashed" for an analysis. Here's it. I would be happy if someone could help me with that!

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Thu 23.04.2020 08:25:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042320-9421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x135345)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8027C7DF345, 0xFFFF960572CDF6E8, 0xFFFF960572CDEF30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
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 23.04.2020 08:25:44 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!memset+0x5384)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8027C7DF345, 0xFFFF960572CDF6E8, 0xFFFF960572CDEF30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 22.04.2020 08:19:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042220-5484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B7AB0)
Bugcheck code: 0xC2 (0xD, 0xFFFFDB8D81380840, 0xFFFFF800, 0x774E63678500CA42)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 22.04.2020 07:21:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042220-5968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0xC2 (0xD, 0xFFFF8F82DBFDDD50, 0xFFFFF802, 0x660285F48A544F0F)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 22.04.2020 07:14:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042220-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0xC2 (0xD, 0xFFFFDD883F502720, 0x61253C6, 0x4101C38227769C31)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Bassplate]

Hey,

my windows 10 crashes with a blue screen frequently. I thought it might be connected with an audio driver, since it happened a few times while using audioproductionsoftware. Anyhow, it happened aswell during the startup. I used "Whocrashed" for an analysis. Here's it. I would be happy if someone could help me with that!

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Thu 23.04.2020 08:25:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042320-9421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x135345)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8027C7DF345, 0xFFFF960572CDF6E8, 0xFFFF960572CDEF30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
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 23.04.2020 08:25:44 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!memset+0x5384)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8027C7DF345, 0xFFFF960572CDF6E8, 0xFFFF960572CDEF30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 22.04.2020 08:19:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042220-5484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B7AB0)
Bugcheck code: 0xC2 (0xD, 0xFFFFDB8D81380840, 0xFFFFF800, 0x774E63678500CA42)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 22.04.2020 07:21:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042220-5968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0xC2 (0xD, 0xFFFF8F82DBFDDD50, 0xFFFFF802, 0x660285F48A544F0F)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 22.04.2020 07:14:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042220-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0xC2 (0xD, 0xFFFFDD883F502720, 0x61253C6, 0x4101C38227769C31)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Sounds more like an corrupt windows DLC or something with windows functioning....It may be an Hardrive error as well...
How many drives do you have connected?Whats your system specs?
Try resetting your Windows(That helps for many crashes and situations according this crash dumps!)
Back up files and begin a fresh start of windows or reset windows and keep files