Windows 10 BSOD, Bad_Pool_Caller, IRQL_Not_Less_Or_Equal, Help.

DarkChrono

Commendable
Mar 10, 2016
8
0
1,510
Windows 10 BSOD, Bad_Pool_Caller,
so I originally built this desktop with windows 7 pro, I upgraded to windows 8.1 and it constantly Bsod'd because of drivers presumably but I also think something during the install went wrong.
I tried many times to clean re-install windows 8.1 to no avail my system just wouldn't let me....

Let it sit a few months, using my laptop, and came back to it today, used the media creation tool installed windows 10 as far as I can tell it's fully up to date, my laptops hard drive seems to be failing, so I backed up my files to my external hard drive and was in the process of downloading to my desktop it's been running since 2:00 AM this morning (3/9/2016)
I left it on overnight reinstalling my games on steam, it was fine didn't crash, was certain the bsod errors were gone. within the last hour I was watching youtube while the external hard drive was downloading the files to my desktop.
It bsod'd with only about I think 60 gigabytes of content to transfer left, I'm not really sure how to access or read the DMP or if it's going to be a continued thing, but I uploaded it to mediafire if anyone here needs it to help me, I'm just coming here pre-preemptively because I know you're all very good with what you do.
So I figured some expert knowledge could only help, as stated the BSOD error is BAD_POOL_CALLER for some reason the mp file is over a gigabyte.

Thanks in advance any and all help will be appreciated!

Here's the .dmp

https://www.mediafire.com/?973a8v235t5c3b8

Thanks all!

Also I'm not sure if I posted this in the right forum, so sorry in advance it seemed like the correct one.

Edit:
I'm not sure if this will help but about 10 minutes after posting this, I started transferring the last little bit from my external to my desktop, and not even 3 minutes after I started the transfer again it BSOD'd again, it restarted to quick for me to memorize the error but it said something about kernel.
I truly hope you guys can help, and I wish I knew why the dmp's are so big.
So, the second dmp won't even upload at all, so I'm at a loss there, I wanted to point out that my antivirus is the most recent free avg and, that I use a program called Advanced systemcare by iobit, I've used it since their very first release, and I usually update my drivers via their driver booster program, so if that helps any insight is extremely helpful!

If it helps at all my Motherboard is a Asus M5A97 LE R2.0
I updated my BIOS to the most recent and I think that fixed the kernel error, I pulled a bad ram stick, that I located via memtest 86
and I just now completely uninstalled all my graphics card drivers and everything that comes with it, and restarted then reinstalled, same goes for audio, and lan drivers.
I can't even upload the dmp files now because they literally do nothing when trying to upload to my sites just sit in queue. I'll be following the responses as closely as possible, but I did all the stuff I saw around the web (in the time since my last post) with the drivers and everything, so here's hoping I already fixed it, but if you'd like to extend a helping hand, please do!
 

DarkChrono

Commendable
Mar 10, 2016
8
0
1,510


I suppose I understand but, can you rephrase, what exactly do you mean by trying different components, so far as far as I can tell, the only times it crashed, since I finished upgrading to windows 10 last night was these recent crashes while I was transferring my data from the external hard drive to my desktop, both crashes were from that.
 

DarkChrono

Commendable
Mar 10, 2016
8
0
1,510
So after running who crashed this is what it gave me.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 3/10/2016 5:32:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031016-15500-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFindPrefixHashEntry+0x1DF)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8011FBB54EF, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a kernel-mode program 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 3/10/2016 4:29:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030916-15703-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC2 (0x99, 0xFFFFC001DA79EBF0, 0x0, 0x0)
Error: BAD_POOL_CALLER
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 Thu 3/10/2016 4:29:36 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC2 (0x99, 0xFFFFC001DA79EBF0, 0x0, 0x0)
Error: BAD_POOL_CALLER
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 3/9/2016 6:37:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030816-13000-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF6DFFFFFFF80, 0x2, 0x0, 0xFFFFF803142B128F)
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 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.
 

Colif

Win 11 Master
Moderator
I won't guess what that all means, I can see that lots of people appear to be having issues with that file but I cannot locate a universal solution.

about your bios, here is what it says on the Asus web site: https://www.asus.com/support/FAQ/1008280/

 

DarkChrono

Commendable
Mar 10, 2016
8
0
1,510


Thanks, yeah just after I ran who crashed, I ended up reading how and updated to the most recent bios, so hopefully that will help, I'm hoping someone comes along that can tell me what they think/feel is wrong, and I'm also hoping that with the bios update and everything, hopefully everything will be fine, guess i'll find out later today when I try to finally finish my download from the external hard drive but I truly appreciate your help.
 

DarkChrono

Commendable
Mar 10, 2016
8
0
1,510
okay, so no errors until today, I just blue screened it was an IRQL_Not_Less_Or_Equal
I googled around quickly and decided to run msinfo32.exe,
I have a list of everything in the conflicts/sharing tab but really don't know what I'm looking at, or how to handle it? So I'm going to copy and paste and hopefully someone can help.

I/O Port 0x00000000-0x000003AF PCI Bus
I/O Port 0x00000000-0x000003AF Direct memory access controller
I/O Port 0x00000000-0x000003AF Motherboard resources

Memory Address 0xF0000000-0xF7FFFFFF NVIDIA GeForce GTX 650 Ti
Memory Address 0xF0000000-0xF7FFFFFF PCI-to-PCI Bridge

I/O Port 0x000003C0-0x000003DF NVIDIA GeForce GTX 650 Ti
I/O Port 0x000003C0-0x000003DF PCI-to-PCI Bridge

I/O Port 0x0000E000-0x0000E07F NVIDIA GeForce GTX 650 Ti
I/O Port 0x0000E000-0x0000E07F PCI-to-PCI Bridge

Memory Address 0xFE100000-0xFE1FFFFF PCI-to-PCI Bridge
Memory Address 0xFE100000-0xFE1FFFFF ASMedia USB 3.0 eXtensible Host Controller - 0.96 (Microsoft)

Memory Address 0xFD000000-0xFDFFFFFF NVIDIA GeForce GTX 650 Ti
Memory Address 0xFD000000-0xFDFFFFFF PCI-to-PCI Bridge

Memory Address 0xFA100000-0xFA103FFF Realtek PCIe GBE Family Controller
Memory Address 0xFA100000-0xFA103FFF PCI-to-PCI Bridge

Memory Address 0xFED00000-0xFED003FF High precision event timer
Memory Address 0xFED00000-0xFED003FF Motherboard resources

Memory Address 0xE0000000-0xEFFFFFFF System board
Memory Address 0xE0000000-0xEFFFFFFF PCI Bus

IRQ 18 Standard OpenHCD USB Host Controller
IRQ 18 Standard OpenHCD USB Host Controller

Memory Address 0xA0000-0xBFFFF NVIDIA GeForce GTX 650 Ti
Memory Address 0xA0000-0xBFFFF PCI Bus
Memory Address 0xA0000-0xBFFFF PCI-to-PCI Bridge

I/O Port 0x000003B0-0x000003BB NVIDIA GeForce GTX 650 Ti
I/O Port 0x000003B0-0x000003BB PCI Bus
I/O Port 0x000003B0-0x000003BB PCI-to-PCI Bridge

I/O Port 0x0000D000-0x0000D0FF Realtek PCIe GBE Family Controller
I/O Port 0x0000D000-0x0000D0FF PCI-to-PCI Bridge

I/O Port 0x00000062-0x00000062 Microsoft ACPI-Compliant Embedded Controller
I/O Port 0x00000062-0x00000062 Motherboard resources


I ran who crashed and the only 2 recent dmp's said this...

On Mon 3/14/2016 3:11:40 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF80365EBAEAF)
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 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 Sat 3/12/2016 4:01:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031116-17500-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A01F58C5F705F7, 0x0, 0xC1E7C1F6B47AF92C, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I also believe I already handled the critical structure corruption, I had a bad stick of ram, already handled I believe.

So, I crashed again, today, 3/14/2016 at 8:30 PM it was another critical structure corruption...
I ran who crashed, and it gave me
crash dump file: C:\Windows\Minidump\031416-16484-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A01F59F1C8D4F3, 0x0, 0x895739DD74B490E, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I honestly don't know what else to do, anymore...

Figured out a way to get the dumps working, here's the most recent 3, starting with today's first.

http://www.mediafire.com/download/iay82fsxi6aspl6/031416-16484-01.dmp Today

http://www.mediafire.com/download/yvt5ocxix48t120/031316-17781-01.dmp Yesterday

http://www.mediafire.com/download/3s4bct3l6g8odfi/031116-17500-01.dmp The 11th.